<html>#2691: New features to particle_tracerET
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Leonardo Werneck</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2023_05</td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p>Comment (by Gabriele Bozzola):</p>
<div class="codehilite"><pre><span></span><span> CCTK_VWarn (1, __LINE__, __FILE__, CCTK_THORNSTRING,</span>
<span> "VolumeIntegrals_GRMHD:file_output_routines.C Problem creating directory '%s' "</span>
<span> "for output", actual_dir);</span>
</pre></div>
<p>The thorn name here is <code>VolumeIntegrals_GRMHD</code> which is not the correct one.</p>
<blockquote>
<p>The thorn’s output is non-standard because it deals with arrays, not grid functions. Each particles' position is evolved using the thorn’s own RK method. Thus each line of the output file looks like “time x_1 y_1 z_1 x_2 y_2 z_2 …” where the subscript is the particle ID and (x,y,z) the particle position.</p>
</blockquote>
<p>The positions are already grid arrays, why not outputting those with Carpet directly? E.g., one could directly output <code>particle_tracerET::particle_position_x</code>as an HDF5 file in CarpetIOHDF5 (or as an ASCII file in CarpetIOASCII). (In that case, it would be nice if the size of the array was not hardcoded in the <code>interface.ccl</code>).</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2691/new-features-to-particle_traceret'>https://bitbucket.org/einsteintoolkit/tickets/issues/2691/new-features-to-particle_traceret</a></p>
</html>