Model ensemble pull request#55
Merged
vxfung merged 19 commits intoFung-Lab:mainfrom Jan 7, 2024
orivera2280:main
Merged
Conversation
vxfung
approved these changes
Jan 7, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Most changes are in the base_trainer and property_trainer files. Generally, model ensemble methods are indicated by if statements checking for the type of model (if it is a list, it is a model ensemble) or by checking if the "model_ensemble" parameter from the config is > 1. I also made changes to the task.py file to support predictions on ensembles. These are indicated by the checks for the type of the data loader (if list, then it assumes a model ensemble is being used).