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

New Experiment 1pctCO2-bgc #15

Open
ChrisJones-MOHC opened this issue Feb 27, 2025 · 9 comments · May be fixed by #63
Open

New Experiment 1pctCO2-bgc #15

ChrisJones-MOHC opened this issue Feb 27, 2025 · 9 comments · May be fixed by #63
Labels
delta requires a change experiment

Comments

@ChrisJones-MOHC
Copy link

ChrisJones-MOHC commented Feb 27, 2025

Experiment ID

1pctCO2-bgc

Experiment Title

biogeochemically-coupled version of 1 percent per year increasing CO2 experiment

Description

1pctCO2-bgc is retained from CMIP6.

It is a simulation which branches from piControl with a 1% per year increase in CO2 concentration from pre-industrial levels, with the CO2 “biogeochemically-coupled”. This means that only the model’s carbon cycle components (both land and ocean) respond to the increase in CO2, whereas the model’s radiation code uses a constant, preindustrial concentration of CO2.

The 1pctCO2 DECK simulation is required for comparison. This experiment is designed to isolate carbon-concentration and carbon climate elements of the global carbon feedbacks. It will also enable calibration of climate emulators.

See Jones et al 2016: https://gmd.copernicus.org/articles/9/2853/2016/ , especially section 3.2.3

Example of use/analysis is Arora et al. 2020: https://bg.copernicus.org/articles/17/4173/2020/

MIP / Activity ID (registered)

C4MIP

MIP / Activity ID (unregistered)

No response

Parent Experiment

piControl

Custom Parent Experiment

No response

Sub-experiment

none

Priority Tier

1

Source type codes for required model components

AOGCM, BGC

Source type codes for additional allowed model components

AER, CHEM, ISM

Start Date

none

Branch Date

No response

(Minimum) Number of Years

150

Issue Type

experiment

Issue Kind

new

@ChrisJones-MOHC ChrisJones-MOHC added delta requires a change experiment labels Feb 27, 2025
@github-actions github-actions bot changed the title Add/Modify: Experiment: <biogeochemically-coupled version of 1 percent per year increasing CO2 experiment> New Experiment:1pctCO2-bgc Mar 12, 2025
@WCRP-CMIP WCRP-CMIP deleted a comment from github-actions bot Mar 12, 2025
Copy link

Validation failed:

1 issues found.

Validation Errors

Field Error Message Error Type
branch-date Value error, Invalid date format for value: same as 1pctCO2 DECK simulation value_error

@wolfiex
Copy link
Member

wolfiex commented Mar 12, 2025

@ChrisJones-MOHC can you correct the branch date in submission text above when you are ready.

The description of the format is given in the form https://github.com/WCRP-CMIP/CMIP7-CVs/issues/new?template=cmipld_experiment.yml

@matthew-mizielinski can you advise if different.

@taylor13
Copy link

I think this might be a problem with our form. For his experiment, Chris Jones has correctly stated the constraint on the Start Date and Branch Date, which are up to the data provider (within those constraints).

Also, I'm not sure what the difference is between "start date" and "branch date". Is that made clear somewhere?

@github-actions github-actions bot changed the title New Experiment:1pctCO2-bgc New Experiment 1pctCO2-bgc Mar 13, 2025
@matthew-mizielinski
Copy link
Contributor

matthew-mizielinski commented Mar 13, 2025

@wolfiex , I've removed the information from the start and end dates to follow how this was done in CMIP6. I think this is the simplest way to address this if you are going to automatically pull information from issues.

@taylor13, branch date is the point in the parent experiment from which the initial conditions are to be taken (e.g. for scenarios it should be end of the historical). While I'm very used to this (it had to go in file metadata last time around) it didn't appear in the CMIP6 experiment CV. Chat with @wolfiex about removing it if you see fit.

@taylor13
Copy link

For any simulation initialized from the control run, we cannot specify a "branch_date" and I agree, it shouldn't appear in the experiment CV. However, for anyone wanting to analyze CMIP experiments, the "branch_date" is an essential piece of information, which is why it must be recorded as a global attribute in files.

@wolfiex
Copy link
Member

wolfiex commented Mar 14, 2025

In which case I suggest that none needs to be entered and for it to no just be left blank.

@taylor13
Copy link

I don't think some MIP planners know what is meant by "parent experiment". They might think it refers to the experiment that the new experiment is patterned after. Perhaps more guidance should be provided on the form soliciting registration information. Otherwise, we'll have to iterate correcting obvious mistakes. In any case, someone knowledgeable will need to review the information gathered. Likely that will fall on the CV task team, so I think we should review the form before it is distributed.

Copy link

Validation failed:

1 issues found.

Validation Errors

Field Error Message Error Type
start-date Value error, Invalid date format for value: No response value_error

Copy link

New Pull Request: #63

@github-actions github-actions bot linked a pull request Mar 19, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
delta requires a change experiment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants