Repository navigation
HyP3 isce3 v0.3.0
Important
This release includes a major change to the hyp3-isce3 development environment! hyp3-isce3 now uses pixi to manage development environments.
Added
- Added a
--subset LON_MIN LAT_MIN LON_MAX LAT_MAXoption that streams cropped input RSLCs to a WGS84 bounding box before processing, so the InSAR workflow runs on a small radar-coordinate patch (minutes instead of hours for a full frame) and the GUNW output is bounded to that area of interest. - Added the
hyp3_isce3.crop_rslcmodule, which maps the AOI into each RSLC's radar grid with isce3geo2rdrand writes a cropped RSLC. The cropped product's identification times,boundingPolygon, geolocation grid, andprocessingInformationmetadata cubes are kept consistent with the crop so the resulting GUNW metadata reflects the AOI. - Added authentication function.
Changed
- Changed
referenceandsecondaryparameters forgranules. - hyp3-isce3 now uses pixi to manage development environments instead of conda/mamba. For more info, see #23.
- Environments, their dependencies, etc. are now all configured in the
tool.pixisections of thepyproject.toml - Pixi now writes a
pixi.lockfile. - The Dockerfile uses the pixi base image and
entrypoint.shhas been updated to use the pixi environment accordingly.
- Environments, their dependencies, etc. are now all configured in the
- hyp3-isce3 docker images are now multiarch, supporting linux-amd64 and linux-arm64. For more info, see #23.
- CI/CD pipelines that required an
environment.ymlhave been reimplemented to use pixi, includingbuild.yml,static-analysis.ymlandtest.yml.
Removed
- Environment/requirements files used by conda/mamba, such as
environment.ymlandrequirements-*.txt, in favor of pixi config and lock files.