[PIPE2D-1260] flux calibration vector is zero for medium resolution data Created: 19/Jul/23 Updated: 27/Jul/23 |
|
| Status: | Open |
| Project: | DRP 2-D Pipeline |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | Masayuki Tanaka | Assignee: | Masayuki Tanaka |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
The flux calibration task does not work for the medium band data. Here is an example. I do not know which part of the task failed but will dig into it.
|
| Comments |
| Comment by Masayuki Tanaka [ 27/Jul/23 ] |
|
The zero flux calibration vector was due to a stupid bug in my code, and it is actually non-zero. But, the flux-calibrated pfsSingle seems to show a discontiguity in the overall normalization between the b and m arms.
|
| Comment by Masayuki Tanaka [ 27/Jul/23 ] |
|
...and it is not clear the possible offset is due to flux calibration or something else. |
| Comment by price [ 27/Jul/23 ] |
|
The normalisation spectra for b and m come from different exposures (taken at very different times), so I think that's expected. |
| Comment by Masayuki Tanaka [ 27/Jul/23 ] |
|
So, the offset is due to the way (or when) the quartz spectra were taken? The offset is already there in pfsMerged. Note that the plotted are different objects from the plot above. |
| Comment by price [ 27/Jul/23 ] |
|
That's right. |
| Comment by rhl [ 27/Jul/23 ] |
|
We could/should use the brn data in conjunction with bmn to fix the normalisation of the m data. Do we need a separate ticket for that work? |
| Comment by Masayuki Tanaka [ 27/Jul/23 ] |
|
Yabe-kun told me that we took a set of bmn quartz data in this run. Perhaps new calibs from this run may solve the problem? |