Investigating additional stage axes. #1094
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm trying to investigate whether or not we will run into any issues with the multi-position table when additional stage axes are added.
After adding a new axis to the configuration file, I do see the axis listed in the multi-position table, but without any entries:

If I do not correctly specify the flip flags, I get this exception:
Traceback
To prevent this particular error from happening, I added a .get call that defaults to False.
If I run a multi-position acquisition with empty values, I get an exception.
Traceback
For this one, I wrapped the bottom_anticipated_images in a try/except statement.
And finally, after rebooting the software, and running a multi position acquisition, I get this error in the logs:
Traceback