Skip to content

Conversation

@AleksiNummelin
Copy link
Collaborator

This pull request introduces a new folder and a set of scripts that are useful when running BLOM on standalone mode. Most notably, it includes limits.json and limits_from_json.py that create the limits namelist file needed by BLOM. At a later stage, this python-based functionality could replace the current shell script cime_config/buildnml used in the NorESM system.

The limits_from_json.py reads in the master limits.json file and optionally a user-provided user_nl_blom namelist and creates a final limits file for BLOM. In future, one could either have a configuration specific limits.json file, or a configuration specific user_nl_blom file (perhaps renamed to something else). I believe the latter option would be better.

The limits.json file in this pull request is mostly specific to the 'channel' setup and does not include iHAMOCC namelists. This can functionality can be easily added.

In addition, this pull request includes a run script that can be used on Betzy and a HOWTO file (pending proper documentation).

@milicak
Copy link
Collaborator

milicak commented Apr 23, 2021

I am not quite sure this is the right way to go, because there are multiple idealized experiments in BLOM as of now.
We should dicuss how to run all these idealized experiments stand alone.
I suggested @matsbn before to create another project such as BLOM_examples and commit all the necessary scripts such as in this pull to that project. That is one way, there might be others. It is better to discuss this.

@AleksiNummelin
Copy link
Collaborator Author

We should probably have a separate discussion. I think the main contribution here is the functionality to create limits files and I think that type of functionality could live in a 'utils' folder. I think @matsbn has created some infrastructure for creating a case when running outside NorESM.

@AleksiNummelin
Copy link
Collaborator Author

Whatever the optimal format of including these changes, I realized that actually the idealized setups should be accompanied with limits file, because otherwise, one doesn't know the namelist settings those cases are supposed to be run with.

@matsbn
Copy link
Contributor

matsbn commented Apr 23, 2021

Not sure what is best, having run configurations in a separate repository or in the BLOM repository itself. So a good idea to have a discussion on this.

@AleksiNummelin AleksiNummelin linked an issue Apr 28, 2021 that may be closed by this pull request
Copy link
Contributor

@TomasTorsvik TomasTorsvik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, this PR has been dormant for way too long. I suggest we include it in the master branch since (1) it includes useful information on running BLOM on Betzy, (2) it doesn't break anything, and (3) we don't have any immediate plans to store this information elsewhere.

Should we decide to make a new structure for external utilities, we can always pull it out again in the future.

@TomasTorsvik
Copy link
Contributor

This one has been stalled for a long time. I don't think this PR will be merged in at this point, so I close it now.

@github-project-automation github-project-automation bot moved this from Todo to Done in NorESM Development Nov 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Restructuring of BLOM directory

4 participants