#474: LFRic-Nudging: Part-A: Introduce ability to read nudging datafiles by mcdalvi · Pull Request #474 · MetOffice/lfric_apps

Mohit Dalvi (mcdalvi) · 2026-04-30T16:20:18Z

PR Summary

Sci/Tech Reviewer: Thomas Bendall (@tommbendall)
Code Reviewer: Matthew Hambley (@MatthewHambley)

This PR introduces the ability to read in datafiles that will be used for Nudging the Momentum models (Ref: Nudging NWP to AI/ML models - possibly targeting PS49).
The handling of Nudging data is modelled on existing lateral boundary condition handling in LFRic since they are both required to be interpolated from high time resolution file data on every model timestep.
Nudging changes summary:

Ability to read in nudging data for temperature, U-wind, V-wind and Log surface pressure (required for vertical remapping to model levels).
New [namelist:nudging], which will be active when theta or wind are 'forced by nudging' (in namelist:external_forcing). A corresponding upgrade_macro to add the namelist and I/O related items.
Introduce routine create_nudging_fields to create the nudging input fields as '2-D with user-specified (nudge_data) levels'. Corresponding grid_def_nudging.xml and grid_def_nudging_coarse.xml added to lfric_atm/metadata/.
Introduce ability to read in nudging data on native ('dynamics') or a coarser grid, with rationalising of routines that create the model fields ('make_spec', 'create_model_data') to accept both aerosol and nudging coarse mesh definitions.
Note that the above requires a LFRIC_CORE change to allow defining 3-D coarse grid fields as ''multigrid_ll'' x ndata.
Define a nudging_time_axis which will be populated based on the actual number of time records in the specified nudging file.
Introduce two new rose-stem tests lfric_atm_nwp_gal9_nudging-C48 that reads nudging files on the model grid and lfric_atm_nwp_gal9_nudging_coarse-C48 that reads in data at a lower resolution (C12) grid. This currently uses nudging data created from ERA5 source, but aim is to expand this to AIFS and other models.
At this stage the reference fields are only made available to LFRic and do not modify temperature/ winds.
linked #369: Allow coarse-grid fields with ndata levels: vn3.1 read coarse 2d lfric_core#369

Code Quality Checklist

I have performed a self-review of my own code
My code follows the project's style guidelines
Comments have been included that aid understanding and enhance the readability of the code
My changes generate no new warnings
All automated checks in the CI pipeline have completed successfully

Testing

I have tested this change locally, using the LFRic Apps rose-stem suite
If any tests fail (rose-stem or CI) the reason is understood and acceptable (e.g. kgo changes)
I have added tests to cover new functionality as appropriate (e.g. system tests, unit tests, etc.)
Any new tests have been assigned an appropriate amount of compute resource and have been allocated to an appropriate testing group (i.e. the developer tests are for jobs which use a small amount of compute resource and complete in a matter of minutes)

Test Branch: test2_vn31_nudging_data

trac.log

Test Suite Results - lfric_apps - test2_vn31_nudging_data/run4

Suite Information

Item	Value
Suite Name	test2_vn31_nudging_data/run4
Suite User	mohit.dalvi
Workflow Start	2026-05-29T17:58:29
Groups Run	developer', 'lfric_atm_azspice_extra

Dependency	Reference	Main Like
casim	MetOffice/casim@2026.03.2	True
jules	MetOffice/jules@2026.03.2	True
lfric_apps	mcdalvi/lfric_apps@test2_vn31_nudging_data	False
lfric_core	mcdalvi/lfric_core@vn3.1_read_coarse_2d	True
moci	MetOffice/moci@2026.03.2	True
SimSys_Scripts	MetOffice/SimSys_Scripts@cab3315	True
socrates	MetOffice/socrates@2026.03.2	True
socrates-spectral	MetOffice/socrates-spectral@2026.03.2	True
ukca	MetOffice/ukca@1cdb9c2	True

Task Information

✅ succeeded tasks - 1259

Security Considerations

I have reviewed my changes for potential security issues
Sensitive data is properly handled (if applicable)
Authentication and authorisation are properly implemented (if applicable)

Performance Impact

Performance of the code has been considered and, if applicable, suitable performance measurements have been conducted

AI Assistance and Attribution

Some of the content of this change has been produced with the assistance of Generative AI tool name (e.g., Met Office Github Copilot Enterprise, Github Copilot Personal, ChatGPT GPT-4, etc) and I have followed the Simulation Systems AI policy (including attribution labels)

VsCode - code completion/ snippets.

Documentation

Where appropriate I have updated documentation related to this change and confirmed that it builds correctly

PSyclone Approval

If you have edited any PSyclone-related code (e.g. PSyKAl-lite, Kernel interface, optimisation scripts, LFRic data structure code) then please contact the TCD Team

Sci/Tech Review

I understand this area of code and the changes being added
The proposed changes correspond to the pull request description
Documentation is sufficient (do documentation papers need updating)
Sufficient testing has been completed

(Please alert the code reviewer via a tag when you have approved the SR)

Code Review

All dependencies have been resolved
Related Issues have been properly linked and addressed
CLA compliance has been confirmed
Code quality standards have been met
Tests are adequate and have passed
Documentation is complete and accurate
Security considerations have been addressed
Performance impact is acceptable

…se-stem changes.

… time-axis definitions

…r the new arguments

DanStoneMO · 2026-05-01T09:30:12Z

Is there any chance main could be merged into this branch? I'm currently unable to test the changes with JEDI due to the conflicts

Mohit Dalvi (mcdalvi) · 2026-05-01T09:46:55Z

Apologies, I was not aware creating a PR triggers all this activity ! I have changed it to draft till all my testing is complete.

…at are defined in source code; implement upgrade macro

…2bit as done for other azspice runs; remove unused additions to ancil reading code

…b object

Mohit Dalvi (mcdalvi) · 2026-05-14T15:37:02Z

Merged main into branch at [08455b0](url).

Sample plots

Comparing data from ERA file (left) with lfric_atm_nudging diagnostic .
*Note that ERA data are single time snapshots while output fields are interpolated between ERA snapshots to model timestep and then averaged before output.

Mohit Dalvi (mcdalvi) · 2026-05-15T10:16:25Z

Input test files for $BIGDATA

The input files for the lfric_atm_nwp_gal9_nudging_xx tests have been generated using ERA5 reanalysts data provided by by the Copernicus Climate Change Service distributed via the Copernicus Data Service. Dataset information, including usage terms can be found here: https://cds.climate.copernicus.eu/datasets/reanalysis-era5-complete?tab=documentation

The files proposed to be added to $BIGDATA are:
/data/users/mohit.dalvi/lfric/data/nudge/era/C12/era5_nudge_L137_C12_2021032400-2706.nc
/data/users/mohit.dalvi/lfric/data/nudge/era/C48/era5_nudge_L137_C48_MG_2021032400-2706.nc

Both the files contain the following attributes:

		:licence = "The ERA5 data from Copernicus Climate Change Service is licensed under the CC-BY licence. 
Highlights and key features of the licence are here: https://creativecommons.org/licenses/by/4.0/. 
Full legal text is provided here:https://creativecommons.org/licenses/by/4.0/legalcode" ;

		:attribution = "Generated using or contains modified Copernicus Climate Change Service information .
 Neither the European Commission nor ECMWF is responsible for any use that may be made of the Copernicus
 information or data it contains." ;

		:references = "Hersbach, H. et al, (2017): Complete ERA5 from 1940: Fifth generation of ECMWF
 atmospheric reanalyses of the global climate. Copernicus Climate Change Service (C3S) Data Store (CDS). DOI: 
10.24381/cds.143582cf"

iboutle

Hi Mohit

I know this isn't fully ready yet, but I'm on leave next week so wanted to give some comments and code-owner approval so you can get this into code review by next Friday. Hopefully nothing too challenging, but a few requests and suggestions below.

Cheers

Ian

…definition and diagnostic list - this requires creating the fields in main%none

…ice_extra*

James Bruten (james-bruten-mo)

Thanks

DanStoneMO

Tested this and can confirm this works fine with JEDI, no linked JEDI PR will be needed

DanStoneMO · 2026-05-19T14:31:34Z

  <axis id="lw_bands_radiation_levels" name="lw_bands_radiation_levels" />
  <axis id="photolysis_pathways" name="photolysis_pathways" />
-  <axis id="photol_species" name="photol_species" />
+  <axis id="photol_species" name="photol_species" />  


Only thing to note from me is this rogue space here

Thanks DanStoneMO . I have fixed that in my copy

Thomas Bendall (tommbendall)

Science Review
This PR adds the technical infrastructure for nudging to ERA or AIFS data, and will be followed by a PR to add the science to perform the nudging itself (including only nudging certain length scales).

Thanks so much for this Mohit -- it looks great. I have two more major thoughts, and then a handful of other suggestions that I've commented in the code.

Do you think we should reorder the ERA ancil data vertically before we add it to BIG_DATA_DIR? (I'm assuming we haven't done this yet)... That would make the vertical interpolation more efficient when we get to that. If that's too much work before the deadline then we can potentially do it later when adding AIFS data?
I have an annoying suggestion to change the settings of the nudging-era-coarse test, which is to set the aerosols to be on the dynamics mesh rather than keeping them on a coarse mesh. I just thought this would be a bit cleaner in the test-suite, so have added suggestions on how to do this

…e mesh only for nudging. Use ERA files inverted from original top-bottom order (level=1=top) to bottom-top order

Mohit Dalvi (mcdalvi) · 2026-05-19T17:12:57Z

Thomas Bendall (@tommbendall) I have reversed the ERA file data using 'ncpdq -a hybrid' and using the new files in the tests now.
Also reveted nudging_era_coarse test to use coarse grid only for Nudging. 642225b

Test results updated.

…for aerosols

Thomas Bendall (tommbendall)

Thanks for all of this! The changes look good to me and I'm happy to approve this.

cjohnson-pi

I think there will be an interaction/conflict with #502 where I have reorganised create_model_data. Essentially, there shouldn't be an impact from #474 on linear_driver, which will be enabled by #502.

It will just depend on which ticket goes on first as to how to address this.

Matthew Hambley (MatthewHambley)

A few things to consider while we think about the linked ticket.

Matthew Hambley (MatthewHambley) · 2026-05-21T07:12:25Z

+    type(mesh_type), pointer :: mesh => null()
+    type(mesh_type), pointer :: twod_mesh => null()


We no longer require initialisation on declaration of pointers. In fact we now prohibit it. Please use nullify(pointer) at the top of the procedure code, if it is not otherwise immediately initialised.

Done b906772. also updated neighbouring pointer declarations for consistency.

Matthew Hambley (MatthewHambley) · 2026-05-21T07:24:11Z

    if (present(twod)) field_spec%twod=twod
    if (present(empty)) field_spec%empty=empty
    if (present(coarse)) field_spec%coarse=coarse
+    if (present(coarse_mesh_name)) field_spec%mesh_name=coarse_mesh_name


Why is the generic field_spec%mesh_name being assigned from the specific course_mesh_name. If the type member is generic, the initialising variable should be too. If the initialising variable is specific, the type member should also be.

Code updated to use coarse_mesh_name throughout. b906772

Matthew Hambley (MatthewHambley) · 2026-05-21T07:29:51Z

            else
               dim = 1
            end if
+      case ('ecmwf_levels')


Does this actually have anything to do with ECMWF or is that just the source of the data which happens to be being used at the moment?

Changed to nudging_levels in all references now. b906772

Matthew Hambley (MatthewHambley) · 2026-05-21T08:11:29Z

+
+    type(field_maker_type) :: creator
+
+    call log_event('GungHo: Creating nudging fields...', LOG_LEVEL_INFO)


Does this need to be "info" level. We already suffer the logging being much too talkative. This goes for all other new event logs.

Changed to LOG_LEVEL_TRACE.

Matthew Hambley (MatthewHambley) · 2026-05-21T08:13:40Z

+    call processor%apply(make_spec(                                            &
+            'surface_pressure_nudging_ext_ref', main%none, W3,                 &
+            coarse=coarse_nudging,                                             &
+            coarse_mesh_name=nudging_mesh_name,                                &
+            twod=.true., time_axis=axis%nudging                                &
+    ))


Do we always want to nudge surface pressure? The other fields are conditional on configuration.

Surface pressure in the model is not nudged. This field read from the datafiles will be used to re-create the source model vertical profile while remapping the nudging data onto model mesh.
Since the remapping is needed when any one of theta and wind is being nudged (i.e. create_nudging_fields is called) there is no condition around reading this field itself.

A comment to that effect will help future developers.

Matthew Hambley (MatthewHambley) · 2026-05-21T08:19:56Z

+        if (coarse_rad_aerosol) then
+          mesh_name = aerosol_mesh_name
+        else
+          mesh_name = ''
+        end if


Wasn't this set above, outside the conditional? Do we have code duplication here?

Duplicate statements removed. b906772.

Matthew Hambley (MatthewHambley) · 2026-05-21T08:23:59Z

   !> @brief Map moisture array enumerators to moisture array.
  type(time_axis_dict_type), parameter :: time_axis_dict &
-    = time_axis_dict_type(525,529,536)
+    = time_axis_dict_type(525,529,536,542)


Where do these numbers come from? UM code? A comment to explain this would be handy.

These numbers are part of the field_spec design itself. See original comments lfric_core:#4208, which seem to indicate they have to be unique for each field, within a different range for each field category.

I see that, in which case, a comment explaining that this is where these numbers are defined and they are opaque identifiers with no intrinsic meaning would help future developers.

A better solution still would be to define them as integer, parameter :: usefule_name = 525, then use them here. If you make these parameters public, they can be used outside the module. If that is their purpose. Even if it isn't, keeping them private but having useful names would help developers of this module.

thomasmelvin

All looks good to me

…cation

Matthew Hambley (MatthewHambley)

There are also changes requested for core which may effect this change.

Matthew Hambley (MatthewHambley) · 2026-06-04T12:18:56Z

@@ -0,0 +1,112 @@
+!-----------------------------------------------------------------------------
+! (c) Crown copyright 2025 Met Office. All rights reserved.


Wrong year, although we are not including year in the copyright statement any more.

Matthew Hambley (MatthewHambley) · 2026-06-04T12:22:38Z

+  use external_forcing_config_mod, only : theta_forcing_nudging,               &
+                                          theta_forcing,                       &
+                                          wind_forcing_nudging,                &
+                                          wind_forcing


Please use the new configuration API. You can find documentation of this at https://metoffice.github.io/lfric_core/how_to_use_it/lfric_datamodel/modeldb.html#accessing-configuration-data but please ask if you have further questions.

Matthew Hambley (@MatthewHambley)
Re: using modeldb to access configuration values: I have attempted to implement this for process_nudging_fields. However process_nudging_fields is also called in gungho_model_mod/before_context_close, same as the LBC fields. This before_contaxt_close routine name is actually passed as a procedure pointer to init_io -> lfric_core:driver_io and finally called from lfric_xios_context_mod. I cannot see a way to use the modeldb argument at this level in the code hierarchy.
Thomas Bendall (@tommbendall)

Matthew Hambley (MatthewHambley) · 2026-06-04T12:25:00Z

+  !> @param[in]    mesh       The current 3d mesh
+  !> @param[in]    twod_mesh  The current 2d mesh (not used here)
+  !> @param[in]    mapper     Provides access to the field collections
+  !> @param[in]    clock      The model clock
+  subroutine create_nudging_fields(mesh, twod_mesh, mapper, clock)


If the 2D mesh isn't being used, why pass it in? If it is needed later, then it can be obtained from the mesh collection. Something like mesh_collection%get_mesh(mesh, extrusion=TWOD) but check the API.

Given that you also need the clock and field collections, it might be more straight forward to pass modeldb in. Note that it also contains the configuration so no need to pass that either.

Matthew Hambley (MatthewHambley) · 2026-06-04T12:41:01Z

   !> @brief Map moisture array enumerators to moisture array.
  type(time_axis_dict_type), parameter :: time_axis_dict &
-    = time_axis_dict_type(525,529,536)
+    = time_axis_dict_type(525,529,536,542)


I see that, in which case, a comment explaining that this is where these numbers are defined and they are opaque identifiers with no intrinsic meaning would help future developers.

A better solution still would be to define them as integer, parameter :: usefule_name = 525, then use them here. If you make these parameters public, they can be used outside the module. If that is their purpose. Even if it isn't, keeping them private but having useful names would help developers of this module.

Matthew Hambley (MatthewHambley) · 2026-06-04T12:46:11Z

    logical(l_def)     :: coarse    = .false.             ! Is it coarse?
+    character(str_def) :: coarse_mesh_name = ''           ! Name of the coarse mesh, or blank string


In the long run I don't think "coarseness" is a useful property. Instead some measure of resolution would provide more generalised information. However, given you are following the existing patter, I wont insist on it for this change. Please have a think about the general case and if there is one, raise an issue and link it here.

Matthew Hambley (MatthewHambley) · 2026-06-04T12:48:53Z

+  end subroutine create_nudging_fields
+
+  !> @brief Iterate over active nudging fields and apply an arbitrary
+  !! processor to the field specifiers.


Please document the subroutine arguments.

Matthew Hambley (MatthewHambley) · 2026-06-04T12:49:42Z

+    use multires_coupling_config_mod,  only : coarse_nudging,                  &
+                                              nudging_mesh_name


As noted above, we are migrating to configuration objects.

Matthew Hambley (MatthewHambley) · 2026-06-04T12:51:56Z

+    call processor%apply(make_spec(                                            &
+            'surface_pressure_nudging_ext_ref', main%none, W3,                 &
+            coarse=coarse_nudging,                                             &
+            coarse_mesh_name=nudging_mesh_name,                                &
+            twod=.true., time_axis=axis%nudging                                &
+    ))


A comment to that effect will help future developers.

Matthew Hambley (MatthewHambley) · 2026-06-04T12:53:39Z

+    if (coarse_rad_aerosol) then
+      mesh_name = aerosol_mesh_name
+    else
+      mesh_name = ''
+    end if
+


Can you just pass the mesh object rather than messing about with names?

…places where *process_nudging_fields* is called

github-actions · 2026-06-11T15:39:02Z

⚠️ Hello Mohit Dalvi (@mcdalvi)!

Your CLA signature was found on the base branch, but you appear to have modified the CONTRIBUTORS.md file in this PR.

Please do not edit the CONTRIBUTORS.md file. If you have already signed the CLA, revert changes to the file and your signature will be picked up.

Mohit Dalvi (mcdalvi) added 3 commits April 29, 2026 10:44

Interim Commit while migrating from FCM branch - XML, namelist and ro…

0389dfc

…se-stem changes.

Second commit transferring changes from FCM: Nudging field and file ,…

388b69b

… time-axis definitions

Compilation fixes, mainly updating other calls to setup_model_data fo…

8a745da

…r the new arguments

Mohit Dalvi (mcdalvi) requested review from a team, cjohnson-pi, iboutle, Matt Shin (matthewrmshin), Steven Sandbach (ss421) and thomasmelvin as code owners April 30, 2026 16:20

Mohit Dalvi (mcdalvi) requested review from Matthew Hambley (MatthewHambley) and removed request for a team April 30, 2026 16:20

github-actions Bot assigned Mohit Dalvi (mcdalvi) Apr 30, 2026

Mohit Dalvi (mcdalvi) changed the title ~~LFRic-Nudging: Part-A: Introduce ability to read nudging datafiles : vn3.1.1 read nudging data~~ #74: LFRic-Nudging: Part-A: Introduce ability to read nudging datafiles : vn3.1.1 read nudging data Apr 30, 2026

Mohit Dalvi (mcdalvi) changed the title ~~#74: LFRic-Nudging: Part-A: Introduce ability to read nudging datafiles : vn3.1.1 read nudging data~~ #474: LFRic-Nudging: Part-A: Introduce ability to read nudging datafiles : vn3.1.1 read nudging data Apr 30, 2026

Mohit Dalvi (mcdalvi) added 2 commits April 30, 2026 17:36

Improve trigerring in metadata

e2c6817

include files that were not explicitly 'git add'ed

05b457a

Mohit Dalvi (mcdalvi) marked this pull request as draft May 1, 2026 09:45

Mohit Dalvi (mcdalvi) added Linked Core This PR is linked to a MetOffice/lfric_core PR KGO This PR contains changes to KGO macro This PR contains a metadata upgrade macro labels May 1, 2026

Mohit Dalvi (mcdalvi) added 2 commits May 5, 2026 11:13

First round of fixes from testing: only handle fields and settings th…

f1f0ddb

…at are defined in source code; implement upgrade macro

Fixes -mostly aligning field definitions; rationalised tests to use 3…

dd2ed96

…2bit as done for other azspice runs; remove unused additions to ancil reading code

Mohit Dalvi (mcdalvi) modified the milestone: Summer 2026 May 12, 2026

Mohit Dalvi (mcdalvi) mentioned this pull request May 12, 2026

#369: Allow coarse-grid fields with ndata levels: vn3.1 read coarse 2d MetOffice/lfric_core#369

Open

29 tasks

Mohit Dalvi (mcdalvi) added 2 commits May 13, 2026 15:13

merge into origin/main at 08455b0

de251b0

modify path to point to files containing licence information

8baec12

Mohit Dalvi (mcdalvi) added 2 commits May 14, 2026 10:43

Metadata fiex and re-alignment with configuration variables in modeld…

d4f3adc

…b object

more metadata and style fixes

50f08f3

iboutle approved these changes May 15, 2026

View reviewed changes

Changes in response to Code owner review: Remove new fields from xml …

7723834

…definition and diagnostic list - this requires creating the fields in main%none

Mohit Dalvi (mcdalvi) marked this pull request as ready for review May 18, 2026 09:01

Mohit Dalvi (mcdalvi) requested a review from James Bruten (james-bruten-mo) as a code owner May 18, 2026 09:01

github-actions Bot requested a review from Thomas Bendall (tommbendall) May 18, 2026 09:04

James Bruten (james-bruten-mo) requested changes May 18, 2026

View reviewed changes

Comment thread rose-stem/site/meto/groups/groups_lfric_atm.cylc Outdated

Rename test group to reflect target system and add to *lfric_atm_azsp…

d48f524

…ice_extra*

James Bruten (james-bruten-mo) approved these changes May 18, 2026

View reviewed changes

DanStoneMO approved these changes May 19, 2026

View reviewed changes

DanStoneMO reviewed May 19, 2026

View reviewed changes

Thomas Bendall (tommbendall) requested changes May 19, 2026

View reviewed changes

Changes from review -configure *nudging_era_coarse* test to use coars…

642225b

…e mesh only for nudging. Use ERA files inverted from original top-bottom order (level=1=top) to bottom-top order

Update KGO for *nudging_coarse* test, now reverted back to main mesh …

3293ee2

…for aerosols

Thomas Bendall (tommbendall) approved these changes May 20, 2026

View reviewed changes

Mohit Dalvi (mcdalvi) changed the title ~~#474: LFRic-Nudging: Part-A: Introduce ability to read nudging datafiles : vn3.1.1 read nudging data~~ #474: LFRic-Nudging: Part-A: Introduce ability to read nudging datafiles May 20, 2026

cjohnson-pi approved these changes May 21, 2026

View reviewed changes

Matthew Hambley (MatthewHambley) requested changes May 21, 2026

View reviewed changes

thomasmelvin approved these changes May 21, 2026

View reviewed changes

Changes from Review- mainly consistent naming of fields; remove dupli…

b906772

…cation

github-actions Bot added the cla-modified The CLA has been modified as part of this PR - added by GA label May 29, 2026

Mohit Dalvi (mcdalvi) requested a review from Matthew Hambley (MatthewHambley) June 2, 2026 16:07

Matthew Hambley (MatthewHambley) requested changes Jun 4, 2026

View reviewed changes

Mohit Dalvi (mcdalvi) added 2 commits June 5, 2026 10:45

Attempt to get away from hardwired numbers in collection declaration.

6975f0a

Revert some changes after review as modeldb may not available in all …

344ff27

…places where *process_nudging_fields* is called

		type(mesh_type), pointer :: mesh => null()
		type(mesh_type), pointer :: twod_mesh => null()


		type(field_maker_type) :: creator

		call log_event('GungHo: Creating nudging fields...', LOG_LEVEL_INFO)

		@@ -0,0 +1,112 @@
		!-----------------------------------------------------------------------------
		! (c) Crown copyright 2025 Met Office. All rights reserved.

		logical(l_def) :: coarse = .false. ! Is it coarse?
		character(str_def) :: coarse_mesh_name = '' ! Name of the coarse mesh, or blank string

		use multires_coupling_config_mod, only : coarse_nudging, &
		nudging_mesh_name

Conversation

Mohit Dalvi (mcdalvi) commented Apr 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary

Code Quality Checklist

Testing

trac.log

Test Suite Results - lfric_apps - test2_vn31_nudging_data/run4

Suite Information

Task Information

Security Considerations

Performance Impact

AI Assistance and Attribution

Documentation

PSyclone Approval

Sci/Tech Review

Code Review

Uh oh!

DanStoneMO commented May 1, 2026

Uh oh!

Mohit Dalvi (mcdalvi) commented May 1, 2026

Uh oh!

Mohit Dalvi (mcdalvi) commented May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Sample plots

Uh oh!

Mohit Dalvi (mcdalvi) commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Input test files for $BIGDATA

Uh oh!

iboutle left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

James Bruten (james-bruten-mo) left a comment

Choose a reason for hiding this comment

Uh oh!

DanStoneMO left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Thomas Bendall (tommbendall) left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Mohit Dalvi (mcdalvi) commented May 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Thomas Bendall (tommbendall) left a comment

Choose a reason for hiding this comment

Uh oh!

cjohnson-pi left a comment

Choose a reason for hiding this comment

Uh oh!

Matthew Hambley (MatthewHambley) left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Mohit Dalvi (mcdalvi) commented Apr 30, 2026 •

edited

Loading

Mohit Dalvi (mcdalvi) commented May 14, 2026 •

edited

Loading

Mohit Dalvi (mcdalvi) commented May 15, 2026 •

edited

Loading

Mohit Dalvi (mcdalvi) commented May 19, 2026 •

edited

Loading