More general purpose plate-related functions.

[BradyAJohnston]

Hello @seaaan !

I've been working on some other plate-adjacent packages. {plater} is fantastic for the reading of plate-based metadata and the like. I have having the need to have more general purpose plate-related functions for dealing with well IDs, column / row data and plate layouts and the like. I started compiling them into a more general-purpose utility package (currently {wellr}.

I thought before I go any further with it, I should ask if maybe incorporating into plater, or exposing some of the internal functions inside of plater might be the better way to go. My overarching idea would be to have a utility package that multiple different packages, such as plater and tidyqpcr could then utilise, to try and start ensuring consistent API etc across packages that are working on the same data types (plate-based data), and to have it come under the ropensci banner.

I'm open to any of your thoughts on the matter!

[seaaan]

Thanks so much for your nice message and interest in plater. I'm glad to hear that it's useful for you! I'm definitely happy to expose internal plater functions if they're useful for other packages. Or you're welcome to copy them into a general purpose package such as wellr. I definitely see the appeal of a utility package that could be used for multiple plate-related packages. My current schedule doesn't leave me with much time to work on plater, so I couldn't contribute to your efforts other than with enthusiasm!

…

On Wed, Aug 3, 2022, 10:31 PM Brady Johnston ***@***.***> wrote: Hello @seaaan <https://github.com/seaaan> ! I've been working on some other plate-adjacent packages. {plater} is fantastic for the reading of plate-based metadata and the like. I have having the need to have more general purpose plate-related functions for dealing with well IDs, column / row data and plate layouts and the like. I started compiling them into a more general-purpose utility package (currently {wellr} <https://rforbiochemists.github.io/wellr/>. I thought before I go any further with it, I should ask if maybe incorporating into plater, or exposing some of the internal functions inside of plater might be the better way to go. My overarching idea would be to have a utility package that multiple different packages, such as plater and tidyqpcr could then utilise, to try and start ensuring consistent API etc across packages that are working on the same data types (plate-based data). I'm open to any of your thoughts on the matter! — Reply to this email directly, view it on GitHub <#28>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACQM25K3FVBZYJ53CG65A6TVXNITDANCNFSM55RFYSDQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>