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

p7b not reproduceable itself #684

Closed
jiandewang opened this issue Jul 9, 2021 · 16 comments · Fixed by #606
Closed

p7b not reproduceable itself #684

jiandewang opened this issue Jul 9, 2021 · 16 comments · Fixed by #606
Labels
bug Something isn't working

Comments

@jiandewang
Copy link
Collaborator

Description

It is found that p7b is not reproduceable by itself. This is confirmed from Xu Li, Weizhong and Jiande's independent tests. Attached is the tmpsfc difference between two runs from sfcf00.nc
Tsfc

To Reproduce:

checkout https://github.com/ufs-community/ufs-weather-model/tree/release/P7b
compile and run any one of the p7b case twice
compare the results

@jiandewang jiandewang added the bug Something isn't working label Jul 9, 2021
@jiandewang
Copy link
Collaborator Author

a good start to track this issue is turn back to p7a to see whether same issue exists or not. However p7a is no longer available to run as "input_data_20210608" has been deleted.
A question for EIB group: is it fine to use the existing input data before 20210608 to run p7a ? what's new in 20210608? will the new stuff have any impact to p7a setting ?

@DeniseWorthen
Copy link
Collaborator

There is a directory prototype7-input-data-20210608. In that directory, the MERRA2 input has been corrected.

@SMoorthi-emc
Copy link
Contributor

SMoorthi-emc commented Jul 9, 2021 via email

@jiandewang
Copy link
Collaborator Author

@SMoorthi-emc : thanks for the good news

@jiandewang
Copy link
Collaborator Author

@DeniseWorthen thanks for the information. I am going to try p7a with that fixed file dir.

@jiandewang
Copy link
Collaborator Author

my two p7a runs with "prototype7-input-data-20210608" got identical results. So the issue must be related to the new features in p7b.

@DeniseWorthen
Copy link
Collaborator

To eliminate Mushy thermo as a cause, you can comment out these two settings:

export KTHERM=2
export TFREEZE_OPTION='mushy'

That will return to the default (old) settings.

@jiandewang
Copy link
Collaborator Author

@DeniseWorthen : thanks for the info., will try

@SMoorthi-emc
Copy link
Contributor

SMoorthi-emc commented Jul 9, 2021 via email

@jiandewang
Copy link
Collaborator Author

@SMoorthi-emc OK will wait for your PR's merge. Thanks

@DeniseWorthen
Copy link
Collaborator

DeniseWorthen commented Jul 9, 2021

@SMoorthi-emc Isn't this gcycle fix the only change that is in p7b but not in FV3 develop right now? But the current develop branch does reproduce itself; is there a bug in the gcycle fix that P7b has which will get fixed your PR?

@SMoorthi-emc
Copy link
Contributor

SMoorthi-emc commented Jul 9, 2021 via email

@DeniseWorthen
Copy link
Collaborator

@SMoorthi-emc Jiande reminded me we are running the P7 w/ threads so that explains my confusion.

@SMoorthi-emc
Copy link
Contributor

Denise, It turned out that I was not using mushy thermodynamics. So, I made three new runs with mushy thermodynamics and the results are reproducing, including restart run (all three runs are with two threads, including the ocean).

@jiandewang
Copy link
Collaborator Author

I turned off mushy, results not reproduceable, so mushy is not the cause

@bingfu-NOAA
Copy link

I had one issue related to NSST restart, might be not related to this one.
But I suggest turn off NSST spinup and give a try?
change 2,1,0,0,0 to 2,0,0,0,0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants