Hi Everyone,
I'm from a small Boston based company called Meenta, and we are launching a beta for our NovaSeq Runshare Program for a small cohort of users and hosts (think Uber Pool for NGS).
Initial versions will work like so: If you have a project coming up you can post and other researchers can find you. You can set your preferences for who you would share your flow cell with; internal to your university, read type, a specific flow cell type, number of samples etc.
Researchers can set their favorites so they get updated with new projects that match their watch parameters. When researchers are ready to share, we will have a ‘join’ and ‘invite’ process to allow the researchers to communicate. When a project is ready to go, they can choose a provider and submit a sample. Our core sample management features handle all the communications, shipping labels, tracking, and updates, as well as the split invoices, and data delivery.
But we need feedback on how best to help researchers find and share lanes, hence this beta project.
Apply here!
Why would someone want to do this rather than send samples to a company/core and have them do the work of ensuring the flow cells are filled?
Maybe cost and turnaround time is better?
I guess that's their hope. We'll see what happens.
Hi Devon, thanks for your question. In short, a lot of the companies/cores on the supplier side that we work with are academic cores where utilization rates of their instruments are generally low. They often don't have another project to run through at the same time which means the user eats the extra cost or has to wait even longer to get their data. When this is fully up and running the user will be able to book the RunShare on demand (as they currently can on our platform for a specific instrument/individual run - think of it as AirBnb for Genomic Sequencing).
Interesting, well I hope it works out :)
This would work only where a submitter is willing to start with samples not ready to run libraries. A core would be foolish to take a submitter at their own word, unless the participants are willing to share the cost of the MiSeq nano run (or perhaps your suppliers build that in) to check library compatibility.
Good point! Some suppliers do build in the MiSeq Nano run into their runs already. Keep in mind though that the application will allow a submitter to find a run with the right read length, read type and indices etc...matched to a given NovaSeq run...like Uber Pool where all the riders are going to the same destination with the same requirements. Would welcome your input as we build out the app...
You are assuming that users are going to have correct/provide right information. Seen too many people making errors with own metadata over the years :-) Very likely with index sequences.