check tiles-specstatus EFFTIME_SPEC=0.0 cases
- Dominant language
- Python
- Stars
- 42
- Forks
- 26
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 15
Description
Check cases where surveyops/trunk/ops/tiles-specstatus.ecsv has EFFTIME_SPEC=0.0, but exposure_tables/ has exposures that aren't flagged as ignore. Some of these might be bookkeeping propagation errors, but EFFTIME_SPEC=0.0 prevents them from being included in future productions. Or if they really are catastrophically bad exposures, they should be flagged as such in the exposure tables.
```
20201209 00066641 80194 cmx other - EFFTIME_SPEC=0.0
20201211 00066978 80254 cmx other - EFFTIME_SPEC=0.0
20201211 00066979 80254 cmx other - EFFTIME_SPEC=0.0
20201211 00066982 80254 cmx other - EFFTIME_SPEC=0.0
20201211 00067012 80293 cmx other - EFFTIME_SPEC=0.0
20201212 00067265 80254 cmx other - EFFTIME_SPEC=0.0
20201212 00067266 80254 cmx other - EFFTIME_SPEC=0.0
20210328 00082608 80724 sv1 other - EFFTIME_SPEC=0.0 <<< In Fuji/Guadalupe
20210430 00086750 81097 sv2 dark - EFFTIME_SPEC=0.0 <<< In Fuji/Guadalupe
20210505 00087359 81098 sv2 dark - EFFTIME_SPEC=0.0 <<< In Fuji/Guadalupe
20211206 00112669 42853 main backup - EFFTIME_SPEC=0.0
20211212 00113540 41853 main backup - EFFTIME_SPEC=0.0
20211212 00113541 41850 main backup - EFFTIME_SPEC=0.0
20211217 00114487 41710 main backup - EFFTIME_SPEC=0.0
20211217 00114493 42760 main backup - EFFTIME_SPEC=0.0
20211218 00114619 41371 main backup - EFFTIME_SPEC=0.0
20211218 00114623 41372 main backup - EFFTIME_SPEC=0.0
20211218 00114624 41379 main backup - EFFTIME_SPEC=0.0
20211218 00114625 41244 main backup - EFFTIME_SPEC=0.0
20220112 00118313 42997 main backup - EFFTIME_SPEC=0.0
20220112 00118322 43008 main backup - EFFTIME_SPEC=0.0
20220129 00120690 41532 main backup - EFFTIME_SPEC=0.0
20220221 00123283 25880 main bright - EFFTIME_SPEC=0.0
```
Tile 80724 was added to Iron by hand since it was a tile of interest to MWS that used it for a GD1 analysis with Fuji data.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the listed exposures in exposure_tables/ with EFFTIME_SPEC in surveyops/trunk/ops/tiles-specstatus.ecsv. Investigate whether each mismatch reflects a bookkeeping propagation error or a genuinely unusable exposure, noting tile 80724's manual inclusion in Iron. Done means the listed cases have consistent effective-time bookkeeping or appropriate ignore flags for unusable exposures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100