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  

|
April 21, 2009 09:13AM
Hi Jana,

The quick but lousy answer first... Use ctrl-s to suspend the terminal
process, which will do nothing until you tell it to continue, usually
via ctrl-q.

---

The better answer... Never run commands to process your data without
storing the output in a file. It is quite common to need to see the
output later (such as this case), and quite difficult to read all of it
as it flies by on the screen. To do this, pipe stdout and stderr through
the 'tee' program, which sends output both back to the terminal window
and to the text file that you specify.

For example, suppose my 3dDeconvolve command is in the file run.3dDecon
(and let us assume that any shell syntax is in tcsh, not bash). Then I
would execute the script via:

tcsh -x run.3dDecon |& tee output.run.3dDecon


The '-x' option to 3dDeconvolve will echo the commands to the terminal
before actually executing them (so your actual 3dDeconvolve command will
be saved in the output, too).

The '|&' symbol pair means to pipe both stdout and stderr. Normally one
just plays with stdout via '|'. But often error/warning messages are
sent to the stderr file stream, and they are most important to catch.

So stdout and stderr are both piped to the 'tee' program, which simply
duplicates the input, sending it both back to the screen (so the user
gets to see it) and to whatever file the user specified (output.run.3dDecon
in this case).

So after the command is done, 'output.run.3dDecon' will contain all of the
commands, plus their output. It is just a text file, so it can be viewed
with an editor or maybe with the 'less' (or more) program.

- rick

Subject Author Posted

warnings

Jana April 21, 2009 05:03AM

Re: warnings

rick reynolds April 21, 2009 09:13AM

Re: warnings

Jana April 21, 2009 02:24PM

Re: warnings

rick reynolds April 21, 2009 02:46PM

Re: warnings

Jana April 22, 2009 02:04AM

Re: warnings

Jana April 22, 2009 02:10AM

Re: warnings

James Keidel April 22, 2009 07:33AM

Re: warnings

Jana April 22, 2009 08:46AM

Re: warnings

James Keidel April 22, 2009 09:28AM

Re: warnings

rick reynolds April 22, 2009 09:59AM

Re: warnings

Jana April 22, 2009 10:45AM

Re: warnings

rick reynolds April 22, 2009 11:07AM

Re: warnings

Jana April 23, 2009 03:12AM