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

Refactor and cleanup statemachine #30

Open
gnthibault opened this issue Dec 30, 2022 · 1 comment
Open

Refactor and cleanup statemachine #30

gnthibault opened this issue Dec 30, 2022 · 1 comment

Comments

@gnthibault
Copy link
Owner

We expect that one can easily change the states, so it means that NO mention to explicit next_state should be found anywhere in the state python file.
The idea is:

  1. Do a large "merge" to get all changes from original project, that might require even rewritten project history: https://github.com/panoptes/POCS
  2. Refer to a generic transition in python code, and expect the destination state to be defined in the state yaml file.
    Example: call
    tracking_ok_trigger
    or
    tracking_error_trigger in the code, and in the config yaml have something like:
    -
        source: tracking
        dest: focusing
        trigger: tracking_ok_trigger
        conditions: mount_is_tracking

or

    -
        source: tracking
        dest: focusing
        trigger: tracking_error_trigger

@gnthibault
Copy link
Owner Author

Please checkout: https://github.com/AstroHuntsman/

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

1 participant