<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:04:15 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>[PIPE2D-1204] Ingest defects for multiple instruments in Gen3</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE2D-1204</link>
                <project id="10002" key="PIPE2D">DRP 2-D Pipeline</project>
                    <description>&lt;p&gt;We are currently building the defects in the drp&amp;#95;pfs&amp;#95;data package because Gen3 apparently requires that, but we need to treat the different instruments (sim, LAM, Subaru) separately. &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=jbosch&quot; class=&quot;user-hover&quot; rel=&quot;jbosch&quot;&gt;jbosch&lt;/a&gt; recommends:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The natural way to do that would be to have a physical_detector dimension to go with the usual detector &lt;span class=&quot;error&quot;&gt;&amp;#91;slot&amp;#93;&lt;/span&gt; dimension, with another &quot;dimension element&quot; table that says which physical_detector maps to each detector for each observation, possibly mediated by a new site dimension.&lt;br/&gt;
I&apos;ve left out everything but the linkage between dimensions.&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;
site:
	keys: ...
	...
exposure:
	keys: ...
	...
	requires: [intrument]
	implies: [psf_design_id, dither, site]
physical_detector:
    keys: ...
	...
	requires: [instrument]
detector:
    ...
	requires: [instrument]
site_detector:
    ...
	requires: [site, detector]
	implies: [physical_detector]
	always_join: &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
exposure_site:
	...
	requires: [site, exposure]
	always_join: &lt;span class=&quot;code-keyword&quot;&gt;true&lt;/span&gt;
...
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;As a side note, you probably don&apos;t need to have both visit and exposure.  I&apos;d recommend collapsing that down to just one, and then you don&apos;t need visit_system or visit_definition, either.&lt;br/&gt;
A version with no site and an exposure_detector join-table defined as&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;
requires: [exposure, detector]
implies: [physical_detector]
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;would be a slightly denormalized variant, which might be useful both to avoid a join and allow some site to shuffle detectors around in the future without, but it&apos;d mean a lot of redundant entries in the database if that&apos;ll never happen.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://lsstc.slack.com/archives/C01FBUGM2CV/p1681957305549699&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;Link to Slack thread.&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="23362">PIPE2D-1204</key>
            <summary>Ingest defects for multiple instruments in Gen3</summary>
                <type id="10001" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10515&amp;avatarType=issuetype">Story</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="1" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="price">price</assignee>
                                    <reporter username="price">price</reporter>
                        <labels>
                    </labels>
                <created>Thu, 20 Apr 2023 17:46:00 +0000</created>
                <updated>Thu, 20 Apr 2023 17:46:32 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                        <attachments>
                    </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|zzswsf:</customfieldvalue>

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