HyP3 v10.3.2

Changed

• Increased compute resources for the time series step of SRG_TIME_SERIES jobs.

HyP3 v10.3.1

Fixed

• We no longer globally ignore ruff's ANN401 rule, which flags function parameters annotated with Any.
• Replaced uses of Any with static type annotations where appropriate.

HyP3 v10.3.0

Added

• The HyP3 API will now report the API version in the OpenAPI specification and the Swagger UI for all deployments.

Changed

• render-cf.py now determines the version number to report in the API from the git history and tags using setuptools_scm.

Warning

In CI/CD pipelines, to dynamically calculate the version number you must now check out the full history and tags (no shallow clones). In GitHub Actions, this usually looks like specifying fetch-depth: 0 with actions/checkout. For pipelines where you do not care about an accurate version number, you can still use a shallow clone by setting the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_HYP3 environment variable, see: http://setuptools-scm.readthedocs.io/en/latest/overrides/.

HyP3 v10.2.1

Changed

• Adjusted memory requirements for OPERA_DISP_TMS jobs.

HyP3 v10.2.0

Added

• Added a new job type INSAR_ISCE_MULTI_BURST to process and mosaic multiple bursts to the hyp3-avo, azdwr-hyp3, hyp3-cargill, hyp3-bgc-engineering, and hyp3-carter deployments.
• Added the OPERA_DISP_TMS job type to the hyp3-edc-prod deployment.

Removed

• The measurement_type, start_date, and end_date API parameters for the OPERA_DISP_TMS job type have been removed
  in favor of hardcoded constants.

HyP3 v10.1.0

Added

• Added a new job type INSAR_ISCE_MULTI_BURST to HyP3 to process and mosaic multiple bursts.

HyP3 v10.0.1

Changed

• get_files now directly updates the files, logs, browse_images, thumbnail_images, and expiration_time fields in the Jobs table, rather than returning those values to be updated later by the JOB_SUCCEEDED or JOB_FAILED step. Resolves SRG_TIME_SERIES jobs with a large number of inputs exceeding the 256 KiB maximum output size for a Step Functions state.

HyP3 v10.0.0

Added

• The internal job spec syntax for cost_profiles now supports using an array as a cost parameter. The value used for the cost lookup will be the length of the array.

Changed

• The response structure of the /costs API endpoint has changed to support multiple cost parameters. See the costs_response schema in openapi-spec.yml.j2 for a detailed explanation.
• The internal job spec syntax for cost_profiles has changed to support multiple cost parameters. See INSAR_ISCE_MULTI_BURST.yml for an example of using multiple cost parameters.
• The EDC cost profile for the INSAR_ISCE_MULTI_BURST job type now implements variable credit costs based on the looks parameter and the number of scene pairs. Currently this does not affect any user-facing deployments.
• The API now returns sensible error messages if an INSAR_ISCE_MULTI_BURST job is given with less than 1 scene or more than 15 scenes for either reference or secondary, rather than the generic not valid under any of the given schemas error message.

HyP3 v9.5.4

Changed

• Combined start_execution_worker and start_execution_manager into one start_execution AWS Lambda function. Fixes #2518.

HyP3 v9.5.3

Fixed

• When the API returns an error for an INSAR_ISCE_BURST job because the requested scenes have different polarizations, the error message now always includes the requested polarizations in the same order as the requested scenes (previously, the order of the polarizations was not guaranteed). For example, passing two scenes with VV and HH polarizations, respectively, results in the error message: The requested scenes need to have the same polarization, got: VV, HH
• The API validation behavior for the INSAR_ISCE_MULTI_BURST job type is now more closely aligned with the CLI validation for the underlying HyP3 ISCE2 container. Currently, this only affects the hyp3-multi-burst-sandbox deployment.
• The requested scene names are now validated before DEM coverage for both INSAR_ISCE_BURST and INSAR_ISCE_MULTI_BURST.
• The lambda_logging.log_exceptions decorator (for logging unhandled exceptions in AWS Lambda functions) now returns the wrapped function's return value rather than always returning None.
• Ruff now enforces that all functions and methods must have type annotations.
• Updated the DIST-S1 entrypoint of the image and changed the job spec accordingly.