Closed ckeeling closed 3 years ago
@ckeeling
Thanks for reporting the failure - I'll try to add code to handle this error. Although the best place is maybe when the liftOver failed (or after "Map contains 0 markers in 0 linkage groups").
However, it is a little strange that liftOver
uses this much RAM? Did you have a biggish .chain
file or .bed
file?
Haibao
Hello @tanghaibao
The .chain was 20MB and the .bed was 90KB. I am running ALLMAPS within a Singularity image. In the first case is was run in an environment with 8GB, and the second with 128GB; I didn't determine the minimum that was needed.
I see now an earlier still-open issue by @wolverineGT has a similar output.
Cheers, Chris
Hi I also encountered the same problem, how can I solve it? Thanks!
Hi, I've just encountered this problem when trying to plot a macrosynteny figure in MCScan.
SOLVED: Spaces in the seqids file. Removed them and it worked
Although the test data worked fine, I am getting an error near the end of this command with my own data. In this case I have only one csv file merged into the bed, but I get the same if I have two csv files:
Most of the files are generated, but not the plots.
The files unmapped and Steven.lifted.bed are made but are empty. If I run the following command alone, it gets "killed":
This was run with 8GB of RAM. When I repeated the python allmaps command with 128GB available, it finished properly. Thus, it seems that liftOver is being killed due to insufficient memory, and this failure is not being noticed or properly handled by allmaps. Maybe it could check if the lifted.bed file contains 0 markers in 0 linkage groups, and display an error.
Otherwise, awesome!