search

cedadev / snap

SNAP Coordinated Stratospheric Nudging Experiments
BSD 2-Clause "Simplified" License
0 stars 6 forks source link

Directory Structure for SNAP #1

Open charliepascoe opened 3 years ago

charliepascoe commented 3 years ago

I suggest we use the same pattern as the CMIP6 and CCMI-2022 archives e.g. /snap/data//////////

For ccmi-2022 we're using the date that data is uploaded to CEDA for the version number and we're asking users to create a version directory for this, so data uploaded on 26th March 2021 would have vv20210326

aph42 commented 3 years ago

I like that policy for the version number and am happy to adopt it.

Would <member_id> be a separate directory for each ensemble member? Given that each ensemble member is a relatively short integration (~45 days) and we will have many of them, I'm inclined at the moment to put all members into the same leaf directory, and use initialization date instead as a higher level division. Say:

/snap/data//////////

There's also part of me that wants to flatten this a bit and remove the grid_label level since I don't anticipate there being many variants (and the information will be in the file names). But if experience shows that it's better to include it, I can accept that.

leknifrg commented 3 years ago

If we use Charlotte's initial suggestion, there should be 24 different possible experiments IDs, corresponding to each of the 4 planned variations of nudging, 3 different SSW events, and 2 different initialization dates for each event.

Peter - we only have two initialization dates, so the net effect of your suggestion is 12 different experiment IDs and two different initializations dates, right?

I don't see a major advantage either way.