measurement error
jakeberv opened this issue · comments
Is there a way to include standard error for input traits in an l1ou analysis?
Hi Jacob,
Do you mean the error of measurement for trait values? If so, there's no
input for that.
If you know the distribution of the error, you may be able to do some
bootstrap procedure.
…On Thu, Nov 11, 2021 at 1:03 PM Jacob S. Berv ***@***.***> wrote:
Is there a way to include standard error for input traits in an l1ou
analysis?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#48>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB65XC4K7RHR5BUH77O7FVLULQAQPANCNFSM5H3BCA6A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
Yes— exactly, like standard error for the trait values.
For example
https://academic.oup.com/sysbio/article/56/2/252/1687174 <https://academic.oup.com/sysbio/article/56/2/252/1687174>
https://besjournals.onlinelibrary.wiley.com/doi/full/10.1111/2041-210x.12337 <https://besjournals.onlinelibrary.wiley.com/doi/full/10.1111/2041-210x.12337>
It would be great to be able to naturally account for the error in trait values — as this seems to have an strong impact on model selection
Bootstrapping with slight variations in the trait values based on some distribution for each tip is an interesting idea!
Thanks,
Jake
… On Nov 15, 2021, at 11:46 AM, Mohammad Khabbazian ***@***.***> wrote:
Hi Jacob,
Do you mean the error of measurement for trait values? If so, there's no
input for that.
If you know the distribution of the error, you may be able to do some
bootstrap procedure.
On Thu, Nov 11, 2021 at 1:03 PM Jacob S. Berv ***@***.***>
wrote:
> Is there a way to include standard error for input traits in an l1ou
> analysis?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#48>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AB65XC4K7RHR5BUH77O7FVLULQAQPANCNFSM5H3BCA6A>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKMB23UUQCWDXIXIUUTGS5TUME2PRANCNFSM5H3BCA6A>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.