<html>#2542: Support for creating and saving 1D histograms
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Wolfgang Kastaun</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Carpet</td></tr>
</table>
<p>Comment (by Wolfgang Kastaun):</p>
<p>Such a low level kernel may be a good building block for implementing the histograms, but is only addressing part of the problem. The callback function could store histograms of local data, but this still has to be reduced globally at some point. When exactly to schedule the reduction and the resetting of the histograms between timesteps will then probably become another dark art (scheduling GLOBAL-LATE or GLOBAL-EARLY and what bin?). It also does not handle output in a standard format, nor the basic histogram code. In short, I think histograms are such a basic feature that they should be very easy to create for the user, similar to scalar reductions.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2542/support-for-creating-and-saving-1d'>https://bitbucket.org/einsteintoolkit/tickets/issues/2542/support-for-creating-and-saving-1d</a></p>
</html>