Feature #1478
Allow for asymmetric parameter errors
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assigned To: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Duration: |
Description
So far GModelPar
only supports symmetric errors. Support for asymmetric errors should be added.
Recurrence
No recurrence.
History
#1 Updated by Knödlseder Jürgen almost 9 years ago
- Start date deleted (
06/19/2015)
Note that the implementation should be done in the GOptimizerPar
class, not the GModelPar
class.
We have to decide how to name the asymmetric errors in the XML file. We also need to decide how to name the GOptimizerPar
methods to access the asymmetric errors.
I see basically two choices.
1) add an asymmetry parameter given for example by and define the mean error as . Then and . This reutilizes the existing error
attribute of the class. For symmetric errors we simply would have , which would be the default in case that no alpha
is provided in the XML file (we may think about a better name for the parameter, e.g. asymmtry
or error_asymmetry
or something like that).
2) introduce two new parameters, something like error_pos
and error_neg
. This would however make the existing error attribute obsolete in case that an asymmetric error exists.
The only advantage that I see in 2) over 1) is that the error are more “readable” (you don’t need to apply the above formulae). However, solution 1) would be a more natural expansion of symmetric errors.
#2 Updated by Knödlseder Jürgen over 8 years ago
- Target version set to 1.2.0
#3 Updated by Knödlseder Jürgen almost 8 years ago
- Target version changed from 1.2.0 to 1.3.0
#4 Updated by Knödlseder Jürgen over 7 years ago
- Target version changed from 1.3.0 to 1.4.0
#5 Updated by Knödlseder Jürgen over 7 years ago
- Target version deleted (
1.4.0)