-
Notifications
You must be signed in to change notification settings - Fork 4
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
Modelling workflow #61
Comments
Hi Ben, I think |
Hi @zmcucunuba -- thanks. I agree that users certainly need warnings if their data aren't in the right form. But (sorry, playing Devil's advocate), couldn't that just be done when they do: Is there another reason a user would want to have the object returned by |
Haha, I guess you're right @ben18785! Perhaps It's just me being extremely step-by-step-oriented. |
Just to add - what is the bare minimum information required for the different models to run, the minimum that should be supplied in the user input data? But I guess it also depends how much user interaction the workflow requires, or how complex the models are in which case the user gives more information.. |
@ntorresd is going to look at allowing the |
At the moment, a user does the following to fit their model:
prepare_serodata
functionprepare_serodata
to get data in a form required by the modelling (essentially some additional columns are added to the dataset)run_seromodel
to fit the model.I'd suggest that users don't really need / want to see
prepare_serodata
, so they'd pass the raw data direct torun_seromodel
.The text was updated successfully, but these errors were encountered: