PFS-JIRA

PFS-JIRA https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us

8.3.4

803005

13-09-2019

[PIPE1D-7] Investigate LINENAME content in output FITS file https://pfspipe.ipmu.jp/jira/browse/PIPE1D-7 DRP 1D pipeline <p>Satoshi TAKITA raised an issue concerning the content of LINENAME field inside the output FITS file.</p> <p><b>Satoshi TAKITA, on 02/14/19</b></p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>I cannot recognize the LINENAME. It says as b'((\xa8\xc6\xab\x7f'. What kind of names will be stored in this column?</pre> </div></div> PIPE1D-7

Investigate LINENAME content in output FITS file

Task Normal Done Done Pierre-Yves CHABAUD Pierre-Yves CHABAUD Tue, 19 Feb 2019 08:44:07 +0000 Fri, 11 Sep 2020 11:48:04 +0000 Fri, 11 Sep 2020 11:48:04 +0000 0 3 <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=takita" class="user-hover" rel="takita">takita</a> : the LINENAME field was not fed in your software version, so the content should not be interpreted. It's solved and will be part of the next release. Thank you for having raised it.</p> <p>Is it a blocking point and do you want a fix for your version ? or could you wait for next release (next week) ? (honestly I prefer last one <img class="emoticon" src="https://pfspipe.ipmu.jp/jira/images/icons/emoticons/wink.png" height="16" width="16" align="absmiddle" alt="" border="0"/>)</p> <p>OK, there's no need to rush. I wait the next release.</p> <p>Although the new pipeline was not yet working at NAOJ, I have checked the sample output files (pfs_datapack_sp8), and found another problem about 'LINENAME'. This field was defined as "TFORM = 15A", but this was not enough to describe the full line name, like '<span class="error">[OIII]</span> (double-foo)' (see attached image). However, I prefer using short name like 'oiii_4959' which was used in SDSS. Here is what I'm thinking about line names.<br/> linelist = <span class="error">['abs_h_alpha', 'abs_h_beta', 'abs_h_gamma', 'abs_h_delta', 'neiii_3869', 'h_delta', 'h_gamma', 'h_beta', 'oiii_5007', 'oiii_4959', 'hei_5876', 'oi_6300', 'nii_6548', 'h_alpha', 'nii_6584', 'sii_6717', 'sii_6731', 'ariii7135', 'oii_3729', 'oii_3726', 'civ_1550', 'civ_1548', 'ly_alpha', 'oiii_4363']</span><br/> Note that wavelengths were selected from SDSS ones.</p> <p>Ok, I get. Idealy it could be nice to change the line names in the dedicated calibration file, but I expect side effects. So, in short time, I will match simply our line names with SDSS ones at the end of processing ( i.e. writing product)</p> <p>In the latest pipeline, it looks that the lines are still like this:<br/> ['HalphaA' 'HbetaA' 'HgammaA' 'HdeltaA' 'NeIII' 'Hdelta' 'Hgamma' 'Hbeta' '<span class="error">[OIII]</span>(doublet-' '<span class="error">[OIII]</span>(doublet-' 'HeI5876' '<span class="error">[OI]</span>6301' '<span class="error">[NII]</span>(doublet-1' 'Halpha' '<span class="error">[NII]</span>(doublet-1' '<span class="error">[SII]</span>6716' '<span class="error">[SII]</span>6731' 'ArIII7136' '<span class="error">[OII]</span>3729' '<span class="error">[OII]</span>3726' 'CIV1550' 'CIV1548' 'LyAE' 'OIII4364']<br/> <br/> </p> Development Rank 0|u0006w: