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-831 DRP 2-D Pipeline <p>As discussed during last SPS hardware telecon, dcb2 and dcb cables are not completely identical.<br/> Basically, fiber bundles are labelled identically but LAM have shown that they don't necessary illuminate the same fibers on the slit.<br/> How do we handle this properly ? <br/> From the DRP pov, do we create new bundle label to capture dcb2 specificities ?<br/> (yellow2, blue2...etc)<br/> pfsConfig/pfsDesign would still be sufficient regardless the cable.<br/> <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=price" class="user-hover" rel="price">price</a> <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a> thoughts ?</p> PIPE2D-831

capture dcb2 fiber bundle to slithole conversion specificities.

Task Normal Won't Fix Won't Fix arnaud.lefur arnaud.lefur Wed, 5 May 2021 19:19:03 +0000 Mon, 3 Jul 2023 20:17:27 +0000 Mon, 3 Jul 2023 20:17:27 +0000 0 3 <p>The new labels idea sounds good to me. We just need to associate a <tt>pfsDesignId</tt> with a particular arrangement of fibers.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> self.add("blue", next(hexIt), "LAM blue cable", [32, 111, 223, 289, 418, 518, 620]) self.add("green", next(hexIt), "LAM green cable", [63, 192, 255, 401, 464, 525, 587]) self.add("orange", next(hexIt), "LAM orange cable", [12, 60, 110, 161, 210, 259, 341]) self.add("red1", next(hexIt), "LAM red #1 cable", [2]) self.add("red2", next(hexIt), "LAM red #2 cable", [3]) self.add("red3", next(hexIt), "LAM red #3 cable", [308]) self.add("red4", next(hexIt), "LAM red #4 cable", [339]) self.add("red5", next(hexIt), "LAM red #5 cable", [340]) self.add("red6", next(hexIt), "LAM red #6 cable", [342]) self.add("red7", next(hexIt), "LAM red #7 cable", [649]) self.add("red8", next(hexIt), "LAM red #8 cable", [650]) self.add("yellow", next(hexIt), "LAM yellow cable", [347, 400, 449, 466, 545, 593, 641]) </pre> </div></div> <p>dcb has 12 genuine bundles.<br/> <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=fmadec" class="user-hover" rel="fmadec">fmadec</a> how many "new bundle" would be required for dcb2 ?</p> <p>The red single fiber are identical as green and orange bundle</p> <p>so yellow and blue bundles have some difference between DC1 and DCB2</p> <p>see <a href="https://sumire.pbworks.com/w/file/fetch/144177297/DCB2_Mapping_Report_20210505.pdf" class="external-link" rel="nofollow">https://sumire.pbworks.com/w/file/fetch/144177297/DCB2_Mapping_Report_20210505.pdf</a></p> <p>during the last telecon, you propose to have the same bundle names but  according to switch cable is used the corresponding fiberIds change, right?</p> <p>so makeDummyCable be could also handle this by adding on option to select which DCB cable is used :</p> <p>for ex: makeDummyCable "yellow" dcb=dcb2 or smthg like that</p> <p>we also pointed out that there is a keyword that defines which DCB or source is used so we will know which DCB was used in anycase</p> <p> </p> <p>Thanks, so two additional bundles.<br/> Right, but I was thinking to handle that at the actor level, the user declare "yellow, blue, red1, red4, red8". which dcb2Actor convert to yellow2, blue2, red1, red4, red8.<br/> So dcb and dcb2 does not generate the same pfsDesignId.</p> <p>there are 12 genuine dcb bundles, +2 dcb2 bundles out of maximum 16 values with the current design.<br/> <b>But</b> , there are those non-dcb design which are also tracked there</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>self.add("engineering", next(hexIt), "Engineering", engineering) self.add("9mtp", next(hexIt), "Right science fibers", [ff for ff in science if ff &lt; 273]) self.add("12mtpS12", next(hexIt), "Left science fibers", [ff for ff in science if ff &gt; 273]) self.add("12mtpS34", next(hexIt), "Left science fibers without some", </pre> </div></div> <p>It was a nice workaround at that time, but I'm not sure that's the right way.<br/> I don't think "engineering" is actually relevant, since it's alway connected, different fiber...<br/> And about allFiberLamp, we could mimic what was done with SuNSS:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>if lightSource == 'sunss': designId = 0xdeadbeef </pre> </div></div> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a> opinions ?</p> <p>agree for engineering fiber, we should clarify that</p> <p>for allfiber we still need to define either 9mtp or 12mtpS12 or 12mtpS34 (we may even change those names since we know now all Slit have 600 fibers except one</p> <p> </p> <p>Right, and since we cannot declare per-gang lightSource, it would have to be :</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>sps declareLightSource sm1=afl9mtp sps declareLightSource sm1=afl12mtp </pre> </div></div> <p>I wonder about that (S12, S34), since it's actually a property of cable A not cable B.</p> <p>euh, right maybe for pfsDesign</p> <p>but we need a way to define correclty pfsConfig</p> <p>we need to define which fiber is illuminated so need to define that, but initially it was S12 and S34 because sm 1 and 2 was supposed to have 600 fibers while 3 and 4 597fibers</p> <p>we know now that FCA4 has 597 fibers (is installed on SM2)</p> <p> </p> Relates INSTRM-1233 Development Rank 0|02qpjd:00r20060i20018000i Reviewers arnaud.lefur Sprint 2DDRP-2021 A5 2DDRP-2021 A 6 2DDRP-2021 A 7 2DDRP-2021 A 8 Story Points 2.0