You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wish to pass a parameter to a protocol after it has been uploaded to the robot. This would allow things like changing how many wells are dispensed into without having numerous similar protocols.
What is the recommended way (if any) to pass parameters that can be read by a protocol file?
I can't see an obvious way of passing parameters to the protocol file when uploading a protocol (POST /protocols) or creating a run for a protocol (POST /runs) via the HTTP API.
Ultimately I want the protocol to be able to accept parameters like this:
fromopentronsimportprotocol_apidefrun(protocol: protocol_api.ProtocolContext, num_wells: int):
# use `num_wells`...
I noticed that protocol has a bundled_data attribute, but that only seems to be useable when uploading a protocol via the CLI and not the HTTP API, correct?
The text was updated successfully, but these errors were encountered:
Hey, I'm running into similar issues where I want to run multiple protocols dynamically after each other but want to use parameters to keep track of used tips, however the page you're referring too seems to be lost. Do you still have the working method or something similar that works?
I wish to pass a parameter to a protocol after it has been uploaded to the robot. This would allow things like changing how many wells are dispensed into without having numerous similar protocols.
What is the recommended way (if any) to pass parameters that can be read by a protocol file?
I can't see an obvious way of passing parameters to the protocol file when uploading a protocol (
POST /protocols
) or creating a run for a protocol (POST /runs
) via the HTTP API.Ultimately I want the protocol to be able to accept parameters like this:
I noticed that
protocol
has abundled_data
attribute, but that only seems to be useable when uploading a protocol via the CLI and not the HTTP API, correct?The text was updated successfully, but these errors were encountered: