2011.07.28 17:30 "Re: [Tiff] Using photon lists rather than rasters", by

The idea about a better predictor to improve compression of niche scientific images is interesting. Along the same direction, Terry could really use the new compression type for that. Think about that: if it's a new predictor that nobody today knows how to decode, and if it's much more advanced than today's "TIFF predictor" (even though it is indeed a predictor in mathematical/pedantic terms), it doesn't hurt to make its own compression type. As for the photon images, it will require something superbly advanced algorithms, something that blends several existing advanced algorithms together that nobody has seen before. Like: multi-resolution (or progressive-resolution), some kind of CABAC (which is both context-sensitive and uses arithmetic coding), etc. That said, the larger TIFF community may try to compel you to (1) open source your implementation and (2) give up, or sign over all intellectual rights and copyrights of that specification, and for that matter (3) it still leaves you vulnerable to patent lawsuits while the larger TIFF community just sit and watch. Therefore, it's important to remember that ultimately you have to decide what to do with your invention; you may decide whether to open it or not. If in doubt, talk to your company or employer lawyer. Thanks,

rwong_002@hotmail.com <mailto:rwong_002@hotmail.com>

Disclaimer: The opinions expressed here are the views of the writer(s) and do not necessarily reflect the views and opinions of the writers’ employer(s). Neither the writer(s), nor the writers’ employers, make any claim as to the accuracy of the opinions expressed here.

 From: ccox@adobe.com
To: tiff@lists.maptools.org

Date: Wed, 27 Jul 2011 16:57:30 -0700

Subject: Re: [Tiff] Using photon lists rather than rasters

Re: [Tiff] Using photon lists rather than rasters

Tagged Image File Format.

I would rather not see a TIFF “image” that is not an image and is not readable by other software.

TIFF already gets too much abuse with undocumented custom compression types that render the files useless.

In this case you are creating a vector display list, for which there are more appropriate types.

Personally, I’d just apply a better predictor to improve compression and keep the image data. If all you need are locations/centroids of photon hits – you could easily convert the image to a 1 bit/sample representation and compress that.

Chris

On 7/27/11 3:51 PM, "Terry L. Sprout" <Terry.Sprout@Agile-Automation.com> wrote:

Viewers that do not understand your photons list will simply ignore it