I have installed FIRMM v2.1.3. When the main window comes up and I press start it displays Initializing Startup Routine at the top and hangs. Any ideas for debugging?

Hi Christopher,

Do you have a screenshot or a copy/paste of the output coming from your terminal? That would definitely help in elucidating your issue.

-Andrew

Thanks for your quick response.
I have attached a screenshot. I have just pressed the start button. There are no error messages that appear.
The test option -t causes some filenames to be printed to the console but when I press start it still stalls at initialising.
I have tested this on ubuntu 16.04, 18.04 and centos 7, the same thing happens.

What is it waiting to do? Does it require a port to be open?

What can I do to increase debug info?

Christopher,

Thanks for trying FIRMM!  We are happy to help either here on the forums or over email at info@firmm.io.  That message and the stalling means that either FIRMM may have been started before you had any folders streaming into your SAMBA shared directory between the SIEMENS scanner and the FIRMM PC OR there is a folder in the SAMBA share, but none of the DICOMs are EPI sequences yet.  I feel the former case is more likely, given your screenshot, as I would expect to see patient info in your Patient Info Table had it found the folder and SIEMENS DICOMs were there.

As for debug info, we don't suppress any important status messages so what you see in the terminal is all the relevant troubleshooting information.  Standard status messages are what go into the blue status bar above the FD plot in the web interface.

Side note: If running "FIRMM -t" works, then FIRMM is operating correctly and it is using the appropriate port forwarded through the FIRMM Docker image.  Unfortunately, you will need to test whether the scanner is able to stream DICOMs to the SAMBA share separately.

~Eric

Originally there were some shortcut files in the incoming directory. I deleted them, then ran FIRMM and it still got stuck. The FIRMM process pegs 1 cpu at 100% usage.

At the moment I haven't got it connected to a scanner, I'm just going to copy existing files into the incoming directory ala. the test method.

What should I be seeing in the status window?

Thanks for the help.

FIRMM -t does not work, I get the same problem.

The output on the console follows:

********************************************************
*
* machine = firmmproc-VirtualBox
* incoming dir = /home/firmmproc/FIRMM/incoming
* outgoing dir = /home/firmmproc/FIRMM/outgoing
* django dir = /home/firmmproc/FIRMM/django
* resampling to 4mm = Yes
*
********************************************************

../test/dicom/003_image_0001.dcm
../test/dicom/003_image_0002.dcm
../test/dicom/003_image_0003.dcm
../test/dicom/003_image_0004.dcm
../test/dicom/003_image_0005.dcm
../test/dicom/005_image_0001.dcm
../test/dicom/005_image_0002.dcm
../test/dicom/005_image_0003.dcm
../test/dicom/005_image_0004.dcm
../test/dicom/005_image_0005.dcm
../test/dicom/007_image_0001.dcm
../test/dicom/007_image_0002.dcm
../test/dicom/007_image_0003.dcm
../test/dicom/007_image_0004.dcm
../test/dicom/007_image_0005.dcm
mv: cannot stat '../django/live_JSON/*.json': No such file or directory

I just downloaded the version 3 release and it is working. Thank you.

Thanks for continuing to test and give us feedback.  I am not certain what this could be, but my guess at the moment is it has something to do with using a VirtualBox as the FIRMM PC.  We had never tested this kind of setup.  We will look into this and get back to you on this forum.

Oh!  I missed this message.  That version 3 beta is our release candidate, so just note that we recommend updating to the release version after it is posted here to continue receiving bugfixes and update messages.  Thanks!

The same problem occurred on a real PC with Ubuntu 16.04 and Centos 7 so it wasn't confined to VirtualBox.

Will definitely upgrade to the release version when it comes out.
The output so far looks really nice.

Originally posted by Christopher Adamson:
Thanks, Christopher!  Let us know if any other issues or questions arise.