New AerChemMIP SSP experiments

[martinjuckes]

Experiments identified in CV issue #873.

@wjcollins : can you tell me what the data requirements for these experiments are? Should it be the same as ssp370SST?

[wjcollins]

The ssp370-lowNTCFCH4 diagnostics are as for ssp370
The ssp370SST-lowNTCFCH4 diagnostics are as for ssp370SST

[martinjuckes]

@wjcollins : Thanks.

Is ssp370pdSST (CV #759) also the same as ssp370SST?

[durack1]

@martinjuckes @taylor13 the relevant linked issues are
WCRP-CMIP/CMIP6_CVs#873
WCRP-CMIP/CMIP6_CVs#867
WCRP-CMIP/CMIP6_CVs#760
WCRP-CMIP/CMIP6_CVs#759
WCRP-CMIP/CMIP6_CVs#739

[martinjuckes]

@durack1 : what is the relevance?

[durack1]

@martinjuckes each of the linked issues in the CMIP6_CVs listed above included discussions around the new (and revised) AerChemMIP experiments. After the 10th March 2020 WIP telecon these closed issues were reopened so the data request and ES-DOCs could re-sync. @charliepascoe has started this work and confirmed that ES-DOCs is now consistent for WCRP-CMIP/CMIP6_CVs#739, the other issues remain open.

If the data request now includes the histSST-noLu experiment, then we are no longer waiting on the data request to sync, and the CMIP6_CVs issue (WCRP-CMIP/CMIP6_CVs#739) can be closed.

[martinjuckes]

@durack1 : As I tried to explain at the telco, the data request requires information which is not in the CVs, If people want stuff added to the data request, they need to provide information specifying what they need to have added. The fact that you appear not to understand the process or the objectives makes this difficult.

I'm waiting for a response from Bill Collins to my question above. As far as I can tell, your comments have no relevance to this discussion.

[wjcollins]

Just spotted that there was a question for me here.
The experiment ssp370pdSST uses different SST forcing data from ssp370SST. In all other respects, including diagnostics, it is identical.

[martinjuckes]

@wjcollins : this is now fixed in 01.00.32

[durack1]

@martinjuckes there may have been some unclear messaging here, so I will attempt to clear up.

In the case that the new CMIP5 for example experiments have been defined, the starting point for the data request for new experiments was their CMIP6 direct counterparts, so for historical-cmip5 == historical for e.g. I note however that historical-cmip5 is labelled tier 2, (historical is tier 1) so if that automagically drops certain high (temporal) frequency data then so be it