In your doc, N2 is regarded as the more restrictive criterion, and should be less than N1. However, if we assume error is positive, T2 is always greater than T1, and N1 becomes the more restrictive one. If we pass the _fluxerr to sigma, it is choosing N1=3 and N2=4 that check for the same criterion, not N2=2.
As you mentioned in the doc, the flare candidate definition follows the criteria in Chang et al. (2015). But in this paper, according to the equation (3a)
the data points refer to magnitude, not flux.
Therefore, the "+ error" makes sense here
Fully agree, thanks for pointing it our! Something went wrong at some point in the development (the original function in Appaloos does it the right way). Changed it!
What needs to be created or improved?
There might be something wrong with the definition of T2.
Can you provide an example?
The criteria is defined in altai.py as below:
In your doc, N2 is regarded as the more restrictive criterion, and should be less than N1. However, if we assume error is positive, T2 is always greater than T1, and N1 becomes the more restrictive one. If we pass the _fluxerr to sigma, it is choosing N1=3 and N2=4 that check for the same criterion, not N2=2.
As you mentioned in the doc, the flare candidate definition follows the criteria in Chang et al. (2015). But in this paper, according to the equation (3a)
the data points refer to magnitude, not flux. Therefore, the "+ error" makes sense here
but should be "- error" when it comes to flux.
What is the goal / expected behaviour?
T2 should be defined as below: