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
January 31, 2003 02:34PM
You are confusing the "-type" flag (which has to do with the dataset output) with the input image type. to3d tries to auto-detect the input image type. This is failing badly in your case.

I could add a flag to to3d to tell it to skip trying the DICOM image type. But I can't do that today - I'm too busy. If you are reading the typical 8192 byte long 64x64 files from MCW, then you can change the image filename specification from
exp1/exp1\*
to something like
'3D:0:0:64:64:1:exp1/exp1*'
which should force the input image files to be read in the correct way.

bob cox
Reply Quote
RSS
Subject Author Posted

to3d errors

Dominic Cheng January 31, 2003 12:04PM

Re: to3d errors

bob cox January 31, 2003 12:49PM

Re: to3d errors

Dominic Cheng January 31, 2003 02:17PM

Re: to3d errors

bob cox January 31, 2003 02:34PM

Re: to3d errors

Dominic Cheng January 31, 2003 04:00PM