-
Notifications
You must be signed in to change notification settings - Fork 119
molecular devices plate readers #715
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
also, very important, please update the list of supported machines! https://github.com/PyLabRobot/pylabrobot/blob/main/docs/user_guide/machines.md |
1675cd6 to
2b2f7f9
Compare
| Returns: | ||
| A list of dictionaries, one for each timepoint. Each dictionary has a key (0, 0) | ||
| and a value containing the data, temperature, and time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why key it by (0,0)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some readers allow wavelength filtering for luminescence and some don't. should we use 0 as key or something else?
| Returns: | ||
| A list of dictionaries, one for each timepoint. Each dictionary has a key (wavelength, 0) | ||
| and a value containing the data, temperature, and time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not use the wavelength as the key directly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't we want to have tuple as key for the sake of consistency among all read types?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indexing with ,0 is strange in the api. They are slightly different reads, I don't see why we would use the same format for all
|
ready to merge? |
|
we still have this problem: #715 (comment) right now if I merged this it would break all protocol using a plate reader, there needs to be a migration path |
|
is the change in the last commit (“format”) not enough?
…On Sat, Nov 8, 2025 at 20:44 Rick Wierenga ***@***.***> wrote:
*rickwierenga* left a comment (PyLabRobot/pylabrobot#715)
<#715 (comment)>
we still have this problem: #715 (comment)
<#715 (comment)>
right now if I merged this it would break all protocol using a plate
reader, there needs to be a migration path
—
Reply to this email directly, view it on GitHub
<#715 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BWQC2YVLV2NUZCKJUIDCD53333BEFAVCNFSM6AAAAACJKFKTLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMBXGUZDGMJYGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
my bad 😬 |
molecular devices spectramax plate readers: m5 and 384plus