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.
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
Adding code to analyze the siginificant wave heigh in GSI 3D Analysis (see issue #601) #614
Adding code to analyze the siginificant wave heigh in GSI 3D Analysis (see issue #601) #614
Changes from 1 commit
e117611
8fd2251
f603756
8020227
8432590
f3db06b
67b02a9
1a4bab4
aa08628
7888831
99dd00a
f6031bd
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
combine Line 1831 with Line 1830 and remove the comment
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.
Will do. Thank you!
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.
remove the comment in Line 1851
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.
Will do , Thank you!
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.
we may NOT want to write out this information for each PE? Otherwise, it will be too many for runs using lots of PEs.
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.
These lines are done only on the PE which reads the surface firstguess, not by all the PEs. So only one PE prints this message. In the real run if GSI, it ddid show just one line in the "stdout" log 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 understand that for regional FV3 netcdf files, we use parallel I/O. You may check with @TingLei-NOAA whether parallel I/O applies to howv (if not yet, we may want to get it done in parallel, which will benefit the NA_3km domain)
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.
@guoqing-noaa Thanks for bringing out this point. For being now, in the parallel io for fv3-lam, these 2d fields are not considered ,which are still treated by subs like gsi_fv3net2d_read. In the future, when those 2d fields are more and more in the future, we may need to consider a similar parallelization to them.
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.
@TingLei-NOAA @guoqing-noaa
Thank you, Ting, for the explanation on this point.
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.
@TingLei-NOAA Thanks for the explanation. I think howv maybe the first 2D field to be read by regional GSI?
@GangZhao-NOAA it will be good if we can get the information about what extra minutes are needed to read the extra howv field for NA_3km domain. Thanks!
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.
@guoqing-noaa there are a group of 2d fields to be read in in gsi_fv3ncf2d_read and somes are written out through gsi_fv3ncdf_write_sfc in the current gsi.
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.
@TingLei-NOAA There is a subroutine gsi_fv3ncdf2d_read_v1(...) but it is never called anywhere. Do you have any idea what it is for? Thanks!
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.
@guoqing-noaa That is originally supposed to read some 2d fields from cold start files, while never actually implemented and used. It could be removed safely.
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.
@guoqing-noaa @TingLei-NOAA
As Ting answered, there are a bunch of 2d fields read from 2-D firstguess file (sfc_data.nc), including t2m, q2m and howv.
As for the "information about what extra minutes are needed to read the extra howv field for NA_3km domain", to be honest, I do not know. But the adding the analysis of howv (including reading firstguess, output analysis, read obs and cost function, minimisation, etc) does not increase the time cost much, even for 3km NA domain.
With my testing case on 3km NA domain, on Hera hybrid run (with gdas ensemble) without howv the wall-clock time is 973 seconds, with howv it is 974 seconds.
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.
remove comments in line 1953
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.
Will do. Thanks!
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 don't understand why we need to broadcast i_howv_in_data? Should it be decided by each PE? Also I cannot think about a situation where one PE has HOWV data at firstguess while another PE doesn't?
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.
The task to read the surface fristguess data is done only by one PE, not by alll PEs, so "i_howv_in_data" is updated only on this specific PE. To use "i_howv_in_data" later on other PEs. it has to be broadcasts to all PEs.
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.
remove comments in Line 3232
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.
will do. Thanks!