Closed jdcla closed 1 year ago
Hi @jdcla if you want to report a bug, you need to use the template. On the bug tracker, "New issue" -> "Get started" (Bug report), fill the report accordingly. I cannot help you without minimal information needed to trace the problem.
Please increase the logging level to DEBUG
before opening an issue.
Looking at the periodic-offsets.csv
file you pasted above, the highest peak you get is 151, so you do not even pass the min_metagene_profile_count = 1000
filter. The problem is not with Rp-Bp, but with your data. This could suggest that your library didn't work, i.e. there is no evidence to support periodicity, unless maybe this is a downsampled data, etc.
Nevertheless, if you really want to use this data, or have good reasons to do this, there are a few options. You can change the default params in the config, or use fixed lengths and offsets, see Rp-Bp parameters.
Thank you eboileau, the problem was indeed with the data.
Running the full Rp-bp pipeline causes me to run into this error for multiple datasets I own.
An example file for which the current error occurs:
The command I run for the pipeline:
run-all-rpbp-instances ribo/${dataset}/out/rpbp/rpbp.yml --num-cpus 22 --logging-level INFO --mem 50G
However, I feel like this issue is not caused by something particular I'm doing wrong, but could rather be fixed by adjusting a parameter that improves the
xxx_-unique.periodic-offsets.csv
file. I am however at a loss right now.