b.e30_beta06_megan.B1850C_MTt4s.ne30.001

Open
#128 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
data

Research direction

Start with the CESM code base at /glade/work/fvitt/cesm/cesm3_0_beta06_megan/ and review the CMIP7 input data under /glade/campaign/acom/acom-da/cmip7/ne30/. Check the listed namelist changes and new volcanic emissions requirement; done means producing the b.e30_beta06_megan.B1850C_MTt4s.ne30.001 piControl run with the requested updated forcings.

Written by the indexing model from the issue text.

Description

Purpose of the run

Test a piControl simulation with updated CMIP7 emissions, updated MEGAN biogenic emissions, and updated volcanic forcing file to produce forcings for specified oxidants simulations.
Compset B1850C_MTt4s

Description of the run
  • Use /glade/work/fvitt/cesm/cesm3_0_beta06_megan/ code base for updates in MEGAN emissions
  • Update to CMIP7 emissions: /glade/campaign/acom/acom-da/cmip7/ne30/
    therefore extend to chemistry.
  • Update to use new volcanic emissions
Suffix in the casename

b.e30_beta06_megan.B1850C_MTt4s.ne30.001

Namelist modifications

@cecilehannay do we need these namelist changes?

phys_grid_ctem_nfreq=-6
phys_grid_ctem_zm_nbas=120
phys_grid_ctem_za_nlat=90

solar_irrad_data_file= '/glade/campaign/cesm/development/cross-wg/inputdata/SolarForcingCMIP7piControl_c20250103.nc'
bnd_topo = '/glade/campaign/cgd/amp/pel/topo/cesm3/ne30pg3_gmted2010_modis_bedmachine_nc3000_Laplace0050_noleak_20250325.nc'

micro_mg_dcs= 600.D-6
cldfrc_dp1 = 0.05
clubb_c8 = 4.6

Source modifications

SourceMods

Sandbox

Requested sandbox or tag

Contact info

Contact information

Any other relevant information

Enter relevant info

Dominant language
No language data
Stars
11
Forks
3
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NCAR/cesm_dev

All issues in NCAR/cesm_dev

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.