You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data augmentation operations should be exposed in the configuration file. This would allow user ti activate/deactivate them as they need.
We should also include support for external libraries (e.g. Albumentations) to do so, so we don't have to code them all.
The text was updated successfully, but these errors were encountered:
As of today, Albumentations has too many limitations (for our purpose), such as:
Most of the transformations can only be done on 3 channel images. Our system is generic anough so someone would be able to use it with >3 channels input images. An example of this limitation is provided in the code here
Some transformations assume that input images are uint8. Since we do not want to limit the use of GDL to uint8 images, I'm not sure we should use libraries that makes that assumptions.
Albumentations is not quite suited for our purposes. We'll reconsider the use of this library (or another one) to manage data augmentation later.
In the meantime, we'll still expose our data augmentation operations in the configuration file.
Data augmentation operations should be exposed in the configuration file. This would allow user ti activate/deactivate them as they need.
We should also include support for external libraries (e.g. Albumentations) to do so, so we don't have to code them all.
The text was updated successfully, but these errors were encountered: