Skip to content
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

Detect ARB database type (fail on pt server internal type) #73

Closed
gdauria opened this issue May 15, 2019 · 3 comments · Fixed by #82
Closed

Detect ARB database type (fail on pt server internal type) #73

gdauria opened this issue May 15, 2019 · 3 comments · Fixed by #82
Milestone

Comments

@gdauria
Copy link

gdauria commented May 15, 2019

Dear Sir/Mrs,
I have an issue on using sina-1.6.0.
I do not know if this is the right place but I started an arb_pt_server and trying to assign a whole gene 16S sequence I have back always the same error: 21:01:28 [align] Internal error - incomplete data for alignment

./sina -i test.fasta -o test.sina --ptport=:/home/user/tmp/pt_ssu_1 --db /home/user/ramDisk/SSURef_NR99_123_SILVA_12_07_15_opt.arb --search --search-db /home/user/ramDisk/SSURef_NR99_123_SILVA_12_07_15_opt.arb --search-port=:/home/user/tmp/pt_ssu_1 
21:01:26 [SINA] This is SINA 1.6.0.
21:01:27 [SINA] Aligner ready. Processing sequences
21:01:28 [align] Internal error - incomplete data for alignment
21:01:28 [SINA] Took 1.407s to align 1 sequences (0.710342 sequences/s)
21:01:28 [SINA] SINA finished.
Processing: 100% |--------------------------------------| 1/1 [00:00:01 / 00:00:00]
21:01:28 [ARB I/O] Closing ARB database '"/home/user/ramDisk/SSURef_NR99_123_SILVA_12_07_15_opt.arb"' ...

I started the arb_pt_server from the sina-1.6.0 folder using following command:
bin/arb_pt_server -D/home/user/ramDisk/SSURef_NR99_123_SILVA_12_07_15_opt.arb -T:/home/user/tmp/pt_ssu_1

Everything seems fine having the following last lines:

Building PT-Server for alignment 'ali_16s'...
Database contains 597607 species
Progress: Checking data
...................................................................... [100.0%] used: 0s
[done]
- mapping ptindex ('/home/gdauria/ramDisk/SSURef_NR99_123_SILVA_12_07_15_opt.arb.pt', 1.85 Gb) from disk
[startup took 24m43s]
ok, server is running.

I do not have any clue about what is wrong.

Thank you for your help

Giuseppe

@epruesse
Copy link
Owner

Hi @gdauria!

Thanks, this does look like a regression. I will have a look into it. Running with an externally launched PT server wasn't on my list for testing and may have a bug.

Is there a reason you want/need to do it that way? The 1.6.0 comes with an internal replacement for the PT server, so you can just run this:

./sina -i test.fasta -o test.sina --db /home/user/ramDisk/SSURef_NR99_123_SILVA_12_07_15_opt.arb --search 

Or, you can just allow SINA to launch and terminate the PT server internally by not specifying the --pt-port and --search-port options.

I'd recommend the internal PT server replacement. It's much faster, has equivalent accuracy and you don't have to bother with launching things separately. The PT server option is in there mostly so you can compare results between the old and new approaches still having the old mechanics available. It also has a few more options, but you aren't using any of those (and in my experience they don't help anyway).

@gdauria
Copy link
Author

gdauria commented May 16, 2019 via email

@epruesse
Copy link
Owner

epruesse commented Dec 5, 2019

Ok - I figured out what the cause of this was.

The arb_pt_server will (in ARB >6) compress the ARB database it is given, so by running arb_pt_server -Dmydb.arb -T:some.sock, mydb.arb got turned into something that isn't a normal ARB database. And then SINA failed to work with that.

=> Detect if an ARB database is actually legit.

@epruesse epruesse added this to the 1.6.1 - bug fixes milestone Dec 5, 2019
@epruesse epruesse changed the title Internal error - incomplete data for alignment Detect ARB database type (fail on pt server internal type) Dec 5, 2019
@epruesse epruesse modified the milestones: 1.6.1 - bug fixes, 1.7.0 Mar 12, 2020
@epruesse epruesse mentioned this issue Mar 13, 2020
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants