-
Notifications
You must be signed in to change notification settings - Fork 205
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
RUN_TYPE and GET_REFCASE wrong for SSP extensions #148
Comments
GET_REFCASE isn't being set to TRUE for most cases. It seems like it should be for cases when REFCASE is set. I'm adding changes that set GET_REFCASE to TRUE when these particular compsets are triggered, but it seems like it should be more general than that. @jedwards4b and @fischer-ncar can you comment on this? Should GET_REFCASE be set more generally? Or just for these extension compsets? Or should I leave GET_REFCASE like it is? |
GET_REFCASE should only be true for the specific compsets that have refcases in inputdata, do not set it in general or we will be getting lots of requests for data that isn't there. |
Well my point is that there's a ton of specific settings for specific REFCASES that are NOT setting GET_REFCASE to TRUE and seem like they should. For here I'm just adding these specific REFCASES for GET_REFCASE, but it seems like these other REFCASES should set it as well. I don't mean a general setting for everything, but for the specific compsets that do set a REFCASE. |
Looks like this was merged, so closing. |
cam6_2_030: Fix for floating point issue in GW drag.
Summary of Issue:
RUN_TYPE and GET_REFCASE are wrong fro the SSP extensions
Expected behavior and actual behavior:
RUN_TYPE is startup but should be hybrid
and GET_REF_CASE is FALSE, but should be TRUE
Steps to reproduce the problem. Include externals description file(s) and link to public repository):
Setup a case for: BWSSP585extcmip6, BWSSP534osextcmip6, or BWSSP126extcmip6
What is the changeset ID of the code, and the machine you are using:
cesm2.1.4-rc.01
on cheyenne, but machine doesn't matter.
have you modified the code? If so, it must be committed and available for testing: No
The text was updated successfully, but these errors were encountered: