Hi All,

Since there have been some changes people might be interested in, I
have uploaded a new package for gifticlib version 0.0.12, including
gifti_tool version 0.3.

select updates in gifticlib since 0.0.9 (now 0.0.12):

- added gifti_create_image() interface
- added gifti_copy_gifti_image() and gifti_convert_to_float()
- must now link libniftiio

select updates in gifti_tool since 0.0.0 (now 0.3):

- added dataset creation ability (see -new_* options)
- added dataset modification ability (see -mod_* options)

For more details, see the output of:

gifti_tool -gifti_hist
gifti_tool -hist

The download link is:

http://www.nitrc.org/frs/download.php/14...

---

I hope to actually have a "release" version (1.0.0) within the
next few weeks (the next phone conference is the "hard" dealine).

- rick

Hi all,
I am having some issues regarding getting either of the binary formats to write properly (everything is reading ok) with gifti_io. Please notice I am *not* using gifti_tool. I've looked through the source and I can't find a good reason that it is behaving badly for me. When I try to write a NIFTI_ENCODING_B64BIN type data array, the data section write empty. When I write with the gzip compression, I get the same string of characters in the data segment:

eJwDAAAAAAE=

This string is apprent regardless of the data being written. To confuse matters, the ASCII encoding works perfectly.

I have libz 1.2.3 installed, and I believe that it is properly linked in to the gifti binaries.

Any help would be great!

Thanks,
Erik

Hi Erik,

It looks like the data is considered empty. I suspect that encoded string is some sort of header for decompressing later.

One thing you could try is setting the verbose level fairly high for the write operation (like even 4 or 5).

Does everything seem to be correctly written besides the data? If so, what does "gifti_tool -test" say about the file?

Feel free to mail me such a file, or the verbose output.

- rick