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
Currently, the finest grain TimeScale present in PsyNeuLink is TimeStep. This corresponds to "the execution of all Mechanisms allowed to execute from a single consideration_set of a Scheduler".
This is problematic in cases where a mechanism, such as an LCA, executes multiple times in a given TimeStep. In these cases, all executions of the mechanism in that TimeStep will be logged as occurring at the exact same Time.
To fix this, we should implement one finer grained TimeScale that represents the number of executions of a Mechanism within a given TimeStep. It was suggested that the name for this finer-grained TimeScale is implied to be "Call" by our Conditions (AfterNCalls, etc.), but there was also a suggestion that "Cycle" may be a better name.
As part of the effort of modifying Time in PsyNeuLink, there was also a suggestion that what is currently known as "Pass" should be renamed to "Execution Step" for clarity. We should consider this suggestion.
The text was updated successfully, but these errors were encountered:
On Mar 3, 2020, at 4:16 PM, dillontsmith <notifications@github.com<mailto:notifications@github.com>> wrote:
Currently, the finest grain TimeScale present in PsyNeuLink is TimeStep. This corresponds to "the execution of all Mechanisms allowed to execute from a single consideration_set of a Scheduler".
This is problematic in cases where a mechanism, such as an LCA, executes multiple times in a given TimeStep. In these cases, all executions of the mechanism in that TimeStep will be logged as occurring at the exact same Time.
The number of executions *is* reflected in the number of Passes. The issue is more about nomenclature rather than mechanics.
To fix this, we should implement one finer grained TimeScale that represents the number of executions of a Mechanism within a given TimeStep.
Though, as noted above, this is marked by Passes.
It was suggested that the name for this finer-grained TimeScale is implied to be "Call" by our Conditions (AfterNCalls, etc.), but there was also a suggestion that "Cycle" may be a better name.
As part of the effort of modifying Time in PsyNeuLink, there was also a suggestion that what is currently known as "Pass" should be renamed to "Execution Step" for clarity. We should consider this suggestion.
And then Pass would be renamed as TimeStep.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#1506?email_source=notifications&email_token=ACSHKGACDXJVFMKEKFODAKTRFVXRLA5CNFSM4LATKZ32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ISFBKVA>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACSHKGGQNHIP2SWCVPVPX23RFVXRLANCNFSM4LATKZ3Q>.
Currently, the finest grain TimeScale present in PsyNeuLink is TimeStep. This corresponds to "the execution of all Mechanisms allowed to execute from a single consideration_set of a Scheduler".
This is problematic in cases where a mechanism, such as an LCA, executes multiple times in a given TimeStep. In these cases, all executions of the mechanism in that TimeStep will be logged as occurring at the exact same Time.
To fix this, we should implement one finer grained TimeScale that represents the number of executions of a Mechanism within a given TimeStep. It was suggested that the name for this finer-grained TimeScale is implied to be "Call" by our Conditions (AfterNCalls, etc.), but there was also a suggestion that "Cycle" may be a better name.
As part of the effort of modifying Time in PsyNeuLink, there was also a suggestion that what is currently known as "Pass" should be renamed to "Execution Step" for clarity. We should consider this suggestion.
The text was updated successfully, but these errors were encountered: