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 28, 2012 09:25PM
Ah. I am not sure what to even do about this.

There are steps during the processing that run tcsh commands
to get output from other programs to use in afni_proc.py (and in
other programs).

In your cases, just starting another t-shell outputs all sorts of
garbage from FreeSurfer, and so that garbage ends up part of,
in this case, the view extension (like +orig).

But it means that afni_proc.py or any other program can
never run a command and grab the output. That is not
reasonable to me. It seems like a big mistake to run something
that outputs a bunch of text every time a new shell is started.

- rick
Subject Author Posted

strange afni_proc.py behavior

Anonymous User November 27, 2012 02:32PM

Re: strange afni_proc.py behavior

David Molfese November 27, 2012 03:40PM

Re: strange afni_proc.py behavior

rick reynolds November 27, 2012 09:51PM

Re: strange afni_proc.py behavior

David Molfese November 28, 2012 02:02PM

Re: strange afni_proc.py behavior

rick reynolds November 28, 2012 09:25PM

Re: strange afni_proc.py behavior

Peter Molfese November 28, 2012 09:45PM

Re: strange afni_proc.py behavior

rick reynolds November 28, 2012 09:59PM