-
Notifications
You must be signed in to change notification settings - Fork 0
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
Same neuron as sleep? #1
Comments
More or less, yes. I was looking for a solution to delay a synapse and the only thing I came up with was to start thread, what would launch a synapse after a given time. The ability to delay without start a synapse is equal to the sleep neuron. I just added it because time.sleep was already needed. |
I you use the sleep neuron in first place (first neuron of the list) it will wait before running the first task, yes. |
The main purpose for me was, if I go sleep, tell Kalliope to turn everything off except of a lamp in my living room what goes off after an hour. But with the sleep neuron Kalliope is sleeping and cant to do anything at this moment, the synapse delay is running as a thread so Kalliope is still functional. |
Oh ok! I see. Nice idea. You should update your doc to explain this then ! |
Like you see Im not good in explain something especially in English :) I was hopping it would be clear with the synapse example and the comment that it would run as thread. But yes I would update the docs then. |
Ok, I looked at the code. you use a subprocess to call a new instance of kallioe with |
This was my first neuron I wrote and basically I just took the Async shell from the shell neuron and removed the stuff I don´t needed. So no big deal, but it worked the last few months and I thought, why not share. Now I have some more experience with python and the code of Kalliope whereby I would probably try to use the SynapaseLauncher directly instead of calling the shell. But I think that´s what you mean with "implement it natively"? |
Looks like the ame as the offical "sleep" neuron. Doesn't it?
The text was updated successfully, but these errors were encountered: