Define the best API for users to apply augmentations in a probabilistic manner.
See original GitHub issueMaybe this will look like:
RandomChance(layer, rate=0.5)
or maybe:
MaybeApply(layer, rate=0.5)
Either way, this is important for the composition of image augmentation pipelines.
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (12 by maintainers)
Top Results From Across the Web
mdbloice/Augmentor: Image augmentation library in ... - GitHub
The purpose of Augmentor is to automate image augmentation (artificial data generation) in order to expand datasets as input for machine learning algorithms, ......
Read more >Augmentor Documentation
The Pipeline module is the user facing API for the Augmentor package. It contains the Pipeline class which is used to create pipeline...
Read more >Efficient Augmentation via Data Subsampling - arXiv
In this work, we aim to make data augmentation more efficient and user-friendly by identifying subsamples of the full dataset that are good...
Read more >Data Augmentation in NLP: Best Practices From a Kaggle ...
Apply data augmentation to your text data. Data augmentation techniques are used to generate additional, synthetic data using the data you have.
Read more >Distribution-preserving data augmentation - PMC - NCBI
Data augmentation methods can produce good results with different parameters in different types of problems. Even a single augmentation ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think that we need to reason a little bit more in general about what kind of access to the augmentation layers an auto augmentation policy need to achieve. Then I suppose we could think at
RandomApply
as just one of the simplest policy.I don’t know if @haifeng-jin has any feedback.
@LukeWood What you’re referring trivial to implement, in the breath, you can also say that implementing
rate
is also trivial to implement to end-users. The feature request in no. 2 is not actually a random request. It’s followed in practice.If you see other popular augmentation libraries, for example,
img_aug
andalbumentation
, all of them offers such feature to users. In addition, if you see thetorch-vision
, you would find the same. Intorch
, you can useRandomChoice
to apply a single transformation randomly picked from a list with a given probability. If this info motivates you, please reconsider the request.