-
Notifications
You must be signed in to change notification settings - Fork 8
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
Example project info file for paired end sequencing with >1 barcode and multiple lanes #27
Comments
Have you read the Get started section ? There is a section called project info file ... |
Hi Thierry, yes I did read this section, that's why I started the issue... You write (for the paired end setup):
and on the multiple lanes scenario (in the FAQ section):
but these descriptions don't provide enough details to understand how the file should be organised if one has multiple barcodes per sample or where the information about lanes should go if one has multiple lanes in an experiment. I know I can trial and error this, but it would be very helpful if one could see an example of the project info file for different setups. |
It seems |
I share the codes I use, but stackr is really just for my personal use and the collaborators I work with. If you used stacks before and went on to check the google group, you see it's almost a full time job... I'll clarify all of this on the readme page of the package so that there is no expectations. Sorry. Best of luck |
@jarekbryk @konopinski |
Hi,
it would be very helpful if you could provide an example project info file as the instructions are a bit unclear about what it should look like if one has multiple plates/lanes in the paired-end scenario. For example: should the file have another column called LANES?
Similarly, it would be very helpful to see how to add multiple barcodes per sample (ie scenario 5 in section 4.1.1 of Stacks manual) - should they be in the same column separated with some delimiter? Or should there be two columns for barcodes? If the latter, what should their names be?
A simple example file would clarify this :-)
This looks like a very exciting way to "tidy up" a typically messy Stacks workflow. Thanks a lot!
The text was updated successfully, but these errors were encountered: