bug: Aspirating with "/runs/{run_id}/commands" does not lower the tip to proper location

[Xanngo]

bug: Aspirating with "/runs/{run_id}/commands" does not lower the tip to proper location

[SyntaxColoring]

Thanks for the detailed report.

When utilizing the "/runs/{run_id}/commands" to aspirate from a well, the tip is positioned just beneath the top of the well, rather than the anticipated location, which is directly above the well's bottom.

This is expected behavior when working with Protocol Engine commands, including the POST /runs/{id}/commands endpoint (docs). There, the default is top. This is different from the Python Protocol API, where the default is near the bottom, as you're expecting.

Inspection of the same command, but executed from a protocol created from the opentron app gives this result:
[...]
showing that the request params are the same, but the results are the ones expected.

Hm, yeah. I suspect that's a bug or limitation in the way we're translating old protocols (Python Protocol API v≤2.13, JSONv≤5) into the new command shapes. I suspect if you looked at the output of a new protocol, it would have the correct wellLocation.