HyP3 v9.4.0

Changed

• The OPERA_DISP_TMS job type is now a fan-out/fan-in workflow.

Fixed

• Previously there was a bug in which fan-out job steps, defined using the map: for item in items syntax, would fail if items was an array of non-string values, because AWS Batch SubmitJob expects string parameters. This bug has been fixed by converting each value to a string before passing it to SubmitJob.

HyP3 v9.3.0

Added

• Added velocity option for the tile_type parameter of OPERA_DISP_TMS jobs
• Restored previously deleted hyp3-opera-disp-sandbox deployment
• Added validator to check that bounds provided do not exceed maximum size for SRG jobs

Removed

• Removed default bounds option for SRG jobs

HyP3 v9.2.0

Added

• Add mypy to static-analysis workflow
• OPERA_DISP_TMS job type is now available in EDC UAT deployment

Changed

• Upgrade to Python 3.13

Removed

• Remove hyp3-opera-disp-sandbox deployment

HyP3 v9.1.1

Changed

• The static-analysis Github Actions workflow now uses ruff rather than flake8 for linting.

HyP3 v9.1.0

Added

• Add a new https://hyp3-opera-disp-sandbox.asf.alaska.edu deployment with an OPERA_DISP_TMS job type for generating tilesets for the OPERA displacement tool.

HyP3 v9.0.1

Changed

• Upgrade to Amazon Linux 2023 AMI for Earthdata Cloud deployments

HyP3 v9.0.0

Changed

• All failed jobs now have a processing_times value of null.

Fixed

• Resolve a regression introduced by the previous release (v8.0.0) in which a processing step could report a negative processing time if the underlying AWS Batch job had a failed attempt that did not include a StartedAt field. Fixes #2485
• Upgrade from Flask v2.2.5 to v3.0.3. Fixes #2491
• Specify our custom JSON encoder by subclassing flask.json.provider.JSONProvider. See pallets/flask#4692

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.