-
Notifications
You must be signed in to change notification settings - Fork 20
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
Decouple Ensembling #175
Decouple Ensembling #175
Conversation
(Something to think about) Should I consider modularizing each part of the ML code? I can't recall if I tested each ML function individually with edge cases. There's a possibility that while HAC might work even though PCA fails when dealing with those edge cases. Right now the code will not run HAC after PCA fails due to the assumption that HAC will also fail. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The overall design is good. I only have minor suggestions.
Should I consider modularizing each part of the ML code?
This is low priority for me given how many other things we have to work on. If a user ever requests that or has a problem with it, we could implement it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have any major comments remaining. I'll test locally and merge if everything looks good.
The tests passed locally. However, when I ran with the config file, I was confused about the the data1 outputs. Should we have ML outputs (e.g. PCA output) for Omics Integrator 1? We run it with 4 parameter combinations and the summary table shows:
I didn't get those outputs. |
When I run OI1 locally, I am getting back outputs for the ml step. I keep rerunning oi1 for the config file and seem to be getting back what I expect. |
When I ran it, I thought I did not get those OI1 ML outputs. However, I tested it again and I did. I could have been mistaken or had some temporary error. |
I got distracted and decoupled the ensembling code #163