https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/PIPE2D-850 DRP 2-D Pipeline <p>Some datas at LAM have been made with the wrong PfsDesign (by declaring the wrong used fibres) : </p> <p> </p> <p>visit range =  26112..26135, 25696..25709, 25900..25904</p> <p> </p> <p>The PfsDesign hash code will be change by changing (addition lign) in HeaderFixes.py , in the obs_pfs repository.</p> PIPE2D-850

Update PFSDESIGN on some Lam Headers exposures

Bug Minor Won't Fix Won't Fix Romain Philippe Lhoussaine ben brahim Romain Philippe Lhoussaine ben brahim Fri, 4 Jun 2021 16:36:52 +0000 Thu, 1 Jul 2021 09:42:00 +0000 Thu, 1 Jul 2021 09:42:00 +0000 obs_pfs 0 6 <p>As noted in #pfs-princeton channel, this seems to be connected with problems in masterbiases, taken 25710-25724 not being assigned a PfsDesign as well</p> <p> </p> <p> </p> <p>I think PfsDesign is correct but one fiber is hidden, that should not prevent to do a detrend, right ?</p> <p>I personnaly use BIAS 391 and DARK 390</p> <p> </p> <p>see discussion  in #pfs-princeton, ingesting biases from 25710=25724 fails with <br/> ingestPfs.parse WARN: No value set for pfsDesignId; using default (0x0000000000000000)<br/> ingestPfs INFO: /tigress/HSC/PFS/LAM/raw/2021-05-31/sps/PFLA02571022.fits -<del>&lt;link&gt;</del>-&gt; /tigress/HSC/PFS/LAM/2021-05-31/PFLA025710r2.fits<br/> Traceback (most recent call last):<br/> File "/tigress/HSC/PFS/stack/20190925/stack/miniconda3-4.5.12-1172c30/Linux64/obs_pfs/w.2021.24/python/lsst/obs/pfs/ingest.py", line 653, in runFile<br/> self.ingestPfsConfig(pfsConfigDir, hduInfoList<span class="error">&#91;0&#93;</span>, args)<br/> File "/tigress/HSC/PFS/stack/20190925/stack/miniconda3-4.5.12-1172c30/Linux64/obs_pfs/w.2021.24/python/lsst/obs/pfs/ingest.py", line 555, in ingestPfsConfig<br/> (pfsDesignId,))<br/> RuntimeError: Unable to find PfsConfig or PfsDesign for pfsDesignId=0x0000000000000000</p> <p>Few of them are bad, I believe the light source was wrong</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>(conda-ics) alefur@PFS-WS2:/data/raw/2021-05-31/sps$ fitsheader PFLA02571*22.fits |grep 'W_PFD' W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none (conda-ics) alefur@PFS-WS2:/data/raw/2021-05-31/sps$ fitsheader PFLA02572*22.fits |grep 'W_PFD' W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 9999. / pfsDesign, from none W_PFDSGN= 1099528409104 / pfsDesign, from dcb W_PFDSGN= 1099528409104 / pfsDesign, from dcb W_PFDSGN= 1099528409104 / pfsDesign, from dcb W_PFDSGN= 1099528409104 / pfsDesign, from dcb W_PFDSGN= 1099528409104 / pfsDesign, from dcb </pre> </div></div> <p>The issue is not due to wrong PFSDESIGN.</p> Blocks PIPE2D-828 Development Rank 0|zzs4wj:zzzr Reviewers hassan Sprint 2DDRP-2021 A5 2DDRP-2021 A 6 Story Points 3.0