I can only visually overlay my workflows over each other for now but if I were to construct a tool…
- Query the worktable at the start, during (major movements) and end of runs (alternate -comment to AuditTrail)
- Query the labware when it’s used and for how long (alternate - comment to AuditTrail)
- Generate a ton of run data
- Map the positional run data using something like Seaborn
First, if you’re not commenting actions to the AuditTrail, you absolutely should.
Second, abstracting your workflows so they’re programmatic also allows you to query in advance where things are and will be. If you’re dragging and dropping your commands into scripts, it’s tougher and your best bet is what I stated above.
Final boss challenge: parse the Logviewer Logs for positional data but eeesh.