Rejecting topside TEC when suborbital TEC is negative
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 payload names no file or function, so start by searching the repository for the TEC correction code that handles topside TEC. Find where the topside profile is combined with the total TEC and where the suborbital TEC value is computed. Done means the code discards the topside TEC and uses total TEC alone when the topside exceeds the total, with a test covering that case. Issue #153 is also referenced but not described here.
Written by the indexing model from the issue text.
Description
There may be cases where the topside TEC profile exceeds the total TEC, which is physically inconsistent. In such cases, the TEC correction algorithm should reject the topside TEC and use the total TEC only.
Posting this issue here so that the ADT can keep track of it and address it down the line.
Also, a reminder to ourselves that #153 still needs to be addressed.
- Dominant language
- Python
- Stars
- 250
- Forks
- 92
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 16
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 isce-framework/isce3
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
isce-framework/isce3#353 ·
Maintainers usually reply within 1 day
-
Performance: per-pixel dynamic scheduling and unneeded atomics in RTC `_normalizeRtcArea` cost ~11% of GCOV geocode time at NISAR scalePossibly taken @s-sasaki-earthsea-wizard claimed this 77 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
isce-framework/isce3#341 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
isce-framework/isce3#290 · 1 comment · 3 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
isce-framework/isce3#255 ·
Maintainers usually reply within 1 day
-
GCOV/GSLC: geocoded `referenceTerrainHeight` is entirely NaN because a 1-D LUT is misdetected as 2-DPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 74/100
isce-framework/isce3#402 ·
Maintainers usually reply within 1 day
All issues in isce-framework/isce3
Similar issues
-
priority middle
Difficulty 1/5 Under an hour Newbie friendliness 62/100
KATO-Hiro/AtCoderClans#12940 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
huggingface/huggingface_hub#5283 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
bug example
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day