-
Notifications
You must be signed in to change notification settings - Fork 388
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
USAVars Augmentation maps to 0 #1432
Comments
Also not sure to what extent other current datasets might have the same issue because it's a silent bug. |
This is another reason I want #985. Although I don't think rasterio can statically infer the type of the file, so maybe that wouldn't help. We'd have to carefully annotate each read. |
I am reopening this because I had two other people tell me they had the same thing happening with their custom datasets. Is there maybe a way we could implement a warning at some stage?
Or some other check, because it's a quiet sneaky phenomenon, that takes some digging to understand why. |
We could certainly warn, but I want to make sure warnings are uncommon. I also really want to get rid of our I think one of the following solutions would be fine:
There are roughly sorted in order from "this is what I want long-term" to "this would be tolerable short-term". |
Description
In the USAVars Datamodule, the default augmentation from NonGeoDatamodule is used. However, the dataset returns uint8 data, and it comes out of the augmentation still as uint8. This means you get an error when trying to train but also that your input images are just all zeros.
Steps to reproduce
Version
'0.5.0.dev0'
The text was updated successfully, but these errors were encountered: