-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Post DUSC Instructor thoughts #24
Comments
This is great, thanks for the helpful feedback @DimmestP. I'll try to find some time to think about how the points can be addressed (and would welcome pull requests in the meantime!). Some really quick thoughts:
I have mixed feelings about switching to a non-medical dataset (though I admit partly because of my own bias towards health data!). Wouldn't any dataset we choose have some kind of topic? I dislike "toy datasets" like Iris etc, so I'd be happy to switch but preferably to something interesting.
Agreed, definitely more work needed here. I intentionally tried to reduce time spent on data pre-processing because it is covered in an earlier workshop, but I agree that evaluation, tasks, etc would be good topics.
For me this is a tough one. I have found the vizualisation aspect of the workshop to be important, and it's not ideal that the ability to visualize models diminishes as number of features increases. Ideally I'd like it if we could (1) keep visualization and (2) work out how to incorporate more features when needed (e.g. to demonstrate improved performance).
I agree the gradient boosting section needs work. I'd like to keep if possible, and add more detail. At this point in the workshop, I usually take people to PubMed and point out some of the papers that have been published on this dataset using XGBoost. Not that they are exciting papers, but that prior to the workshop I think many people would believe those papers were doing something special.
Definitely, there are a bunch of things like this that need cleaning up! |
Thoughts after DUSC workshop 15/11/23:
The text was updated successfully, but these errors were encountered: