CESM_postprocessing icon indicating copy to clipboard operation
CESM_postprocessing copied to clipboard

need check_input_data like tool for CESM postprocessing

Open bertinia opened this issue 9 years ago • 2 comments

If a user wants to include their own input data sets to the diagnostics for testing and/or development, there currently isn't a clear process in place. One idea is as follows:

  1. Allow for multiple ':' separated paths in *_DIAGOBSPATH XML variable.
  2. The check_input_data module would aggregate files in the paths string and then create symlinks to all input data files in $PP_CASE_PATH/[comp]_data
  3. The *_DIAGOBSROOT single path setting would then be set to the $PP_CASE_PATH/[comp]_data before being passed to the NCL.

This has the advantage of not requiring SVN gatekeeper or common obs_data local dir permissions to work with user specified input files. The user can then later ask to have their datasets included in the WG obs_data repo for wider use.

bertinia avatar Aug 30 '16 20:08 bertinia

Here is the table with the most current list of required inputdata sets on NCAR glade:

CESM_pp_sets.pdf

bertinia avatar Sep 23 '16 18:09 bertinia

These are some notes from Cecile regarding required metadata that needs to included in any CAM or AMWG diag input data sets:

Required:

-data_title: Short title of the data -data_summary: Short paragraph about the data. -data_creator: your name and email -cesm_contact: Contact liaison or co-chair of AMWG -creation_date: Full date of dataset creation -update_date: Full date of most recent modification -history: Updates to changes made to the data. -data_script: script to generate data (will be available in the SVN repository ?)

Strongly recommended:

-data_description_url: A web-page with a description if available: This could be the climatedataguide webpage. -data_source_url: The web page where the raw data can be downloaded -data_reference: Full reference for the dataset if available -data_doi: If doi of data exists -climo_years: Year 1-year N of the climatological averaging period. -data_mods: Any special substantive (non resolution) modifications that were made to the input data set purely for the purpose of using it in CESM.

The more info the better. The script to reproduce data is important. It doesn't need to be in good shape. Just what you used is enough

A few examples of the metadata we added in recent files:

/glade/p/cesmdata/cseg/inputdata/atm/cam/topo/ fv_0.9x1.25-gmted2010_modis-cam_fv_smooth-intermediate_ncube3000-no_anisoSGH_c151029.nc

/glade/p/cesmdata/cseg/inputdata/atm/cam/solar/SolarForcingCMIP6piControl_c160921.nc

/glade/p/cesmdata/cseg/inputdata/atm/cam/ozone/oxid_ozone_WACCM_CCMI_REFC1_2000_cycle_3D_monthly_c20160531.nc

bertinia avatar Sep 30 '16 16:09 bertinia