isce-framework / isce-framework/dolphin
Figure out how to encapsulate `snaphu-py` crashes/failures to not stop the entire workflow
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 153
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
If we are unwrapping many interferograms, we may not want a single failed snaphu-pu job to stop everything.
One possible reason- if we attempt multiple variants of unwrapping (ordering from easier/faster/more approximate to longer-running), we'd like to use earlier successes even if later jobs fail.
(this might be a better question to raise in snaphu-py for possible segfault handling changes)
Contributor 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.
Research direction
Start by reviewing the workflow that unwraps many interferograms and the snaphu-py job boundary; the issue names no files or tests. Reproduce a failed job and determine whether failures can be isolated so earlier successful variants remain usable, or whether segfault handling belongs upstream in snaphu-py.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100