PFS-JIRA

PFS-JIRA https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us

8.3.4

803005

13-09-2019

[REDMINE1D-373] [RM-8547] Change log 0.46.0 https://pfspipe.ipmu.jp/jira/browse/REDMINE1D-373 1D Redmine <p><em><font color="#505f79"> Created on 2023-12-14 13:38:33 by Pierre-yves Chabaud. % Done: 100</font></em></p> <p>Added</p> <p>Changed</p> <p>Deprecated</p> <p>Removed</p> <p>Fixed</p> REDMINE1D-373

[RM-8547] Change log 0.46.0

Task Normal Done Done Redmine-Jira Migtation Redmine-Jira Migtation Thu, 14 Dec 2023 18:16:40 +0000 Tue, 6 Feb 2024 18:22:09 +0000 Tue, 6 Feb 2024 18:22:09 +0000 0 1 <p>Comment by Pierre-yves Chabaud on 2024-01-11 16:39:08:<br/> *<b>Added</b>*</p> <ul> <li>The API now handles multiple lsf</li> <li>In full multiobs, Amazed provides now one model per observation</li> <li>"not and" operator have been added to filtering feature</li> <li>A warning is raised when lambda range is clamped (it occurs when user lambda range is not compliant with the lambda grid of the input spectrum)</li> <li>String vectors type are now available in Amazed output</li> <li>The flux uncertainty with direct integration method is now available in Amazed output</li> </ul> <p>*<b>Changed</b>*</p> <ul> <li>Change line ID as line number in linecatalog, ensuring uniqueness of line name, wavelength (rounded to 2 decimals) and type (E or A)</li> <li>Change version of LBFGSpp to v0.3.0</li> <li>Changes the way of dealing with redshifts candidates with overlapping integration ranges. In case of overlap greater than 30%, only the best candidates (i.e. highest proba) is selected. In other case, the overlap is equally splitted and candidates are both kept</li> </ul> <p>*<b>Deprecated</b>*</p> <p>*<b>Removed</b>*</p> <p>*<b>Fixed</b>*</p> <ul> <li>The linemeas method is no more executed when redshift solver has failed</li> <li>Better protect bad calibration directory content from segfault, and raise informative exceptions</li> <li>Line ratio amplitude of absorption lines and Lya asym parameters have been fixed in the photometric model</li> </ul> <p>Comment by Didier Vibert on 2024-01-12 11:03:33:<br/> Pierre-yves Chabaud wrote in #note-2:<br/> > *<b>Added</b>*<br/> ><br/> <span class="error">[commentaire: il manque l'ajout du checker de paramètre]</span></p> <ul> <li>The API is now checking the syntax of the json input parameter file, raising an error if the syntax is wrong or if some required parameters are missing, issueing a warning for each unused parameter<br/> > * The API now handles multiple lsf<br/> included in each spectrum of a multi-obs<br/> ( but the current multi-obs in interleave mode is only able to handle one lsf: the first of the list is chosen)<br/> > * In full multiobs, Amazed provides now one model per observation<br/> > * "not and" operator have been added to filtering feature<br/> > * A warning is raised when lambda range is clamped (it occurs when user lambda range is not compliant with the lambda grid of the input spectrum)<br/> > * String vectors type are now available in Amazed output<br/> > * The flux uncertainty with direct integration method is now available in Amazed output<br/> > <br/> > *<b>Changed</b>*<br/> > <br/> > * Change line ID as line number in linecatalog, ensuring uniqueness of line name, wavelength (rounded to 2 decimals) and type (E or A)<br/> > * Change version of LBFGSpp to v0.3.0<br/> > * Changes the way of dealing with redshift candidates with overlapping integration ranges. In case of overlap greater than 30%, only the best candidates (i.e. highest proba) is selected. In other case, the overlap is equally splitted and candidates are both kept<br/> ><br/> [ il manque l'issue #8525 => modif des linecatalog et lineratio, peut être un recap à demander à @vlebrun]<br/> > *<b>Deprecated</b>*<br/> > <br/> > *<b>Removed</b>*<br/> > <br/> > *<b>Fixed</b>*<br/> > <br/> > * The linemeas method is no more executed when redshift solver has failed<br/> > * Better protect bad calibration directory content from segfault, and raise informative exceptions<br/> > * Line ratio amplitude of absorption lines and Lya asym parameters have been fixed in the photometric model</li> <li>output of fitted Line ratio main amplitude of absorption lines</li> <li>output of fitted Lya asym parameters</li> <li>output of fitted photometric model</li> <li>computation of cumulative SNR of strong emmission lines fixed and added a cumulative SNR al all emission lines</li> </ul> <p>Comment by Pierre-yves Chabaud on 2024-01-16 15:13:13:<br/> Last version to validate:</p> <p>*<b>Added</b>*</p> <ul> <li>The API is now checking the syntax of the json input parameter file, raising an error if the syntax is wrong or if some required parameters are missing, issueing a warning for each unused parameter</li> <li>The API is now handling one lsf per observation (but the current multi-observation in interleave mode is only able to handle one lsf: the first of the list is chosen)</li> <li>In full multi-observation mode, Amazed provides now one model per observation</li> <li>"not and" operator have been added to filtering feature</li> <li>A warning is raised when lambda range is clamped (it occurs when user lambda range is not compliant with the lambda grid of the input spectrum)</li> <li>String vectors type are now available in Amazed output</li> <li>The flux uncertainty with direct integration method is now available in Amazed output</li> <li>The cumulative SNR for all emission lines is now available in Amazed output</li> </ul> <p>*<b>Changed</b>*</p> <ul> <li>Change line ID as line number in linecatalog, ensuring uniqueness of line name, wavelength (rounded to 2 decimals) and type (E or A)</li> <li>Change version of LBFGSpp to v0.3.0</li> <li>Changes the way of dealing with redshifts candidates with overlapping integration ranges. In case of overlap greater than 30%, only the best candidates (i.e. highest proba) is selected. In other case, the overlap is equally splitted and candidates are both kept</li> </ul> <p>*<b>Deprecated</b>*</p> <p>*<b>Removed</b>*</p> <p>*<b>Fixed</b>*</p> <ul> <li>The linemeas method is no more executed when redshift solver has failed</li> <li>Better protect bad calibration directory content from segfault, and raise informative exceptions</li> <li>The output of fitted Line ratio main amplitude of absorption lines is fixed</li> <li>The output of fitted Lya asym parameters is fixed</li> <li>The output of fitted photometric model is fixed</li> <li>The computation of cumulative SNR of strong emmission lines is fixed</li> </ul> <p>Comment by Didier Vibert on 2024-01-16 15:50:27:<br/> c'est bon pour moi</p> <p>Comment by Pierre-yves Chabaud on 2024-01-17 08:59:13:<br/> <a href="https://gitlab.lam.fr/CPF/cpf-redshift/-/merge_requests/573" class="external-link" rel="nofollow">https://gitlab.lam.fr/CPF/cpf-redshift/-/merge_requests/573</a></p> <p>Comment by Pierre-yves Chabaud on 2024-01-17 10:03:24:<br/> Merged into @develop@ (@6f3e9a3a@)</p> Development Rank 0|zzt0nz: