<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 15:31:59 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>[REDMINE1D-364] [RM-8501] [linemodel] enable the joint fit of superposed absorption and emission lines </title>
                <link>https://pfspipe.ipmu.jp/jira/browse/REDMINE1D-364</link>
                <project id="11002" key="REDMINE1D">1D Redmine </project>
                    <description>&lt;p&gt;&lt;em&gt;&lt;font color=&quot;#505f79&quot;&gt; Created on 2023-11-24 14:45:01 by Didier Vibert. % Done: 0&lt;/font&gt;&lt;/em&gt;&lt;/p&gt;


&lt;p&gt;This concerns only the hybrid fitter and the derived lbfgsb fitter.&lt;br/&gt;
The individual fitter by definition is fitting each line-element individually (independently).&lt;br/&gt;
The svd and svdlc fitter are already fitting all the element jointly (the latter, svdlc, adding the joint fit of the continuum).&lt;br/&gt;
=&amp;gt; we should test the SVD fitter in line ratio mode, instead of individual fitter to fit jointly the 2 global ampitudes of emission and absorption. It will require more CPU, but I guess not too much...&lt;/p&gt;

&lt;p&gt;Currently the hybrid fitter is launching the svd (or lbfgsb) fitter on lists of line elements sharing pixels. But the grouping of the line elements is restricted to group line elements of the same type, leading to fit independently emission and absorption elements that overlaps (See CLineModelElementList::getOverlappingElements).&lt;/p&gt;

&lt;p&gt;Note: the hybrid fitter has also an option &quot;improveBalmerfit&quot; that corrects a-posteriori the superposed emission and absorption lines (currently only the Balmer  lines: Halpha,beta,gamma,delta), if the emission absorption width are significantly different. &lt;/p&gt;

&lt;p&gt;If we activate the joint fit of emission and absorption, then it should be exclusive of the &quot;improveBalmer&quot; option. &lt;br/&gt;
=&amp;gt; 2 parameters, or one parameter with 3 options.&lt;/p&gt;

&lt;p&gt;@vlebrun, are there other lines that have emission and absorption which could be added to the  &quot;improveBalmer&quot; option  ? &lt;br/&gt;
Looking at the linecatalog, I see:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;the Paschen series  P5_beta,6_gamma,7_delta,8_epsilon,9,10,11 (Palpha 18756.1 is only listed in emission in the linecatalog)&lt;/li&gt;
	&lt;li&gt;the other Balmer lines: Hepsilon,8,9,10,11&lt;/li&gt;
	&lt;li&gt;doublet MGII 2804.29 &amp;amp; 2797.11&lt;/li&gt;
	&lt;li&gt;doublet CIV &lt;b&gt;bizarre les longueurs d&apos;ondes emission et absorption sont l&#233;g&#232;rement diff&#233;rentes&lt;/b&gt;: Abs = 1550.79 &amp;amp; 1548.19 vs Em = 1551.19 &amp;amp; 1548.61 ???&lt;/li&gt;
	&lt;li&gt;LyAlpha,beta,gamma&lt;/li&gt;
	&lt;li&gt;OVI 1037 &amp;amp; OVI 1031&lt;/li&gt;
&lt;/ul&gt;


</description>
                <environment></environment>
        <key id="24311">REDMINE1D-364</key>
            <summary>[RM-8501] [linemodel] enable the joint fit of superposed absorption and emission lines </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="r2j.migrate">Redmine-Jira Migtation</assignee>
                                    <reporter username="r2j.migrate">Redmine-Jira Migtation</reporter>
                        <labels>
                    </labels>
                <created>Fri, 24 Nov 2023 18:16:11 +0000</created>
                <updated>Fri, 24 Nov 2023 18:16:41 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="36116" author="r2j.migrate" created="Fri, 24 Nov 2023 18:16:32 +0000"  >&lt;p&gt;Comment by Vincent Le Brun on 2023-11-24 15:16:05:&lt;br/&gt;
Since the absorption and emission are the same for all lines (and then can different) I&apos;d say all lines for which we wan to fit absorption and emission together have to be included in the list of &apos;improve_Balmer_fit&apos;, for which we should than change the name. &lt;/p&gt;

&lt;p&gt;I will check CIV wavelength&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|zzt0in:</customfieldvalue>

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