Exclude extra columns in labels df (TrainConfig) and filepaths df (PredictConfig) #186
Conversation
This file contains 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.
For the labels csv, we required "filepath" and "label" and support optional columns "split" and/or "site." If a labels csv contains extra columns, we should exclude those as these can lead to unintended consequences.
For example, if there is a column with "species_" prefix, e.g. "species_VE", this column will get included in the species list (which results from label -> species -> get dummies -> filter columns with "species_"). By explicitly excluding extra columns, we avoid this bug.
Similarly for predict, we should exclude any columns that are not "filepath" as this interferes with indexing in the dataloader.