2025‐02‐12

Feb 12, 2025

Agenda:

1. Announcements
2. Observational Datasets

Notes:

• Want concrete plan for storing data

• Q: do we want a top-level CUPiD/ directory in inputdata/ in case users want to pull down all of the CUPiD datasets?

  • use case: an individual downloads some CESM output to their own university cluster, and wants to run CUPiD on it

    • How do they know what files to pull out of inputdata?
    • Can we write a script that does an svn checkout of each component's analysis_datasets directory?
    • Want to touch base with Jim

• Q: Can we standardize some file formatting? E.g. "netCDF with useful metadata and date in the file name"

  • Do some groups need binary files? Can they include date stamps still?

  • Some rule before copying to inputdata?

  • TODO: future meeting to discuss minimum requirements for file name and contents

    • Dates covered by dataset included in filename (for climatologies, still indicate years used to create it)
      • Is a climatology refered to as _climo or _climatology?
    • netCDF file format
    • metadata that describes process of generating dataset (scripts used should be publicly available)

• CESM Forum related to datasets? Or should those questions go to github (either tagging person who created the notebook using the dataset or the person who created the dataset itself)

• Observational directory for CAS: select subset of [mostly monthly] variables

  • Component data is controlled by components, how can we help components manage their data?

  • Common atmospheric variables are stored, some reanalysis (ERA5 currently the go-to)

    • How can this be used by CUPiD community? May depend on what atmosphere group thinks of as key metrics

  • Should each component have a point-person who knows what data is commonly used? Or would that be too chaotic?

    • More tasks for the community liaisons?

  • Is this really broader than CUPiD? Keeping it CUPiD-specific would be easier to manage

    • Can always move data into the CUPiD directory structure of inputdata when CUPiD needs it

• Next steps

  • Update CUPiD to pass /glade/campaign/cesm/development/cross-wg/diagnostic_framework/CUPiD_obs_data to all notebooks (can append subdirectories there)
  • Talk to Jim about inputdata
  • Talk to liaisons about directory structure
  • Make sure PR template points to right place!