-
Notifications
You must be signed in to change notification settings - Fork 150
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
changes to allow USE_MGBF be able to be off #772
Draft
TingLei-daprediction
wants to merge
4
commits into
NOAA-EMC:develop
Choose a base branch
from
TingLei-daprediction:feature/gsi_mgbf_turned_off
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
7ab15cb
change to allow USE_MGBF be able to be off
TingLei-daprediction cf3a3a3
According to Russ' suggestion, using BUILD_MGBF on the top level to …
TingLei-daprediction f3ef08c
Merge branch 'develop' into feature/gsi_mgbf_turned_off
TingLei-daprediction 4e85ebd
Merge branch 'develop' into feature/gsi_mgbf_turned_off
TingLei-daprediction File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
USE_MGBF_def
is the wrong variable.CMakeLists.txt
setsUSE_MGBF
.USE_MGBF_def
needs to be changed toUSE_MGBF
The same comment applies to all occurrences of
USE_MGBF_def
in this source code file.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 wanted to use different names in cmake files and the fortran source codes
in src/gsi/CMakeLists.txt, there is :
That makes USE_MGBF_def to be used as the preprocessing option.
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 set
USE_MGBF
toON
inCMakeLists.txt
. This broke the buildLooks like the error is that the first MGBF
ifdef
inhybrid_ensemble_isotropic.F90
referencesUSE_MGBF
while all the other ifdefs reference
USE_MGBF_def
. We need to pick one.My preference is to use
USE_MGBF
consistently throughCMakeLists.txt
and the source code. That said, I am not a cmake expert. Maybe the the two varaible approach ofUSE_MGBF
&USE_MGBF_def
is better.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.
Russ, Thanks for exploring on them. I think use of one variable or two variable is just a stylish problem. In this case, up to now, there are no actual differences. Using two variables ( as for USE_GSDCLOUD vs RR_CLOUDANALYSIS) just gives a reminder on how those directives in the source codes are being recognized by the compiler.
If it is ok with you, I still prefer to following the use of such a "two variable" approach in the previous GSI setup as for the above GSDCLOUD management.
If you think the "one variable" approach is better enough that we don't need use the same "two variable" approach in GSI for similar situations , I can change it later .
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.
My preference remains to use one variable,
USE_MGBF
, all the way through. This is more readable thanUSE_MGBF_def
and less confusing. You are the developer. It's your PR. Do as you wish.