Hi Community,
Today, I added a new namelist to my suite. I’m wondering if it’s possible to format it so that the new section is redirected to the correct subsection. I would also like to format each input differently. I think I probably need to add a new ns and maybe the full_ns in the meta/rose.conf. Does anyone have a template for how to do this? Thanks in advance for your help.
Best regards,
Estanislao
Hi Estanislao,
I’m guessing the new namelist has been added to the um app?
If so then you will need to modify the rose-meta.conf file in the UM repository. Assuming you already have a UM branch with your code changes to handle the namelist then you will find the rose-meta.conf file in the rose-meta/um-atmos/HEAD directory. Use the existing namelists in there as a template.
Then use rose edit -M <path of working copy of branch/rose-meta/> to point to the new metadata file.
There is some general UM metadata info here: https://code.metoffice.gov.uk/trac/um/wiki/UMMetadata
Regards,
Ros
Hi Ros,
thanks for your help. My suite does not have those subfolder. Do you know any idx where I can find a suite with those subfolders?
Best regards,
Estanislao
Hi Estanislao,
The rose-meta/um-atmos/HEAD is in the UM source code repository. It is not part of the suite. When you add new namelists and namelist items to the UM app there is usually accompanying UM source code changes which you make in a UM branch.
Please confirm you are adding namelist items to the UM app in your suite and if not please tell me the suite id and the path to the file you have added them to so I can advise better.
Regards,
Ros
Hi Ros,
I am trying to add the COARE3.5 scheme to the NEMO3.6 version of my suite. To do this, I need to include namsbc_blk within namsbc. I would like to provide a working idx, but I am currently encountering some build issues that I hope to resolve. It seems that the NEMO source files I was using became incompatible after making the changes, leading to merging errors. Interestingly, these errors occurred in completely unrelated (and unmodified) Fortran routines. As a result, I am now attempting to edit the main UKESM1.2 NEMO source to incorporate these changes.
Best regards,
Estanislao
Hi Estanislao,
NEMO/CICE metadata is in the MOCI code repository on MOSRS fcm:moci.x-tr under the rose-meta/ocean_ice directory. I can’t point you to the exact sub-directory below there without seeing your suite, however you should be able to work it out by looking in the ~/roses/<suiteid>/app/nemo_cice/rose-app.conf file. At the top you will see a meta= line, this will tell you the path to the metadata.
Cheers,
Ros
Hi Ros,
I have already found the file I want to change, but I am not sure how to do it without affecting other users. My suite meta is in ocean_ice/GO6/HEAD, which means that the NEMO configuration is in ocean_ice/nemo/v3.6_GO6_CO6_v4. What I want to do is add the namsbc_blk lines from ocean_ice/nemo/v4.0.1_GO8 into ocean_ice/nemo/v3.6_GO6_CO6_v4. Should I create my own configuration for this?
fcm copy fcm:moci.x-tr somthing
fcm checkout somthing folder_to
then add the lines
and fcm commit?
Hi Estanislao,
Create a new branch and check it out.
puma2$ fcm bc <new_branch_name> fcm:moci.x-tr #Create a new branch
puma2$ fcm co fcm:moci.x-br/dev/estanislaogavilan/r5783_<new_branch_name> # Checkout new branch
Then edit the required file and run fcm commit
This is just for the metadata so the new namelist elements you’ve added to the suite render nicely in the rose-edit GUI.
Cheers,
Ros.
Hi Ros,
Thank you so much for this tutorial. The suite looks very tidy now. I have one last question: the command rose edit -M <path of working copy of branch/rose-meta/> only previews the changes. If I want to add my new format, should I write the path as ../../branches/dev/estanislaogavilan/r5783_nemo36_coare/rose-meta/ or can I just add the config in a folder and use import in the rose-app.conf?
Best regards,
Estanisalo
Hi Estanislao,
In the app/nemo_cice/rose-app.conf file change the meta= line at the top to be the absolute path to your branch working copy.
Cheers,
Ros
Hi ros,
thanks so much. Now, the suite can load the format perfectly fine.