Skip to content

Releases: ASFHyP3/hyp3

HyP3 v9.5.2

28 Feb 22:54
f27162a
Compare
Choose a tag to compare

Added

  • The ARIA_S1_GUNW job type is now available in the hyp3-edc-prod deployment.

Changed

  • OPERA-DIST-S1 runtime increases from 3 to 6 hours for experimentation.

Fixed

  • OPERA-DIST-S1 job spec had wrong CLI interface (e.g. --n-lookbacks should be --n_lookbacks).

HyP3 v9.5.1

26 Feb 01:11
ae6c66d
Compare
Choose a tag to compare

Added

  • OPERA_DIST_S1 job type to all ARIA Tibet and NISAR JPL deployments.
  • Stood up a new hyp3-tibet-jpl-test deployment for the ARIA Tibet project at JPL.

Changed

  • Increased throughput for hyp3-cargill (640 -> 1600 vCPUs) to support their processing needs.

Removed

  • Removed the hyp3-enterprise-test deployment.

HyP3 v9.5.0

25 Feb 23:22
b5677a7
Compare
Choose a tag to compare

Added

  • ARIA_S1_GUNW job type to hyp3-edc-uat deployment.
  • All jobs now have sns:Publish permissions for SNS topics in the same AWS region and account for the purpose of sending messages to a co-located deployment of https://github.com/ASFHyP3/ingest-adapter.

Changed

  • The reserved bucket_prefix job spec parameter has been renamed to job_id and can be referenced as Ref::job_id within each step's command field.
  • The job_id parameter of the ARIA_RAIDER job type has been renamed to gunw_job_id.
  • The AUTORIFT_ITS_LIVE job type now accepts Sentinel-1 burst products.
  • ruff now checks for incorrect docstrings (missing docstrings are still allowed), incomplete type annotations (missing annotations are still allowed), and opportunities to use pathlib.
  • Cloudformation parameter overrides are now provided via a .json file input to the deploy-hyp3 GitHub action.
  • The OriginAccessIdentityId used in EDC deployments has been renamed to BucketReadPricipals and now accepts multiple values.

HyP3 v9.4.0

04 Feb 22:19
77229f3
Compare
Choose a tag to compare

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

27 Jan 19:36
28430d2
Compare
Choose a tag to compare

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

08 Jan 23:05
5b5c355
Compare
Choose a tag to compare

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

18 Dec 00:06
6e66660
Compare
Choose a tag to compare

Changed

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

HyP3 v9.1.0

09 Dec 18:35
16b1b34
Compare
Choose a tag to compare

Added

HyP3 v9.0.1

20 Nov 19:35
b4a9205
Compare
Choose a tag to compare

Changed

  • Upgrade to Amazon Linux 2023 AMI for Earthdata Cloud deployments

HyP3 v9.0.0

13 Nov 23:05
865f4c6
Compare
Choose a tag to compare

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