Support multi Vs30 in calcs

For calculations only, not web services.

Expected behavior:

• If the config.hazard.vs30s array is empty, sites will be built and run using defaults and data in the supplied sites file.
• If not empty, code will loop over each value and site vs30 will always be set to that value; any vs30 in a site file will be ignored
• If not empty, hazard and disagg results will be nested in parent directories by vs30 value, e.g. vs30-760.

n.b. disagg-iml with vs30 dependent IMLs will only use the first value in config.hazard.vs30s; should probably have program throw exception or issue warning if multiple vs30s present

added Enhancement Hazard-Disagg labels

changed the description

mentioned in issue nshmp-lib#138 (closed)

mentioned in issue nshmp-lib#140 (closed)

nshmp-haz needs to pass in the vs30 when the sites are initialized (inside a new site condition loop), or override the site default vs30. Currently nshmp-lib is not using any config parameters to override the default of 760. See nshmp-lib#140 (closed)

changed the description

Current behavior (as of !598 (merged)) results in one (incremented) hazout directory with a vs30-#### subfolder for each vs30 specified in the hazard.vs30s array (i.e. hazout/vs30-#1, hazout-1/vs30-#2, ...) and the calc-config.json and HazardCalc.log files are placed into the last hazout-# folder. If no vs30 values are specified (empty array), no vs30 subdirectory is used. Currently HazardExport.createOutputDir() doesn't want to clobber existing directories and increments hazout for every vs30 loop.

• Omit the vs30-#### subfolder if only a single vs30 is specified? (yes?)
  • pass in the single vs30 value to readSites() and pass in OptionalDouble.empty() to calc()
• Reuse the hazout directory created for the first vs30?
  • this may require passing the hazout output directory from the first vs30 into calc() -> HazardExport.create() -> ...createOutputDir() and allowing reuse of an existing folder
  • alternatively, clean up the multiple folders in the AWS web app and leave the incremented hazout folders for local runs.

added Unplanned label

Directory creation should not be left to HazardExport.
Reopening nshmp-lib#140 (closed)

This issue is highlighting some unnecessary complexity in HazardCalc. The calculation of hazard is already multithreaded, but calculation and result writing are both wrapped up in Callable task classes and handed to an executor but with no real purpose as the code blocks until all sites have been calculated.

added 2023 label

Cleaned up callables in HazardCalc

changed milestone to %NSHM Hazard Tool Launch - 2

Resolved in !600 (merged)

closed