Trac June 2017

trac@lists.einsteintoolkit.org

1 participants
96 discussions

[Einstein Toolkit] #1974: Add WVUThorns_Diagnostics to the ET
by Einstein Toolkit 25 Jan '19

25 Jan '19

#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

1 8

[Einstein Toolkit] #1718: MemSpeed: Re-use allocated memory
by Einstein Toolkit 23 Jan '19

23 Jan '19

#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

1 6

[Einstein Toolkit] #331: SimFactory does not abort if it has been given a nonexistent optionlist
by Einstein Toolkit 13 Dec '18

13 Dec '18

#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

1 5

[Einstein Toolkit] #228: Make it easier for users to create accounts on TRAC
by Einstein Toolkit 12 Dec '18

12 Dec '18

#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

1 1

[Einstein Toolkit] #270: Need web instructions for building on a new machine
by Einstein Toolkit 12 Dec '18

12 Dec '18

#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

1 3

[Einstein Toolkit] #1804: Provide an Einstein Toolkit User Guide
by Einstein Toolkit 12 Dec '18

12 Dec '18

#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

1 2

[Einstein Toolkit] #2046: list of ET members out of date
by Einstein Toolkit 27 Nov '18

27 Nov '18

#2046: list of ET members out of date -------------------------------------+-------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit website | Version: development version Keywords: | -------------------------------------+-------------------------------------- The current list of ET members on http://einsteintoolkit.org/members.html is out of date (mostly I guess because there is no way to update one's information). Eg looking at http://einsteintoolkit.org/members.html Charalampos Markakis would be at Southampton (he has been at NCSA since 2016), Philipp Moesta would be at Caltech (he has been in Berkeley for a couple years now). Tanja Bode is no longer at Tuebingen but at UCSC etc etc. My suggestion would be to contact all persons listed for their current institution and remove those that do not respond within a month. For future registration I suggest that we ask for an email address and ping the addresses once a year, removing stale ones. We should also include a paragraph to contact maintainers(a)einsteintoolkit.org to update ones affiliation in any email send out along with the registration. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2046> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #1889: correct finding normalization value for relerr compuation
by Einstein Toolkit 31 Aug '18

31 Aug '18

#1889: correct finding normalization value for relerr compuation --------------------+------------------------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: development version Keywords: | --------------------+------------------------------------------------------- Before it would have taken the larger of the abs value of the new and old data of the last data set rather than the largest abs value of the new and old data of all the datasets. This will make relative errros smaller and will be particularly noticeable in cases where the last dataset was small or zero. This should get rid of the "Error, how did I get here" warnings (that really indicated an logic error). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1889> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1885: support bibtex in thorn documenation files
by Einstein Toolkit 28 Aug '18

28 Aug '18

#1885: support bibtex in thorn documenation files -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- The pull request https://bitbucket.org/cactuscode/cactus/pull-requests/new?source=rhaas /docs-bibtex&t=1 adds support for bibtex to Cactus' documentation system. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1885> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #2042: new thorns for hydro analysis
by Einstein Toolkit 28 Aug '18

28 Aug '18

#2042: new thorns for hydro analysis -------------------------+-------------------------------------------------- Reporter: knarf | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Component: Other | Version: development version Keywords: | -------------------------+-------------------------------------------------- The LSU and Parma groups developed, and used for publications, a set of two thorns for analysis of hydro quantities, in particular for mode analysis. We would like to have those included in the Einstein Toolkit. We are aware that a few things are still missing for that (documentation, test suites), but before we go that extra step and create all of that, we want to be sure the following is seen as 'ok': The main thorn (GRHydro_Analysis, _not_ to be specific to GRHydro, it only inherits hydrobase - could and should probably be renames) does reductions of quire a few quantities. In practice, the memory required for this turned out to be a problem on some machines. These reductions are done at ANALYSIS, which means even telling Cactus to allocate/deallocate not once, globally, but instead doing that every time step does not help. Thus, there is a second thorn, a utility thorn called 'TempPool'. It's task is nothing else than to provide an array of grid functions that are always allocated, but which can be used by other thorns for, reductions - and, and this is the interesting part - can be re-used by other thorns, for other reductions after that; within the same time step in ANALYSIS. This is how TempPool is used by GRHydro_Analysis. TempPool is not tied to GRHydro_Analysis. Any other thorn can also request storage there, but there currently isn't another thorn. It just seemed to good idea to split this functionality. The book keeping already now makes sure that the number of allocated grid functions is only as large the maximum of any thorn using it. The relevant code can be found here: https://bitbucket.org/GravityPR/prthorns/src I'd like another developer to have a look and give input. Once/If this is deemed ok to be included, we will add the necessary documentation and test suites and make a proper proposal for inclusion. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2042> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac June 2017