<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:33:42 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>[DAMD-49] Clarify use of expId</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/DAMD-49</link>
                <project id="10400" key="DAMD">Data Model</project>
                    <description>&lt;p&gt;This ticket has been separated out from &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/DAMD-42&quot; title=&quot;Reconsider the details of the pfsConfig/pfiDesign split&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DAMD-42&quot;&gt;&lt;del&gt;DAMD-42&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The concept of &lt;tt&gt;expId&lt;/tt&gt; had been introduced as part of &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/DAMD-32&quot; title=&quot;Split pfsConfig into pre- and post- mapping files.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DAMD-32&quot;&gt;&lt;del&gt;DAMD-32&lt;/del&gt;&lt;/a&gt;, but with limited information. Please clarify the rationale of introducing this new field.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/DAMD-32&quot; title=&quot;Split pfsConfig into pre- and post- mapping files.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DAMD-32&quot;&gt;&lt;del&gt;DAMD-32&lt;/del&gt;&lt;/a&gt; introduces additional code in relation to &lt;tt&gt;expId&lt;/tt&gt;. If it is agreed that &lt;tt&gt;expId&lt;/tt&gt; is not required, should it be replaced or removed? If the former, what existing information should it be replaced with?&lt;/p&gt;</description>
                <environment></environment>
        <key id="13510">DAMD-49</key>
            <summary>Clarify use of expId</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="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="price">price</assignee>
                                    <reporter username="hassan">hassan</reporter>
                        <labels>
                    </labels>
                <created>Wed, 3 Apr 2019 20:53:24 +0000</created>
                <updated>Mon, 10 Jun 2019 19:48:18 +0000</updated>
                            <resolved>Thu, 23 May 2019 18:37:57 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                <comments>
                            <comment id="15354" author="price" created="Wed, 24 Apr 2019 18:49:58 +0000"  >&lt;p&gt;Craig and I thought &lt;tt&gt;expId&lt;/tt&gt; would be preferable (&lt;tt&gt;visit&lt;/tt&gt; is an LSST-ism), so I tried to replace &lt;tt&gt;visit&lt;/tt&gt; with &lt;tt&gt;expId&lt;/tt&gt; but found that &lt;tt&gt;visit&lt;/tt&gt; is hard-wired in the LSST Butler in places. Hopefully it won&#8217;t be in the next version of the butler, but that&#8217;s a while away. I don&apos;t care either way, and suggest we just go with &lt;tt&gt;visit&lt;/tt&gt; (at least in the pipeline; the instrument software shouldn&apos;t care what the pipeline calls it).&lt;/p&gt;</comment>
                            <comment id="15355" author="cloomis" created="Wed, 24 Apr 2019 18:54:13 +0000"  >&lt;p&gt;+1 on &lt;tt&gt;visit&lt;/tt&gt; &amp;#8211; it is time to choose one term and to use it consistently. Including the instrument software. &lt;/p&gt;</comment>
                            <comment id="15360" author="hassan" created="Thu, 25 Apr 2019 20:22:44 +0000"  >&lt;p&gt;Following 2D DRP tech telecon earlier today - agreed to replace &lt;tt&gt;expId&lt;/tt&gt; with &lt;tt&gt;visit&lt;/tt&gt;. Some technical details  (use of &lt;tt&gt;expId&lt;/tt&gt; &lt;em&gt;and&lt;/em&gt; &lt;tt&gt;visit&lt;/tt&gt;) in certain calls) to be discussed between &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=price&quot; class=&quot;user-hover&quot; rel=&quot;price&quot;&gt;price&lt;/a&gt; and &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hassan&quot; class=&quot;user-hover&quot; rel=&quot;hassan&quot;&gt;hassan&lt;/a&gt;. &#160;&lt;/p&gt;</comment>
                            <comment id="15421" author="hassan" created="Mon, 6 May 2019 17:05:09 +0000"  >&lt;p&gt;Additionally, replace &lt;tt&gt;expHash&lt;/tt&gt; with &lt;tt&gt;pfsVisitHash&lt;/tt&gt; .&lt;/p&gt;</comment>
                            <comment id="15507" author="hassan" created="Thu, 23 May 2019 18:37:57 +0000"  >&lt;p&gt;Merged to master (commit 457f484).&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="13576">DAMD-57</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="13612">PIPE2D-434</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="13435">DAMD-48</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="13347">DAMD-42</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="12356">DAMD-32</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|zx004g:</customfieldvalue>

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