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

Analysis of Paired-end reads #440

Closed
oliverdesousa opened this issue Sep 25, 2024 · 1 comment
Closed

Analysis of Paired-end reads #440

oliverdesousa opened this issue Sep 25, 2024 · 1 comment

Comments

@oliverdesousa
Copy link

Hi, I am trying to run the pipeline using the paired-end miRNA reads given to me for analysis. I have used the below structure for my CSV file for the input.

sample, fastq_1, fastq_2
clone1, path/to/fwd/read/clone1_1.fastq.gz, path/to/rvs/read/clone1_2.fastq.gz
...

When I have attempted to run with the below command it provides an error when running miRtrace. The error seems to be a problem with the input miRtrace is receiving - "ERROR ~ Unknown method invocation getFileName on ArrayList type". The custom config I have just has memory and CPU specifications.

sudo nextflow run nf-core/smrnaseq
-profile singularity
--input test_38.csv
--genome 'GRCh38'
--mirtrace_species 'hsa'
--protocol 'illumina'
--outdir pipe_output/
-c nextflow.config

Is there something i am doing wrong when trying to run paired-end reads or is there a specific way to do this?

@apeltzer
Copy link
Member

Just as a side node to some of the points you mentioned there:

  • The pipeline should only use SE data, not PE - the read length of a SE read is already longer than what we target to analyze - the fastq_2 is therefore not considered
  • There is an open PR Fix paired end sample handling #439 that fixes some feedback / handles some logic errors, will be in dev very soon
  • If you use -r dev to run the pipeline and remove the fastq_2 entries, the pipeline should already run fine

And please don't run the pipeline with sudo, this is not necessary and if it does, there should be some misconfiguration happening on your system.

If the problem persists, please let us know and re-open the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants