Trac April 2018

trac@lists.einsteintoolkit.org

2 participants
54 discussions

[Einstein Toolkit] #2119: The binary neutron star gallery example gives different results with the release candiate.
by Einstein Toolkit 22 Aug '18

22 Aug '18

#2119: The binary neutron star gallery example gives different results with the release candiate. ---------------------+------------------------------------------------------ Reporter: diener | Owner: Type: defect | Status: new Priority: blocker | Milestone: ET_2018_02 Component: Other | Version: development version Keywords: | ---------------------+------------------------------------------------------ The late part of the waveform plot looks very different in the release candidate than on the gallery page. For l=2, m=2 mode of psi_4 extracted at R=300 (that seems to be the correct data file as otherwise the scale on the y-axis don't match) the merger seem to happen slightly later and the waveform after merger is completely different. The gallery page plot: [[Image(/home/diener/tmp/mp_Psi4_l2_m2_r300.00.png)]] The new plot: [[Image(/home/diener/tmp/mp_Psi4_l2_m2_r300.00_new.png)]] -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2119> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 13

[Einstein Toolkit] #2131: Boundary thorn
by Einstein Toolkit 22 Aug '18

22 Aug '18

#2131: Boundary thorn -------------------------------------------------------+-------------------- Reporter: miguel.zilhao.nogueira@… | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: Boundary | -------------------------------------------------------+-------------------- i was trying to do a (unigrid) run with "scalar" boundary conditions on some variables but with uneven boundary width, ie width of 2 grid points on the x and y axis and 0 on the z axis. in the documentation of the Boundary thorn it states that one should create a table passing this information in an array called "BOUNDARY_WIDTH": "The table handle identifies a table which holds extra arguments for the particular boundary condition that is requested. For example, if a negative value is passed for the boundary width, then the boundary condition will look in this table for a 2d-element integer array, which holds the width of each face of the boundary (for a d dimensional grid variable). (The first element of the array holds the width of the ‘-x’ face, the second the ‘+x’ face, the third the ‘-y’ face, etc.)" so i've accordingly created the following table {{{ call Util_TableCreateFromString(param_table_handle, "BOUNDARY_WIDTH = { 2 2 2 2 0 0 }") {{{ and then registered the variables with {{{ ierr = Boundary_SelectGroupForBC(cctkGH, CCTK_ALL_FACES, -one, & param_table_handle, "ScalarBase::phi", "scalar") }}} however, i was getting errors like the following: {{{ Boundary/src/Check.c:130: BndSanityCheckWidths: Assertion `dim < (int)sizeof(dims)' failed. }}} inspecting that file, this is only triggered if {{{(boundary_widths[i] > 100 || boundary_widths[i] < 0)}}} which meant that my BOUNDARY_WIDTH array was likely not being parsed correctly. digging a little bit deeper, i've found the following in ScalarBoundary.c:138 (and analogous for the other files under CactusBase/Boundary/src): {{{ /* Determine boundary width on all faces */ /* allocate memory for buffer */ gdim = CCTK_GroupDimI(gi); if (gdim > max_gdim) { width_alldirs = (CCTK_INT *)realloc(width_alldirs, 2 * gdim * sizeof(CCTK_INT)); max_gdim = gdim; } /* fill it with values, either from table or the boundary_width parameter */ if (widths[i] < 0) { err = Util_TableGetIntArray(tables[i], gdim, width_alldirs, "BOUNDARY_WIDTH"); }}} it seems to me that this last line should be instead {{{ err = Util_TableGetIntArray(tables[i], 2 * gdim, width_alldirs, "BOUNDARY_WIDTH"); }}} for consistency with the rest of the file and with the documentation, right? indeed, with this change the errors disappeared. i've attached a simple patch that applies this on this file, but i guess an equivalent change would be needed also for the rest of the Boundary files... if this patch is correct, could this be ported to the current release? and if it's not correct, is there anything i'm missing, in order to register the boundary conditions? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2131> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 11

[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] #2145: ET web certificates to expire Jul 1st
by Einstein Toolkit 08 Aug '18

08 Aug '18

#2145: ET web certificates to expire Jul 1st ---------------------------------+---------------------------- Reporter: Frank Löffler | Type: defect Status: new | Priority: minor Milestone: | Component: Cactus website Version: development version | Keywords: ---------------------------------+---------------------------- Several ET web certificates are about to expire July 1st and should be replaced before then: einsteintoolkit.org trac.einsteintoolkit.org svn.einsteintoolkit.org (also get a new one here even though we don't use it anymore) Setting priority to 'minor' as there is still quite some time. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2145> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 10

[Einstein Toolkit] #2135: CAPTCHA on docs.einsteintoolkit.org may stop working soon
by Einstein Toolkit 08 Aug '18

08 Aug '18

#2135: CAPTCHA on docs.einsteintoolkit.org may stop working soon ---------------------------------+-------------------------------------- Reporter: Roland Haas | Type: defect Status: new | Priority: major Milestone: | Component: EinsteinToolkit website Version: development version | Keywords: docs.einsteintoolkit.org ---------------------------------+-------------------------------------- Every once in a while, when I forgot to properly log into the wiki an want to save a page, I am confronted by a CAPTCHA to prove that I am human. A subset of those CAPTCHAs actually look like that attached screenshot, ie they seem to indicate that the CAPTCHAs may stop working on 2018-03-31 which is rather soon. [[Image(2018-03-21-092921.png)]] I am not sure if this can be fixed by a relatively painless update of a plugin or if it will require complete update of the wiki server. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2135> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 14

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac April 2018