Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document preview_namelist usage #1277

Open
rljacob opened this issue Mar 24, 2017 · 7 comments
Open

Document preview_namelist usage #1277

rljacob opened this issue Mar 24, 2017 · 7 comments

Comments

@rljacob
Copy link
Member

rljacob commented Mar 24, 2017

The logic for when preview_namelist is called and how it keeps namelists in sync should be documented. Its a script available to user's so we should tell them when they might need to run it if they don't want CIME to do it all for them.

@rljacob
Copy link
Member Author

rljacob commented Mar 24, 2017

For a regular create_newcase, I think this is the sequence and reasons:

  • Called during case.build before the actual build:
    • because some builds need namelist info. First time all namelists are built.
  • Called in case.submit
    • because users may have changed an xml file after building.
  • Called in case.run
    • because users may have changed an xml file while the job is in the queue before it runs.

@jedwards4b
Copy link
Contributor

You mean preview_namelists

@rljacob rljacob changed the title Document create_namelist usage Document preview_namelist usage Mar 24, 2017
@rljacob
Copy link
Member Author

rljacob commented Mar 24, 2017

Thanks. Fixed it.

@rljacob
Copy link
Member Author

rljacob commented Mar 24, 2017

According to @jgfouca in #1203 (comment), this is the sequence for create_test:

  1. Called post-SETUP by create_test (if compare or generate baselines)
  2. Called in build.py for sharedlib build
  3. Called in case.submit
  4. Called once per invocation of case_run.run_model

agsalin pushed a commit that referenced this issue Mar 29, 2017
Add IBM compiler macro
Also add a flag to report compile times.
And keep Mira/Cetus settings identical.

[BFB] - Bit-For-Bit
jgfouca pushed a commit that referenced this issue Feb 23, 2018
Add IBM compiler macro
Also add a flag to report compile times.
And keep Mira/Cetus settings identical.

[BFB] - Bit-For-Bit
jgfouca pushed a commit that referenced this issue Mar 13, 2018
Add IBM compiler macro
Also add a flag to report compile times.
And keep Mira/Cetus settings identical.

[BFB] - Bit-For-Bit
@github-actions
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@rljacob
Copy link
Member Author

rljacob commented Nov 20, 2023

still need this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants