Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: obs_decam
-
Labels:None
-
Team:SQuaRE
Description
As DECam data will be one of the precursor data sets used to assess the quality of LSST code, we need this module in LSST-controlled repositories.
Attachments
Issue Links
- blocks
-
- Done
-
- Done
- is blocked by
-
- Done
-
- Implemented
- relates to
-
- Done
- mentioned in
-
Page Loading...
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Assignee | Mario Juric [ mjuric ] |
| Assignee | Mario Juric [ mjuric ] |
| Component/s | obs_decam [ 12851 ] |
| Assignee | David Nidever [ nidever ] |
| Team | SQuaRE [ 10302 ] |
| Remote Link | This issue links to "Page (Confluence)" [ 13076 ] |
| Remote Link | This issue links to "Page (Confluence)" [ 13076 ] | This issue links to "Page (Confluence)" [ 13076 ] |
| Watchers | Hsin-Fang Chiang, Mario Juric [ Hsin-Fang Chiang, Mario Juric ] | Hsin-Fang Chiang, Mario Juric, Simon Krughoff [ Hsin-Fang Chiang, Mario Juric, Simon Krughoff ] |
Sounds to me that #3 is independent and not covered by this ticket, and can be removed from here. But I'm not completely sure what Mario Juric meant in the first place.
Hsin-Fang Chiang
added a comment - Sounds to me that #3 is independent and not covered by this ticket, and can be removed from here. But I'm not completely sure what Mario Juric meant in the first place. Isn't DECam ISR covered by DM-4191?
Yes, I added a related link. I am asking that the scope of this ticket be clarified so it is clear when the work in the ticket is completed. If this is actually meant to be an epic containing other work tickets rather than a story then that is also fine.
It seems that #2 and #3 are already covered by tickets and #1 is done.
Yes, currently we can do ISR to the extent as described in DM-4191. But I don't think we need a fully functional ISR for obs_decam to be included in Jenkins. The descriptions sound to me that it's happy enough to take data preprocessed by the Community Pipeline.
(p.s. I'm not defining what is "fully functional" either...)
Hsin-Fang Chiang
added a comment - Yes, currently we can do ISR to the extent as described in DM-4191 . But I don't think we need a fully functional ISR for obs_decam to be included in Jenkins. The descriptions sound to me that it's happy enough to take data preprocessed by the Community Pipeline.
(p.s. I'm not defining what is "fully functional" either...) Now that I re-read the original ticket description I see that it was saying that ISR would not be included to start with. Maybe we just close this ticket on the basis that the repo is now official (and tweak the description accordingly).
sounds good to me
| Summary | Include obs_decam into official LSST repositories, and make it user friendly | Include obs_decam into official LSST repositories |
| Description | As DECam data will be one of the precursor data sets used to assess the quality of LSST code, we need this module in LSST-controlled repositories, and we need to make sure it's easy to use on DECam data with ISR removed by the Community Pipeline. | As DECam data will be one of the precursor data sets used to assess the quality of LSST code, we need this module in LSST-controlled repositories. |
The repository is now part of the LSST github org.
| Resolution | Done [ 10000 ] | |
| Status | To Do [ 10001 ] | Done [ 10002 ] |
Can we split this ticket into multiple items (or else limit its scope if covered by existing tickets). I see these distinct items here:
1. Add obs_decam to LSST github
2. Add obs_decam to Jenkins
3. Add ISR to obs_decam
4. Make it easy to use.
#1 is done and #3 is being worked on. #4 is a bit vague.