Error when running qAlign from QuasR package for sequence alignment & QC.
Entering edit mode
Last seen 2.8 years ago

I'm trying to check the quality of my paired end read sequencing data. I am following this pipeline ( which uses QuasR in the first step.

My list of paired files is stoed in sampleFile. Currently this file cannot be read into the function. Not sure why.

Also open to using other alignment or QC pathways if I can align to multiple different genomes.

auxFile <- "Ref_Genomes/auxiliaries.txt"
sampleFile <- "./HCV_rna_paired.txt"
genomeName <- "BSgenome.Hsapiens.UCSC.hg38"
td <- tempdir()

proj1 <- qAlign(sampleFile, genome=genomeName, auxiliaryFile=auxFile)

Error: Cannot open ./HCV_rns_paired.txt

QualityControl Alignment QuasR • 842 views
Entering edit mode
Last seen 23 months ago

This is a bit confusing: the link you give above points to the cutadapt paper in the reference list of a paper about "ve-SEQ". The "ve-SEQ" paper seems to cite our QuasR package (reference 20), but my guess is that this citation is incorrect. The relevant text says:

"De-multiplexed sequence read-pairs were trimmed of low-quality bases using QUASR v7.01 [20] and adapter sequences with CutAdapt version 1.7.1 [21] and subsequently discarded if either read had less than 50b remaining sequence or if both reads matched the human reference sequence using Bowtie version 2.2.4 [22]."

The reason why I think this is a mixup is that there is no version 7.01 of QuasR (the current, most recent release version is 1.30). Also, QuasR does not support Bowtie version 2.

Could it be that the correct reference was , which describes the software (most recent version is 7.01 from June 2012)? Unfortunately the two have the same name...

In any case, the above error most likely indicates that the file "HCV_rna_paired.txt" does not exist in the current working directory of your R process (you can obtain that using getwd()).


Login before adding your answer.

Traffic: 515 users visited in the last hour
Help About
Access RSS

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6