Trac February 2013

trac@lists.einsteintoolkit.org

1 participants
177 discussions

[Einstein Toolkit] #650: User is not asked for Mercurial authentication information initially
by Einstein Toolkit 23 May '13

23 May '13

#650: User is not asked for Mercurial authentication information initially ---------------------------+------------------------------------------------ Reporter: hinder | Owner: eric9 Type: defect | Status: new Priority: major | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------+------------------------------------------------ When running GetComponents without the "-a" (anonymous) option, the user is asked initially for authentication information for any authenticated repositories. However, the Carpet repository is not included in this list. This leads to the authentication prompt much later when Carpet is actually being checked out, and here it is not possible to say "anonymous". I believe the problem occurs on line 846 of GetComponents: {{{ # if AUTH_URL is defined we want to find the username: if ( defined( $component->{AUTH_URL} ) and ( $component->{TYPE} eq 'cvs' or $component->{TYPE} eq 'svn' or $component->{TYPE} eq 'darcs' or $component->{TYPE} eq 'git' ) ) { }}} where Mercurial (hg) is not included in that list. The attached (untested) patch adds hg to that list, but I don't know if this is sufficient to fix the problem. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/650> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #1229: provide downloadable tarball of ET
by Einstein Toolkit 22 May '13

22 May '13

#1229: provide downloadable tarball of ET -------------------------------------+-------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit website | Version: Keywords: | -------------------------------------+-------------------------------------- I created a mock up download page (with one paragraph changed) with a tar ball of the current release version of the ET. http://www.tapir.caltech.edu/~rhaas/ET/ To provide the tarball we would need some way to store data on the web- sever that is not archived via svn (or live with ~200MB commmits). Alternatively I am happy to have the tarball live in in my webspace and keep the link though a more "permanent" storage site might be more useful. The tarball would need to be updated whenever the release branch(es) change. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1229> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 15

[Einstein Toolkit] #1267: CCTK_Info, CCTK_Warn, CCTK_Error not documented
by Einstein Toolkit 22 May '13

22 May '13

#1267: CCTK_Info, CCTK_Warn, CCTK_Error not documented ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | ----------------------+----------------------------------------------------- The reference manual lacks documentation for CCTK_Info, CCTK_Warn, CCTK_Error. Only their "V" equivalents and their macro equivalents are documented. In addition, I see that the documentation claims that these three functions are "internal" functions. This is not true -- if this was true, they would have CCTKi_ prefixes. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1267> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1221: Reduction weight anomaly when using zero CoordBase::boundary_shiftout_*
by Einstein Toolkit 17 May '13

17 May '13

#1221: Reduction weight anomaly when using zero CoordBase::boundary_shiftout_* ------------------------+--------------------------------------------------- Reporter: bentivegna | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: Carpet | Version: development version Keywords: | ------------------------+--------------------------------------------------- When using a refinement level that covers the entire grid, and setting the CoordBase::boundary_shiftout_* parameters to zero, the following warning appears: INFO (CarpetReduce): Simulation domain volume: 8000 INFO (CarpetReduce): Additional excised volume: 0 INFO (CarpetReduce): Reduction weight sum: 9141 WARNING level 1 in thorn CarpetReduce processor 0 host socket.local (line 137 of /Users/bennie/CactusTrees/TrueAMR/arrangements/Carpet/CarpetReduce/src/mask_test.c): -> Simulation domain volume and reduction weight sum differ This can be reproduced using the attached parameter file. The problem seems to arise at the boundaries of the restricted region: I would expect the coarse grid to carry zero reduction weight everywhere (as it does if the shiftout is one), but the boundaries have a non-zero weight instead, which leads to double counting, and hence the difference between domain volume and weight sum. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1221> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 13

[Einstein Toolkit] #1171: WeylScal4 schedule order is incorrect
by Einstein Toolkit 17 May '13

17 May '13

#1171: WeylScal4 schedule order is incorrect -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: WeylScal4 testsuite | -----------------------------------+---------------------------------------- WeylScal4 contains a calculation for computing the I and J invariants from the Psis. This calculation is not scheduled explicitly after the Psis. Therefore, Cactus will probably schedule the routines alphabetically, which should be wrong. This should be corrected either with an After or Schedule element in the calculation. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1171> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 12

[Einstein Toolkit] #283: Update and make CoreDoc.pdf available in the EinsteinToolkit website
by Einstein Toolkit 10 May '13

10 May '13

#283: Update and make CoreDoc.pdf available in the EinsteinToolkit website -------------------------------------+-------------------------------------- Reporter: bmundim | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit website | Version: Keywords: | -------------------------------------+-------------------------------------- The advanced concepts document: http://cactuscode.org/documentation/CoreDoc.pdf should be updated and made available in the ET website, both in pdf and html. Does anyone know where its .tex file version is located? Thanks, Bruno. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/283> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #931: CartGrid3D's dependency on Boundary
by Einstein Toolkit 10 May '13

10 May '13

#931: CartGrid3D's dependency on Boundary --------------------+------------------------------------------------------- Reporter: jtao | Owner: Type: defect | Status: new Priority: minor | Milestone: Cactus_4.1.0 Component: Cactus | Version: Cactus_4.0.0 Keywords: | --------------------+------------------------------------------------------- CartGrid3D_ApplyBC in CartGrid3D is scheduled in BoundaryConditions, which is defined in the Boundary thorn. I can see that this is related with the symmetric boundary conditions but could we handle it in boundary ? It seems to me that it is not a good idea to have the grid thorn depend on the boundary thorn. While making boundary depending on grid is more reasonable if we have to introduce the dependency between these two thorns. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/931> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 10

[Einstein Toolkit] #808: testsuites in HDF5
by Einstein Toolkit 10 May '13

10 May '13

#808: testsuites in HDF5 -------------------------+-------------------------------------------------- Reporter: jtao | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Cactus_4.1.0 Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- Instead of constructing tools to compare Carpet ascii output from multiple processes, how about building tools to diff files HDF5 ? Compared to ASCII: HDF5 testsuites may have several advantages: small, fast, portable, independent of number of process. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/808> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 13

[Einstein Toolkit] #1111: Missing fortran compiler prevents CCTK_REAL8 from being defined.
by Einstein Toolkit 09 May '13

09 May '13

#1111: Missing fortran compiler prevents CCTK_REAL8 from being defined. ---------------------+------------------------------------------------------ Reporter: sbrandt | Owner: Type: defect | Status: new Priority: major | Milestone: Cactus_4.1.0 Component: Cactus | Version: Cactus_4.0.0 Keywords: | ---------------------+------------------------------------------------------ If the fortran compiler is missing or invalid, Cactus does not create the definition for CCTK_REAL8, CCTK_REAL4, etc. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1111> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #1261: Suspicious logic in NewRad thorn
by Einstein Toolkit 09 May '13

09 May '13

#1261: Suspicious logic in NewRad thorn -----------------------------------------+---------------------------------- Reporter: wolfgang.kastaun@… | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: newrad boundary | -----------------------------------------+---------------------------------- In NewRad boundary conditions, there is some logic to determine for which faces/edges/corners BC should be applied. This logic is duplicated in two files, extrap.cc and newrad.cc. In the latter, there is the line (324 in the Oersted release) all_physbnd_or_ghostbnd = all_physbnd_or_ghostbnd and (is_physbnd[2*d+0] or not is_ipbnd[2*d+0]); for the left boundary, while the same thing for the right boundary reads all_physbnd_or_ghostbnd = all_physbnd_or_ghostbnd and (is_physbnd[2*d+1] or not is_ipbnd[2*d+1]); in line 337. In extrap.cc, the right boundary is treated the same, for the left one however we have in line 136 all_physbnd_or_ghostbnd = all_physbnd_or_ghostbnd and (is_physbnd[2*d+0] or is_ipbnd[2*d+0]); Note the "or" instead of "or not". I have no idea what this conditions are supposed to do, but it looks inconsistent. If it is correct, can someone enlighten me ? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1261> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 13

← Newer
1
...
9
10
11
12
13
14
15
...
18
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac February 2013