Update the INSAR_ISCE job definitions for new features from JPL
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The issue lists INSAR_ISCE_TEST.yml and INSAR_ISCE.yml as the job specs to update, with related work tracked in issues #1416, #1452, #1451, #1448, and #1447. Read those linked issues and the two job definitions first to understand which parameters are already covered; done means the requested options are represented in both specs as applicable. The thread has had no comment for over three years, so check for current project direction before starting.
Written by the indexing model from the issue text.
Description
JPL is working on a variety of updates to the ARIA-S1-GUNW products and would like to include the new option/parameters in the INSAR_ISCE_TEST and INSAR_ISCE job specs.
# Available in `INSAR_ISCE_TEST.yml`
- [ ] #1416
- [ ] #1452
- [ ] #1451
- [ ] #1448
- [ ] #1447
- [ ] provide an option to turn on and off dense offsets
- [ ] provide an option to specify output product pixel spacing (90m or 30m)
- [ ] option to add an unfiltered coherence layer to INSAR_ISCE output
# Available in `INSAR_ISCE.yml`
- [ ] #1416
- [ ] Option to specify a frame id for INSAR_ISCE jobs
- [ ] Option to enable Ionospheric correction in INSAR_ISCE output
- [ ] Option to enable Enhanced Spectral Diversity correction in INSAR_ISCE output
- [ ] Option to enable Solid Earth Tides correction in INSAR_ISCE output
- [ ] provide an option to turn on and off dense offsets
- [ ] provide an option to specify output product pixel spacing (90m or 30m)
- [ ] option to add an unfiltered coherence layer to INSAR_ISCE output
- Dominant language
- Python
- Stars
- 53
- Forks
- 13
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ASFHyP3/hyp3
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Most static tests fail when a date-like string is provided as an example value in a job spec YAMLOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Jira Bug
Difficulty 1/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
FinanceFlash/unvibecode#699 ·
Maintainers usually reply within 1 day
-
enhancement Website
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OWASP/OWASP-Hunting#96 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
micropython/micropython#19942 ·
Maintainers usually reply within 1 day
-
A rebuild posts "not part of this build" success to the commit's failed `nix-build` gate and effectsPossibly taken @Padraic-O-Mhuiris claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
`epoch.Integer` raises a raw OverflowError for integers too large to convert to a floatPossibly taken @arindam77 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pydantic/pydantic-extra-types#479 ·
Maintainers usually reply within 1 day