Closed skchronicles closed 8 months ago
Also, here is the command that was run if you want to try to reproduce the error on your side:
$ sicer -t chip.bed -c input.bed -s hg38 -rt 100 -w 300 -f 168 -egf 0.75 -g 600 -fdr 1E-2 -cpu 8 -o .
If you want, I can also submit a PR with the fix. Please let me know what you think, and have a great evening!
@zanglab @jinyongyoo I submitted a PR with a fix.
Please see: https://github.com/zanglab/SICER2/pull/25
Hello there,
I hope you are having a great day, and that all is going well on your side! Thank you for creating and maintaining this awesome tool. SICER2 is an awesome broad peak caller.
While running SICER2, I ran into the following error:
After looking at the traceback, I was able to trace the error message to here: https://github.com/zanglab/SICER2/blob/15fdbf03d3477c5069efb2556956feee97fb990a/sicer/src/remove_redundant_reads.py#L109
My input BED files contains
.
characters in the score column of the file, which is causing a ValueError when the score dtype is set tonp.int32
.Here is a preview of my input BED files:
I was able to test/debug this from my side. I can reproduce and fix the error by changing the score dtype to an unicode string of length 6:
For the time being, I have just edited my file to replace any
.
chars in the score column to0
. With that being said, I just wanted to confirm if that is okay. Are you internally using the information in the score column anywhere? I just want to confirm that setting it to 0 will not cause any unwanted side-effects.Please let me know what you think.
Best regards, @skchronicles