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

relock should only occur if its necessity was confirmed twice #279

Open
lneuhaus opened this issue May 31, 2017 · 0 comments
Open

relock should only occur if its necessity was confirmed twice #279

lneuhaus opened this issue May 31, 2017 · 0 comments
Assignees

Comments

@lneuhaus
Copy link
Collaborator

lneuhaus commented May 31, 2017

The dominant source of delocking is a temporary unlocking (someone smashes on the table or abruptly opens the door) which is however often recovered by itself. However, if a lost lock is detected, the sequence is restarted without hesitation, thereby hindering a 'natural lock recovery'. More importantly, since we only sample a fraction of the time to check for islocked (1% of all data), we should directly enforce a robust unlocked condition before relocking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant