There is something horribly wrong with filtering.

Question

There is something horribly wrong with filtering.

Closed this issue 4 years ago · 2 comments

See. eg. "/data/Nastja/2020_11_18/Experiment3a.nd2"

Answer 1 · 2020-11-23T14:09:21.000Z

Possible cause?

Answer 2 · 2020-12-09T20:08:42.000Z

There was a bug in fast_filtering with write=False, which still wrote the .showTime entry. Then, when recalculated in examine without rebinning, the previous timescale entry, created for example while loading the region, was still remembered. Fixed now