-
Notifications
You must be signed in to change notification settings - Fork 4
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
More plate formats #29
Comments
Thanks so much for your interest in plater. Sorry for the lack of support
for your plate shapes! I was not aware of that 15-well shape.
I currently don't have any time to devote to developing plater. I'd be
happy to review a pull request if that's something you're able to
contribute. If not, could you please provide a list of the plate shapes you
need? I'll keep this issue open for next time I have some spare time to
devote to plater.
…On Wed, Dec 6, 2023 at 11:27 PM Angel Angelov ***@***.***> wrote:
Currently there is a very stringent check for the plate format, and some
existing plates are not supported.
For example a plate with 15 wells - 5 columns and 3 rows. Could this be
relaxed?
From what I can see, the number of rows and columns is inferred from the
plate_size argument of view_plate()
—
Reply to this email directly, view it on GitHub
<#29>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACQM25IZYCMCKFWPPFQ47WTYIFVXFAVCNFSM6AAAAABAKSZR5GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAZTAMBXGM4TQMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
OK thanks, I will give it a try... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there is a very stringent check for the plate format, and some existing plates are not supported.
For example a plate with 15 wells - 5 columns and 3 rows. Could this be relaxed?
From what I can see, the number of rows and columns is inferred from the
plate_size
argument ofview_plate()
The text was updated successfully, but these errors were encountered: