-
Notifications
You must be signed in to change notification settings - Fork 7
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
fastq naming pattern hard coded? #16
Comments
Hi Phil, |
Hi Lachlan, It's a bit fiddly. This is what I've got working. Command line:
metadata file:
And then running it from within the directory with your fastqs in. |
Thanks Dr Flashington the 2003rd, |
Great, glad it helped! |
Hello,
Thanks for developing this tool for the community. I'm running BiG-MAP.map on some data and I had a problem getting the fastq sample names from the sample sheet to match up with the fastq paths given on the command line.
I eventually solved this problem by looking at the source code and seeing that you were getting the name from the fastq file name by splitting on underscores and taking the zero-eth item. Unfortunately my fastqs have underscores in the name, like this 32580_8#24_R2.fastq.gz. I could get BiG-MAP.map to run by re-naming my fastqs to be like 32580-8#24_R2.fastq.gz, but perhaps some other users might not dig in this far?
I know it's a nightmare dealing with all the different ways that people write the sample name in their fastq file names, perhaps you could include the path to the fastqs as an entry in the sample sheet?
Best,
Phil
The text was updated successfully, but these errors were encountered: