Opened 4 months ago

Closed 4 months ago

#2722 closed help (fixed)

Editing suite to add NEMO Namelist information

Reported by: m.couldrey Owned by: um_support
Component: Rose/Cylc Keywords: namelist, NEMO, ancillary file
Cc: Platform: NEXCS
UM Version: 10.7

Description

Hi CMS, I am trying to modify my suite (u-az004) to read in an extra anciliary file and add the field in this file to the air-sea fluxes in an HadGEM3 (GC3.1 N96 ORCA1). I have taken a branch of the NEMO code and can see that files like sbcblk_core.F90 have the infrastructure to read in fields that can be used to force NEMO (when run uncoupled to an atmosphere). In my configuration, the surface boundary condition is instead managed by sbccpl.F90. What I'd like to do is incorporate the sorts of methods that I see in sbcblk_core.F90 to read in a field (in an nc file) in sbccpl.F90.

In my suite (in rose), I can see namelist options for NEMO's Surface Boundary Condition when run using either fully coupled or Core forcing. It seems like NEMO gets passed information describing Core fields from the suite. For example, the file name, frequency, variable name etc of sn_qsr shortwave solar radiation are editable fields in the suite under nemo-cice/namelist/NEMO namelist/Surface Boundary Condition/Core? forcing (namsbc_core). So I assume I should pass information about my ancil field to NEMO in the same way: by adding some namelist information to my suite in the Coupled Forcing section.

I'm not quite sure how to do this, though; where might I find the files that I could edit to add in new namelist information (i.e. to copy some part of the Core forcing section of the suite across into the Coupled section)? I see that to edit to edit the suite info and suite conf parts of my suite I make changes in suite.rc or rose-suite.conf, and the metadata is stored in the meta folder. Where would I edit the sections of my suite described under the nemo-cice section? I guess a lot of my questions stem from not fully understanding how my suite interacts with the NEMO code.

Change History (7)

comment:1 Changed 4 months ago by willie

Hi Matthew,

The meta-data for the nemo-cice app is, you can see, ocean_ice/GO6/nemo36_gsi8_v2. This is stored in ~fcm/rose-meta. You will need to make your own copy of this file and add your variables there.

As you say, in your nemo-cice rose-app.conf file, you need to add/extend you namelists there.

I hope that helps.

Willie

comment:2 Changed 4 months ago by m.couldrey

Hi Willie

Thanks for the tip! I now the see the ~fcm/rose-meta etc directory and the necessary files. Is it advisable to fcm checkout the rose-meta.conf (if so how would I do this?), or just cp it and somehow point my suite to it?

Thanks for your help!
Matthew

comment:3 Changed 4 months ago by willie

Hi Matthew,

Just copy it. Then in the suite nemo-cice page, enter the full path to the copy.

Willie

comment:4 Changed 4 months ago by m.couldrey

Hi Willie

Thanks, I've managed to get copy of the metadata file (actually I see that rose-suite.conf points to two other rose-suit.conf files, one for nemo and one for cice, but I took a copy of the nemo one and pointed my suite to the original for the cice one) and pointed the suite to it, and that seems to have worked. I'm now getting an error under suite-conf telling me that two namelists (nambbc and nambbl) are compulsory, but not used in my configuration. I'm confused because in my namelist_cfg I can see that nambbc and nambbl are included.

Thanks for all your help with these things!
Matt

comment:5 Changed 4 months ago by willie

Hi Matthew,

You've copied them (why two) into the suite meta-data directory u-az004. This will attempt to apply the meta-data to the whole suite, NEMO, CICE, UM, everything. So these need to be removed.

You need to create a meta-data directory called meta under the nemo_cice app and copy the meta-data there.

Once you're happy with the new set up, run fcm status to tell you about the changes you made. Some will be new files prefixed by a ?. You need to fcm add these to your project.

Willie

comment:6 Changed 4 months ago by m.couldrey

Hi Willie

Ah, I see, thanks for clearing that up. That should keep me ticking over for now!

Thank you for helping me with this!
Matt

comment:7 Changed 4 months ago by willie

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.