Closed ejm714 closed 2 years ago
Name | Link |
---|---|
Latest commit | 0fdbc20af975645e989a7d22e8b2c365fbd9f304 |
Latest deploy log | https://app.netlify.com/sites/silly-keller-664934/deploys/63334834199b35000819d6d2 |
Deploy Preview | https://deploy-preview-236--silly-keller-664934.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
π Deployed on https://deploy-preview-236--silly-keller-664934.netlify.app
Merging #236 (0fdbc20) into master (0a894a5) will increase coverage by
0.0%
. The diff coverage is100.0%
.
Fixes #234
229 introduced a bug whereby the new columns added to the labels file were in a different order than what is on the model. This PR fixes that by setting up the correct one hot encoded labels in the
preprocess_labels
validator rather thaninstantiate_model
. Using theuse_default_model_labels
, we know whether the labels file should contain columns (with all zeroes) for species that are not present in the labels but are on the base model. Using a pd.Categorical beforeget_dummies
allows us to generate these columns.Running
zamba train --config tests/assets/sample_train_config.yaml
now works; the labels file has three species present in zamba but trains a model that outputs the full set of 32 labels.