#1974: Add WVUThorns_Diagnostics to the ET
--------------------------------+-------------------------------------------
Reporter: zachetie@… | Owner:
Type: enhancement | Status: new
Priority: unset | Milestone:
Component: Other | Version: development version
Keywords: |
--------------------------------+-------------------------------------------
I have open-sourced a very useful set of diagnostic routines for GRMHD,
GRHD, and even vacuum simulations.
The thorns are available here:
https://bitbucket.org/zach_etienne/wvuthorns_diagnostics
Here's a brief description of each thorn:
Brief description of included thorns
'''Seed_Magnetic_Fields-modified''' Extended Seed_Magnetic_Fields thorn
for binary neutron stars. Supercedes Seed_Magnetic_Fields thorn.
'''Meudon_Bin_NS-modified''' Modifications to Meudon BNS initial data
thorn to disable the overwriting of initial lapse/shift, which acts to
significantly reduce coordinate eccentricity. Supercedes Meudon_Bin_NS
thorn.
'''VolumeIntegrals_GRMHD''' Nice GRMHD volume integration thorn, currently
depends on IllinoisGRMHD and Carpet. Performs volume integrals on
arbitrary "Swiss-cheese"-like topologies, and even interoperates with
Carpet to track NS centers of mass.
'''VolumeIntegrals_vacuum''' Nice GRMHD volume integration thorn,
currently depends on ML_BSSN. There is a bit of code duplication and
duplicated functionality between VI_GRMHD and VI_vacuum, to ensure that
VI_vacuum can be used without enabling a GRMHD code. There is probably a
better way of doing this, but I haven't had the time to think deeply about
this.
'''particle_tracerET''' Solves the ODE \partial_t x^i = v^i for typically
thousands of tracer particles, using an RK4 integration atop the current
timestepping. E.g., one RK4 substep in the particle integration might
occur every 16 RK4 substeps in the GRMHD evolution. These tracer particle
positions are quite useful for visualizing magnetic field lines in a
consistent way from frame-to-frame in a movie (recall that in the GRMHD
approximation, the magnetic field lines stay attached the fluid elements
they thread ["Flux Freezing"]). Note that the velocity must be consistent
with the velocity appearing in the GRMHD induction equation. This thorn
reads in the HydroBase vel[] vector gridfunction, which assumes the
Valencia formalism, and converts it into the induction equation velocity.
'''smallbPoynET''' Computes b^i^, b^2^, and three spatial components of
Poynting flux. It also computes (-1-u,,0,,), which is useful for tracking
unbound matter.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1974>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2161: make ET mailing lists searchable
---------------------------------+----------------------------
Reporter: Roland Haas | Type: enhancement
Status: new | Priority: minor
Milestone: | Component: Cactus website
Version: development version | Keywords:
---------------------------------+----------------------------
Right now there is no explicit search field for the Einstein Toolkit
mailing lists. Google apparently indexes them.
At the ET meeting at GeorgiaTech in 2018 it was suggested that a FAQ as
well as the ability to search the mailing list would be useful.
Such a functionality should be added to the ET wiki and ET website
respectively.
Something like this:
{{{
<form action="https://www.google.com/search" class="searchform"
method="get" name="searchform" target="_blank">
<input name="sitesearch" type="hidden" value="example.com">
<input autocomplete="on" class="form-control search" name="q"
placeholder="Search in example.com" required="required" type="text">
<button class="button" type="submit">Search</button>
</form>
}}}
seems to work and one can limit to particular lists by setting site to
something like {{{site:lists.einsteintoolkit.org/pipermail/users}}}
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2161>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2101: Add Lean_public and Proca thorns to the ET
-------------------------------------------------------+--------------------
Reporter: miguel.zilhao.nogueira@… | Owner:
Type: enhancement | Status: new
Priority: unset | Milestone: ET_2018_08
Component: EinsteinToolkit thorn | Version: development version
Keywords: Lean_public |
-------------------------------------------------------+--------------------
As discussed during the European ET meeting in Mallorca and during the
2018-01-22 ET telecon, we have a couple of Cactus thorns that we'd like to
make available to the general ET community. These include: an updated
evolution code that we used to evolve Proca fields
(https://arxiv.org/abs/1505.00797), the corresponding analysis and initial
data thorns, as well as a general metric evolution thorn (based on Uli
Sperhake's Lean). We have been cleaning up the codes, and they are now
available in following (public) bitbucket repositories:
https://bitbucket.org/canuda/lean_publichttps://bitbucket.org/canuda/proca
Included are some testsuites as well as some basic README files. We are
currently working on a paper that would also serve as documentation. We
would be very grateful if these could be considered for inclusion in the
2018_08 release.
Sincerely,
Helvi Witek
Miguel Zilhão
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2101>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1718: MemSpeed: Re-use allocated memory
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
Allocating memory is slow. In thorn MemSpeed, we should re-use memory that
has been allocated instead of allocating new memory for each benchmark.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1718>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2106: Make ParseFile.c more robust
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: unset | Milestone:
Component: Cactus | Version: development version
Keywords: |
----------------------+-----------------------------------------------------
We don't check for all the errors yet.
https://bitbucket.org/cactuscode/cactus/pull-requests/45/flesh-make-
parsefilec-a-bit-more-robust/diff
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2106>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#331: SimFactory does not abort if it has been given a nonexistent optionlist
------------------------+---------------------------------------------------
Reporter: hinder | Owner: mthomas
Type: defect | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
If I specify a nonexistent optionlist in a machine's .ini file, I get the
warning
Info: optionlist is: None
Warning: no option list specified, using blank option list
This is incorrect. I have specified an optionlist, but it has not been
found, which indicates an error. In this case I would expect a fatal
error.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/331>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2059: SimFactory should detect the number of cores automatically
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
SimFactory should detect the number of cores automatically. See pull
request by Mikael Sahrling: https://bitbucket.org/simfactory/simfactory2
/pull-requests/20/simdtpy-detect-number-of-cpus/diff.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2059>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#228: Make it easier for users to create accounts on TRAC
----------------------------------+-----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit trac | Version:
Keywords: |
----------------------------------+-----------------------------------------
Currently, in order to interact fully with TRAC, it is necessary to have a
CCT account. I would prefer that all potential users of the ET/Cactus
TRAC could create accounts. This way, it would be possible for all bug
reporters to be notified of changes to the tickets they create, and makes
it more likely that they will respond to requests for further information
and confirmations of fixes.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/228>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#270: Need web instructions for building on a new machine
-------------------------------------+--------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
We should have instructions on the web that explain how to build the
Einstein Toolkit on a new machine, i.e. a machine for which we don't have
a SimFactory entry already. This seems to be a fairly common case for new
users, who rather want to build on their own machine instead of on Queen
Bee.
This should probably concentrate on configuring Cactus first, i.e. on
configuring SimFactory for building a configuration. Job submission etc.
should come later.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/270>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1804: Provide an Einstein Toolkit User Guide
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Other | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
We currently have documentation for individual thorns, but there is no
documentation for the toolkit as a whole, describing how best to
accomplish certain tasks. The [http://arxiv.org/abs/1111.3344 Einstein
Toolkit paper] is a good starting point, but it is a static document, and
is not quite at the level of documentation. I propose to take the paper
and convert it into a user guide for the ET. It should not replicate
detailed information already available in thorn documentation (rather it
should link to it), but should provide a high level overview. It should
also contain best practices for working with the ET. This would be the
first point of reference for new users of the toolkit.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1804>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit