NITRC Framewise Integrated Real-time MRI Monitoring Forum: firmm

vNav MPRAGE support?

Ursula Tooley — Tue, 16 Jul 2019 22:37:18 GMT

Hi,

I heard by emailing that this would be available soon...is it in the works? I could spend a lot of time trying to hack it myself, but would love it if it's just sitting somewhere waiting to be released...seems like having real-time estimates of motion from T1s would be a huge advance.

Best,
Ursula

A posteriori filtering of resting state

Romain Duprat — Fri, 07 Jun 2019 18:56:56 GMT

HI,

Is there a way to use firmm notch filter on previously acquired scans (i.e. resting states acquired without firmm). I thought I could just load up previous DICOM directly from the firmm GUI but we only have access to a few json files?
Best,

Romain

RE: Scanner unable to connect to FIRMM server

Eric Earl — Thu, 29 Nov 2018 20:34:56 GMT

[i]Originally posted by Greg Book:[/i][quote]I'm still having trouble getting the scanner console to connect to the FIRMM container. Is there anything else I can try?[/quote]
Greg,

I'm so sorry we haven't provided you support on this yet! Please email the team more complete details of your FIRMM system setup, FIRMM version in use, and maybe your scanner software version as well to info@firmm.io so we can track this better and get you a faster answer.

Thanks,
~Eric

RE: Scanner unable to connect to FIRMM server

Greg Book — Thu, 29 Nov 2018 20:06:41 GMT

I'm still having trouble getting the scanner console to connect to the FIRMM container. Is there anything else I can try?

Scanner unable to connect to FIRMM server

Greg Book — Fri, 09 Nov 2018 20:04:07 GMT

Hello,
I have been testing out FIRMM, and gotten through all of the installation, however when running the start_firmm.bat on the scanner console, it is not able to connect.
I am able to ping the FIRMM server, and the docker container is running, with a webpage displayed. I've turned off the firewall and selinux on the server as well.

What might be happening?

RE: Volume arrival delay

Eric Earl — Mon, 01 Oct 2018 14:48:33 GMT

[i]Originally posted by Ian Ballard:[/i][quote]Hi Earl,

A suggestion from the real-time fMRI list fixed the problem. I thought I would let you know in case it interests you.

It turns out that the default is for the computer to write data every 5 seconds on older systems, which is why scans appeared in alternating packets of 2 or 3 (at a 2s TR). You can change this to write every 500ms by setting "SendBuffered" to False using ideacmdtool and xbuilder and scans arrive in regular intervals of one TR +- a handful of ms.

Thank you,

Ian[/quote]
[color=#000000]Nice discovery! Thanks for the info cross-posting to our forum.[/color]

[color=#000000]~Eric[/color]

RE: Volume arrival delay

Ian Ballard — Fri, 28 Sep 2018 20:42:20 GMT

Hi Earl,

A suggestion from the real-time fMRI list fixed the problem. I thought I would let you know in case it interests you.

It turns out that the default is for the computer to write data every 5 seconds on older systems, which is why scans appeared in alternating packets of 2 or 3 (at a 2s TR). You can change this to write every 500ms by setting "SendBuffered" to False using ideacmdtool and xbuilder and scans arrive in regular intervals of one TR +- a handful of ms.

Thank you,

Ian

RE: Volume arrival delay

Eric Earl — Fri, 28 Sep 2018 18:01:51 GMT

Ian,

At that TR I can't imaging why your reconstruction computer would take that long to get DICOMs over your network to the FIRMM computer. I guess you could investigate your network speed bgetween the scanner and the firmm PC and maybe evaluate your scanner's reconstruction speed separately?

~Eric

RE: Volume arrival delay

Ian Ballard — Fri, 28 Sep 2018 17:51:09 GMT

[i]Originally posted by Eric Earl:[/i][quote]Ian, what is your TR? Is it about 2 seconds (just guessing based on your delay and volume counts there)?[/quote][color=#000000]Hello Eric,[/color]

[color=#000000]Yes the TR is 2 seconds. Thanks![/color]

RE: Volume arrival delay

Eric Earl — Fri, 28 Sep 2018 16:28:07 GMT

Ian, what is your TR? Is it about 2 seconds (just guessing based on your delay and volume counts there)?