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

ATOS says it is ARMED but when pressing start, says not all objects are ARMED #602

Open
Angeleon opened this issue Oct 12, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@Angeleon
Copy link
Contributor

Describe the bug
Occasionally when running a scenario with more than 1 testobject, the state is reported as "ARMED", but when clicking on "Start" it reports "Not all objects are in state ARMED" (Not exact phrase). This has been found when ATOS is running a simulation, but there should be nothing in this that is simulation specific.

Rate of occurance: 2/30 times or so.

To Reproduce
Steps to reproduce the behavior:
Run a scenario with more than one TestObject
Initiate
Connect
Arm
Start

Sometimes this issue will occur.

Expected behavior
If ATOS shows state ARMED, all objects should be ARMED as well.

Branch or release information (please complete the following information):

  • Branch/release name: feature_simulationController, but should be present in dev and main as well.
@Angeleon Angeleon added the bug Something isn't working label Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant