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.

HyP3 v7.7.2

Change

• Renamed the SRG_GSLC_CPU job to SRG_GSLC
• Changed the SRG_GSLC job to use the hyp3-srg image, rather than hyp3-back-projection since the repository was renamed.

HyP3 v7.7.1

Removed

• The ESA_USERNAME and ESA_PASSWORD secrets have been removed from the job specs that no longer require them (those that use the hyp3-gamma, hyp3-isce2, hyp3-autorift, or hyp3-back-projection images).

HyP3 v7.7.0

Added

• ARIA_AUTORIFT.yml job spec for Solid Earth offset tracking in the ARIA JPL deployments

Changed

• Increased throughput for hyp3-a19-jpl (0 -> 4,000 vCPUs) to support continued processing of ARIA GUNW products.
• The hyp3-a19-jpl and hyp3-nisar-jpl deployments now use the m6id[n] instance families to reduce the high number of spot interruptions seen with wth c6id instance family.
• Increased available vCPUs for DAAC deployments.

Removed

• The INSAR_ISCE_TEST.yml job spec, which only differed from INSAR_ISCE.yml in support of different instance families, has been removed now that all ARIA JPL deployments are using the same instance families again.