Skip to content
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

Noisify can drive signal values negative #232

Open
cmarooney-stfc opened this issue Sep 23, 2020 · 0 comments
Open

Noisify can drive signal values negative #232

cmarooney-stfc opened this issue Sep 23, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@cmarooney-stfc
Copy link
Collaborator

Noisify (herbert_core\utilities\math) modifies the signal values of its input by adding fMR where f is an input scaling factor defaulting to 0.1, M is the maximum value in the signal vector, and R is a random number.

Currently R is chosen from a normal distribution with std.dev=1 and presumably mean of zero (the documentation is coy, just says standard normal). This means that in principle the signal can go negative; this will be more likely as f is made larger. From discussion at a standup meeting, this may not generally be wrong, but really should only be expected as a result of background subtraction, where it is a permissible artifact.

Possible solutions include truncating the distribution generally or for particular pixel values, or replacing it with an appropriate uniform distribution which does not have this problem. This issue is opened for discussion of the best alternative and whether to change to it.

@oerc0122 oerc0122 added the bug Something isn't working label Dec 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants