-
Notifications
You must be signed in to change notification settings - Fork 378
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
Vaihingen datamodule #851
Comments
My vote is for data augmentation that pads or crops to a consistent size. How much do image sizes vary? A lot of other datasets have image sizes that vary by ± 1 px, so those are much easier to take care of. |
There are 16 samples in the training dataset and they are more like "tiles" or "scenes". I think the datamodule should randomly sample fixed size crops from them. The sizes:
|
In that case, we should convert |
They aren't georeferenced |
Guess we can do something like this then: https://kornia-tutorials.readthedocs.io/en/latest/geometry_generate_patch.html |
OSCDDataModule is a good reference. It also has variable sized images and we take random crops during training. |
Description
I would expect that with a existing Vaihingen datamodule, I only need to define a segmentation task and a
pl.Trainer
to train a model on this dataset (but maybe this expectation is wrong). However, the Vaihingen dataset has variable sized image dimensions, and therefore one cannot specify abatch_size>1
because otherwise tensors cannot be stacked. So either there should be a collate function for the dataloaders in the datamodule or some comment in the documentation because the default batch_size of the datamodule is 64.Steps to reproduce
Version
0.4.0.dev0
The text was updated successfully, but these errors were encountered: