More complex paths in exerciser tool

[EvanKirshenbaum]

This one has been on my whiteboard for a while, but I just got a request for it from Corey Downs (who doesn't yet have a GitHub account).

The path task in the joey/wombat exerciser tool allows you to specify a simple path for a drop to walk, but it would be useful to be able to specify more complex paths that allow more than one thing to happen on a tick and to specify actions on well pads and gates in addition to board pads. This last will be crucial for debugging dispensing sequences.

This could be done on the command line, by having a more complex syntax for the --path option or it could be done by having a task that read an external file (probably of the same form that would be written by the macro recording tool envisioned in #32). This would allow an actual language (spec'd in antlr4?) to make the specification less cryptic.

I'll probably want to investigate both approaches--first get a simple (if ugly) command-line way to deal with well pads/gates and have things happen at the same time and then do a more complex read-from-a-file approach.

Migrated from internal repository. Originally created by @EvanKirshenbaum on Aug 03, 2021 at 1:56 PM PDT.

[EvanKirshenbaum]

This issue was referenced by the following commits before migration:

• d58f3f33ab8476434f6b4212d3a7c0aa4e9bb454 by @EvanKirshenbaum on Aug 18, 2021 at 11:02 AM PDT
• 4535164c4564bde1036b4259b273ef3a33dd4336 by @EvanKirshenbaum on Sep 04, 2021 at 4:45 PM PDT
• 2215f78fc74d78b92e57f81a96e5be3ec249ae9e by @EvanKirshenbaum on Sep 09, 2021 at 9:52 AM PDT
• b89dfcc2f44bbfbcc10a3fab6d2e653c1ebf88cd by @EvanKirshenbaum on Sep 10, 2021 at 4:29 PM PDT
• eefec3317deb6c682988071e800a3904ddafdc88 by @EvanKirshenbaum on Sep 12, 2021 at 10:57 AM PDT
• b5542e05c29c2cde34b1161e00ac9e1c05a403aa by @EvanKirshenbaum on Sep 14, 2021 at 10:36 AM PDT
• 3b411f63abcc6003a9dc412531b6c2f6747d6e22 by @EvanKirshenbaum on Sep 16, 2021 at 3:22 PM PDT
• f5ddffdc04176822740862077981651749338b7a by @EvanKirshenbaum on Sep 19, 2021 at 8:55 PM PDT
• e01ec8b83015fb3aa769053eb31e375bf49395be by @EvanKirshenbaum on Sep 21, 2021 at 2:43 PM PDT
• a840fb8926c3f8e07dc4de32e2fb587504945ea2 by @EvanKirshenbaum on Sep 22, 2021 at 10:34 AM PDT
• f909dd6c92a6e24559a9abec9bf02cf045b28f82 by @EvanKirshenbaum on Sep 23, 2021 at 5:07 PM PDT
• 749c0e9dea97f0fca568275e91cc343cf8aa3334 by @EvanKirshenbaum on Sep 24, 2021 at 10:23 AM PDT
• 549892acf4ee9e68e70df6cd66cb153d1a82d43e by @EvanKirshenbaum on Sep 24, 2021 at 1:44 PM PDT
• f79dcf0cf2bda9c7fcd43093200ba417035df3d6 by @EvanKirshenbaum on Sep 27, 2021 at 12:13 PM PDT
• a972f6cdecf85fe4d9b476eb3ed255581d79df54 by @EvanKirshenbaum on Oct 01, 2021 at 3:32 PM PDT
• 58f9217980d35d6007874d19bbd005a6a50b9038 by @EvanKirshenbaum on Oct 03, 2021 at 1:27 PM PDT
• 31f0cca03becc5a3010a06cdaacd2c80af4dec8f by @EvanKirshenbaum on Oct 07, 2021 at 1:18 PM PDT
• d4103c7fe73d09e5df49ae82627787756bfef5fd by @EvanKirshenbaum on Oct 08, 2021 at 5:22 PM PDT
• 79eb2bbe401bf7cfe0700ef9fe82bbc45bb2f552 by @EvanKirshenbaum on Oct 25, 2021 at 9:58 AM PDT
• 15ffab981a464c77f7d61529a96b8dc503ff6d10 by @EvanKirshenbaum on Oct 28, 2021 at 11:17 AM PDT
• 7bfbc2957a3bb4be0be9c970ae47a76525a4a79b by @EvanKirshenbaum on Oct 29, 2021 at 2:42 PM PDT
• 7b72cc71081c0428cb0cb723fa062b233efeed33 by @EvanKirshenbaum on Nov 01, 2021 at 11:39 AM PDT
• ff679a5c4ee47b17993dae6cefa848ca55472441 by @EvanKirshenbaum on Nov 09, 2021 at 2:47 PM PST
• 2957021bb936dc3d43f566416c6839aa9e939a33 by @EvanKirshenbaum on Nov 13, 2021 at 10:31 AM PST

[EvanKirshenbaum]

There's now a working macro language and a text box to type expressions in the GUI. According to Corey, it's actually useful.

I'm going to capture a few to-dos here so that I can clean off my whiteboard, and I'll try to work through them quickly and close up this issue. Any of these that hits any real difficulty should probably be opened as an issue of its own.

• [ ] Add a "reload" box to the GUI so that the macro file can be edited off-line and reloaded.
  • Open question of what to do with variables in the environment. I suspect that what I should probably do is reload to a new environment, and then copy over any bindings from the old environment that weren't overwritten. (But this may screw up bindings to macros that depend on names that had been bound to other types. (Do I have to keep track of external dependencies for macros?)
• [x] Add more param types for macros.
  • Currently have drop, pad, well, and int. Should add all the rest.
• [x] Check to make sure that there's only one unnamed param of a given type.
• [x] Add op to remove drop from board (e.g., when entering a well). Maybe both "removed from board" and "entered well"
• [x] Ensure (either in emitted code or in general motion op) that an error is signaled if a drop isn't on the board when moved.
• [x] Add general attributes (e.g., x, y, dist, state) rather than having separate rule lines.
  • Will probably mean a new enum/ish with allowed object and return types, maybe generation function.
• [x] General conditional statement
• [x] Comparison operators (e.g., ==, <)
• [x] floats
• [ ] loops
• [x] explicit type decls on variables (rather than just using the manifest type of the expr).
• [ ] Possibly drop inference (a la what happens on mouse clicks).
• [x] Directions as actual values
• [x] Function calls using computed macros rather than just names.
• [x] Print strings and values
• [ ] Rows and columns as types
• [ ] Need to do a serious look at precedence order in expression rules.
• [x] Computed delta expressions (in dir d)
• [x] "Maybe" types and "has attr" expressions.
• [ ] "is property" expressions.

  Migrated from internal repository. Originally created by @EvanKirshenbaum on Sep 23, 2021 at 10:36 AM PDT.