Open forstater opened 9 years ago
As a suggestion along these lines, have the user input the expected range of baseline currents, and set the program to ignore any sections of data for which the baseline deviates outside of that range. I have used this in the past, it is simple and effective.
The other problem is the event partition code classifies a long gating step (with tens of thousands of data points) as an event causing the fit algorithm to get bogged down.
Two possible solutions:
(a) Would it be possible to set a maximum event duration cutoff (or number of points)? In my experience, gating events are generally partitioned but cannot be fit.
(b) One less generalized option - for systems (such as EBS) which can rapidly change voltage in response to gating , could the gating observation time and clearing time be used to remove these events?
FYI - I recall opening a more detailed ticket about this at one point on bitbucket, including some test files, any chance you're still able to access the bitbucket issue tracker?
Reproducing Bitbucket issue 23:
Analysis fails when encountering a gating channel. No further events are fit and software appears to continue attempting to process this event indefinitely. Attached is a zip file containing the necessary information to replicate this problem. This occurs in both the current development version and in v1.0a5.1. Below are images of the event in question.
Problem: Channel gating can cause analysis to stall or terminate. MOSAIC should gracefully handle gating events and remove them prior to analysis or avoid fitting them.