Releases: ASFHyP3/hyp3
Releases · ASFHyP3/hyp3
HyP3-v0.8.10
Added
- AutoRIFT jobs now allow submission with Landsat 8 Collection 2 granules
Changed
- AutoRIFT jobs now only accept Sentinel-2 L1C granules, rather than any Sentinel-2 granules
Removed
- API responses are no longer validated against the OpenAPI schema.
GET /jobs
requests for jobs
with legacy parameter values (e.g. S2 L2A granules) will no longer return HTTP 500 errors.
HyP3-v0.8.9
Changed
- INSAR_GAMMA jobs now use the hyp3-gamma plugin to do processing
HyP3-v0.8.8
Changed
- RTC_GAMMA jobs now use the hyp3-gamma plugin to do processing
HyP3-v0.8.7
Added
- Autorift jobs now allow submission with Sentinel 2 granules
HyP3-v0.8.6
Added
- A new
include_scattering_area
paramter has been added forRTC_GAMMA
jobs, which includes a GeoTIFF of scattering area in the product package. This supports creation of composites of RTC images using Local Resolution Weighting per Small (2012) https://doi.org/10.1109/IGARSS.2012.6350465. - Cloudwatch request metrics are now enabled for the S3 content bucket
HyP3-v0.8.5
Changed
- Api Gateway access logs are now in JSON format for easier parsing by Cloudwatch Insights
- Api Gateway access logs now include
responseLatency
anduserAgent
fields. Unusedcaller
anduserId
fields are no longer included.
HyP3-v0.8.4
Changed
/
now redirects to/ui
HyP3-v0.8.3
Changed
- Increased compute to allow 200 concurrent instances.
HyP3-v0.8.2
Changed
- Refactored dynamodb interactions
dynamo.py
in the api code now manages all dynamodb interactions for the api- added tests for new dynamo module
- added paging for dynamodb query calls
HyP3-v0.8.1
Added
- Added Code of Conduct and Contributing Guidelines
Changed
MonthlyJobQuotaPerUser
stack parameter no longer has a default, and the value can now be set to zero.- Value is now set to
200
for ASF deployments. - Value is now set to
0
for the autoRIFT deployment.
- Value is now set to
POST /jobs
requests now allow up to 200 jobs per request, up from 25