Skip to main navigation Skip to search Skip to main content

Fluid data compression and ROI detection using run length method

  • Shota Ishikawa
  • , Haiyuan Wu
  • , Chongke Bi
  • , Qian Chen
  • , Hirokazu Taki
  • , Kenji Ono

Research output: Contribution to journalConference articlepeer-review

Abstract

It is difficult to carry out visualization of the large-scale time-varying data directly, even with the supercomputers. Data compression and ROI (Region of Interest) detection are often used to improve efficiency of the visualization of numerical data. It is well known that the Run Length encoding is a good technique to compress the data where the same sequence appeared repeatedly, such as an image with little change, or a set of smooth fluid data. Another advantage of Run Length encoding is that it can be applied to every dimension of data separately. Therefore, the Run Length method can be implemented easily as a parallel processing algorithm. We proposed two different Run Length based methods. When using the Run Length method to compress a data set, its size may increase after the compression if the data does not contain many repeated parts. We only apply the compression for the case that the data can be compressed effectively. By checking the compression ratio, we can detect ROI. The effectiveness and efficiency of the proposed methods are demonstrated through comparing with several existing compression methods using different sets of fluid data.

Original languageEnglish
Pages (from-to)1284-1291
Number of pages8
JournalProcedia Computer Science
Volume35
Issue numberC
DOIs
Publication statusPublished - 2014
Externally publishedYes
EventInternational Conference on Knowledge-Based and Intelligent Information and Engineering Systems, KES 2014 - Gdynia, Poland
Duration: Sept 15 2014Sept 17 2014

All Science Journal Classification (ASJC) codes

  • General Computer Science

Fingerprint

Dive into the research topics of 'Fluid data compression and ROI detection using run length method'. Together they form a unique fingerprint.

Cite this