...

The information that follows is an outline of the steps that were taken to develop the Linov-v3 input forcing data for SSP370, and SSP585 SSP component sets ("compsets") for E3SM version 3. These same steps may or may not work for previous or future versions of E3SM.  The instructions are accurate to the best of the author's knowledge. If errors are found in this document, please notify Jinbo Xie or add a comment to this page. A high-level overview of compset input forcing creation (from 2022, some information may be obsolete!) can be found in Creating SSP370 and SSP585 compsets for E3SM; the information outlined below is intended to supplement this workflow overview by providing greater detail and is specific to the Linoz-v3 input forcing specific to the historical, SSP370 and SSP585 compsets for E3SMv3. The example below is for SSP370, but the process is the same for SSP585 all other SSPs with the minimum change in several instances (the latest version of c20231207 includes Linoz file for components of SSP370 to SSP585 in several instancesHistorical, SSP119, SSP126, SSP245, SSP370, SSP434, SSP460, SSP534-over, and SSP585).

The output files are:

linv3_1849-2101_CMIP6_Hist_SSP370_10deg_58km_c20230430.nc
linv3_1849-2101_CMIP6_Hist_SSP585_10deg_58km_c20230430.nc

Creation of E3SM SSP370 input files for Linoz-v3

Linoz-v3 files (SSP370)

For SSP370, the Linoz-v3 forcing data must be produced before Linoz-v3 can be run on E3SMv3.

...

One additional namelist entry, linoz_data_path, defines the path to linoz_data_file.  Below are instructions on how to convert raw input4mips data files to Linoz-v3 input files for E3SM.  These instructions assume the user has access to IDL and Fortran compilers, and the workflow was invoked on Livermore Computing server of SYRAH.

linoz_data_file

For linoz_data_file, the UCI chemistry box model (we’ll denote this BOXMODEL) provided by Michael J Prather and Juno Hsu (Unlicensed) was used to process the raw input4mips files into the netcdf form usable by E3SMv3.

...