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
|
rick reynolds
April 13, 2023 09:36PM
Hello,

At a glance, that looks okay, because while the shell fails to match it, an AFNI program could (via the AFNI library).
But since you are using a wildcard, it must exactly match a file name on disk. So try adding .HEAD at the end of the REML+orig dataset name.

Of course, adding .HEAD will probably mean that the shell will then succeed in matching it in the 3dUndump command, and then the AFNI library will never see the '*'.

In any case, try using a complete file name.

- rick
Reply Quote
RSS
Subject Author Posted

3dUndump and using wildcard characters (*)

franciss April 13, 2023 05:43PM

Re: 3dUndump and using wildcard characters (*)

rick reynolds April 13, 2023 09:36PM

Re: 3dUndump and using wildcard characters (*)

franciss April 17, 2023 02:26PM