-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use of weighted results in surprising behaviour in the estimate #344
Comments
The last value with all the unequally weighted data appears to be incorrect. |
However the calculations are correct. As David Fox confirmed
|
We will turn off this functionality until a better solution is found. |
I disagree with what David Fox has written above. Weighting the data in a tail end of a distribution will likely increase the length of the tails. This is because these data points will be the focus of fitting the distribution. This could be useful if the species in the tails are of great importance and if there are few data points to represent the class of taxa that are found to be sensitive. In this case it would be a useful too to have to weight the distribution more on these species so an estimate can be made that will be protective of that group of species. I do not think this function should be removed as it is not erroneous. It just does not behave similar to weighting when it is done in a regression. I therefore think this functionality should not be removed. |
One potential resolution for this is to leave the weighting function based on log-likelihood available, but include a section in the technical details vignette explaining that the current implementation is correct, but that this may result in unexpected behavior. Text from the Phase III report should make a good starting point for this vignette update. |
I agree. I think we just need to explain what weighting the tails means when fitting distributions using MDL and how this can be useful for ecotoxicologists. |
Created on 2024-01-22 with reprex v2.1.0
The text was updated successfully, but these errors were encountered: