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

coupled run 1 w/ wscale_factor #358

Closed
adamrher opened this issue Aug 8, 2023 · 5 comments
Closed

coupled run 1 w/ wscale_factor #358

adamrher opened this issue Aug 8, 2023 · 5 comments
Labels
Run request Label for CAM developpers who requested a new development simulation

Comments

@adamrher
Copy link
Collaborator

adamrher commented Aug 8, 2023

Description of the run

Same as #356 except

microp_aero_wsub_scale  = 1.0->0.75

Suffix in the casename

Suffix

Namelist modifications

Namelist

Source modifications

SourceMods

Sandbox

Requested sandbox or tag

Contact info

@adamrher @PeterHjortLauritzen

Any other relevant information

Enter relevant info

@adamrher adamrher added the Run request Label for CAM developpers who requested a new development simulation label Aug 8, 2023
@cecilehannay
Copy link
Collaborator

@klindsay28: Gustavo mentioned to me the ocean group wanted to modify the diag_table in the next run. I don't have the new diag_table. Is it ok to start the run with the current one?

@klindsay28
Copy link

@cecilehannay , sorry I missed this earlier.
I'm not sure what Gustavo had in mind.
However, he did update some stuff in
/glade/scratch/gmarques/for_cecile/diag_table.
For now, please use that, replacing the case name there with your new case name.

@cecilehannay
Copy link
Collaborator

klindsay28: I started the run with the diag_table I had. But I could edit the diag_table when continuing the run.

@cecilehannay
Copy link
Collaborator

see run #361

@klindsay28
Copy link

The changes that I'm aware of Gustavo putting into that file modified the filenames of transports across various sections.

A drawback with the current diag_table is that it is not compatible with MOM6 archive pattern matching in this tag, so the files are not getting moved to $DOUT_S/ocn/hist.

So a benefit of changing diag_table is that newly written transports files would get archived.
However, it would also change filename patterns mid-run, making analysis rather inconvenient.

Option 1: Leave diag_table as is, manually move transports files to $DOUT_S/ocn/hist

Option 2: Update diag_table, manually move existing transports files to $DOUT_S/ocn/hist, and rename them to match new filename patterns.

Option 1 seems like the least work to me. I suggest going with that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Run request Label for CAM developpers who requested a new development simulation
Projects
None yet
Development

No branches or pull requests

3 participants