Trac July 2017

trac@lists.einsteintoolkit.org

1 participants
90 discussions

[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

[Einstein Toolkit] #2008: NaNs when running static tov on >40 cores
by Einstein Toolkit 22 Aug '18

22 Aug '18

#2008: NaNs when running static tov on >40 cores -----------------------------------+---------------------------------------- Reporter: allgwy001@… | Owner: Type: defect | Status: new Priority: unset | Milestone: Component: Other | Version: ET_2016_05 Keywords: | -----------------------------------+---------------------------------------- I've been trying to run the static tov example parameter file on an HPC cluster using >40 cores, but this results in NaNs in the data. I can't remember whether the issue first appears at 40 or 41 cores (and won't be able to check this for the next few days), but using 41+ cores definitely gives me NaNs. I remember testing with 39 cores and several other lower values (down to 4), but these runs all seemed fine. So far, I've been able to run larger simulations (e.g. BBHs) on more than 40 cores (same cluster) without any apparent issues. I'll attach the static tov parameter file I used (I think I changed one or two outdated parameters), as well as the PBS script and error/output files from a static tov run on 44 cores. The static tov runs were intended for speed test purposes. The results of the speed tests I've run so far (on fewer than 40 cores) seem quite strange to me, so I'm going to attach a text file with walltimes and CPU times for these runs, too. Any comments would be appreciated! -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2008> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

2 13

[Einstein Toolkit] #1263: Multipole does not handle variable names correctly
by Einstein Toolkit 13 Aug '18

13 Aug '18

#1263: Multipole does not handle variable names correctly -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: Multipole | -----------------------------------+---------------------------------------- When you specify variables for Multipole to decompose, you have the option of giving it a "name" for the variable to be used in the output filename. This is useful if you are decomposing Psi4r, with imaginary part Psi4i, and want the file to just be named "Psi4". If you don't specify a name, it is supposed to use the original variable name. However, at the moment, this last part seems to be broken. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1263> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #1201: Incorrect dtshift in Exact with shift_add_{x, y, z} parameters
by Einstein Toolkit 09 Aug '18

09 Aug '18

#1201: Incorrect dtshift in Exact with shift_add_{x,y,z} parameters -----------------------------------+---------------------------------------- Reporter: barry.wardell | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- The Exact thorn has shift_add_{x,y,z} parameters for adding a constant to the shift. Considering these as a coordinate transformation using a vector v^i = [shift_add_x, shift_add_y, shift_add_z], such a transformation should affect both the shift and its time derivative. This is because the time derivative in the new coordinates differs from the time derivative in the old coordinates by a term v^j d(beta^i)/dx^j. This is correctly implemented as a 4D coordinate transformation in the EinsteinExact thorns and I have verified that the difference relative to the Exact thorn is given by this missing term. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1201> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #1097: Describe Tmunu in GRHydro
by Einstein Toolkit 09 Aug '18

09 Aug '18

#1097: Describe Tmunu in GRHydro -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- Describe in GRHydro's documentation how Tmunu is defined -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1097> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #660: Make MHD multipatch-aware
by Einstein Toolkit 09 Aug '18

09 Aug '18

#660: Make MHD multipatch-aware -----------------------------------+---------------------------------------- Reporter: tbode | Owner: tbode Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- At least the Con2PrimM routines need to be multipatch-aware. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/660> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #1690: The test system should treat a nonzero exit code from Cactus as a failure
by Einstein Toolkit 08 Aug '18

08 Aug '18

#1690: The test system should treat a nonzero exit code from Cactus as a failure --------------------+------------------------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: | --------------------+------------------------------------------------------- The test system seems to ignore the fact that Cactus exits with a nonzero exit code. It displays Cactus exited with error code 1 Please check the logfile... No files created in test directory Success: 0 files identical And in the summary at the end, it treats this as a passing test. In this case, there were no test reference files and no files output, because the test (by design) does not produce any data, it just aborts if the test fails. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1690> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #1103: simfactory download page points to outdated version
by Einstein Toolkit 02 Aug '18

02 Aug '18

#1103: simfactory download page points to outdated version ------------------------+--------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- currently http://simfactory.org/simfactory/download/ points to https://svn.cct.lsu.edu/repos/numrel/simfactory2/branches/ET_2011_10 for the "current" version, which is from the last release -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1103> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 13

[Einstein Toolkit] #1523: Use Piraha to Parse all CCL files
by Einstein Toolkit 02 Aug '18

02 Aug '18

#1523: Use Piraha to Parse all CCL files -------------------------+-------------------------------------------------- Reporter: sbrandt | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Cactus_4.3.0 Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- Piraha should be used to parse all the CCL files. This would give us a well-defined grammar and the ability to let other tools use the CCL files in a reliable way. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1523> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 11

[Einstein Toolkit] #1949: provide floating branch to "current release" and links to it
by Einstein Toolkit 17 Jul '18

17 Jul '18

#1949: provide floating branch to "current release" and links to it -----------------------------+---------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Other | Version: development version Keywords: EinsteinToolkit | -----------------------------+---------------------------------------------- In order to not always have to update all websites with the correct ULRs to the then current release it would be good if we were to provide a "current release" branch of the ET which always points to the head of the current release branch/tag. Ie right now it would be identical to 2016_05. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1949> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 11

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac July 2017