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
It might be interesting, as an alternative to, or in complement in, the FSM mode (see #51) and the enumeration variables (see #90), to support an integrator.
An integrator would be an integer variable, whose initial value and speed of change would be set in an action block, and whose value crossing a threshold could be tested in an event block. In that sense, it would be somewhat similar to the timer in VPL1, but would be more flexible. Properly implemented, it could allow interesting activities especially at the level of bio-inspired algorithms, for instance synchronised blinking like fireflies or Grey Walter's tortoises.
Here is a proposed detailed set of operations:
Event: Crossing threshold, user-given threshold.
Action: Setting the value and the speed of change, possibly relative.
I envision the value to wrap around, simply mapping it to an int16.
Here is an example of design:
The text was updated successfully, but these errors were encountered:
It might be interesting, as an alternative to, or in complement in, the FSM mode (see #51) and the enumeration variables (see #90), to support an integrator.
An integrator would be an integer variable, whose initial value and speed of change would be set in an action block, and whose value crossing a threshold could be tested in an event block. In that sense, it would be somewhat similar to the timer in VPL1, but would be more flexible. Properly implemented, it could allow interesting activities especially at the level of bio-inspired algorithms, for instance synchronised blinking like fireflies or Grey Walter's tortoises.
Here is a proposed detailed set of operations:
I envision the value to wrap around, simply mapping it to an int16.
Here is an example of design:
The text was updated successfully, but these errors were encountered: