[PIPE2D-844] reduceExposure output detectorMap gets overriden Created: 21/May/21 Updated: 26/May/21 Resolved: 26/May/21 |
|
| Status: | Done |
| Project: | DRP 2-D Pipeline |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Normal |
| Reporter: | arnaud.lefur | Assignee: | price |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | 2DDRP-2021 A5 | ||||||||
| Reviewers: | arnaud.lefur | ||||||||
| Description |
|
reduceExposure produce an updated detectorMap but it hasn't been affected with a unique identifier, so it gets overridden with the next visit. |
| Comments |
| Comment by rhl [ 21/May/21 ] |
|
This is a little tricky. We currently treat DetectorMaps as calibrations, so we'd need to ingest these files. I don't think we want to do that, as these are perturbations on a certified DetectorMap. Maybe we need a new data type? |
| Comment by price [ 21/May/21 ] |
|
New butler dataset is what I was thinking. |
| Comment by price [ 26/May/21 ] |
|
arnaud.lefur's solution was effective to keep the pipeline from clobbering the detectorMap, but I've changed it to use a new butler dataset because that also allows us to read the detectorMap in using the butler. arnaud.lefur, could you please check that this works for you? |
| Comment by arnaud.lefur [ 26/May/21 ] |
|
fine with me, thanks. |
| Comment by price [ 26/May/21 ] |
|
Merged. |