<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:00:48 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-982] Evaluate uncertainties in extinction correction for the PS1-Gaia catalog</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/PIPE2D-982</link>
                <project id="10002" key="PIPE2D">DRP 2-D Pipeline</project>
                    <description>&lt;p&gt;Based on parallax uncertainties from Gaia, estimate uncertainties in extinction correction for PS1 photometry.&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="22631">PIPE2D-982</key>
            <summary>Evaluate uncertainties in extinction correction for the PS1-Gaia catalog</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="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="ishigaki">ishigaki</assignee>
                                    <reporter username="ishigaki">ishigaki</reporter>
                        <labels>
                            <label>flux-calibration</label>
                    </labels>
                <created>Sun, 20 Feb 2022 20:31:42 +0000</created>
                <updated>Wed, 26 Apr 2023 05:50:33 +0000</updated>
                            <resolved>Wed, 26 Apr 2023 05:50:33 +0000</resolved>
                                                                        <due>Fri, 4 Mar 2022 00:00:00 +0900</due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="30558" author="ishigaki" created="Tue, 8 Mar 2022 06:30:27 +0000"  >&lt;p&gt;I attached slides that explain an alternative method to infer stellar types taking into account extinction and distance uncertainties.&#160;&lt;/p&gt;

&lt;p&gt;This method is very similar to what is adopted by Green et al. 2014, when they infer a 3D dust extinction to individual stars. The advantage is that we can directly obtain a probability distribution of stellar intrinsic parameters (age, metallicity, mass, temperature, etc.) taking into account the uncertainties in distance and extinction, both of which are crucial for selecting F-stars from photometric information. &#160;The major difficulty at the moment is a computational cost (~1 day, with multiprocessing with 50 CPUs ). &#160;I will address this issue in the next week.&#160;&lt;/p&gt;</comment>
                            <comment id="30559" author="msyktnk" created="Tue, 8 Mar 2022 08:04:37 +0000"  >&lt;p&gt;I probably have discouraged you on a separate ticket, apologies.&#160; I am very impressed by the slides; this is a very careful approach and looks really great.&#160; My only concern is the compute time as you say; can we classify millions/billions of stars this way?&#160; If my concern turns out not to be a problem, great, we should adopt this approach.&#160; Otherwise, we might want to consider a little simpler algorithm...?&lt;/p&gt;</comment>
                            <comment id="30560" author="ishigaki" created="Tue, 8 Mar 2022 09:14:54 +0000"  >&lt;p&gt;Thanks for your prompt reply! I will investigate whether we could reduce the computation time.&#160;&lt;/p&gt;</comment>
                            <comment id="30589" author="ishigaki" created="Wed, 16 Mar 2022 05:56:32 +0000"  >&lt;p&gt;The computation time for the MCMC analysis, mentioned in my previous post, has been reduced to 2-3 hours for one star with 50 CPUs. This may be still too long to process &amp;gt;100 million sources within a reasonable time scale.&#160;&lt;/p&gt;

&lt;p&gt;I think, therefore, we could take a hybrid approach;&#160;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;We first use the logistic regression algorithm, as we previously adopted. This method provides the probability of being an F star for all the Gaia-PS1 crossmatched sources with reliable parallax and griz photometry. To take into account the extinction correction/distance uncertainties, we flag objects with unreliable distance or reddening estimates.&#160;&lt;/li&gt;
	&lt;li&gt;The MCMC analysis will be used as a supplementary information, if we want to prioritize among the Fstar candidates selected in the Step 1.&#160;&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;As for the flagging of unreliable distance/reddening, stars with reddening uncertainty &amp;gt; 20% or distance uncertainty &amp;gt; 20 % are flagged at the moment. I attach a figure for the Gmag histogram of all Fstars and unflagged (reliable) Fstars for a small region of the sky. &#160;&lt;/p&gt;

&lt;p&gt;As for Step 2, I will continue trying to speed up the parameter estimates. &#160;&lt;/p&gt;

&lt;p&gt;Any comments or suggestions, especially on how we flag the F-star candidates, are appreciated.&lt;/p&gt;</comment>
                            <comment id="32466" author="ishigaki" created="Fri, 24 Mar 2023 01:16:00 +0000"  >&lt;p&gt;With the new method using brutus code, the uncertainties in extinction correction are fully taken into account for the stellar temperature determination. The code outputs the posterior probability distribution of Teff given photometric data (PS1 griz) and the priors on Galactic stars. The validity of the new method should be tested by upcoming engineering observations.&#160;&lt;/p&gt;</comment>
                            <comment id="32622" author="msyktnk" created="Wed, 26 Apr 2023 05:50:33 +0000"  >&lt;p&gt;We will have to see how accurate the uncertainties from brutus are with real data, but that is the scope of a future ticket.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="13356">PIPE2D-362</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="22633">PIPE2D-984</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="22634">PIPE2D-985</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="22632">PIPE2D-983</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="15119" name="FluxStandards_extinction.pdf" size="448915" author="ishigaki" created="Tue, 8 Mar 2022 06:20:16 +0000"/>
                            <attachment id="15133" name="hist_fprob_flags.png" size="16603" author="ishigaki" created="Wed, 16 Mar 2022 05:55:01 +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_10006" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>PIPE2D-303</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|zzst3z:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10100" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Reviewers</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>msyktnk</customfieldvalue>

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