I have a two main questions about basic runs in Icepack (version 1.3.0). Ultimately I wish to perform a few Icepack simulations altering the model a little.
A successful run
=============
If I follow the user guide: 3.3. Testing Icepack — Icepack documentation
And perform e.g. a single test (in pwd0=/Users/simondriscoll/Documents/Icepack/)
./icepack.setup --test smoke --mach conda --env macos --testid t00
Then with
cd conda_macos_smoke_col_1x1.t00
./icepack.build
./icepack.submit
I receive from these two (ultimately):
./icepack.build: COMPILE SUCCESSFUL
...
ICEPACK COMPLETED SUCCESSFULLY
done ./icepack.run
respectfully. I.e. Icepack seems to run successfully. This is done in the directory, pwd1 = /Users/simondriscoll/Documents/Icepack/conda_macos_smoke_col_1x1.t00
This also affects another directory, on a totally different path. In pwd_dirs = /Users/simondriscoll/icepack-dirs/
(I think Icepack made this directory pwd_dirs when I ported it, not myself, but I am not certain)
This directory contains 4 sub-directories: 1) baseline/ 2) input/ 3) runs/ 4) cases/
And upon: ./icepack.build in pwd1 it creates: pwd2 = /Users/simondriscoll/icepack-dirs/runs/conda_macos_smoke_col_1x1.t00/
This contains only ls = "compile/ icepack*"
Upon ./icepack.submit more is added.
This means I have two directories, seemingly of the same test/run etc.
For pwd1 'ls' gives:
Macros.conda_macos README.case env.conda_macos* icepack.run* icepack.submit* icepack_in logs/ setup_run_dirs.csh* Makefile casescripts/ icepack.build* icepack.settings* icepack.test* icepack_in.sedbak makdep.c* test_output
For pwd2 'ls' gives:
compile/ history/ ice_diag.icefree ice_diag.slab icepack.runlog.211124-173141 icepack_in env.conda_macos* ice_diag.full_ITD ice_diag.land icepack* icepack.settings* restart/
Changing namelist
==============
If I wanted to do an ensemble of simulations, changing something in Icepack, I am informed that the best way to change things in Icepack (e.g. the forcing data, schemes, parameters etc.) is through the namelist icepack_in this avoids having to recompile the model.
There are two directories created from my test, both with two icepack_in's. pwd1, pwd2.
Can I clarify the /icepack.build is the compilation step? And secondly should I modify the icepack_in file in pwd1? Thus a workflow could be some sort of loop in a script of the form:
- "modify icepack_in in pwd1"
- ./icepack.submit (this overrides anything in pwd2 if this directory exists)
- therefore save output from pwd2"
(and repeat)
It appears that pwd1 contains a sort of "master" version, and the model output is in pwd2. Is my interpretation/understanding correct so far?
My second major question is if I wanted to do e.g. run Icepack with N-ICE data 3.2. Running Icepack — Icepack documentation by setting atm_data_type = NICE in the icepack_in namelist, and say I changed something simple like the number of ice thickness categories in a loop (3,4,5,6,7, say).
How should I submit this? Is this a "case" or a "suite" (or test suite? or "ensemble of single tests"). And what is meant by a case? For example. There seem to be many options for how I would wish to run Icepack, e.g. "-- test smoke" and I am not sure what they mean and which to choose.
What is the best way to submit cleanly an ensemble of same-forcing different parameter value (such as ice thickness categories)? Many thanks!
A successful run
=============
If I follow the user guide: 3.3. Testing Icepack — Icepack documentation
And perform e.g. a single test (in pwd0=/Users/simondriscoll/Documents/Icepack/)
./icepack.setup --test smoke --mach conda --env macos --testid t00
Then with
cd conda_macos_smoke_col_1x1.t00
./icepack.build
./icepack.submit
I receive from these two (ultimately):
./icepack.build: COMPILE SUCCESSFUL
...
ICEPACK COMPLETED SUCCESSFULLY
done ./icepack.run
respectfully. I.e. Icepack seems to run successfully. This is done in the directory, pwd1 = /Users/simondriscoll/Documents/Icepack/conda_macos_smoke_col_1x1.t00
This also affects another directory, on a totally different path. In pwd_dirs = /Users/simondriscoll/icepack-dirs/
(I think Icepack made this directory pwd_dirs when I ported it, not myself, but I am not certain)
This directory contains 4 sub-directories: 1) baseline/ 2) input/ 3) runs/ 4) cases/
And upon: ./icepack.build in pwd1 it creates: pwd2 = /Users/simondriscoll/icepack-dirs/runs/conda_macos_smoke_col_1x1.t00/
This contains only ls = "compile/ icepack*"
Upon ./icepack.submit more is added.
This means I have two directories, seemingly of the same test/run etc.
For pwd1 'ls' gives:
Macros.conda_macos README.case env.conda_macos* icepack.run* icepack.submit* icepack_in logs/ setup_run_dirs.csh* Makefile casescripts/ icepack.build* icepack.settings* icepack.test* icepack_in.sedbak makdep.c* test_output
For pwd2 'ls' gives:
compile/ history/ ice_diag.icefree ice_diag.slab icepack.runlog.211124-173141 icepack_in env.conda_macos* ice_diag.full_ITD ice_diag.land icepack* icepack.settings* restart/
Changing namelist
==============
If I wanted to do an ensemble of simulations, changing something in Icepack, I am informed that the best way to change things in Icepack (e.g. the forcing data, schemes, parameters etc.) is through the namelist icepack_in this avoids having to recompile the model.
There are two directories created from my test, both with two icepack_in's. pwd1, pwd2.
Can I clarify the /icepack.build is the compilation step? And secondly should I modify the icepack_in file in pwd1? Thus a workflow could be some sort of loop in a script of the form:
- "modify icepack_in in pwd1"
- ./icepack.submit (this overrides anything in pwd2 if this directory exists)
- therefore save output from pwd2"
(and repeat)
It appears that pwd1 contains a sort of "master" version, and the model output is in pwd2. Is my interpretation/understanding correct so far?
My second major question is if I wanted to do e.g. run Icepack with N-ICE data 3.2. Running Icepack — Icepack documentation by setting atm_data_type = NICE in the icepack_in namelist, and say I changed something simple like the number of ice thickness categories in a loop (3,4,5,6,7, say).
How should I submit this? Is this a "case" or a "suite" (or test suite? or "ensemble of single tests"). And what is meant by a case? For example. There seem to be many options for how I would wish to run Icepack, e.g. "-- test smoke" and I am not sure what they mean and which to choose.
What is the best way to submit cleanly an ensemble of same-forcing different parameter value (such as ice thickness categories)? Many thanks!