My regulator doesn want to see nonparametric limits, but DUMPStat automatically uses them when the data are neither normally nor lognormally distributed – what can I do?
In the DUMPStat statistical options, the “Rare Event Statistics” setting can be used to override the choice of nonparametric limits, even for events with high detection frequencies. When “Poisson” is selected, you will never get a nonparametric limit. When computing a prediction limit, if the detection frequency is insufficient to compute a parametric limit (a “Rare event”), you will either get a nonparametric limit or a Poisson limit, depending on the “Rare Event Statistics” setting in your statistical options. For inter-well comparisons, if the detection frequency is sufficient to compute a parametric limit, the background data are tested for normality. If they pass this test, you will get a normal limit. If they fail, the data are tested for lognormality. If the data are found to be lognormally distributed, you will get a lognormal limit. If both tests fail, then the “Rare events” setting is used — even though the detection frequency is high. If “Nonparametric” is selected you will
Related Questions
- My regulator doesn want to see nonparametric limits, but DUMPStat automatically uses them when the data are neither normally nor lognormally distributed - what can I do?
- Can ethograms be automatically generated using body acceleration data from free-ranging birds?
- Where is all the data coming from that is automatically entered?