Skip to content
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

Add explicit out-of-frame inference #154

Open
edvinf opened this issue Dec 26, 2024 · 0 comments · Fixed by #155
Open

Add explicit out-of-frame inference #154

edvinf opened this issue Dec 26, 2024 · 0 comments · Fixed by #155
Assignees
Labels
analytical issues for new analytical estimation workflow release1.6 Issues that must be solved before release of 1.6 unstableRepo proposed solution to issue is in the develop branch and the unstable repository

Comments

@edvinf
Copy link
Contributor

edvinf commented Dec 26, 2024

Currently, estimates for target population that is outside of sampling-frame is supported by pragmatic inclusion of some Stratification-variables. E.g. use only "species" to pretend that the sampling-frame was larger than it actually was. We should add a more explicit step. Where mean weights and frequencies are imputed to out-of-frame strata, before application of RatioEstimation.

@edvinf edvinf added analytical issues for new analytical estimation workflow release2.0 Issues that must be solved before release of 2.0 labels Dec 26, 2024
@edvinf edvinf self-assigned this Dec 26, 2024
@edvinf edvinf added release1.6 Issues that must be solved before release of 1.6 and removed release2.0 Issues that must be solved before release of 2.0 labels Dec 27, 2024
@edvinf edvinf linked a pull request Jan 3, 2025 that will close this issue
@edvinf edvinf added the unstableRepo proposed solution to issue is in the develop branch and the unstable repository label Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analytical issues for new analytical estimation workflow release1.6 Issues that must be solved before release of 1.6 unstableRepo proposed solution to issue is in the develop branch and the unstable repository
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant