Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Implement p_mode="per_example" in Compose()

See original GitHub issue

Hi, thanks for this great software!

Is per_example supported currently or not? With the ValueError raised in Compose (https://github.com/asteroid-team/torch-audiomentations/blob/master/torch_audiomentations/core/composition.py#L30), I assume it is not supported in Compose. But the readme says it is supported - does it mean that it’s supported in individual transforms but not in Compose?

Maybe it’s worth using it in the example code in readme 😃

Issue Analytics

State:
Created 2 years ago
Comments:13 (6 by maintainers)

Top GitHub Comments

2reactions

keunwoochoicommented, Jul 23, 2021

Agree that p_mode="per_example" would be the most relevant. I changed the figure on my side.

Related to that, I think p_mode="per_example" would be quite necessary in Compose(). I don’t know the implementation deeply enough but why would it be not well-defined? I’d assume, if Compose(p_mode="per_example", p=0.8), 20% of examples would be never augmented while 80% of them would go through the stochastic augmentation pipeline.

0reactions

iver56commented, Oct 29, 2021

I’m glad you like it 😃 If you want to make a contribution, that would be welcome