Closed leetamm2 closed 1 year ago
Hello again,
I tried running tinyRNA with just the file that was able to get through fastp as mentioned above. It was able to get through the bowtie steps but the same error message came up when it reached tinycounts (I also tried resuming run by using tiny recount):
(tinyrna) Tammy@Tammys-MacBook tinyrna_2023-01-13_11-27-35_run_directory % tiny recount --config run_config.yml
Resuming pipeline execution at the tiny-count step...
[2023-01-13 11:32:41] INFO /Users/Tammy/miniconda3/envs/tinyrna/bin/cwltool 3.1.20220628170238
[2023-01-13 11:32:41] INFO Resolved '/Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl' to 'file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl'
[2023-01-13 11:32:43] INFO [workflow ] starting step counter
[2023-01-13 11:32:43] INFO [workflow ] start
[2023-01-13 11:32:43] INFO [step counter] start
[2023-01-13 11:32:43] INFO [job counter] /private/tmp/docker_tmpb3j87co4$ tiny-count \
-p \
-nh \
true \
-o \
tinyrna_2023-01-13_11-32-40 \
-pf \
/private/tmp/docker_tmpcod7gxea/stgd4d8bd31-0c68-4170-8cf1-b00779ea7133/paths.yml \
-sv \
Cython > /private/tmp/docker_tmpb3j87co4/console_output.log
Traceback (most recent call last):
File "/Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/rna/counter/counter.py", line 249, in main
counter = FeatureCounter(gff_files, selection, **args)
File "/Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/rna/counter/features.py", line 36, in __init__
Features(*reference_tables.get())
File "/Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/rna/util.py", line 26, in wrapper
return_val = func(*args, **kwargs)
File "/Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/rna/counter/hts_parsing.py", line 490, in get
raise ValueError("No features were retained while parsing your GFF file.\n"
ValueError: No features were retained while parsing your GFF file.
This may be due to a lack of features matching 'Select for...with value...'
tiny-count encountered an error. Don't worry! You don't have to start over.
You can resume the pipeline at tiny-count. To do so:
1. cd into your Run Directory
2. Run "tiny recount --config your_run_config.yml"
(that's the processed run config) ^^^
[2023-01-13 11:33:36] INFO [job counter] Max memory used: 61MiB
[2023-01-13 11:33:36] ERROR [job counter] Job error:
("Error collecting output for parameter 'alignment_stats': ../../../miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/tools/tiny-count.cwl:116:7: Did not find output file with glob pattern: '['tinyrna_2023-01-13_11-32-40_alignment_stats.csv']'.", {})
[2023-01-13 11:33:36] WARNING [job counter] completed permanentFail
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/feature_counts
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/rule_counts
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/norm_counts
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/mapped_nt_len_dist
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/assigned_nt_len_dist
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/alignment_stats
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/summary_stats
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/console_output
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/decollapsed_sams
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/intermed_out_files
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/alignment_diags
[2023-01-13 11:33:36] ERROR [step counter] Output is missing expected field file:///Users/Tammy/miniconda3/envs/tinyrna/lib/python3.9/site-packages/tiny/cwl/workflows/tiny-resume.cwl#counter/selection_diags
[2023-01-13 11:33:36] WARNING [step counter] completed permanentFail
[2023-01-13 11:33:36] INFO [workflow ] completed permanentFail
{
"counter_out_dir": null,
"dge_out_dir": null,
"plotter_out_dir": null
}
[2023-01-13 11:33:36] WARNING Final process status is permanentFail
Thanks again!
Hey @leetamm2, thank you for reaching out.
The majority of the terminal output produced by the tiny
command comes from the workflow runner, cwltool, which doesn't have any special knowledge about the tools it runs in each step so the errors it produces are fairly generic.
Most tools have their terminal output redirected to a log file for auto-documentation. This output is fully captured for third party tools and partially captured, allowing errors through, for tinyRNA tools. The CWL specification doesn't currently support redirecting output to a log file and to the terminal, but I have contacted the CWL team proposing a new capture method that would make this situation more user-friendly.
The terminal output you included does not indicate that any fastq files completed quality filtering. The workflow runner indicated that it was preparing a second fastp job, but the first job immediately exited so the workflow runner terminated the workflow before the second job could begin. fastp returns 255 for all errors so we'll need to see what it said:
verbosity: debug
and save it.tiny run
again using this Run Config. This will generate a lot of terminal output. 2>
. The path to the fastp log file will be printed after this token.open {path}
in your terminal, where {path} is what you copiedverbosity: normal
in your Run Config once you're done. Otherwise large intermediate files will be left in your temporary files directory.This will allow you to see the specific error fastp encountered.
While "Error collecting output for parameter" was also included in this output, this isn't the same issue as your first post; it's a generic error from the workflow runner. Since this step is a tinyRNA tool, error messages are printed on the terminal and if you look a little further up in the output you'll see:
ValueError: No features were retained while parsing your GFF file.
This may be due to a lack of features matching 'Select for...with value...'
This means that there is an incompatibility between the selection rules in your Features Sheet and the features in your GFF file. You may be selecting for GFF column 9 attributes that aren't present, or you may be using filters for sources/types (GFF columns 2 and 3) that aren't present.
We intend to streamline this debugging process in a future release to make it more user friendly
Hi @AlexTate ,
Thanks for the prompt response.
I've followed the steps you've suggested and was able to open the log files:
for my first file there seems to be a decompressing error:
Detecting adapter sequence for read1...
ERROR: igzip: encountered while decompressing file: /private/tmp/docker_tmpru2e279a/stg685defcb-b2ed-4c9f-bcc6-01d4abf0111f/Batch1SAMP_S1_L001_R1_001.fastq.gz
Does this suggest that my file is corrupted?
You're right, the exact ValueError appeared for my second file. I'm quite new to sequencing analysis so my apologies in advance, is there an example of how the features.csv should be set up? I kept everything default since I wasn't sure what to select for.
Thanks again for your help!
Hi @leetamm2, If you email us your GFF/GTF file and your features.csv we would be happy to help troubleshoot the counting issue. See the tinyRNA preprint on biorxiv for my email address. In regards to the fastq file, you may want to try decompressing it with the command "gzip -d file_name" and then count the number of lines with "wc -l file_name". If you divide the number returned by wc by 4, it will give you the number of reads. If the number of reads is not what you expect based on the sequencing report (assuming you have access to it), or if you get a decimal number (which would indicate the file is truncated assuming it doesn't have any header lines), or if the "gzip -d" command throws an error, then the file was likely corrupted. Let us know and we can help you with that as well.
Closing issue due to inactivity
Hello,
I've ran into an error: "Error collecting output for parameter" while running tinyrna on my mac
Basic description of the error
I have two small RNA-seq sequencing files that I would like to process using tinyrna. After completing the samples.csv, features.csv and updating paths.yml, I ran the run_config.yml as instructed. My first fastq file was processed but the second one failed to go pass the fastp step. Maybe it's an issue with my files?
Environment
Operating System: Mac OS Monterey tinyrna version: v1.2.1
Reproducible example
My fasta files are too big to attach but I can email it.
Input configuration
Error message and traceback
Thank you!