#637: output puncture velocity in puncturetracker
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: PunctureTracker |
-----------------------------------+----------------------------------------
the attached patch allows the puncture velocities to be output (simply
moves the result of an interpolation into grid functions).
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/637>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#661: have puncture tracker output the puncture velocities
-------------------+--------------------------------------------------------
Reporter: rhaas | Type: enhancement
Status: new | Priority: minor
Milestone: | Component: EinsteinToolkit thorn
Version: | Keywords: PunctureTracker
-------------------+--------------------------------------------------------
the attached patch outputs the puncture velocity (ie the shift) at the
location of the puncture.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/661>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#658: ET component homepages
-------------------------------------+--------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
It would be good to have a "home page" on the web for each important
component in the ET. Components such as Cactus, Carpet, and Kranc have
home pages already. We could host pages for the major thorns, linking to
the documentation and the SVN repo. This is somewhat already accomplished
by having the ET thorn guide available, but links to sections of this
change when it is regenerated, and it is not very user-friendly.
These pages could contain the information from the thorn README files
(which should be kept up-to-date), and this could be the starting point.
We could write the README files in a markdown language such as ReST, which
is already human-readable in a text editor, and then use an automated tool
such as Sphinx or rst2html to convert these to HTML for the web.
Information on a homepage could include:
* Author list and copyright;
* Licence;
* Brief description of what the thorn does;
* Permanent link to the documentation (thorn-doc);
* Instructions for checking out the thorn (svn);
* Link to open tickets relating to this component (those with the
component name in the keywords, for those that don't have a TRAC component
assigned).
Components such as McLachlan, TwoPunctures, WeylScal4 and GRHydro would be
some good initial candidates for having pages describing them. It would
be good if there was a web presence for ET thorns, so that Google searches
might find them.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/658>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#656: GRHYdro::Bcons has wrong tensorparity in interface.ccl
-------------------+--------------------------------------------------------
Reporter: rhaas | Type: defect
Status: new | Priority: major
Milestone: | Component: Other
Version: | Keywords: GRHydro
-------------------+--------------------------------------------------------
the B field is a pseudovector so tensorparity should be -1 (as it already
is for HydroBase). Will commit fix later today.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/656>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#653: Create a CACTUS_EXE_DIR variable
-------------------------+--------------------------------------------------
Reporter: bmundim | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
CACTUS_CONFIGS_DIR allows us to have the configs directory
outside the Cactus tree (please see ticket #652). I suggest
to create a similar variable for the executables, a
CACTUS_EXE_DIR variable. It would work in the direction of
separating source code from generated executables, objects,
libraries, etc...
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/653>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit