AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

|
November 18, 2016 03:29AM
Hi! After talking to Rick we decided that I should post this.

Some of our researchers are using 3dGroupInCorr and the AFNI viewer for trying to optimize DMN seed locations. They have experienced some issues with 3dGroupInCorr closing the connection randomly. This can occur after just 1 click or 20 clicks and might happen 1-2 times a day. AFNI is installed on a remote server and accessed via ssh -X. This has, to our knowlage, never happend on a local AFNI session. This is the terminal output:
afni -NIML &

 3dGroupInCorr -setA ALL.grpincorr.niml

++ 3dGroupInCorr: AFNI version=AFNI_16.3.04 (Oct 19 2016) [64-bit]

++ Authored by: Cox, the Mad Correlator

++ GIC: data file ALL.grpincorr.data found with 11,413,107,472 bytes of data

++ GIC: -setA opened, contains 46 datasets, 862408 time series, 11,413,107,472 bytes

++ GIC: page faulting (reading) data into memory

 + setA:0123456789.0123456789.0123456789.0123456789.0123456789.!

++ GIC: total .data bytes input = 11,413,107,472 (about 11 billion [giga])

++ GIC: --- Be sure to start AFNI with the '-niml' command line option

 +      ---  [or press the NIML+PO button if you forgot '-niml']

++ Opening NIML socket 'tcp:localhost:53213' to AFNI. Connected!

++ NIML connection opened from 127.0.0.1 (tcp:host:53213,AFNI_GroupInCorr_NIML)

++ 3dGroupInCorr stands ready to do thy bidding, O Master smiling smiley !!

 + GIC: OpenMP thread count = 15

++ Added 3dGroupInCorr dataset 'A_GRP_ICORR+tlrc' to controller [A]

 + 46 datasets in set A

 + ----------------------------------------------------

 + ----- AFNI is now connnected to 3dGroupInCorr! -----

 + ..... Use 'InstaCorr Set' to pick a seed voxel .....

 + ..... (Mouse-right-click menu in image viewer) .....

 + ----------------------------------------------------

++ AFNI GIC: AFNI_gicor_setref called --> ijk=538613

++ AFNI GIC: sending command to 3dGroupInCorr

++ AFNI GIC: called from xyz = 0.00 56.00 29.00 (DICOM), seed radius 0

++ GIC: Received command SETREF_ijk from AFNI

 + GIC:  loaded seed vectors: elapsed=1 ms

 + GIC:  finished correlation-izing: elapsed=1198 ms

 + GIC:  finished t-test-izing: elapsed=258 ms

++ GIC: Reconnecting to AFNI with shared memory channel shm:GrpInCorr_53213:1M+4K

 + GIC:  SHM reconnection *ACTIVE* smiling smiley !!!

 + GIC:  sent results to AFNI: elapsed=208 ms  bytes=6,899,382

 + GIC:  Total elapsed time = 1665 msec

++ Potentially more regions could be found than the 9 reported.

Set the environment variable AFNI_WHEREAMI_MAX_FIND to higher

than 9 if you desire a larger report.

It behooves you to also checkout AFNI_WHEREAMI_MAX_SEARCH_RAD

and AFNI_WHEREAMI_NO_WARN. See whereami -help for detail.

*+ WARNING: GIC: Connection to AFNI broken - trying to restart

reading MNIa_caez_pmaps_18+tlrc(328 million [mega] bytes).........done

++ NIML connection closed from shm:GrpInCorr_53213:1M+4K (shm:GrpInCorr_53213:1M+4K,ZERO)

 + GIC: TCP/IP restart is good smiling smiley

++ NIML connection opened from 127.0.0.1 (tcp:host:53213,AFNI_GroupInCorr_NIML)

*+ WARNING: AFNI GIC: connection to 3dGroupInCorr is broken

It seems like it does re-establish the connection but the time between "+ GIC: TCP/IP restart is good smiling smiley" and "*+ WARNING: AFNI GIC: connection to 3dGroupInCorr is broken" is probably very short.

Any insights?

Best,
Robin



Edited 2 time(s). Last edit at 11/18/2016 11:15AM by ptaylor.
Subject Author Posted

Connection to 3dGroupInCorr is broken

Robin November 18, 2016 03:29AM

Re: Connection to 3dGroupInCorr is broken

Bob Cox November 18, 2016 03:40PM

Re: Connection to 3dGroupInCorr is broken

Robin November 21, 2016 06:37AM