Add dry Held-Suarez run script

[LenkaNovak]

closes #759

• I have read and checked the items on the review checklist.

[szy21]

Is the low resolution intended? Otherwise the config file looks good to me. I also think it may be confusing for new users that you need to use coupler modules and functions to run held suarez, but that's probably a separate issue.

[LenkaNovak]

Is the low resolution intended? Otherwise the config file looks good to me. I also think it may be confusing for new users that you need to use coupler modules and functions to run held suarez, but that's probably a separate issue.

Thank you for the review. Yeah, we’ll want to contain all the hierarchy experiment setups in one file for each simulation and with the lowest possible resolution. This is should be sufficient to showcase the modularity of the code with minimal overhead, which is the intent of this paper. We will be showing the more realistic runs with the AMIP setup with data in your paper I guess. :) As for the path of the runscripts, we may eventually move all our hierarchy run scripts into one separate dir, but while we're adding all the cases iteratively, we decided to keep them all in the same dir as the amip run.

[szy21]

Thank you for the review. Yeah, we’ll want to contain all the hierarchy experiment setups in one file for each simulation and with the lowest possible resolution. This is should be sufficient to showcase the modularity of the code with minimal overhead, which is the intent of this paper. We will be showing the more realistic runs with the AMIP setup with data in your paper I guess. :) As for the path of the runscripts, we may eventually move all our hierarchy run scripts into one separate dir, but while we're adding all the cases iteratively, we decided to keep them all in the same dir as the amip run.

Sounds good! For the comment on coupler modules I meant it might be confusing for new users that we need to have e.g.

using ClimaCoupler.FieldExchanger:
    import_atmos_fields!, import_combined_surface_fields!, update_model_sims!, reinit_model_sims!, step_model_sims!
using ClimaCoupler.FluxCalculator:
    PartitionedStateFluxes,
    CombinedStateFluxes,
    combined_turbulent_fluxes!,
    MoninObukhovScheme,
    partitioned_turbulent_fluxes!,
    water_albedo_from_atmosphere!
using ClimaCoupler.Interfacer: CoupledSimulation, SurfaceStub, get_field, update_field!
using ClimaCoupler.Regridder
using ClimaCoupler.Regridder: update_surface_fractions!, combine_surfaces!, binary_mask

even for a simple case like dry Held Suarez. But we don't need to address it now. Are these necessary though?

[LenkaNovak]

Thank you for the review. Yeah, we’ll want to contain all the hierarchy experiment setups in one file for each simulation and with the lowest possible resolution. This is should be sufficient to showcase the modularity of the code with minimal overhead, which is the intent of this paper. We will be showing the more realistic runs with the AMIP setup with data in your paper I guess. :) As for the path of the runscripts, we may eventually move all our hierarchy run scripts into one separate dir, but while we're adding all the cases iteratively, we decided to keep them all in the same dir as the amip run.

Sounds good! For the comment on coupler modules I meant it might be confusing for new users that we need to have e.g.

using ClimaCoupler.FieldExchanger:
    import_atmos_fields!, import_combined_surface_fields!, update_model_sims!, reinit_model_sims!, step_model_sims!
using ClimaCoupler.FluxCalculator:
    PartitionedStateFluxes,
    CombinedStateFluxes,
    combined_turbulent_fluxes!,
    MoninObukhovScheme,
    partitioned_turbulent_fluxes!,
    water_albedo_from_atmosphere!
using ClimaCoupler.Interfacer: CoupledSimulation, SurfaceStub, get_field, update_field!
using ClimaCoupler.Regridder
using ClimaCoupler.Regridder: update_surface_fractions!, combine_surfaces!, binary_mask

even for a simple case like dry Held Suarez. But we don't need to address it now. Are these necessary though?

Ahh I see. Yes, we should prune these actually.

[juliasloan25]

What is this line of the command doing?