-
Notifications
You must be signed in to change notification settings - Fork 2
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
BUg in do_combine_turb #49
Comments
It will replace previous NaNs with the Isn't that what you want? I found recently that we usually get fits with 1-2 points in the fitting range when you're close to the noise floor... |
Maybe its an easy fix. I think the problem is the way you define the criteria: I think it should be simply can you confirm? |
In the old version it overwrites old nans from other masks with the fill value, which is bad I think |
I actually removed that at some point so it's just Again, if you are at the noise floor, you want to fill those values regardless of whether they were flagged earlier? Which other mask is this interfering with? |
for example the Tz<minTz ... |
the T_z mask is applied last to avoid this... (also I made a local change to avoid setting ε=0. really I think we should only set χ=0 but leave ε as NaN. I can push that soon if that would be useful.) |
I guess it interferes with N2 mask. Some reordering would fix that... |
but also with speed masks.... |
or was it supposed to be an extra mask? |
Yes. Mostly because the I see your point though. We should reorder the masks so that we deal with bad fits, noise floor first and then do the rest. Just to be sure that we're talking about the same thing; here's the output from the most recent version:
|
This was a local change that I should get rid off. You wont' see this. |
I was still on the old version, I didn't realize that you made so many changes recently. |
Yes, I think we should reorder the masks more sensibly. The n_freq mask should come before the noise floor mask basically. Everything else can come later I think, |
Hi Deepak, how are things.
I realized a nasty bug in do_combine_turb.m
it is related to the noise_floor_mask and potentially other masks, too.
When I put noise_floor_fill_value to anything other than nan
line 230 [chi, chi.stats.spec_floor_percentage] = ApplyMask(chi, ...
is going to revive values that have been flagged before as nans to
the noise_floor_fill_value.
This is a big issue since it completely messes with the flagging.
The text was updated successfully, but these errors were encountered: