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

Bug in atc insertion/oversampling of lmdb #179

Open
Aastedet opened this issue Dec 20, 2024 · 0 comments
Open

Bug in atc insertion/oversampling of lmdb #179

Aastedet opened this issue Dec 20, 2024 · 0 comments

Comments

@Aastedet
Copy link
Collaborator

Currently, A10BJ06 (semaglutide) seems to be the only atc code being inserted/oversampled. So about 30% of all rows of the synthetic lmdb data is value:

summary(factor(register_data$lmdb$atc))

Since we stopped including based on GLP1-RAs (atc ^A10BJ), we don't "need" to oversample these so much anymore, since we don't need to cover edge cases within them based on vnr/name.

Relates to #146, where we also have to update the functions generating the fake lmdb data.

@Aastedet Aastedet converted this from a draft issue Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant