Trac September 2011

trac@lists.einsteintoolkit.org

1 participants
184 discussions

[Einstein Toolkit] #234: Carpet mailing list is not functioning
by Einstein Toolkit 21 Nov '11

21 Nov '11

#234: Carpet mailing list is not functioning --------------------+------------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: | --------------------+------------------------------------------------------- The Carpet mailing list has been unavailable since 22-Mar-2010. This list provides a forum for discussion of Carpet features and issues, and would be the first port-of-call for new users. As such I think it would be good to resurrect the mailing list. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/234> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #495: MPI error from Carpet with QuasiLocalMeasures: "MPI_SUM is not defined for non-intrinsic datatypes"
by Einstein Toolkit 14 Nov '11

14 Nov '11

#495: MPI error from Carpet with QuasiLocalMeasures: "MPI_SUM is not defined for non-intrinsic datatypes" --------------------+------------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: | --------------------+------------------------------------------------------- In the development (Mercurial) version of Carpet, but not the stable (Git) version, QuasiLocalMeasures fails with the following error message: ... INFO (QuasiLocalMeasures): Landau-Lifshitz angular momentum x: 0.00000 INFO (QuasiLocalMeasures): Landau-Lifshitz angular momentum y: 0.00000 INFO (QuasiLocalMeasures): Landau-Lifshitz angular momentum z: 0.00000 [sl-18:26396] *** An error occurred in MPI_Reduce: the reduction operation MPI_SUM is not defined for non-intrinsic datatypes [sl-18:26396] *** on communicator MPI COMMUNICATOR 3 SPLIT FROM 0 [sl-18:26396] *** MPI_ERR_OP: invalid reduce operation [sl-18:26396] *** MPI_ERRORS_ARE_FATAL (your MPI job will now abort) This affects the QuasiLocalMeasures test suite, but was also reported and discussed on the ET mailing list: http://lists.einsteintoolkit.org/pipermail/users/2011-May/001107.html Additional debugging was suggested to try to locate the reason for the error. (Reporting against Carpet even though it might be a problem in QuasiLocalMeasures because it works in the stable Carpet and this will be a possible blocker for promoting the development Carpet to stable). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/495> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 11

[Einstein Toolkit] #145: EOS_Omni requires HDF5 library. What about if it only uses HDF5 instead?
by Einstein Toolkit 13 Nov '11

13 Nov '11

#145: EOS_Omni requires HDF5 library. What about if it only uses HDF5 instead? ---------------------------+------------------------------------------------ Reporter: bmundim | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Other | Version: Keywords: EOS_Omni HDF5 | ---------------------------+------------------------------------------------ At the moment EOS_Omni requires the HDF5 library to read the nuclear EOS values from a table. Since not all distros have fortran support for the HDF5 library as a default, I propose to change this requirement and provide a fall back in case this support is not present. Perhaps not using the nuclear EOS, or reading from an ASCII file instead. This could be just a temporary solution until the HDF5 library build script becomes more robust. Opinions? Thanks, Bruno. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/145> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #470: Check is wrong inside prolongate_3d_o1_rf2.cc
by Einstein Toolkit 10 Nov '11

10 Nov '11

#470: Check is wrong inside prolongate_3d_o1_rf2.cc ---------------------+------------------------------------------------------ Reporter: sbrandt | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Other | Version: Keywords: | ---------------------+------------------------------------------------------ The problem materialized when creating wave equation tutorials for the Teragrid conference. I was unable to run an FMR application in parallel. The check comprises lines 76-80 of the file: if (not regbbox.expand(offsetlo, offsethi).is_contained_in(srcbbox) or not regbbox .is_contained_in(dstbbox)) { CCTK_WARN (0, "Internal error: region extent is not contained in array extent"); } -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/470> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #365: ADMBase: evolving with evolution_method="static" does not apply boundary conditions
by Einstein Toolkit 10 Nov '11

10 Nov '11

#365: ADMBase: evolving with evolution_method="static" does not apply boundary conditions ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | ----------------------+----------------------------------------------------- When one uses the evolution method ADMBASE::evolution_method = "static" (which is very tempting e.g. for Cowling), then no boundary conditions are applied. This means that the ADMBase variables remain unset on the boundaries after regridding, leading to all sorts of (rather unexpected) problems. The easy solution is to use thorn Exact instead, which applies an exact solution at each time step, including on the boundary. I suggest to remove the ADMBase functionality to provide a "static" evolution method, since this evolution method does not know which boundary condition to apply, and hence is bound to fail in non-trivial situations. Alternatively, ADMBase needs to synchronise in postregrid (and probably a few other bins as well). ADMBase should then also offer to apply an outer boundary condition, in this case probably a Minkowski Dirichlet boundary condition or a von Neumann condition. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/365> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #539: Test recoverML is failing
by Einstein Toolkit 10 Nov '11

10 Nov '11

#539: Test recoverML is failing -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: McLachlan | -----------------------------------+---------------------------------------- Since 26.08.2011, the recoverML test has failed with the stable version of Carpet. The error is: {{{ phi.x.asc: substantial differences significant differences on 1 (out of 42) lines maximum absolute difference in column 13 is 1.922567332939e-08 maximum relative difference in column 13 is 3.71924165894473e-07 (insignificant differences on 12 lines) phi.y.asc: substantial differences significant differences on 2 (out of 66) lines maximum absolute difference in column 13 is 1.92256733397983e-08 maximum relative difference in column 13 is 3.71924166087253e-07 (insignificant differences on 20 lines) }}} Possible candidate commits for causing this failure are: changeset:30/LSUThorns/Vectors {{{ User: eschnett Date: 2011/08/25 12:40 PM Modified: /trunk/src/ vectors-4-SSE.h, vectors-8-SSE2.h Log: Suggest asm statements to support SSE4a with Intel compilers. Indent vector architecture definitions. }}} and {{{ McLachlan: commit 2888d221261da25e7802b76c46ee3e10ca578418 Author: Barry Wardell <barry.wardell(a)gmail.com> Date: Thu Aug 18 00:05:43 2011 +0200 Enable Vectorisation. }}} -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/539> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #520: TOVSolver test cases are failing
by Einstein Toolkit 10 Nov '11

10 Nov '11

#520: TOVSolver test cases are failing -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: TOVSolver testsuite | -----------------------------------+---------------------------------------- The TOVSolver test cases run on 08-Aug-2011 failed. http://damiana2.aei.mpg.de/~ianhin/testsuites/einsteintoolkit/ The errors are related to nontrivial changes in the ADMBase variables: http://damiana2.aei.mpg.de/~ianhin/testsuites/einsteintoolkit/einsteintoolk… This is likely related to changeset:"62/ADMBase" committed as a result of #333. User: hinder Date: 2011/08/17 05:07 PM Modified: /trunk/ interface.ccl /trunk/src/ InitSymBound.c Log: Apply "flat" boundary condition instead of "none" to ADMBase variables In the development version of Carpet, only the interior of the newly created grid is initialized by interpolation, so non-trivial boundary conditions need to be applied. I don't know whether the old or the new results are correct. The failure happens with both the stable and development versions of Carpet. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/520> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #496: WeylScal4 fails tests with development version of Carpet
by Einstein Toolkit 10 Nov '11

10 Nov '11

#496: WeylScal4 fails tests with development version of Carpet --------------------+------------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: | --------------------+------------------------------------------------------- Both WeylScal4 tests fail with the development version of Carpet but not with the stable version. The report is Psi4i.d.asc: substantial differences significant differences on 16 (out of 62) lines maximum absolute difference in column 13 is 0.0042979716483804 maximum relative difference in column 13 is 0.221177389498685 (insignificant differences on 20 lines) Psi4i.z.asc: substantial differences significant differences on 24 (out of 108) lines maximum absolute difference in column 13 is 0.0123048458581252 maximum relative difference in column 13 is 1.43992798290495 (insignificant differences on 54 lines) Psi4r.d.asc: substantial differences significant differences on 16 (out of 62) lines maximum absolute difference in column 13 is 2.99002416115686e-05 maximum relative difference in column 13 is 0.995857600242238 (insignificant differences on 26 lines) Psi4r.x.asc: substantial differences significant differences on 42 (out of 146) lines maximum absolute difference in column 13 is 0.0063512431519604 maximum relative difference in column 13 is 1.35438090371356 (insignificant differences on 84 lines) Psi4r.y.asc: substantial differences significant differences on 42 (out of 146) lines maximum absolute difference in column 13 is 0.0064343032695815 maximum relative difference in column 13 is 1.1458862046889 (insignificant differences on 84 lines) Psi4r.z.asc: substantial differences significant differences on 24 (out of 108) lines maximum absolute difference in column 13 is 0.00010846878486765 maximum relative difference in column 13 is 2.89015233246968 (insignificant differences on 64 lines) One possibility is that the grids in this test are so small that the grid structure is being affected by the Carpet regridding algorithm which ensures proper nesting, and this algorithm might have changed unavoidably between the stable and development versions of Carpet. If we confirm that this is the case, we could either use a larger grid to prevent this from happening, or just regenerate the data. It would be useful to add output of the coordinate gridfunctions to catch the cases where the grids are a different shape. (Reporting against Carpet so it can be fixed as part of the move to the development version) -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/496> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #410: CarpetIOHDF5 may segfault when one_file_per_group is selected
by Einstein Toolkit 09 Nov '11

09 Nov '11

#410: CarpetIOHDF5 may segfault when one_file_per_group is selected --------------------------------+------------------------------------------- Reporter: bmundim | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: Carpet git version | --------------------------------+------------------------------------------- I was facing one of those cryptic MPI error messages on Ranger, where your job quits without any useful error message. It turns out that this parameter file had CarpetIOHDF5::one_file_per_group = "yes" CarpetIOHDF5::out2D_vars = " ADMBase::gxx" and CarpetIOHDF5 would try to loop over the group variables when just one of them was selected. As a result it has accessed memory address that it was not supposed to, consequently killing the job. I have attached the stack back trace. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/410> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #431: Update some external libraries
by Einstein Toolkit 09 Nov '11

09 Nov '11

#431: Update some external libraries -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- Several external libraries have new versions available: LAPACK PETSc curl git These are only minor updates. I suggest to apply them. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/431> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

← Newer
1
...
6
7
8
9
10
11
12
...
19
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac September 2011