Hey, I have an error from HISAT2. Some of the samples are errors and others have this: [Capture3] Auto-detect is actually heplful. HISAT2 runs again on my sample and the second times it works. One question: Why and how? It affects my results in any way? It says “This will inspect the dataset and…

This was probably a small server glitch with setting the metadata. Re-detecting metadata can help (pencil icon > Edit attributes > Datatype). [image] Sammy: It affects my results in any way? Hard to say. You might try rerunning a few and compare. Assuming that you already checked your inputs…

I will come back to this topic with some new informations. So I ran once more the failed samples with autodetect which solved the problem and I rerun the same samples again in HISAT2. This time just one out of five samples requred another auto-detect. The other four ran just fine from the first try …

The zoom scaling looks a bit off, so is not a direct comparison or I am missing something… Mappers are dynamic. Meaning, you will not always get the same exact results each run, in Galaxy or line-command.

[image] jennaj: Mappers are dynamic. Meaning, you will not always get the same exact results each run, in Galaxy or line-command. Thank you. This is actually helpful information. I ran a sample on HISAT2 and Bowtie2 and the differences (besides the splices) were quite rare. More like this (wh…

Just as a note, I’ve been getting the same error with HISAT2, I don’t know why but it happens to my bam files randomly when they are in a queue to be processed further downstream. For example : I had HISAT2 running, and then set up a FeatureCount to take place on the generated bam file (that was c…

Hi @valie_15 There were some server issues at Galaxy Main recently. Please try rerunning now.

Galaxy Community Help

HISAT2 error: Auto-detection

usegalaxy.org support

metadata

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled