AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2000.03.30 10:53 "Complex Floating Point", by Antonio E. Scuri
2000.03.30 13:33 "Re: Complex Floating Point", by Frank Warmerdam
2000.03.30 13:56 "Re: Complex Floating Point", by Antonio E. Scuri
2000.03.30 15:07 "Re: Complex Floating Point", by Chris Hanson
2000.03.30 16:44 "Re: Complex Floating Point", by Antonio E. Scuri
2000.03.30 19:12 "Re: Complex Floating Point", by Cris Luengo
2000.03.31 11:34 "Re: Complex Floating Point", by Antonio E. Scuri
2000.03.31 15:14 "RE: Complex Floating Point", by Martinez, Max
2000.03.31 18:07 "RE: Complex Floating Point", by Martinez, Max
2000.03.31 17:05 "RE: Complex Floating Point", by Antonio E. Scuri
2000.03.31 18:12 "RE: Complex Floating Point", by Antonio E. Scuri
2000.03.31 18:31 "Fwd: RE: Complex Floating Point", by Antonio E. Scuri
2000.04.03 13:12 "Re: Complex Floating Point", by Frank Warmerdam
2000.03.31 18:48 "Re: Complex Floating Point", by Daniel McCoy

2000.03.30 13:56 "Re: Complex Floating Point", by Antonio E. Scuri

I would like to try and discourage you from producing files with 128 bits per sample to represent complex data.

No problem. I am still deciding what to do and any suggestion will be appreciated.

Couldn't you just produce files with two samples, and 64 (or 32) bits each?

You mean 2 images in the file, one with the real part and the other with the imaginary? It is a nice solution.

I realize there wouldn't be any explicit way of recognising them as a real/imaginary pair, but perhaps that could be accomplished by other means?

I knew that a scientific image processing program called Digital Micrograph from Gatan store complex values creating a new type for SampleFormat. But this is terrible, unless there are plans for doing it that I do not know.

scuri