[ET Trac] #2691: New features to particle_tracerET

Gabriele Bozzola trac-noreply at einsteintoolkit.org
Tue Jan 31 11:20:19 CST 2023


#2691: New features to particle_tracerET

 Reporter: Leonardo Werneck
   Status: new
Milestone: ET_2023_05
  Version: 
     Type: enhancement
 Priority: major
Component: 

Comment (by Gabriele Bozzola):

```

        CCTK_VWarn (1, __LINE__, __FILE__, CCTK_THORNSTRING,
                    "VolumeIntegrals_GRMHD:file_output_routines.C Problem creating directory '%s' "
                    "for output", actual_dir);
```

The thorn name here is `VolumeIntegrals_GRMHD` which is not the correct one.

> 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.

The positions are already grid arrays, why not outputting those with Carpet directly? E.g., one could directly output `particle_tracerET::particle_position_x`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 `interface.ccl`\).

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2691/new-features-to-particle_traceret
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.einsteintoolkit.org/pipermail/trac/attachments/20230131/15831f60/attachment.html 


More information about the Trac mailing list