#2633: SummationByPart's Diff_gv aliased function does ont document which part of the grid the computed derivative is valid
Reporter: Roland Haas
Status: closed
Milestone:
Version:
Type: bug
Priority: minor
Component:
Changes (by Peter Diener):
status: closed (was resolved)
Comment (by Peter Diener):
Documentation updated.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2633/summationbyparts-…
#2633: SummationByPart's Diff_gv aliased function does ont document which part of the grid the computed derivative is valid
Reporter: Roland Haas
Status: resolved
Milestone:
Version:
Type: bug
Priority: minor
Component:
Changes (by Peter Diener):
status: resolved (was new)
Comment (by Peter Diener):
Documentation updated to describe the behavior.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2633/summationbyparts-…
#2633: SummationByPart's Diff_gv aliased function does ont document which part of the grid the computed derivative is valid
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: bug
Priority: minor
Component:
Comment (by Peter Diener):
The documentations have been updated.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2633/summationbyparts-…
#2861: Running qc0 with CarpetX
Reporter: Alejandra Gonzalez
Status: open
Milestone:
Version:
Type: bug
Priority: major
Component: EinsteinToolkit thorn
Comment (by Alejandra Gonzalez):
Hi Lucas,
It seems it’s just a warning, since there don’t seem to be errors shown in the output for the AH and the waveform \(which I’m also able to visualize without issues\).
However I haven’t been able to visualize the silo and punturetracker output. For the silo files I try to open them with VisIt but it keeps showing errors so I can’t read anything \(I’m outputting the same variable as your parfile ,\`ADMBaseX::alp\`\). As for the puncture tracker, seeing the files by hand they seem to have sane numbers but I don’t really understand what all those indices are for each coordinate. It’s mostly probably me not understanding how the output is structured I fear, rather than maybe there’s a bug in the code.
Thanks again!
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-…
#2861: Running qc0 with CarpetX
Reporter: Alejandra Gonzalez
Status: open
Milestone:
Version:
Type: bug
Priority: major
Component: EinsteinToolkit thorn
Comment (by Lucas Timotheo Sanches):
Hello Alejandra.
Good to hear that things seem to be working out.
Regarding your warning, it is difficult to say. Dos it crash your simulation at any point or is it just a warning?
Can you check the output from `PunctureTracker` to verify that the puncture locations reported at least make sense?
Regarding subcycling, I’m not a specialist and not really sure since the feature is quite new. You should probably open a new ticket with that question, or better yet, send your question to the mailing list so that we can forward it to the the appropriate developpers.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-…
#2861: Running qc0 with CarpetX
Reporter: Alejandra Gonzalez
Status: open
Milestone:
Version:
Type: bug
Priority: major
Component: EinsteinToolkit thorn
Comment (by Alejandra Gonzalez):
This warning message appears every time with that parfile though:
```
WARNING[L1,P6] (CarpetX): Before reduction: Grid function "TWOPUNCTURESX::puncture_u" is invalid on patch 0, refinement level 5, time level 0; required:
The interior is valid.
The outer boundary is invalid.
The ghost zones are invalid.
, found:
The interior is invalid because: RemakeLevel.
The outer boundary is invalid because: RemakeLevel.
The ghost zones are invalid because: RemakeLevel.
```
Is this something to be concerned about?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-…