jiwoongbio / FMAP

Functional Mapping and Analysis Pipeline for metagenomics and metatranscriptomics studies
Other
26 stars 12 forks source link

32 bit usearch memory limit error when using usearch in the FMP_download.pl #16

Open Anqi-Dai opened 4 years ago

Anqi-Dai commented 4 years ago

Hi, As I'm trying to run FMP_download.pl, I added usearch path. (Because I use a Mac, I can't use diamond).

I was wondering is it better to build usearch db for blast at this step or I can simply skip? Because when I use the 32 bit usearch (free of charge), I got the following error:

`2020-01-03 13:30:17 URL:https://qbrc.swmed.edu/FMAP/FMAP_data/database [46/46] -> "/Users/daia1/MSK/work/projects/FMAP/software/FMAP/FMAP_data/database" [1] 2020-01-03 13:41:10 URL:https://qbrc.swmed.edu/FMAP/FMAP_data/orthology_uniref90_2_2157_4751.20190806012959.fasta.gz [992986879/992986879] -> "/Users/daia1/MSK/work/projects/FMAP/software/FMAP/FMAP_data/orthology_uniref90_2_2157_4751.20190806012959.fasta.gz" [1] usearch v11.0.667_i86osx32, 4.0Gb RAM (34.4Gb total), 16 cores (C) Copyright 2013-18 Robert C. Edgar, all rights reserved. https://drive5.com/usearch

License: XXX@XXX.edu

00:10 2.3Gb 100.0% Reading /Users/daia1/MSK/work/projects/FMAP/software/FMAP/FMAP_data/orthology_uniref90_2_2157_4751.20190806012959.fasta 00:27 2.2Gb 100.0% Masking (fastamino) 01:02 2.2Gb 100.0% Word stats usearch11.0.667_i86osx32(33884,0x420080) malloc: can't allocate region mach_vm_map(size=268337152) failed (error code=3) usearch11.0.667_i86osx32(33884,0x420080) malloc: set a breakpoint in malloc_error_break to debug

/Users/daia1/projects/FMAP/software/usearch11.0.667_i86osx32 -makeudb_ublast /Users/daia1/MSK/work/projects/FMAP/software/FMAP/FMAP_data/orthology_uniref90_2_2157_4751.20190806012959.fasta -output /Users/daia1/MSK/work/projects/FMAP/software/FMAP/FMAP_data/orthology_uniref90_2_2157_4751.20190806012959.udb

---Fatal error--- Memory limit of 32-bit process exceeded, 64-bit build required`

Thank you and happy new year.

Angel

jiwoongbio commented 4 years ago

Can you please use "diamond" instead? If you use "usearch", there will be a restriction of the input size.