I am getting anomalous spikes in my light-curve RATE file. Whats wrong?
This is usually caused by errors in the specified time intervals that are input to the code. So the “spike” manifests itself at the end of a specified time interval and is exceptionally large. Since the time-resolution of SE (or SA) data files can be small, errors on the order of 1e-10 (usually due to machine accuracy errors) in specifying time intervals will manifest as the addition of an extra bin at the end of a specified time interval containing only a few micro-seconds of “time” (the bin will contain the amount of time specified by the nCDLTm or TIMEDEL value). To ensure that this doesn’t happen it is recommended that the user set the parameter “mfracexp” in the parameter file to some small, but non-zero value. This is the “Minimum acceptable fractional exposure” given as some fraction less than 1.0d0. (The default value INDEF will allow all FRACEXP values through.) It is recommended that the user determine an acceptable minimum fractional exposure value and set this parameter to
