FAQs

Is ABO™ different from other compression technologies?

Yes. In the following key aspects:

  • Simplicity
  • Retention of data intelligence
  • Extended data indexing and archiving capabilities

Is ABO™ better than other compression technologies?

ABOTM is better than competing technologies for Medical Images and Text. It has been proved that by leveraging ABO’s Image and Text compression advantage, it is possible to extend this performance to other composite data types. Additionally, ABOTM is being optimized to deliver similar performance improvements on other data types like video and audio.

On what input data sets was the benchmarking done?

The benchmarking was done on public corpuses (Calgary, ACT, Maximum Compression and Canterbury text corpuses, Kodak/ Fuji/ JPEG 2000/ Waterloo image sets) and also on MatrixView’s internal corpus, containing over 20GB of composite data!

How is ABO™ presently delivered?

ABO™ is presently available in the form of two platform offerings:

  • ABOve 2000 - for Medical Images
  • SQZit Platform for Generic Data

What are the platforms ABO™ supports?

The ABOve 2000 platform is available for Windows. The SQZit platform is available for Windows and Linux (Red Hat).

What are the formats ABO™ supports?

The SQZit platform can compress all file types and is specifically optimized for images (bmp, pgm, ppm, pbm, dcm, jpg, png and tiff) and Microsoft Office files.

The ABOve 2000 platform can compress all DICOM-compliant files with extensions (DCM, DICM).

What are the verticals ABO™ can be applied to?

ABO is currently applied in Healthcare Digital Imaging and Enterprise Information Management (EIM) verticals.

‘ABO™ for developers’ – What’s in it?

The SQZit and ABOve 2000 platforms are available in several manifestations – JAVA interfaces, .NET classes, Native DLL’s for the Windows Platform and as Shared Objects / DLL’s for Linux Platform.

What is recompression?

Recompression is literally compressing the compressed!

You are right if you have read elsewhere that compressed data is random and cannot be compressed further. ABO™ cannot compress random data either, but what it can do is replace some inefficient blocks that generated the compressed data originally with customized ABO™ powered blocks that perform better! A feature of this process is that ABO™ can regenerate the original compressed data – making the process completely lossless. There are exceptions to this and that leads us to another interesting concept, namely, Pixel to Pixel lossless compression

What is Pixel to Pixel lossless recompression?

Different implementations of non-standard compression algorithms can generate differently compressed bit streams (e.g., png, zip etc) for the same image. In these cases, it is near impossible for us to regenerate the original compressed stream during recompression. This is in spite of the fact that the compressed bit stream generated by ABO™ will generate a pixel–to–pixel lossless version of the original image. This feature where the compressed bit stream is different in spite of retaining the fidelity of the original image is what we term “Pixel-to-Pixel Lossless recompression”

For further discussions, please contact technology@matrixview.com