-
Notifications
You must be signed in to change notification settings - Fork 64
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
Capgen in SCM: Fix to allow for scheme subcycling. #633
base: develop
Are you sure you want to change the base?
Conversation
if gen_unique: | ||
new_lname = self.new_internal_variable_name(prefix=lname) | ||
newvar = newvar.clone(new_lname) | ||
# Local_name needs to be the local_name for the new |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am very confused by this comment. Should the first Local_name
be lname
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All instances of lname
are replaced, there is no logic to keep the first instance. So for three instances of the same lname, we have lname1
, lname2
, and lname3
, not lname
, lname1
, lname2
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, this is part of #631 and does not impact the sub-cycling isssue
… bugfix/scheme_subcycling
Overview
This PR contains changes to fix scheme subcycing in Capgen and extends the var_compatability_test to exercise subcycling.
UPDATE: Added bugfix for suite-part list ordering.
Description
Create local group variable for subcycle indexing.
Fix bug (
self.loop
->self._loop
) in the Subcycle write phase, and in ccpp_datafile.User interface changes?: No
Fixes: #632
Fixes: #634
Testing:
Added to var_compatibility_test to exercise feature.
This PR contains changes in #631