Skip to content
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

Support for GridION runs #2

Open
dfornika opened this issue Sep 14, 2022 · 0 comments
Open

Support for GridION runs #2

dfornika opened this issue Sep 14, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@dfornika
Copy link
Member

We will be increasing our usage of the GridION sequencer in the near-term.

To consider:
There is not (to my knowledge) a standard SampleSheet format for GridION runs that allows us to easily match up which sample used which barcode, and which sample belongs to which project.

It could be done with a simple .csv file with the following fields:

sample_id
barcode
project_id

...but that file would need to be deposited with a standard filename and in a standard location for each run.

The GridION also outputs a set of raw fastq files for each barcode, but it does not aggregate them into a single fastq file per barcode. That needs to be done by some downstream processing step. Should that happen before or after the run is uploaded? What should the directory structure and naming conventions be for those aggregated fastq files?

@dfornika dfornika added the enhancement New feature or request label Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant