firmm
firmm > RE: Stuck at "Initializing Startup Routine"
Feb 6, 2018 02:02 PM | Eric Earl - National Institute of Mental Health
RE: Stuck at "Initializing Startup Routine"
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
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
Threaded View
Title | Author | Date |
---|---|---|
Christopher Adamson | Feb 6, 2018 | |
Andrew Van | Feb 6, 2018 | |
Christopher Adamson | Feb 6, 2018 | |
Eric Earl | Feb 6, 2018 | |
Christopher Adamson | Feb 7, 2018 | |
Eric Earl | Feb 8, 2018 | |
Christopher Adamson | Feb 8, 2018 | |
Christopher Adamson | Feb 8, 2018 | |
Eric Earl | Feb 8, 2018 | |
Christopher Adamson | Feb 8, 2018 | |
Eric Earl | Feb 9, 2018 | |