You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think "fast" autolock is not a really good description for end users since they won't most probably not notice a different in the time it takes for the lock to engage. Also, there are "fast" in and outputs: would be better not to reuse the name.
late-responding to the ping :D in the paper we used "Jitter tolerant autolock". Might be a good choice for the UI as well as a user doesn't care about the implementation details but wants to know what it does / why they should use it
@hermitdemschoenenleben: the jitter-tolerant is already called like this. It is slow since several spectra are recorded. It's the other mode that is called "fast mode". I guess "simple mode" is probably a better name. And then there is "fast mode" which is PID only as well..
I think "fast" autolock is not a really good description for end users since they won't most probably not notice a different in the time it takes for the lock to engage. Also, there are "fast" in and outputs: would be better not to reuse the name.
I think "simple" would be a better description. Any other ideas, @hermitdemschoenenleben ?
The text was updated successfully, but these errors were encountered: