Skip to content

Running ELM for NGEE Arctic Field Sites using OLMT

Jump to bottom
Verity Salmon edited this page Sep 30, 2022 · 28 revisions

Background

In order to be able to run ELM for the NGEE Arctic Field Sites you will need to complete ALL of the homework activities for the NGEE Arctic Modex workshop listed in the Setting up your Docker desktop wiki page.

When getting geared up to look at a suite of output variables, getting a feel for initial differences across sites, or just figuring out how changes to the model settings/ inputs/ parameters will broadly impact model output it can be extremely useful to do run a "quick" version of a simulation that only takes about 10 minutes to complete but still produces all the output variables. These output values will be somewhat reasonable but should not be considered fully trustworthy.

If you are wanting to do a more serious model run to generate robust model output for in depth analysis, you will need to to perform a "long" run that includes a more extensive spinup period and includes more years of post-spinup data.

Option 1: Quick Run (~10 mins per site)

  • To perform a quick run for a single site, you can copy and paste the following code in your terminal window
  • Note that this code currently specifies a quick run for the beo site (Utqiavgik)
docker run -t -i --hostname=docker --user modeluser -v elmdata:/inputdata -v elmoutput:/output fasstsimulation/elm-builds:elm_v2-for-ngee /scripts/OLMT_docker_example.sh --site_name=beo --ad_spinup_years=20 --final_spinup_years=30 --transient_years=5

This code is broken down by color below to show what each part is doing and some of the options you can edit
basic run code breakdown_ short

  • When ELM is performing a quick run, you will see code moving through your terminal window with a few stops and starts. When the run is complete the terminal window will say the following:
    image

  • If you want to do quick runs for a site other than beo (Utqiagvik), you need need to edit the above code to inlude one of the following:
    --site_name=council
    --site_name=kougarok
    --site_name=teller

Option 2: Long Run (~2+ hours per site)

docker run -t -i --hostname=docker --user modeluser -v elmdata:/inputdata -v elmoutput:/output fasstsimulation/elm-builds:elm_v2-for-ngee /scripts/OLMT_docker_example.sh --site_name=beo --ad_spinup_years=200 --final_spinup_years=600

This slightly modified version of the code is broken down by color below to show what each part is doing and highlight changes made here to make the run longer and output more robust.
basic run code breakdown_ LONG

  • When ELM is performing a long run, you will see code moving through your terminal window with a few stops and starts. Similar to the quick run above, when the run is complete the terminal window will say:
    image

What next?

Next you will want to look at model output from the short or long runs using Jupyter notebooks
INSERT URL HERE

Clone this wiki locally