<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:53:12 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[FIBERALLOC-38] Run ets_fiber_assigner iteratively to avoid trajectory collisions</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/FIBERALLOC-38</link>
                <project id="10500" key="FIBERALLOC">Target to fiber allocation and configuration</project>
                    <description>&lt;p&gt;Currently the ets_fiber_assigner only avoids endpoint collisions of cobra tips with other tips or elbows. By running a provisional solution through the the collision simulator from ics_cobraOps, we can detect trajectory collisions as well. With this information, we can add constraints that disallow simultaneous observation of the problematic paits of targets and re-run the fiber assignment step.&lt;/p&gt;

&lt;p&gt;There are a few caveats to this approach that need to be kept in mind:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;we do not know how many iterations will be needed to arrive at a configuration that has no more trajectory collisions. Depending on the setup in question, there may be quite many.&lt;/li&gt;
	&lt;li&gt;the collision simulator only simulates a single realization of the Cobra movements (as far as I know). Given the stochastic nature of the movements, this does not exclude trajectory collisions when repeating the fiber movements on the real telescope. This can most likely be addressed by adding some sort of safety margin, but this needs more discussion.&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="15108">FIBERALLOC-38</key>
            <summary>Run ets_fiber_assigner iteratively to avoid trajectory collisions</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="10100" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="No further work should be done on this.">Won&apos;t Fix</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="chyan">chyan</assignee>
                                    <reporter username="Martin.Reinecke">Martin Reinecke</reporter>
                        <labels>
                            <label>EngRun</label>
                    </labels>
                <created>Thu, 17 Dec 2020 10:39:03 +0000</created>
                <updated>Sun, 19 Jun 2022 10:53:52 +0000</updated>
                            <resolved>Sun, 19 Jun 2022 10:53:52 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                <comments>
                            <comment id="18181" author="martin.reinecke" created="Thu, 17 Dec 2020 11:01:33 +0000"  >&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;A first implementation is available on the branch tickets/&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/FIBERALLOC-38&quot; title=&quot;Run ets_fiber_assigner iteratively to avoid trajectory collisions&quot; class=&quot;issue-link&quot; data-issue-key=&quot;FIBERALLOC-38&quot;&gt;&lt;del&gt;FIBERALLOC-38&lt;/del&gt;&lt;/a&gt;. It successfully eliminates the trajectory collisions in demo_netflow.py.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=mxhf&quot; class=&quot;user-hover&quot; rel=&quot;mxhf&quot;&gt;mxhf&lt;/a&gt; , it would be great if you could have a look!&lt;/p&gt;

&lt;p&gt;At the moment, I&apos;m re-running the entire assignment if trajectory collisions are detected. Shortcuts may be possible, but have the potential to introduce further complications. My hope is that, at least once we switch to radial moves, trajectory collisions will be extremely rare, so that we might be able to afford to do the full recomputation.&lt;/p&gt;</comment>
                            <comment id="18183" author="mxhf" created="Thu, 17 Dec 2020 11:53:28 +0000"  >&lt;p&gt;just checked it out ....&lt;/p&gt;

&lt;p&gt;Works well. Though with the new XML I do get an error in the simulator.&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Optimal solution found (tolerance 1.00e-04)&lt;/p&gt;

&lt;p&gt;Best objective 8.190310002886e+11, best bound 8.190310002886e+11, gap 0.0000%&lt;/p&gt;

&lt;p&gt;Checking for trajectory collisions&lt;/p&gt;

&lt;p&gt;/Users/mxhf/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/CobraGroup.py:186: RuntimeWarning: invalid value encountered in true_divide&lt;/p&gt;

&lt;p&gt;/Users/mxhf/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/CobraGroup.py:186: RuntimeWarning: invalid value encountered in arccos&lt;/p&gt;

&lt;p&gt;/Users/mxhf/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/CobraGroup.py:314: RuntimeWarning: divide by zero encountered in true_divide&lt;/p&gt;

&lt;p&gt;/Users/mxhf/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/CobraGroup.py:314: RuntimeWarning: invalid value encountered in true_divide&lt;/p&gt;

&lt;p&gt;/Users/mxhf/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/CobraGroup.py:314: RuntimeWarning: invalid value encountered in arccos&lt;/p&gt;

&lt;p&gt;/Users/mxhf/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/CobraGroup.py:315: RuntimeWarning: invalid value encountered in true_divide&lt;/p&gt;

&lt;p&gt;/Users/mxhf/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/CobraGroup.py:315: RuntimeWarning: invalid value encountered in arccos&lt;/p&gt;

&lt;p&gt;---------------------------------------------------------------------------&lt;/p&gt;

&lt;p&gt;ValueError&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; Traceback (most recent call last)&lt;/p&gt;

&lt;p&gt;~/ownCloudRZG/work/MPE/pfs/src/ets_fiberalloc/demo_netflow_ASIAA.py in &amp;lt;module&amp;gt;&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;139&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;140&lt;/b&gt; &#160; &#160; &#160; &#160; simulator = CollisionSimulator(bench, TargetGroup(selectedTargets, ids))&lt;/p&gt;

&lt;p&gt;--&amp;gt; 141 &#160; &#160; &#160; &#160; simulator.run()&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;142&lt;/b&gt; &#160; &#160; &#160; &#160; if np.any(simulator.endPointCollisions):&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;143&lt;/b&gt; &#160; &#160; &#160; &#160; &#160; &#160; print(&quot;ERROR: detected end point collision, which should be impossible&quot;)&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;~/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/CollisionSimulator.py in run(self, solveCollisions)&lt;/p&gt;

&lt;p&gt;&#160;&#160; &#160; &lt;b&gt;96&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&#160;&#160; &#160; &lt;b&gt;97&lt;/b&gt; &#160; &#160; &#160; &#160; # Calculate the cobra trajectories&lt;/p&gt;

&lt;p&gt;---&amp;gt; 98 &#160; &#160; &#160; &#160; self.calculateTrajectories()&lt;/p&gt;

&lt;p&gt;&#160;&#160; &#160; &lt;b&gt;99&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;100&lt;/b&gt; &#160; &#160; &#160; &#160; # Detect cobra collisions during the trajectory&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;~/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/CollisionSimulator.py in calculateTrajectories(self)&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;267&lt;/b&gt; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; finalFiberPositions=self.finalFiberPositions,&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;268&lt;/b&gt; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; movementDirections=self.movementDirections,&lt;/p&gt;

&lt;p&gt;--&amp;gt; 269 &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; movementStrategies=self.movementStrategies)&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;270&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;271&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;~/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/TrajectoryGroup.py in _&lt;em&gt;init&lt;/em&gt;_(self, nSteps, stepWidth, bench, finalFiberPositions, movementDirections, movementStrategies)&lt;/p&gt;

&lt;p&gt;&#160;&#160; &#160; &lt;b&gt;72&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&#160;&#160; &#160; &lt;b&gt;73&lt;/b&gt; &#160; &#160; &#160; &#160; # Calculate the cobra trajectories&lt;/p&gt;

&lt;p&gt;---&amp;gt; 74 &#160; &#160; &#160; &#160; self.calculateCobraTrajectories()&lt;/p&gt;

&lt;p&gt;&#160;&#160; &#160; &lt;b&gt;75&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&#160;&#160; &#160; &lt;b&gt;76&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;~/.pyenv/versions/anaconda3-5.0.1/lib/python3.6/site-packages/ics.cobraOps-0.0.0-py3.6.egg/ics/cobraOps/TrajectoryGroup.py in calculateCobraTrajectories(self)&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;138&lt;/b&gt; &#160; &#160; &#160; &#160; &#160; &#160; initOffset = np.pi + startPhi&lt;span class=&quot;error&quot;&gt;&amp;#91;c&amp;#93;&lt;/span&gt; if posPhiMovement&lt;span class=&quot;error&quot;&gt;&amp;#91;c&amp;#93;&lt;/span&gt; else np.abs(startPhi&lt;span class=&quot;error&quot;&gt;&amp;#91;c&amp;#93;&lt;/span&gt;)&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;139&lt;/b&gt; &#160; &#160; &#160; &#160; &#160; &#160; stepLimits = np.interp([initOffset, initOffset + np.abs(deltaPhi&lt;span class=&quot;error&quot;&gt;&amp;#91;c&amp;#93;&lt;/span&gt;)], phiOffsets, phiSteps)&lt;/p&gt;

&lt;p&gt;--&amp;gt; 140 &#160; &#160; &#160; &#160; &#160; &#160; stepMoves = np.concatenate((np.arange(stepLimits&lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt;, stepLimits&lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt;, self.stepWidth), [stepLimits&lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt;]))&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;141&lt;/b&gt; &#160; &#160; &#160; &#160; &#160; &#160; phiMoves = np.interp(stepMoves, phiSteps, phiOffsets)&lt;/p&gt;

&lt;p&gt;&#160; &#160; &lt;b&gt;142&lt;/b&gt; &#160; &#160; &#160; &#160; &#160; &#160; phiMoves = phiMoves - np.pi if posPhiMovement&lt;span class=&quot;error&quot;&gt;&amp;#91;c&amp;#93;&lt;/span&gt; else -phiMoves&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;ValueError: arange: cannot compute length&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="18203" author="jgracia" created="Wed, 23 Dec 2020 15:08:04 +0000"  >&lt;p&gt;Hi, I updated the cobraOps master branch and now it should work with the new XML files.&lt;/p&gt;

