Re: [amide-users] Export .ima to interfile3.3

[Andy L. <lo...@st...>]

On Sat, 21 Apr 2007, Ana Oliveira wrote:

> I want to use amide to export .ima files to interfile 3.3. My input .ima 
> file is an Hoffman image which is translated according to x axis, y axis 
> and rotated around z axis. When I export Hoffman.ima file to .i33 and 
> open the new interfile file, I become aware that Hoffman is not in the 
> same position anymore.
>
> Can anyone explain me why is this happening?
>

I assume you're doing export->original orientation, which would explain 
the results you're seeing. You probably will need to use 
"export->resliced" for what you aim to do.


> I would be very appreciated if you could also indicate the main 
> differences between the different export methods: export 
> original/resliced orientation; export visible data sets.

"export->original orientation" will output the data without any 
interpolation, this results in the data set being output in the same 
orientation it was originally loaded in. This is because xmedcon (the 
library amide uses to output to the different file formats) doesn't 
support rotations. Most medical imaging formats (e.g. interfile) don't 
support rotations anyway. Translations will be encoded in the output 
file if the file format supports it.

"export->resliced orientation" will interpolate the data when outputing to 
take into account any rotations you've done in amide. The interpolation 
used will be what's currently enabled for the dataset in question.

"export->all visible data sets" is probably not what you want. It's most 
useful for combining two data sets into a single output file (for instance 
a two bed CT scan).

bounding box "inclusive" is useful if you're outputing two separate data 
sets from an AMIDE session that you then want to use in another program 
that will require the data sets to be the same size.

Hope that answers your questions,
Andy