-
Notifications
You must be signed in to change notification settings - Fork 157
Modified config_archive.xml to archive CAM+DART files. #1302
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
base: cam_development
Are you sure you want to change the base?
Conversation
<hist_file_extension>h\d*.*\.nc$</hist_file_extension> | ||
<hist_file_extension>i\..*\.nc$</hist_file_extension> |
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'm wondering about the implications of removing this line: <hist_file_extension>i\..*\.nc$</hist_file_extension>
on other CAM jobs. I will admit that I am by no means an expert on this file and archiving in general, but it appears that we'd no longer be archiving intantaneous history files? Should this line perhaps remain?
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.
That line was replaced by a <rest_file_extension>i\..* line.
This line handles the CAM "initial file", which is the only '.i.' file that I know of.
There may be '.i[a-z0-9]+.' files (someday), but they would be handled differently.
But I would like to hear the opinion of CAM developers about this.
DART needs to have the .i. files archived with the restarts because that's the file
containing the model state which DART needs to use to start CAM at the beginning of each DA cycle.
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 want to be sure we are talking about the same thing.
instantaneous files are the .h0i.
, .h1i.
, ... which is different from the initial file .i.
.
Where will these files go?
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 believe that the .h[0-9]i. files will still be handled by the xlm line:
<hist_file_extension>h\d*.*\.nc(\.gz)?$</hist_file_extension>
which I parse as "h+any_digit+any_number_of_any_characters".
The '.i.' file is currently handled by the line:
<hist_file_extension>i\.\d.*\.nc(\.gz)?$</hist_file_extension>
I believe that the parsing code adds '.' before the regex listed in these .xml files,
so this line only applies to '.i.' and not to the .h[0-9]i. files.
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.
Ditto @cecilehannay . We need to know if this change moves the location of history output and breaks everyone's analysis scripts. Fixable, yes, but it would be good to know in advance.
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.
In my test the .h0i. files ended up in archive/atm/hist, archive/rest/$date, and in $rundir.
I only requested 1 CAM history file.
The .i. files ended up in archive/rest/$date and $rundir.
That's what I intended, but someone else should test it too, especially if I failed to create a CAM file type.
The archive directory is /glade/derecho/scratch/raeder/St_BHISTC_LTso-SE_st-arch/archive.
Thanks for looking into this!
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.
@cecilehannay - Would you be able to checkout @kdraeder's branch and make a quick run similar to ones you are currently making and make sure all that all the history files end up where they should?
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.
@cecilehannay - I have two CAM checkouts for you to test:
- /glade/derecho/scratch/cacraig/cam6_4_089 - A straight checkout of cam6_4_089
- /glade/derecho/scratch/cacraig/cam6_4_089_raeder - A checkout of cam6_4_089 with the DART changes
Please let us know what your runs indicate for both the history and the initial condition files (and any other files for that matter if they change)
I did a few runs to test the new code and I see an issue with the code when more frequent initial conditions are required (for instance I use: First I did a run with the
But if I use
|
@kdraeder - Are you going to supply a fix for this? If not, do you no longer need this PR to go into CAM? |
@cacraigucar I was just working on this! @cecilehannay Thanks for running those tests. In the first pair (inithist = default)
In the last test (inithist = MONTHLY, raeder's archive mods, run for 4 years instead of 2)
How are the intermediate .i. files used? |
@brian-eaton and/or @jedwards4b - Can one of you direct @kdraeder to the code location where he might need to make his mods? |
Have you tried adding .i files to both restart and history? That is add back: |
My test using @jedwards4b suggestion results in copies of the intermediate .i. files in archive/atm/hist I actually tested |
@kdraeder sounds good, thank you. |
I should have written "I'll commit this change and push it for review" |
This would be a fix for issue #1301
I'll provide background or details as needed.