asgs
asgs copied to clipboard
"new ASGS configuration" wizard for common scenarios
Script would use a configuration template, and ask for the following pieces of information:
- mesh to use (present numerical options, 1 through N) (possibly use a YAML mesh database that would eventually replace
config/mesh_defaults.sh) - operator "name"
- platform (auto detect default answer)
- instance name (provide default based on above answers)
- allocation name
- QOS level (and value)
- PPN (present reasonable default)
- num procs per run (present reasonable default)
- max total number of procs in use
- forcing (BACKGROUNDMET or TROPICALCYCLONE)
- forecast cycles (00, 06, 12, 18) if BACKGROUNDMET is selected
- storm number (if TROPICALCYCLONE)
- storm year (TROPICALCYCLONE)
- cold or hot start
- cold start date (if cold start)
- where to look for hot start files (if hot start)
- notification distribution list
Not sure how to automate selection of run scenerios in a simple script, but we may be able to determine a reasonable starting set that can be modified manually.
Other features:
- presents confirmation before writing (looks reasonable? check)
- saves as file name derived from instance name
- automatically runs
define config $filenameandsave profile - suggests to operator that they commit the config file to
masterand push
@wwlwpd I think you've implemented this as an SPA, is that right?
https://tools.adcirc.live/spa/models/ASGS/configure