search

E3SM-Project / e3sm_data_docs

Documentation on E3SM simulations
https://e3sm-project.github.io/e3sm_data_docs/
0 stars 0 forks source link

Add v2.1 simulation info to simulaiton table #48

Open chengzhuzhang opened 1 week ago

chengzhuzhang commented 1 week ago

Paths:https://acme-climate.atlassian.net/wiki/spaces/ED/pages/2766340117/V2+Simulation+Planning CMIP url for all v2.1: https://esgf-node.cels.anl.gov/search?project=CMIP6&activeFacets=%7B%22source_id%22%3A%22E3SM-2-1%22%7D Reference:https://gmd.copernicus.org/preprints/gmd-2024-149/

chengzhuzhang commented 1 week ago

@forsyth2 there might be some finalization needed for publication. I will update once the info is final.

forsyth2 commented 1 week ago

@chengzhuzhang Thanks, should I get started on this or wait until info is finalized? When do we want the data accessible on Data Docs by?

chengzhuzhang commented 1 week ago

No hurry on this, I'm waiting for confirmation from Tony about some clarification questions from Lukasz. No hurry on this, to make the info available in concurrent with this upcoming Newsletter would be fine.

forsyth2 commented 1 week ago

Sounds good, thanks!

forsyth2 commented 4 days ago

@chengzhuzhang I'm assuming we'll need to create reproduction scripts fort the v2.1 runs too, right? That's by far the time-bottleneck on these PRs.

I created an automated process for generating v2 run scripts based on the original and reproduction piControl scripts. https://github.com/E3SM-Project/e3sm_data_docs/blob/main/utils/diff_patch is all those differences, and then https://github.com/E3SM-Project/e3sm_data_docs/blob/main/utils/patch_helper.py is necessary to make further conversions.

What are v2.1 reproduction scripts going to look like? Would they be pretty straightforward v2 -> v2.1 name changes in the reproduction script-generating code? Or completely different changes?

chengzhuzhang commented 4 days ago

@chengzhuzhang I'm assuming we'll need to create reproduction scripts fort the v2.1 runs too, right? That's by far the time-bottleneck on these PRs.

I created an automated process for generating v2 run scripts based on the original and reproduction piControl scripts. https://github.com/E3SM-Project/e3sm_data_docs/blob/main/utils/diff_patch is all those differences, and then https://github.com/E3SM-Project/e3sm_data_docs/blob/main/utils/patch_helper.py is necessary to make further conversions.

What are v2.1 reproduction scripts going to look like? Would they be pretty straightforward v2 -> v2.1 name changes in the reproduction script-generating code? Or completely different changes?

@forsyth2 , Chris ran the v2.1 simulations, I'm tagging @golaz to make sure this questions is addressed correctly.