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

Initialize to a known state #92

Open
jckantor opened this issue Feb 25, 2018 · 2 comments
Open

Initialize to a known state #92

jckantor opened this issue Feb 25, 2018 · 2 comments

Comments

@jckantor
Copy link
Owner

To enable use with notebooks and accommodate typical student use, each open/close cycle for tclab should leave code in a known state. Need to validate and test.

@alchemyst
Copy link
Collaborator

I'm not 100% sure what you mean here. At the moment if someone uses the context manager, everything will get closed and shut down properly. It is too time consuming to connect to the port on each write, so there wil inevitably be the opportunity to open a connection and not close it if you use low-level commands. Perhaps you could elaborate on "open/close cycle"?

@jckantor
Copy link
Owner Author

The problem I encountered was with labtime. It wasn't being reset on TCLab.init() or TCLab.close(), so could be in an odd state upon starting a new session with the device. I did a quick fix on that, but created the issue as a reminder to scan the remaining bits of code to be sure there's a well defined state upon a restart of TCLab.

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

No branches or pull requests

2 participants