Reducing the Analytical Bottleneck for Domain Scientists: Lessons from a Climate Data Visualization Case Study

Aritra Dasgupta, Jorge Poco, Enrico Bertini, Claudio Silva
Computing in Science & Engineering · 2016 · January 1, 2016
Reducing the Analytical Bottleneck for Domain Scientists: Lessons from a Climate Data Visualization Case Study

Reducing the analytical bottleneck in scientific data analysis through iterative exploration of large-scale data. In comparing (a) the state of the art and (b) a bottleneck reduction, we see the time taken for analysis and deriving insights being significantly reduced, leading to a richer exploration of alternative hypotheses on the fly, and consequently, a faster and greater return on investment of analysis time for domain scientists.

Publication Details

Venue
Computing in Science & Engineering
Year
2016
Publication Date
January 1, 2016
DOI
https://doi.org/10.1109/MCSE.2016.7

Materials

Abstract

The gap between large-scale data production rate and the rate of generation of data-driven scientific insights has led to an analytical bottleneck in scientific domains like climate, biology, and so on. This is primarily due to the lack of innovative analytical tools that can help scientists efficiently analyze and explore alternative hypotheses about the data and communicate their findings effectively to a broad audience. In this article, by reflecting on a set of successful collaborative research efforts between with a group of climate scientists and visualization researchers, the 'authors' introspect how interactive visualization can help reduce the analytical bottleneck for domain scientists.

Cite this publication (BIBTEX)

@article{2016-ReducingBottleneck, 
  title={Reducing the Analytical Bottleneck for Domain Scientists: Lessons from a Climate Data Visualization Case Study}, 
  author={Aritra Dasgupta and Jorge Poco and Enrico Bertini and Claudio Silva}, 
  journal={Computing in Science & Engineering}, 
  year={2016}, 
  url={https://doi.org/10.1109/MCSE.2016.7},
  date={2016-01-01},
  volume={18},
  issue={1}
}