<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:53:09 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-33] How to deal with manually provided/cached catalogues for guide star selection?</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/FIBERALLOC-33</link>
                <project id="10500" key="FIBERALLOC">Target to fiber allocation and configuration</project>
                    <description>&lt;p&gt;The description of &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/projects/FIBERALLOC/issues/FIBERALLOC-28&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://pfspipe.ipmu.jp/jira/projects/FIBERALLOC/issues/FIBERALLOC-28&lt;/a&gt; mentions:&lt;/p&gt;

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

&lt;p&gt;&lt;em&gt;But also shuffle must allow for other catalogs (sdss, vizier) &lt;b&gt;and manually supplied catalogs&lt;/b&gt; (e.g. from HSC pre-imaging).&lt;/em&gt;&lt;/p&gt;

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

&lt;p&gt;(emphasis added).&lt;/p&gt;

&lt;p&gt;I&apos;d like to understand better what these manually supplied catalogs look like. If they come in form of table names on a TAP-capable server, everything is fine, but if they are supplied as, e.g., FITS files (which was the case for HETDEX, if I understand correctly), I cannot really deal with them at the moment. Querying anything that is not behind an ADQL-capable front end will require quite significant changes and enhancements to the current version of the code.&lt;/p&gt;</description>
                <environment></environment>
        <key id="14672">FIBERALLOC-33</key>
            <summary>How to deal with manually provided/cached catalogues for guide star selection?</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="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="mxhf">mxhf</assignee>
                                    <reporter username="Martin.Reinecke">Martin Reinecke</reporter>
                        <labels>
                    </labels>
                <created>Fri, 21 Aug 2020 13:30:24 +0000</created>
                <updated>Tue, 29 Sep 2020 20:09:50 +0000</updated>
                                                                            <component>ets_shuffle</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="17573" author="rhl" created="Fri, 21 Aug 2020 13:42:54 +0000"  >&lt;p&gt;Is there some reason not to load these tables into a DB as part of the observing preparation?  I don&apos;t know whether you&apos;d rather have e.g. TAP, sqlite, or postgres but it seems reasonable for this to be done outside this code.&lt;br/&gt;
There are other places that we need to have user-provided catalogues in a PFS-defined format (e.g. pfsDesign files) so I think we are going to have to expect to make this sort of transformation.&lt;/p&gt;</comment>
                            <comment id="17574" author="martin.reinecke" created="Fri, 21 Aug 2020 14:01:40 +0000"  >&lt;p&gt;If there is an option of providing the catalogs in a way that I can access them in a way analogous to the online catalogs, I&apos;m perfectly happy. I can&apos;t judge how much effort this would be, but if it is an acceptable solution, then we can just clarify this in the description of &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/FIBERALLOC-28&quot; title=&quot;Update code to find guide star candidates in guide camera footprints&quot; class=&quot;issue-link&quot; data-issue-key=&quot;FIBERALLOC-28&quot;&gt;&lt;del&gt;FIBERALLOC-28&lt;/del&gt;&lt;/a&gt; and close this issue.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="14622">FIBERALLOC-28</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="14903">INSTRM-1078</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|zzs2hs:</customfieldvalue>

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