&lt;p&gt;Use this demo as an example:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/Subaru-PFS/ics_cobraOps/blob/master/python/ics/demos/demo2.py&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/Subaru-PFS/ics_cobraOps/blob/master/python/ics/demos/demo2.py&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Note that now some cobras have problems, so they are not moved and remain in the home position in simulation. You can use bench.cobras.hasProblem to get the cobras with problems.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Another thing is that I constrain the cobras phi angle to be between -pi and 0. Otherwise the (x,y) --&amp;gt; (tht, phi) calculation is degenerate and it requires a more clever way to calculate it. cobraCharmer can handle these situations, but I didn&apos;t implement it yet in the simulator code, so I force the phi angle to be between -pi and 0.&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;I hope it now works!&lt;/p&gt;</comment>
                            <comment id="18204" author="jgracia" created="Wed, 23 Dec 2020 15:11:11 +0000"  >&lt;p&gt;&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;https://pfspipe.ipmu.jp/jira/secure/attachment/13250/13250_Figure.png&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;I forgot to add that some cobras have very long link lengths. I guess it&apos;s a measure problem, but it creates a lot of trajectory collisions.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;And finally, I didn&apos;t implement yet the radial moves, so the simulator will predict more collisions than with the radial move.&lt;/p&gt;</comment>
                            <comment id="18300" author="mxhf" created="Sun, 27 Dec 2020 14:11:53 +0000"  >&lt;p&gt;Thank you very much for fixing this Javier &amp;amp; Martin!&#160;&lt;/p&gt;

&lt;p&gt;@Javier: demo2 works on my machine, only I noticed a new dependency on&#160;ics_cobraCharmer.&lt;/p&gt;

&lt;p&gt;For this ticket:&lt;/p&gt;

&lt;p&gt;I just committed to &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/FIBERALLOC-38&quot; title=&quot;Run ets_fiber_assigner iteratively to avoid trajectory collisions&quot; class=&quot;issue-link&quot; data-issue-key=&quot;FIBERALLOC-38&quot;&gt;&lt;del&gt;FIBERALLOC-38&lt;/del&gt;&lt;/a&gt;: &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Added netflow_asiaa.py, which is slightly modified version of demo_netflow.py for the PFI testing use case.&lt;/li&gt;
	&lt;li&gt;Added target_generator.py which currently implements a homogenuous target distribution only.&lt;/li&gt;
	&lt;li&gt;Modified netflow.py to also accept target tables in the astropy.table ecsv format.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Please check the attached allocations file as first version for ASIAA. It was generated with the following commands.&lt;/p&gt;

&lt;p&gt;&amp;gt; python target_generator.py --plot -o data/test_sci.dat -r 100000&lt;br/&gt;
&amp;gt; python target_generator.py --plot -o data/test_sky.dat -r 1000&lt;br/&gt;
&amp;gt; python target_generator.py --plot -o data/test_cal.dat -r 40&lt;br/&gt;
&amp;gt; python&#160;netflow_asiaa.py&lt;/p&gt;

&lt;p&gt;mv output.txt pfi_alloc_test_20201227.txt&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/attachment/13300/13300_pfi_alloc_test_20201227.txt&quot; title=&quot;pfi_alloc_test_20201227.txt attached to FIBERALLOC-38&quot;&gt;pfi_alloc_test_20201227.txt&lt;sup&gt;&lt;img class=&quot;rendericon&quot; src=&quot;https://pfspipe.ipmu.jp/jira/images/icons/link_attachment_7.gif&quot; height=&quot;7&quot; width=&quot;7&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/sup&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="18301" author="mxhf" created="Mon, 28 Dec 2020 16:01:34 +0000"  >&lt;p&gt;The most recent netflow_asiaa.py now also writes a PfsDesign fits file.&lt;/p&gt;

&lt;p&gt;This is an example (&lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/attachment/13305/13305_pfsdesign_test_20201228.fits&quot; title=&quot;pfsdesign_test_20201228.fits attached to FIBERALLOC-38&quot;&gt;pfsdesign_test_20201228.fits&lt;sup&gt;&lt;img class=&quot;rendericon&quot; src=&quot;https://pfspipe.ipmu.jp/jira/images/icons/link_attachment_7.gif&quot; height=&quot;7&quot; width=&quot;7&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/sup&gt;&lt;/a&gt;&lt;/span&gt;) with a matching ascii file (&lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/attachment/13303/13303_pfi_alloc_test_20201228.txt&quot; title=&quot;pfi_alloc_test_20201228.txt attached to FIBERALLOC-38&quot;&gt;pfi_alloc_test_20201228.txt&lt;sup&gt;&lt;img class=&quot;rendericon&quot; src=&quot;https://pfspipe.ipmu.jp/jira/images/icons/link_attachment_7.gif&quot; height=&quot;7&quot; width=&quot;7&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/sup&gt;&lt;/a&gt;&lt;/span&gt;).&lt;/p&gt;

&lt;p&gt;Max&lt;/p&gt;</comment>
                            <comment id="18330" author="mxhf" created="Mon, 11 Jan 2021 10:28:32 +0000"  >&lt;p&gt;This images corroborates the issue in the most recent&#160;&lt;/p&gt;

&lt;p&gt;2020-10-15-theta-slow.xml &lt;/p&gt;

&lt;p&gt;I think.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Max&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;https://pfspipe.ipmu.jp/jira/secure/attachment/13314/13314_image-2021-01-11-11-28-25-786.png&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;</comment>
                            <comment id="18767" author="martin.reinecke" created="Mon, 8 Mar 2021 09:36:58 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=mxhf&quot; class=&quot;user-hover&quot; rel=&quot;mxhf&quot;&gt;mxhf&lt;/a&gt; I&apos;m currently working at turning the PFSDesign I/O into library functions. So far I&apos;m making good progress; output is more or less done (thanks to your work in demo_asiaa.py!), but for the input I&apos;m wondering where we are supposed to get the exposure times from... The pfsDesign file describes telescope pointing and orientation, but not the observation duration. Any ideas?&lt;/p&gt;</comment>
                            <comment id="30582" author="yuki.moritani" created="Tue, 15 Mar 2022 19:15:00 +0000"  >&lt;p&gt;Recently this ticked was discussed at the informal meeting between ASIAA, Hassan and PO. By the time of November run, Martin and Max implemented a functionality to write pfsDesign. Some of pfsDesign files were made using (the most) latest version of pfs_utils after the Nov run (and after fixing a few Bug.)&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
/work/pfs/ets/kiyoyabe/test_2022jan/fiber_allocation/commissioning/design

0x65d65dc76164ff80&#160; --&amp;gt; agcc_20211120_0424219 
0x0514a60eadf01a87&#160; --&amp;gt; agcc_20211120_2042567 
0x47dcd57b6af5aa53&#160; --&amp;gt; agcc_20211120_2057506
0x5d2e53852a8d7d35&#160; --&amp;gt; agcc_20211120_2254174
0x691e373818a88a23&#160; --&amp;gt; agcc_20211120_2303420
0x0513dafb2d419f9f&#160; --&amp;gt; agcc_20211121_1831017
0x316c25cd18ca62b2&#160; --&amp;gt; agcc_20211121_2331497 &lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=chyan&quot; class=&quot;user-hover&quot; rel=&quot;chyan&quot;&gt;chyan&lt;/a&gt;&#160;could you try either&#160;0x5d2e53852a8d7d35 or 0x316c25cd18ca62b2? They are several science targets. Most of the cobras are not assigned, but I hope it is OK to test.. (If not, let&apos;s have one.)&lt;/p&gt;</comment>
                            <comment id="31013" author="hassan" created="Fri, 10 Jun 2022 03:49:17 +0000"  >&lt;p&gt;This will be closed based on testing done during the May Eng Run.&lt;/p&gt;</comment>
                            <comment id="31055" author="chyan" created="Sun, 19 Jun 2022 10:53:52 +0000"  >&lt;p&gt;The design file generated and populated in system is always checked by ETS.  Therefore I would close this ticket.  If there is any other problem, we should open another ticket to address the question.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13250" name="Figure.png" size="153039" author="jgracia" created="Wed, 23 Dec 2020 15:09:19 +0000"/>
                            <attachment id="13314" name="image-2021-01-11-11-28-25-786.png" size="1829254" author="mxhf" created="Mon, 11 Jan 2021 10:28:28 +0000"/>
                            <attachment id="13301" name="netflow_asiaa.py" size="7799" author="mxhf" created="Mon, 28 Dec 2020 15:59:38 +0000"/>
                            <attachment id="13300" name="pfi_alloc_test_20201227.txt" size="141225" author="mxhf" created="Sun, 27 Dec 2020 14:11:12 +0000"/>
                            <attachment id="13303" name="pfi_alloc_test_20201228.txt" size="136995" author="mxhf" created="Mon, 28 Dec 2020 16:01:02 +0000"/>
                            <attachment id="13302" name="pfi_alloc_test_20201228.txt" size="136995" author="mxhf" created="Mon, 28 Dec 2020 16:00:43 +0000"/>
                            <attachment id="13305" name="pfsdesign_test_20201228.fits" size="236160" author="mxhf" created="Mon, 28 Dec 2020 16:03:09 +0000"/>
                            <attachment id="13304" name="pfsdesign_test_20201228.fits" size="236160" author="mxhf" created="Mon, 28 Dec 2020 16:01:34 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|02qpqk:y</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>