Trac April 2013

trac@lists.einsteintoolkit.org

1 participants
178 discussions

[Einstein Toolkit] #705: Activation Order in Parameter Files
by Einstein Toolkit 24 May '13

24 May '13

#705: Activation Order in Parameter Files -------------------------+-------------------------------------------------- Reporter: sbrandt | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Cactus_4.1.0 Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- At the moment the ActiveThorns list is sensitive to the order in which thorns are activated if the ActiveThorns parameter is updated multiple times. However, it is not sensitive to the order in which thorns are activated if all thorns are specified in a single line. This inconsistency should be removed, and the order should not matter in either case. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/705> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #1307: Default output directory is '$parfile'
by Einstein Toolkit 24 May '13

24 May '13

#1307: Default output directory is '$parfile' ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: knarf@… Type: defect | Status: new Priority: critical | Milestone: ET_2013_05 Component: Other | Version: Keywords: | ----------------------+----------------------------------------------------- The default output directory is currently '$parfile', but this parameter value is not replaced by the name of the parameter file. It seems that default parameter values are not run through the parser, which would expand "$parfile"? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1307> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 10

[Einstein Toolkit] #526: Reorder ticket states
by Einstein Toolkit 23 May '13

23 May '13

#526: Reorder ticket states ----------------------------------+----------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit trac | Version: Keywords: | ----------------------------------+----------------------------------------- The order in which the ticket states is displayed (in the form where one modifies the ticket state) should be the natural order in which a ticket progresses. The current order is somewhat random. I suggest this order: new confirmed accept reassign review resolve -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/526> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #519: Add all ET repositories to TRAC
by Einstein Toolkit 23 May '13

23 May '13

#519: Add all ET repositories to TRAC ----------------------------------+----------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit trac | Version: Keywords: | ----------------------------------+----------------------------------------- TRAC provides integration with version control systems. It has a list of repositories, and specific changesets and files can be referred to in ticket comments and wiki pages using a convenient syntax. Several ET repositories have been added already. I think this feature is useful, and that the remaining repositories should be added. It would be nice if the links were easier to type. I propose omitting the arrangement name from the repositories, as all thorn names are probably unique, and avoiding spaces which require extra quoting. We have several repositories in Git and Mercurial. It would be nice to include those as well. I believe that there are TRAC plugins to accomplish this in the same way as for SVN. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/519> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1232: Improve output format of Carpet timer trees
by Einstein Toolkit 23 May '13

23 May '13

#1232: Improve output format of Carpet timer trees -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: Carpet | Version: Keywords: | -------------------------+-------------------------------------------------- Marek Blazewicz reports: I was using the timer tree in Carpet. Because it was not too nicely outputted, and I had to format it manually each time, I've fixed it ;). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1232> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1184: Update ubuntu.cfg
by Einstein Toolkit 23 May '13

23 May '13

#1184: Update ubuntu.cfg -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- I suggest to update ubuntu.cfg: - remove some outdated comments - consolidate Fortran line length options - add -ffast-math - correct Fortran OpenMP flag - move -rdynamic to LDFLAGS - add -Wall {{{ $ svn diff ubuntu.cfg Index: ubuntu.cfg =================================================================== --- ubuntu.cfg (revision 1854) +++ ubuntu.cfg (working copy) @@ -19,38 +19,32 @@ CPPFLAGS = -DMPICH_IGNORE_CXX_SEEK FPPFLAGS = -traditional -# no -msse3 -CFLAGS = -g3 -march=native -std=gnu99 -rdynamic -CXXFLAGS = -g3 -march=native -std=gnu++0x -rdynamic +CFLAGS = -g3 -march=native -std=gnu99 +CXXFLAGS = -g3 -march=native -std=gnu++0x F77FLAGS = -g3 -march=native -fcray-pointer -ffixed-line-length-none -F90FLAGS = -g3 -march=native -fcray-pointer -ffixed-line-length-none -LDFLAGS = +F90FLAGS = -g3 -march=native -fcray-pointer -ffixed-line-length-none -ffree-line-length-none +LDFLAGS = -rdynamic -LIBDIRS = +LIBDIRS = C_LINE_DIRECTIVES = yes F_LINE_DIRECTIVES = yes -# -check-uninit fails for asm output operands DEBUG = no CPP_DEBUG_FLAGS = -DCARPET_DEBUG FPP_DEBUG_FLAGS = -DCARPET_DEBUG C_DEBUG_FLAGS = -O0 CXX_DEBUG_FLAGS = -O0 -F77_DEBUG_FLAGS = -O0 -ffixed-line-length-none -F90_DEBUG_FLAGS = -O0 -ffree-line-length-none +F77_DEBUG_FLAGS = -O0 +F90_DEBUG_FLAGS = -O0 -# On Abe, the options -O3, -xT, and -ip lead to segmentation faults -# near MPI calls -# With Intel 9, using -ip prevents debug information for local variables -# With Intel 9, using -O3 leads to very long compile times (> 45 minutes) OPTIMISE = yes CPP_OPTIMISE_FLAGS = -DKRANC_VECTORS # -DCARPET_OPTIMISE -DNDEBUG FPP_OPTIMISE_FLAGS = # -DCARPET_OPTIMISE -DNDEBUG -C_OPTIMISE_FLAGS = -O2 -CXX_OPTIMISE_FLAGS = -O2 -F77_OPTIMISE_FLAGS = -O2 -F90_OPTIMISE_FLAGS = -O2 +C_OPTIMISE_FLAGS = -O2 -ffast-math +CXX_OPTIMISE_FLAGS = -O2 -ffast-math +F77_OPTIMISE_FLAGS = -O2 -ffast-math +F90_OPTIMISE_FLAGS = -O2 -ffast-math PROFILE = no CPP_PROFILE_FLAGS = @@ -62,21 +56,23 @@ OPENMP = no CPP_OPENMP_FLAGS = -fopenmp -FPP_OPENMP_FLAGS = -D_OPENMP +FPP_OPENMP_FLAGS = -fopenmp C_OPENMP_FLAGS = -fopenmp CXX_OPENMP_FLAGS = -fopenmp F77_OPENMP_FLAGS = -fopenmp F90_OPENMP_FLAGS = -fopenmp WARN = yes -CPP_WARN_FLAGS = -FPP_WARN_FLAGS = -C_WARN_FLAGS = -CXX_WARN_FLAGS = -F77_WARN_FLAGS = -F90_WARN_FLAGS = +CPP_WARN_FLAGS = -Wall +FPP_WARN_FLAGS = -Wall +C_WARN_FLAGS = -Wall +CXX_WARN_FLAGS = -Wall +F77_WARN_FLAGS = -Wall +F90_WARN_FLAGS = -Wall -MPI_DIR = /usr + + +MPI_DIR = /usr MPI_INC_DIRS = /usr/include/mpich2 MPI_LIB_DIRS = /usr/lib MPI_LIBS = mpich fmpich mpl }}} -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1184> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 10

[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

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac April 2013