Augmentations #98
Merged
Augmentations #98
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JonasHell
force-pushed
the
augmentations
branch
from
d28a0f7
to
f7f23cf
Compare
constantinpape
approved these changes
Dec 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think the default augementations were still to strong (especially if multiple augmentation were combined), so I adjusted it. Also, I replaced the additive poisson noise with a data-dependent version. After a long discussion with @FynnBe I realized that this makes more sense. Otherwise it is hard to find a default lambda that works regardless of the kind of data (normalized to [0, 1] vs actual photon counts).