Closed faye-romero closed 10 months ago
@faye-romero
The error suggests that there is a record in the BED file that has start > end.
Would you please check this in your mybedfile.bed
? start
is the 2nd column and end
would be the 3rd column.
The faulty line would have 0
in the 2nd column and 0
in the 3rd column, change the end
to 1
like below.
-seq 0 0
+seq 0 1
@tanghaibao ,
Thank you for the quick reply. I have many lines in mybedfile.bed
that look like this:
* 0 -1 mylinkagemap-39:24.154000 *:-1
* 0 -1 mylinkagemap-39:24.179000 *:-1
* 0 -1 mylinkagemap-39:24.179000 *:-1
* 0 -1 mylinkagemap-39:24.179000 *:-1
....
I am assuming these entries are results of markers that were not able to be mapped to my draft genome (i.e. see these matching entries in mylinkagemap.csv
):
#Scaffold ID, scaffold position, LG, genetic position
*,-1,39,24.154
*,-1,39,24.179
*,-1,39,24.179
*,-1,39,24.179
...
Should I just create dummy scaffold names for all of these entries, and replace any -1
values with 0
? Or just remove the entries entirely?
Please note that I am attempting to use ALLMAPS with several draft genomes generated via different methods. This particular draft was generated using hifiasm trio-binning, so it's a maternal-haplotype-resolved assembly; only 97% of markers were successfully mapped. When I use ALLMAPS on the hifiasm primary assembly, I do not run into this issue, as 99.9% of markers successfully map.
@faye-romero
If these markers don't have scaffold position then they won't contribute to scaffolding. Just remove those for now.
@tanghaibao , that did the trick. Thank you for your help.
Hello @tanghaibao, I am getting the following error when trying to run
jcvi.assembly.allmaps path
:I have used ALLMAPS extensively with success in the past and have only come across this error today. Currently,
jcvi.assembly.allmaps merge
works just fine, and I have been able to generate the weights file and the input .bed file with no problem. I have also set jcvi and liftover in my path. Any help would be much appreciated trying to debug this error.