Page 1 of 1

Primatologist crash due to sql problem

Posted: Wed Feb 14, 2018 3:50 pm
by Olivier Coulon
Hello,
although my question is related to the new Primatologist toolbox, I am asking it here because Primatologist comes with BrainRat. Let me know if you want me to post it on the BrainVsa forum.
So I have installed Brainvisa 4.6 on an Ubuntu14.04 machine, as well as on a Debian machine. I tried the primatologist pipeline on both machines with several T1 or T2 macaque images. Every time, the pipeline crashes during the "Atlas Registration -> Transform Application" step, returning the following error :
<class 'sqlite3.OperationalError'>: too many SQL variables
The log says:
DatabaseError
processes.py (3172) in _processExecution:
controller.delete_workflow(wid, True)
client.py (578) in delete_workflow:
return self._engine_proxy.delete_workflow(workflow_id, force)
engine.py (904) in delete_workflow:
self._database_server.delete_workflow(workflow_id)
database_server.py (1484) in delete_workflow:
self.clean()
database_server.py (579) in clean:
raise DatabaseError('%s: %s \n' % (type(e), e))
Do you have any clue what's happening ?
Thanks in advance,

Olivier

Re: Primatologist crash due to sql problem

Posted: Mon Feb 19, 2018 3:59 pm
by riviere
Hi,
Is the problem specific to Primatologist ? It seems to have problems using the sqlite database of Soma-Workflow, so I wonder if the soma-workflow database didn't get corrupted or something.
If you are using local computing, you can exit brainvisa, and remove the file(s) $HOME/.soma-workflow/soma_workflow*.db
(you can also cleanup remaining temporary transfer files $HOME/.soma-workflow/transfered_files/*/*)
then restart.
If you are using remote (client/server) computing you can use soma_workflow_gui, in the connection dialog, there is a button to kill the servers and remove the database.
If the problem is still here, we'll have to investigate deeper...
Denis

Re: Primatologist crash due to sql problem

Posted: Mon Feb 19, 2018 5:01 pm
by Olivier Coulon
Thank you for your answer, Denis, it did fix the problem.
I tried on my Ubuntu machine.
I will try on the Debian, if it does not work I'll let you know but I don't see why not.

Olivier