-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
segfault #16
Comments
Memory looks fine, checked again, reran allowing 480gb of RAM and less than 100 GB was used. Different segfault this time I believe.
|
+1 Same issue during trimming running on a 60X pure ONT mammalian (~2gb) genome with 96 cores.
Non default parameters on the config file:
As a side note when running the bridge or assemble commands the pipeline repeats the previously completed steps (not sure if this is intended behavior). As a workaround I manually modified the necat.pl file commenting out the completed steps:
|
Also encountering this issue during polishing on a 30X * 2.3Gbp plant genome. Running on a single node with 86 threads / 512GB RAM. STDOUT
STDERR
|
+1 Same issue, segmentation fault (core dumped) during the assembly step with v0.0.1_update20200803, single node of 48 cpus and 187 Gb. Did you ever figure out a solution @colindaven @ppapasaikas or @evanrrees ? Do you have any suggestions @xiaochuanle ? |
It seems the authors don't care at all. I'd use other software. |
I am getting an error running
srun -c 56 necat.pl assemble pig2.txt
This is a ca. 18X pure ONT (2019-2020) pig dataset.
Could it be a memory issue ? How can I create a minimal testset of data to find the segfault ?
The command running is something like:
25741 rcug 20 0 71.411g 0.067t 3092 S 5014 13.6 707:23.15 /mnt/ngsnfs/tools/necat/NECAT/Linux-amd64/bin/oc2asmpm -n 100 -z 10 -b 2000 -e 0.5 -j 1 -u+
The text was updated successfully, but these errors were encountered: