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  

Previous Message Next Message
Message List New Topic Print View
|
Bob Cox
June 13, 2017 10:51AM
I looked at these messages again last night. There are 3 issues here:

  1. Your version of AFNI needs updating. ETAC was updated in late May 2017.
  2. For some reason, all the .minmax.1D files didn't get read. That is the substance of the ERROR messages. These are minor errors, and the program continues without further comment. If this problem re-occurs with an updated version of AFNI, I'd like to know about it.
  3. ETAC (3dXClustSim) ends up "killed". This is a message from Unix that the operating system itself deleted the job. In principal, there are many reasons this could happen. In practice, there is only 1 reason -- the program used up all available memory. The updated version of 3dxClustSim should use somewhat less memory, but you may still run into such problems. If that happens, you'll just need to run on a system with more memory available.
Other points are

  • You really should provide a -prefix_clustsim option, instead of letting the program generate a prefix randomly. It will make the messages and files more readable.
  • If you are running from a networked RAID or other attached storage, then it would be better to use the -tempdir option to provide a temprorary directory name on a local drive -- the *.sdat files created can be huge, and reading/writing them over a network drive will slow 3dttest++ and 3dXClustSim down a lot.
Reply Quote
RSS
Subject Author Posted

3dXClustsim issue?

Andrew D. May 31, 2017 11:18AM

Re: 3dXClustsim issue?

Peter Molfese May 31, 2017 11:37AM

Re: 3dXClustsim issue?

Bob Cox June 12, 2017 02:17PM

Re: 3dXClustsim issue?

Bob Cox June 13, 2017 10:51AM