-
Notifications
You must be signed in to change notification settings - Fork 7
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
binner segment fault #54
Comments
Hello Sandro, the sample identifier is a string which you must pass via the command line. The CAMI binning format has a mandatory identifier in the header: The purpose of this identifier is to record unambiguously the data sample that you have processed, other than using a file name or external metadata. You can always use the Gruß Johannes |
thanks funds, layer 8 error, just an string for header output binner, the problem is that the same binner give me a segment fault error:
I did not find anything unusual in my gff (i attached the file). thanks in advanced |
Hi, I ran the binner binary from the extended package 1.3.3e with your attached gff3 file and the taxonomy which is contained in the refpack refseq-viral_67:
I did not get a segfault. Please make sure to run the same commands and check the logfile (default binning.log) for errors. I the problem persists, please report the exact version of the binner, for instance the git commit or release. We recommend to not use development but only the released versions. Gruß Johannes |
thanks @fungs, the tip with the binner versions works for me, I was using the lastet development version (cloning the repository), using last release (1.3.3), and the same command, works fine. |
Still needs to be fixed... |
Fix will be in next release, give meaningful error when -n argument is not given. |
Dears, doing the usage (using blast), and the files that you provide in
doing:
finish ok, But the next step, using binner the software crash
which is that identifier file?
i tried the fai,dmp from taxonomy, and both give segment fault (core dumped) error.
Regards
The text was updated successfully, but these errors were encountered: