HyP3 v8.0.0

Added

• A job step can now be applied to every item in a list using a new map: for <item> in <items> syntax. For example, given a job spec with a granules parameter, a step that includes a map: for granule in granules field is applied to each item in the granules list and can refer to Ref::granule within its command field.
• If a job contains a map step, the processing time value for that step (in the processing_times list in the job's API response) is a sub-list of processing times for the step's iterations, in the same order as the items in the input list.
• A new SRG_TIME_SERIES job type has been added to the hyp3-lavas and hyp3-lavas-test deployments. This workflow uses the new map syntax described above to produce a GSLC for each level-0 Sentinel-1 granule passed via the granules parameter and then produces a time series product from the GSLCs. See the HyP3 SRG plugin.
• The SRG_GSLC job type now includes parameter validation.

Changed

• Changes to custom compute environments:
  • Custom compute environments are now applied to individual job steps rather than to entire jobs. The compute_environment field is now provided at the step level rather than at the top level of the job spec.
  • If the value of the compute_environment field is Default, then the step uses the deployment's default compute environment. Otherwise, the value must be the name of a custom compute environment defined in job_spec/config/compute_environments.yml.
• Other changes to the job spec syntax:
  • The tasks field has been renamed to steps.
  • Job parameters no longer contain a top-level default field. The default field within each parameter's api_schema mapping is still supported.
  • Job specs no longer explicitly define a bucket_prefix parameter. Instead, bucket_prefix is automatically defined and can still be referenced as Ref::bucket_prefix within each step's command field.

HyP3 v7.12.0

Changed

• The hyp3-its-live deployment now uses a greater variety of r6id[n] instances.

HyP3 v7.11.0

Added

• The INSAR_ISCE_BURST job type is now available in the hyp3-avo, hyp3-bgc-engineering, hyp3-cargill, abd hyp3-carter deployments.
• The AUTORIFT job type is now available in the hyp3-bgc-engineering, hyp3-cargill, abd hyp3-carter deployments.

HyP3 v7.10.0

Added

• Added a new INSAR_ISCE_MULTI_BURST job type for running multi-burst InSAR. Currently, this job type is restricted to a special hyp3-multi-burst-sandbox deployment for HyP3 operators. However, this is an important step toward eventually making multi-burst InSAR available for general users.

Changed

• Job validator functions now accept two parameters: the job dictionary and the granule metadata.
• Granule metadata validation now supports reference and secondary job parameters in addition to the existing granules parameter.
• Burst InSAR validators now support multi-burst jobs.
• Replaced the step function's INSPECT_MEMORY_REQUIREMENTS step with a new SET_BATCH_OVERRIDES step, which calls a Lambda function to dynamically calculate Batch container overrides based on job type and parameters.

HyP3 v7.9.3

Fixed

• Added missing cloudformation:DeleteStack permission to cloudformation deployment role in ASF-deployment-ci-cf.yml .

HyP3 v7.9.2

Removed

• Deleted the hyp3-pdc deployment in preparation for archiving the hyp3-flood-monitoring project.

Fixed

• Copied cloudformation permissions from user to cloudformation deployment role in ASF-deployment-ci-cf.yml to address
  breaking AWS IAM change when deploying nested stacks via a cloudformation role.

HyP3 v7.9.1

Changed

• The SRG_GSLC job now takes in a --bounds argument that determines the extent of the DEM used in back projection.

HyP3 v7.9.0

Changed

• The ARIA_AUTORIFT.yml job spec now specifies the optimum number of OpenMP threads and uses a dedicated compute environment with r6id[n] spot instances.
• The AUTORIFT_ITS_LIVE.yml job spec now specifies the optimum number of OpenMP threads.
• The INSAR_ISCE.yml job spec now reserved 16 GB memory for running the DockerizedTopsApp task.
• The hyp3-a19-jpl-test, hyp3-a19-jpl, hyp3-tibet-jpl, and hyp3-nisar-jpl ARIA deployments now uses on-demand m6id[n] instances.
• The hyp3-its-live-test deployment now uses a greater variety of r6id[n] instances.

HyP3 v7.8.1

Fixed

• Upgraded to flask-cors v5.0.0 from v4.0.1. Resolves CVE-2024-6221.

HyP3 v7.8.0

Added

• Allow overriding certain AWS Batch compute environment parameters (including instance types and AMI) within a job spec.
• Allow job spec tasks to require GPU resources.

Changed

• The SRG_GSLC job type now runs within a GPU environment.
• Revert ARIA hyp3 deployments back to C-instance family - including the job-spec CLI parameter omp-num-threads to ensure multiple jobs fit on single instance.
• Deployments with INSAR_ISCE.yml job specs will now use a dedicated compute environment with on-demand instances instead of spot instances for INSAR_ISCE jobs.