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.

Sign up for GitHub

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

Jump to bottom

PROJECT setting in CIME5 (question) #1227

Closed
worleyph opened this issue Jan 18, 2017 · 12 comments · Fixed by #1300
Closed

PROJECT setting in CIME5 (question) #1227

worleyph opened this issue Jan 18, 2017 · 12 comments · Fixed by #1300
Assignees
@jgfouca
Labels
CIME PotentialBug question

Comments

@worleyph
Copy link
Contributor

For reasons I can't remember any more, I had $PROJECT set to a default (now defunct) project in my .tcshrc at the ALCF. With CIME2, the project specified in the ./create_newcase command took precedence over this. With CIME5, this has been reversed - what is set in my environment is what is used in /case.setup, not what is set by the ./create_newcase.

So, this is new behavior. My first question is whether it was intentional. I vaguely remember having a discussion on this topic, pre-CIME and with Bill Sacks in the original introduction of the PROJECT logic into ACME and CESM, and voting for the behavior that was in CIME2. If it was changed intentionally, I'd like to understand the reasoning behind it. If not intentional, I'd like it changed back.
@rljacob rljacob assigned jgfouca and unassigned rljacob Jan 18, 2017
@gold2718
Copy link

@worleyph & @jgfouca
This sounds like an issue which should be in ESMCI/CIME, not in ACME.
It sure sounds like a bug to me since the command line is your last chance to override anything else.

@worleyph
Copy link
Contributor Author

worleyph commented Jan 19, 2017 •
edited
Loading

@gold2718 ,

This sounds like an issue which should be in ESMCI/CIME, not in ACME.

Reporting it here because here (ACME) is where I noticed it, and it affects the ACME community. (I do the same thing for MCT issues that have a direct impact on ACME.) I'll let @jgfouca report it in ESMCI/CIME. Thanks.

@jgfouca
Copy link
Member

jgfouca commented Jan 19, 2017

I'll let @jgfouca report it in ESMCI/CIME. Thanks.

Done.

@worleyph
Copy link
Contributor Author

@jgfouca , thank you.

@jgfouca
Copy link
Member

jgfouca commented Jan 20, 2017

@worleyph I confirmed that the behavior is correct in CIME-5.2. You should see things working correctly once we get 5.2 into ACME.

@jgfouca jgfouca closed this as completed Jan 20, 2017
@worleyph
Copy link
Contributor Author

Thank you. Is there a timeline for that?

@jgfouca
Copy link
Member

jgfouca commented Jan 20, 2017

I would hope within 2-3 weeks.

@worleyph
Copy link
Contributor Author

Need to get this PR done before then then :-).

@jgfouca
Copy link
Member

jgfouca commented Jan 20, 2017

@worleyph is this bug a blocker for you?

@worleyph
Copy link
Contributor Author

Not any more - just took awhile to figure out why I couldn't build on Mira and Cetus. All is good now. Previous comment was essentially to myself to finish this review as soon as possilbe.

@worleyph
Copy link
Contributor Author

Reopening until fix is in place and tested in ACME.

@worleyph worleyph reopened this Jan 31, 2017
@jgfouca
Copy link
Member

jgfouca commented Mar 15, 2017

This is now on master.

@jgfouca jgfouca closed this as completed Mar 15, 2017
@rljacob rljacob mentioned this issue Mar 15, 2017
Merged
agsalin pushed a commit that referenced this issue Apr 13, 2017
@jedwards4b
Merge pull request #1227 from ESMCI/fischer/config_cesm_allactive_mv
7b10920 
Config cesm allactive mv
Update config_files.xml to move config/cesm/allactive to the top of CESM in config/allactive.
config/allactive is being brought in by an external in the CESM subversion checkout.

Test suite: scripts_regression_tests.py, SMS.f09_g16.B1850.yellowstone_intel.allactive-defaultio build
Test baseline:
Test namelist changes:
Test status: bit for bit

Fixes

User interface changes?:

Code review:jedwards
jgfouca pushed a commit that referenced this issue Jan 8, 2018
@jedwards4b
Squashed 'src/externals/pio1/' changes from 96b76c7..b4e6d54
c371da4 
b4e6d54 limit value of pio_max_var_dims
3645510 Merge pull request #1227 from NCAR/pio1_0_cime_merge
6cd47b4 fix whitespace issues pio1

git-subtree-dir: src/externals/pio1
git-subtree-split: b4e6d54044feeaa7be0b400b058735e51c3219c1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jgfouca jgfouca

Labels
CIME PotentialBug question
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update CIME to 5.2.0 E3SM-Project/E3SM
4 participants
@rljacob @gold2718 @jgfouca @worleyph