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
{{ message }}
This repository was archived by the owner on Apr 25, 2026. It is now read-only.
Currently, the types of members of an Automaton struct are fixed: the dynamics is always assumed to be Float64, and the arrays are standard 1-based Vectors. That creates some inflexibility, particularly with regard to the recently-merged schedule synthesis work, which creates a whole extra _ConstructedAutomaton type that could be merged with the regular Automaton. To alleviate this inflexibility, and remove the duplicitous type, we should parameterize the Automaton type and make the schedule synthesis code use it throughout.
Currently, the types of members of an Automaton struct are fixed: the dynamics is always assumed to be Float64, and the arrays are standard 1-based Vectors. That creates some inflexibility, particularly with regard to the recently-merged schedule synthesis work, which creates a whole extra _ConstructedAutomaton type that could be merged with the regular Automaton. To alleviate this inflexibility, and remove the duplicitous type, we should parameterize the Automaton type and make the schedule synthesis code use it throughout.