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.

HyP3 v7.6.0

Changed

• Reduced throughput for hyp3-its-live to prevent Sentinel-2 processing from being rate limited (10,000 -> 2,000 vCPUs).

HyP3 v7.5.0

Added

• The SRG_GSLC_CPU job spec
• The SRG_GSLC_CPU job type to the hyp3-lavas and hyp3-lavas-test HyP3 deployments

Changed

• The hyp3-tibet-jpl deployment now uses the m6id[n] instance families and includes the ARIA_RAIDER job spec

HyP3 v7.4.0

Added

• The hyp3-lavas and hyp3-lavas-test enterprise HyP3 deployments.

HyP3 v7.3.0

This release adds support for access codes. If a user specifies an active access code when they apply for HyP3 access, they will be granted automatic approval without the need for a HyP3 operator to review their application.

If you operate a HyP3 deployment, you can create a new access code by adding an item to the AccessCodesTable DynamoDB table for your deployment, with any string for the access_code attribute and an ISO-formatted UTC timestamp for the start_date and end_date attributes, e.g. 2024-06-01T00:00:00+00:00 and 2024-06-02T00:00:00+00:00 for an access code that becomes active on June 1, 2024 and expires on June 2, 2024.

Added

• The PATCH /user endpoint now includes an optional access_code parameter and returns a 403 response if given an invalid or inactive access code.

Changed

• Turn off hyp3 ACCESS spend by zeroing the max VCPUs in the associated deployment.
• Reduce product lifetime in hyp3 ACCESS deployment to 14 days.