<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:33: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>[DAMD-5] Format for simulated 1-D spectra</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/DAMD-5</link>
                <project id="10400" key="DAMD">Data Model</project>
                    <description>&lt;p&gt;We need to define a format for the spectra that are input to the simulations.  These should come from the science collaborations so need to be flexible enough to capture a lot of different science cases (e.g. stars from GA; z ~ 1.5 galaxies with strong O&lt;span class=&quot;error&quot;&gt;&amp;#91;III&amp;#93;&lt;/span&gt; from cosmology).&lt;/p&gt;

&lt;p&gt;The spectra should be noise free scaled to the observed brightness (and redshifted as appropriate) at sufficiently high sampling spatial that we can interpolate.  The units are TBD, but probably Jy.&lt;/p&gt;

&lt;p&gt;Questions:  Should the lines be listed separately (lambda, EW, width)?  If we don&apos;t do this we are in danger of convolving twice (forcing us to generate simulations at very high resolution).&lt;/p&gt;</description>
                <environment></environment>
        <key id="10204">DAMD-5</key>
            <summary>Format for simulated 1-D spectra</summary>
                <type id="10001" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10515&amp;avatarType=issuetype">Story</type>
                                            <priority id="3" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/major.svg">Major</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="rhl">rhl</assignee>
                                    <reporter username="rhl">rhl</reporter>
                        <labels>
                    </labels>
                <created>Tue, 22 Jul 2014 14:27:10 +0000</created>
                <updated>Mon, 25 Sep 2023 21:34:03 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="10411" author="bick" created="Mon, 22 Dec 2014 05:37:51 +0000"  >&lt;p&gt;Transferring a conversation with RHL on email here for posterity.  Quotes are from bick&apos;s original email, while replies are rhl&apos;s.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Clearly the spectra need to be sampled above the Nyquist limit, and it sounded like the issue was &apos;how much?&apos;.  &lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;It would have to be the nyquist limit of the narrowest lines, not of the spectrograph.  I am concerned that if we smooth the input spectra too much we&apos;ll never simulate the narrowest lines that we really see.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Jim suggested R=10000, Robert bid it up to R=20000 with the concern that we need to be quite a bit above critical to make sure we handle the narrow lines correctly.  Jenny pointed out that narrow lines won&apos;t be a problem for galaxy spectra ... I believe her ... but there are other spectra to consider, of course.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;R = 20000 corresponds to 15km/s so it should be OK for everything except stars.  Maybe 10000 is enough?  Anyway, we need a high enough resolution that the PSF for the narrowest lines we expect come from the instrument not the input model.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;How well do we need to specify the data format at this point?  Is this format intended to also be the 1D output format of the pipeline (with the exception that the output sampling is that of the spectrograph)?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;No, I think we decided against that.  The needs of the input are very different from the output (no need for noise or variance; higher resolution).&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;For spectra with linearized wavelength solutions (or log-linear), the sampling itself is just a WCS in the header, so I guess I&apos;m not clear on why this detail came up as the focus of discussion.  I had assumed the simulator would be able to accept input spectra at any reasonable sampling ... if it&apos;s under-sampled, the sim should produce the garbage we deserve.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Well, one option for inputs would be a set of sampled spectra + a line list (lambda, power, width).  I&apos;m not sure we need to go there.  Or we could specify the input as (flux, lambda) tuples with no assumption that the lambda values are equally spaced &amp;#8212; that allows high resolution in the lines and low in the continuum.&lt;/p&gt;

&lt;p&gt;I don&apos;t think this is hard, we just need to define it.&lt;/p&gt;</comment>
                            <comment id="11291" author="rhl" created="Sat, 3 Sep 2016 18:43:36 +0000"  >&lt;p&gt;N.b.  This is basically a placeholder.  I understand (phonecon 2016-10-07) that the LAM team are now responsible for adding emission lines to the simulated galaxy spectra, so it&apos;d be great to get their input.&lt;/p&gt;</comment>
                            <comment id="15375" author="hassan" created="Fri, 26 Apr 2019 20:55:36 +0000"  >&lt;p&gt;In the current &lt;tt&gt;datamodel.txt&lt;/tt&gt; we have defined a &lt;tt&gt;pfsSimObject&lt;/tt&gt;. This specifies at present only (flux, lambda). Equivalent width is not included. Should this ticket still remain as a placeholder? Should we revisit including the extra line parameters?&lt;/p&gt;
</comment>
                    </comments>
                    <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|zzst9o:</customfieldvalue>

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