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-499 DRP 2-D Pipeline <p>The above members have the same contents but different names. Make them consistent. I propose renaming pfsArm.fiberId to pfsArm.fiberIds</p> PIPE2D-499

Make detectorMap.fiberIds and pfsArm.fiberId consistent

Story Normal Done Done price hassan Fri, 20 Dec 2019 18:00:48 +0000 Mon, 4 Jan 2021 20:23:11 +0000 Thu, 5 Mar 2020 21:19:11 +0000 0 2 <p>There are a lot of other places where <tt>fiberId</tt> is used for an array of fiber IDs (e.g., <a href="https://github.com/Subaru-PFS/datamodel/blob/master/python/pfs/datamodel/pfsConfig.py#L48" class="external-link" rel="nofollow"><tt>PfsConfig</tt></a>, <a href="https://github.com/Subaru-PFS/datamodel/blob/master/python/pfs/datamodel/target.py#L96" class="external-link" rel="nofollow"><tt>TargetObservations</tt></a>, <a href="https://github.com/Subaru-PFS/datamodel/blob/master/python/pfs/datamodel/pfsFiberTrace.py#L26" class="external-link" rel="nofollow"><tt>PfsFiberTrace</tt></a>). Since your concern is consistency, I'm going to change the <tt>DetectorMap.fiberIds</tt> to <tt>fiberId</tt>.</p> <p>It's almost a search-replace.</p> <p>Merged to master.</p> Relates PIPE2D-492 Development Rank 0|02qprx:0i Reviewers hassan Sprint 2DDRP-2021 A Story Points 1.0