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

Missing data #1

Closed
noxtoby opened this issue Nov 28, 2018 · 5 comments
Closed

Missing data #1

noxtoby opened this issue Nov 28, 2018 · 5 comments
Assignees

Comments

@noxtoby
Copy link
Member

noxtoby commented Nov 28, 2018

I get divide by zero errors relating to model likelihood, which I tracked back to missing data causing problems with max() and min(), etc. Couldn't fix it with numpy.nanmax(), so we probably need to devise a robust method for handling missing data.

@ayoung11
Copy link
Collaborator

SuStaIn doesn't handle missing data at the moment, I have an idea about one way to go about it but it needs testing first

@noxtoby
Copy link
Member Author

noxtoby commented Nov 28, 2018

Yeah, I had a think about how to do it without biassing the model, but it's not as straightforward as it is for the EBM.

@armaneshaghi
Copy link
Collaborator

I close this as we have ongoing work on missing variable analysis in SuStaIn at the POND group, to be introduced later.

@d-morrison
Copy link

Any updates on handling missing data?

@noxtoby
Copy link
Member Author

noxtoby commented Aug 1, 2023

@d-morrison — see ZScoreSustainMissingData if using the z score model. If using mixture SustaIn, then you have to handle missing data yourself when calculating the event likelihoods that go into pySuStaIn.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants