#2947: CarpetX: Support 2D output
Reporter: Maxwell Rizzo
Status: new
Milestone:
Version:
Type: enhancement
Priority: minor
Component:
Changes (by Maxwell Rizzo):
Currently 1D slices (x/y/z) and the full 3D output for Grid Functions are both supported output configurations from CarpetX. CarpetX is missing functionality to output GFs sliced along 2D planes (xy, xz, yz).
There is a sublety for how the slice is chosen, given the different centering options, some variables likely will not contain data along the `x/y/z=0` planes exactly, which is a similar sublety that the 1D output slice must resolve, hopefully these can be resolve consistently.
Also from a discussion with Roland, 2D output is inefficient for a Carpet/CarpetX simulation to output, compared to 1D and 3D. A performance test could be useful in gauging if this feature would be worth implementing/using at all in CarpetX.
TSV (or another text file format) probably makes sense as the starting point, if functional a compressed format like OpenPMD would also be desirable, bringing the 2D CarpetX output features in-line to what was present in Carpet.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2947/carpetx-support-2…
#2947: CarpetX: Support 2D output
Reporter: Maxwell Rizzo
Status: new
Milestone:
Version:
Type: enhancement
Priority: minor
Component:
Currently 1D slices (x/y/z) and the full 3D output for Grid Functions are both supported output configurations from CarpetX. CarpetX is missing functionality to output 2D planes (xy, xz, yz).
There is a sublety for how the slice is chosen, given the different centering options, some variables likely will not contain data along the `x/y/z=0` planes exactly, which is a similar sublety that the 1D output slice must resolve, hopefully these can be resolve consistently.
Also from a discussion with Roland, 2D output is inefficient for a Carpet/CarpetX simulation to output, compared to 1D and 3D. A performance test could be useful in gauging if this feature would be worth implementing/using at all in CarpetX.
TSV (or another text file format) probably makes sense as the starting point, if functional a compressed format like OpenPMD would also be desirable, bringing the 2D CarpetX output features in-line to what was present in Carpet.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2947/carpetx-support-2…
#2939: AHFinderDirect: range options for track_origin_source_x/y/z
Reporter: Jordan Nicoules
Status: open
Milestone:
Version:
Type: bug
Priority: minor
Component: EinsteinToolkit thorn
Changes (by Roland Haas):
status: open (was resolved)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2939/ahfinderdirect-ra…
#2939: AHFinderDirect: range options for track_origin_source_x/y/z
Reporter: Jordan Nicoules
Status: resolved
Milestone:
Version:
Type: bug
Priority: minor
Component: EinsteinToolkit thorn
Comment (by Roland Haas):
Still incorrect since will will not accept `puncturetracker::puncture_x` since it requires a `[…]` bit at the end.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2939/ahfinderdirect-ra…
#2939: AHFinderDirect: range options for track_origin_source_x/y/z
Reporter: Jordan Nicoules
Status: resolved
Milestone:
Version:
Type: bug
Priority: minor
Component: EinsteinToolkit thorn
Changes (by Steven R. Brandt):
status: resolved (was new)
Comment (by Steven R. Brandt):
Fixed.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2939/ahfinderdirect-ra…