Adding options (cice.setup -s) for amount of memory needed
#674
Comments
|
@phil-blain, that makes sense. This should not be difficult to do. Thanks. |
16 tasks
apcraig
added a commit
to apcraig/CICE
that referenced
this issue
Aug 10, 2022
Add set_env.memsmall, memmed, memlarge options To use, will require changes to the env machine files. Most machines will probably not use it. See CICE-Consortium#674.
16 tasks
apcraig
added a commit
that referenced
this issue
Aug 15, 2022
* Update/improve debug_blocks output, see #718. * Add ICE_MEMUSE cice.settings flag for batch memory use Add set_env.memsmall, memmed, memlarge options To use, will require changes to the env machine files. Most machines will probably not use it. See #674. * Add setup_machparams.csh to compute batch/launch machine parameters Update cice.batch.csh and cice.launch.csh to use setup_machparams.csh See #650 * Update subroutine diagnostic_abort which calls print_state Update ice_transport_remap and ice_transport_driver to call diagnostic_abort during some errors. See also #622 * Update miniconda install information See #547 * Code cleanup based on compile with -Wall Code cleanup based on -std f2003 and f2008 checks Add -stand f08 to cheyenne_intel debug flags Add -std f2008 to cheyenne_gnu debug flags Code consistent with Fortran 2003 except for use of contiguous in 1d evp code. * Remove all trailing blank space with script * Update the cheyenne env so qc testing works Add configuration/scripts/tests/qctest.yml file Update documentation * Update Icepack * Clean up some output * fix comments * update print_state output
dabail10
pushed a commit
to ESCOMP/CICE
that referenced
this issue
Oct 4, 2022
* Update/improve debug_blocks output, see CICE-Consortium#718. * Add ICE_MEMUSE cice.settings flag for batch memory use Add set_env.memsmall, memmed, memlarge options To use, will require changes to the env machine files. Most machines will probably not use it. See CICE-Consortium#674. * Add setup_machparams.csh to compute batch/launch machine parameters Update cice.batch.csh and cice.launch.csh to use setup_machparams.csh See CICE-Consortium#650 * Update subroutine diagnostic_abort which calls print_state Update ice_transport_remap and ice_transport_driver to call diagnostic_abort during some errors. See also CICE-Consortium#622 * Update miniconda install information See CICE-Consortium#547 * Code cleanup based on compile with -Wall Code cleanup based on -std f2003 and f2008 checks Add -stand f08 to cheyenne_intel debug flags Add -std f2008 to cheyenne_gnu debug flags Code consistent with Fortran 2003 except for use of contiguous in 1d evp code. * Remove all trailing blank space with script * Update the cheyenne env so qc testing works Add configuration/scripts/tests/qctest.yml file Update documentation * Update Icepack * Clean up some output * fix comments * update print_state output
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm porting CICE to our new machines and I'm running into a new situation. On some machines, nodes are shared (jobs do not have exclusive use of a node) and because of that we need to reserve some amount of memory in our job request, or else the job crashes.
I set 5 GB as a first try and most of the base_suite passed, but some tests need higher amounts of memory, up to 20 GB.
I could just ask for 20 GB in cice.batch.csh for all jobs on that machine, but it would be a smarter use of resources if we had options for the amount of memory needed, just as we have for the walltime (
-s short,medium,long). This way we could add these options to the base suite definition file, and it would only affect machines which choose to ask for a specific amount of memory in cice.batch.csh.I hope this is clear enough...
/cc @apcraig
The text was updated successfully, but these errors were encountered: