Register CFMIP4 preliminary data

[daianzhuo]

Hi @durack1 and @znichollscr

I will be uploading some data for the CFMIP4 collaboration and including some details below to hopefully help with the process.

The data will be registered with source_id ImperialCollege-HadISST1-1-0 and ImperialCollege-piClim-deltaSST-1-0, see PR #455. I have run the validation tool locally with the CVs pointed at my local instance and pass without issues.

---

ImperialCollege-piClim-deltaSST-1-0 includes 6 model output SST response patterns to abrupt 4xCO2 forcing that are necessary for the participating centres to perform the piClim-deltaSST experiments, which replaced amip-future4K in CMIP7. The file names are as follows:

• Dtos1x1_CESM2_abrupt-4xCO2_r1i1p1f1.nc
• Dtos1x1_CNRM-ESM2-1_abrupt-4xCO2_r1i1p1f2.nc
• Dtos1x1_CanESM5_abrupt-4xCO2_r1i1p2f1.nc
• Dtos1x1_GFDL-CM4_abrupt-4xCO2_r1i1p1f1.nc
• Dtos1x1_HadGEM3-GC31-LL_abrupt-4xCO2_r1i1p1f3.nc
• Dtos1x1_MIROC6_abrupt-4xCO2_r1i1p1f1.nc
• Dtos1x1_NorESM2-LM_abrupt-4xCO2_r1i1p1f1.nc

With the following global attrs:

'Conventions': 'CF-1.7',
'activity_id': 'input4MIPs',
'contact': 'foo.bar@imperial.ac.uk',
'creation_date': '2026-06-15T20:29:00Z',
'frequency': 'mon',
'source_version': '1.0',
'tracking_id': 'hdl:21.14100/7ddb687d-b416-4fa2-b66c-14d06d7d1651',
'variable_id': 'tos'

---

ImperialCollege-HadISST1-1-0 includes SST and SIC boundary conditions, both "diddled" and non-"diddled", with the following files:

• siconc_HadISST_187001-202512.nc
• siconcbcs_HadISST_187001-202512.nc
• tos_HadISST_187001-202512.nc
• tosbcs_HadISST_187001-202512.nc

With similar attrs:

'Conventions': 'CF-1.7',
'activity_id': 'input4MIPs',
'contact': 'foo.bar@imperial.ac.uk',
'creation_date': '2026-05-21T14:42:00Z',
'frequency': 'mon',
'history': 'Created 2026-05-21 14:42 UTC by process_hadisst.py from HadISST1',
'institution': 'Met Office Hadley Centre',
'mip_era': 'CMIP7',
'references': 'Rayner et al. (2003), doi:10.1029/2002JD002670; Taylor et al. (2000) PCMDI Report 60',
'source': 'UK Met Office Hadley Centre HadISST version 1.1',
'source_version': '1.0',
'title': 'HadISST1 AMIP boundary conditions',
'tracking_id': 'hdl:21.14100/0a0d463d-91af-4e65-a387-d43c6a2a0e3f',
'variable_id': 'siconcbcs'

[durack1]

@daianzhuo nice, glad to see that you've made considerable progress.

We have a bunch of materials that can be used to ascertain target filenames etc - https://input4mips-validation.readthedocs.io/en/latest/how-to-guides/, and the original CMIP6 guidance, which is a little simpler to follow at CMIP6_Forcing_Datasets_Summary, for the PCMDI-AMIP-1-1-10 data, the https://github.com/PCMDI/amipbcs repo should have some useful CMOR snippets.

The filename and directory structure formats will be the most informative to follow.

[daianzhuo]

Hi @durack1, thanks for your reply. I've followed the documentation here to register and validate the data. The data has been standardised already and validated against data that was put through amipBcs. Do I just need to prepare the upload with the file structures and naming conventions you've linked?

From what I understood the data shouldn't be uploaded until source_id is registered (i.e. merging the linked PR above)? Unless it's okay to upload it to the "incoming" directory without this step?

[znichollscr]

Do I just need to prepare the upload with the file structures and naming conventions you've linked?

Yes please

From what I understood the data shouldn't be uploaded until source_id is registered (i.e. merging the linked PR above)? Unless it's okay to upload it to the "incoming" directory without this step?

Please send me an email (zebedee.nicholls@climate-resource.com) and I'll send you a place to upload. The FTP server is, unfortunately, no longer something we can use (sorry, docs out of date)