I am afraid the answer to both questions is no.
Here’s a list of things that come to mind:
- Besides the warning for resources that are exceptionally high, some commands are marked “unsafe”. E.g. the backend_kwarg
use_unsafe_hotel
ofSTARBackend.pick_up_resource
(this method extends the iswap outside of the chasis). - Another one is
STARBackend.move_channel_y
has a check to make sure you don’t crash into other channels. It raises an error if that would happen. - With tip tracking enabled, we raise errors when we think you’re about to drop a tip in a location where we think a tip already exist
- Similar for picking up a tip with a channel that already has one
- There is a check for colliding resources on the Deck level
is there a specific issue you have experienced in the past that can be avoided with nice checks?