[PIPE2D-1291] Unable to retrieve calexp after reducing exposure Created: 31/Aug/23 Updated: 31/Aug/23 Resolved: 31/Aug/23 |
|
| 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 | ||
| Description |
|
Jared reports that on tiger, as he's able to successfully access the pfsArm and pfsMerged, he's not able to access the calexp even though the file exist, the butler.get fails with : NotFoundError:
File "src/PropertySet.cc", line 186, in const std::type_info& lsst::daf::base::PropertySet::typeOf(const string&) const
CALIB not found {0}
lsst::pex::exceptions::NotFoundError: 'CALIB not found'
rerun : /projects/HSC/PFS/Subaru/rerun/edr3-20230829 dataId: dict(arm='r', visit=98042, spectrograph=1) |
| Comments |
| Comment by rhl [ 31/Aug/23 ] |
|
Please provide a complete how-to-repeat |
| Comment by arnaud.lefur [ 31/Aug/23 ] |
|
Just do : and then : import lsst.daf.persistence as dafPersist
butler = dafPersist.Butler('/projects/HSC/PFS/Subaru/rerun/pipe2d-1291')
butler.get('pfsArm', arm='r', spectrograph=1, visit=98042) # OK
butler.get('calexp', arm='r', spectrograph=1, visit=98042) # FAILS
|
| Comment by price [ 31/Aug/23 ] |
|
This is due to the use of a dotted HIERARCH key name (PFS.DRP2D.CALIB) when recording the calib path ( Fix is in obs_pfs, and is currently being tested. |
| Comment by rhl [ 31/Aug/23 ] |
|
That requires me to regenerate my own rerun, which is more than is needed to replicate this problem. So butler = dafPersist.Butler('/projects/HSC/PFS/Subaru/rerun/edr3-20230829') butler.get('calexp', arm='r', spectrograph=1, visit=98042) # FAILS would have been the minimal how-to-repeat. The initial ticket didn't tell me if e.g. a CALIB argument was passed to the butler. But in this case, as so often, Paul's found the real problem |
| Comment by arnaud.lefur [ 31/Aug/23 ] |
|
Thanks. |
| Comment by price [ 31/Aug/23 ] |
|
Yes, I'm afraid so. |
| Comment by arnaud.lefur [ 31/Aug/23 ] |
|
No worries, I did reprocess the data and was able to access the calexp file. |
| Comment by price [ 31/Aug/23 ] |
|
Integration test passed. |