Change verbs in command line interface to be more informative and user friendly.

[hdpriest-ui]

change from 'phase' verbs and file/directory names (2a_grass) to descriptive names instead.

see below: also we should evaluate the actual command verbs for their user-friendliness.

[hdpriest-ui]

@infotroph

will remap example names:

1a_single_site --> single_site
1b_statewide_woody -> statewide_woody
2a_grass --> statewide_grass
3_rowcrop --> statewide_rowcrop_management

this is drawn from my reading of the READMEs; unsure if we want to include the non-PFT information such as the inclusion of events in example 3, or the mixture of orchards and other non-woody sites in 2. Please let me know.

[dlebauer]

That works for me. A few thoughts

• Once we integrate downscaling we will want to differentiate the use of 'statewide' which can refer to both between 'statewide design point run' and 'statewide downscaling of the statewide design point run'
• It may be worth taking a step back and considering 'what exactly do we need to evaluate', i.e. a 1b, 2a, and 3 could potentially be replaced with single example that includes sites with different PFTs. And, once we update PFTs, the initial 'grass' and 'wood' PFTs will be less relevant.

[hdpriest-ui]

These names - and the examples themselves - are definitely still tied to the order in which capability was added or demonstrated to the workflows repo. Its natural that these are the examples we ended up with, but i think we can re-evaluate what each example is for both in code+data, as well as their names. (this might be what you were saying, if i'm understanding your point correctly)

I'd support, in addition to a re-name, an adjustment of the scope & purpose of each example as well. Naively, it seems like the progression in terms of complexity would look something like:

1. single site, single pft
2. multi site, single pft
3. multi site, mixed pft
4. multi site, mixed pft + events

[hdpriest-ui]

Commands:
  help                  Print this usage and help (no scripts run).
  prepare-example-1b    Run preparation steps using the 1b statewide woody crops example scripts.
  prepare-example-2a    Run preparation steps using the 2a grass example scripts.
  prepare-example-3     Run preparation steps using the 3 rowcrop management events example scripts.
  prepare               Run canonical preparation steps using workflow/ scripts.
  run-ensembles         Run step 04 (run model) using existing settings.xml and prepared inputs.

we may also wish to consider changing run-ensembles to run, as this would change:
./magic-ensemble run-ensembles
to
./magic-ensemble run

[infotroph]

I think @hdpriest-ui nailed it with the "sites, pfts, events" framing. Maybe...?

1a_single_site --> single_site
1b_statewide_woody -> multi_site_one_pft
2a_grass --> multi_pft [with a future extension to extract the mixed-pft and sensitivity notebooks into their own demos?]
3_rowcrop --> management_events

[hdpriest-ui]

This would make the overall changes:

1a_single_site --> single_site
1b_statewide_woody -> multi_site_one_pft
2a_grass --> multi_pft
3_rowcrop --> management_events
run-ensembles --> run

I will make these changes everywhere these names appear (in configs, scripts, etc)

However, I refuse to make the help text appear as:

Commands:
  help                  Print this usage and help (no scripts run).
  prepare-multi-site-example    Run preparation steps using the 1b statewide woody crops example scripts.
  prepare-multi-pft-example    Run preparation steps using the 2a grass example scripts.
  prepare-management-events-example     Run preparation steps using the 3 rowcrop management events example scripts.
  prepare               Run canonical preparation steps using workflow/ scripts.
  run         Run step 04 (run model) using existing settings.xml and prepared inputs.

Because that's the worst thing i've ever seen, so will go with something like:

Commands:
  help                   Print this usage and help (no scripts run).
  prepare            Run canonical preparation steps using workflow scripts.
  run                    Run the ensemble analysis using existing specified config and prepared run directory

  Demo Commands:
    prepare-multi-site-demo                         Run preparation steps using the 1b statewide woody crops example scripts.
    prepare-multi-pft-demo                           Run preparation steps using the 2a grass example scripts.
    prepare-management-events-demo     Run preparation steps using the 3 rowcrop management events example scripts.