Trac November 2011

trac@lists.einsteintoolkit.org

2 participants
166 discussions

[Einstein Toolkit] #581: Pass unallocated arrays to Fortran as NULL pointers
by Einstein Toolkit 09 Nov '11

09 Nov '11

#581: Pass unallocated arrays to Fortran as NULL pointers -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- The deleted comment is wrong. We should always pass unallocated arrays to Fortran to catch allocation errors. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/581> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #596: ET installation problem.
by Einstein Toolkit 08 Nov '11

08 Nov '11

#596: ET installation problem. -----------------------+---------------------------------------------------- Reporter: anonymous | Type: defect Status: new | Priority: major Milestone: | Component: Other Version: | Keywords: -----------------------+---------------------------------------------------- Hello, My name is Maxim. I try to get the ET from instruction in tutorial: On the step wget --no-check-certificate https://github.com/gridaphobe/CRL/raw/ET_2011_05/GetComponents chmod 755 GetComponents ./GetComponents -a http://svn.einsteintoolkit.org/manifest/branches/ET_2011_05/einsteintoolkit… Not all throns is downloaded. 0 components checked out. 140 components updated. Unable to process simfactory Unable to process LSUThorns/QuasiLocalMeasures Unable to process LSUThorns/SummationByParts Unable to process LSUThorns/Vectors Unable to process KrancNumericalTools/GenericFD Unable to process McLachlan/doc Unable to process McLachlan/m Unable to process McLachlan/par Unable to process McLachlan/ML_ADMConstraints Unable to process McLachlan/ML_ADMQuantities Unable to process McLachlan/ML_BSSN Unable to process McLachlan/ML_BSSN_Helper Unable to process McLachlan/ML_BSSN_O2 Unable to process McLachlan/ML_BSSN_O2_Helper Unable to process McLachlan/ML_BSSN_Test Unable to process Carpet/doc Unable to process Carpet/Carpet Unable to process Carpet/CarpetEvolutionMask Unable to process Carpet/CarpetIOASCII Unable to process Carpet/CarpetIOBasic Unable to process Carpet/CarpetIOHDF5 Unable to process Carpet/CarpetIOScalar Unable to process Carpet/CarpetInterp Unable to process Carpet/CarpetInterp2 Unable to process Carpet/CarpetLib Unable to process Carpet/CarpetMask Unable to process Carpet/CarpetReduce Unable to process Carpet/CarpetRegrid Unable to process Carpet/CarpetRegrid2 Unable to process Carpet/CarpetSlab Unable to process Carpet/CarpetTracker Unable to process Carpet/LoopControl Unable to process GetComponents Time Elapsed: 108 minutes, 23 seconds I have repeat it 3 times, the result is the same. How to solve this problem? With Best Regards, Maxim -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/596> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #638: Enable symbols for backtraces
by Einstein Toolkit 08 Nov '11

08 Nov '11

#638: Enable symbols for backtraces -------------------------+-------------------------------------------------- Reporter: hinder | Owner: eschnett Type: enhancement | Status: new Priority: major | Milestone: ET_2011_10 Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- The attached patch adds the option -rdynamic to CFLAGS and CXXFLAGS for all optionlists using the Intel or GCC compilers. This makes backtraces from Carpet (new in ET_2011_10) contain meaningful symbols rather than gibberish or nothing. This has been present in datura and damiana for a long time and works well. From man gcc: -rdynamic Pass the flag -export-dynamic to the ELF linker, on targets that support it. This instructs the linker to add all symbols, not only used ones, to the dynamic symbol table. This option is needed for some uses of “dlopen” or to allow obtaining backtraces from within a program. Given the usefulness of good backtraces and the nature of this option, I think it might be feasible and useful to get this in before the release, assuming that there will be another round of tests. I have only enabled this for GCC and Intel because I haven’t tested it with other compilers, nor with Fortran. I clearly haven't tested this on all the machines it applies to. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/638> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #136: Don't rebuild external libraries so often
by Einstein Toolkit 08 Nov '11

08 Nov '11

#136: Don't rebuild external libraries so often -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- One way to keep the external libraries that have been built would be the following. Create a dummy configuration "ext" where all external libraries are built. When another configuration is built, it should be easy to specify to look there for the external libraries, or maybe this should even be the default. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/136> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 27

[Einstein Toolkit] #554: GetComponents deletes local changes
by Einstein Toolkit 08 Nov '11

08 Nov '11

#554: GetComponents deletes local changes ------------------------+--------------------------------------------------- Reporter: eschnett | Owner: eschnett Type: defect | Status: new Priority: blocker | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- After checking out an svn repository with GetComponents, I manually switched to a different branch, and added local changes. GetComponents --update then checked out the original branch and deleted all my local changes. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/554> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #508: list-simulations displays job ID when it doesn't make any sense
by Einstein Toolkit 08 Nov '11

08 Nov '11

#508: list-simulations displays job ID when it doesn't make any sense ------------------------+--------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- The list-simulations command displays a restart number and job ID even for simulations for which there is no job in the queue. The attached patch omits these in that case. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/508> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #222: Dubious code in Hydro_InitExcision.c
by Einstein Toolkit 08 Nov '11

08 Nov '11

#222: Dubious code in Hydro_InitExcision.c ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | ----------------------+----------------------------------------------------- Hydro_InitExcision.c contains the following code: if ( (hydro_initexcision_coordinate_length <= 0.0) && ( ( x_frac > 0.5 - hydro_initexcision_fraction) && ( x_frac < 0.5 + hydro_initexcision_fraction) && ( y_frac > 0.5 - hydro_initexcision_fraction) && ( y_frac < 0.5 + hydro_initexcision_fraction) && ( z_frac > 0.5 - hydro_initexcision_fraction) && ( z_frac < 0.5 + hydro_initexcision_fraction) ) || ( (hydro_initexcision_coordinate_length > 0.0) && ( fabs(x[point]-hydro_initexcision_position_x) <= hydro_initexcision_coordinate_length*0.5) && ( fabs(y[point]-hydro_initexcision_position_y) <= hydro_initexcision_coordinate_length*0.5) && ( fabs(z[point]-hydro_initexcision_position_z) <= hydro_initexcision_coordinate_length*0.5) ) ) This code has an "and" (&&) and an "or" (||) operation at top level. Is this intended? The code would be clearer with an additional set of parenthesis, or by introducing a suitable set of temporaries for sub- expressions. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/222> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #545: Use ssh ProxyCommand instead of multiple ssh commands
by Einstein Toolkit 08 Nov '11

08 Nov '11

#545: Use ssh ProxyCommand instead of multiple ssh commands -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: eschnett Type: enhancement | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- This would simplify quoting, thus also simplify the screen output, and may speed up things on remote connections. Here is an example: ssh -Y -o ProxyCommand='ssh eschnetter(a)mars.perimeterinstitute.ca nc -w 1 curry.pi.local 22' eschnett(a)curry.pi.local -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/545> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #644: Change documentation to talk about SVN instead of CVS
by Einstein Toolkit 08 Nov '11

08 Nov '11

#644: Change documentation to talk about SVN instead of CVS --------------------+------------------------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | --------------------+------------------------------------------------------- The current documentation contains outdated references to CVS. Cactus is now managed using SVN. This patch to the documentation updates the information. It also removes a detailed description of CVS and leaves only a basic guide, pointing users instead to the online SVN manual. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/644> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #643: UserGuide: Document current TRAC system instead of GNATS for problem reports
by Einstein Toolkit 08 Nov '11

08 Nov '11

#643: UserGuide: Document current TRAC system instead of GNATS for problem reports ---------------------------+------------------------------------------------ Reporter: hinder | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: documentation | ---------------------------+------------------------------------------------ The Cactus documentation (a shared appendix between the User Guide and the Reference Manual) currently talks about using the GNATS problem reporting system. We now use TRAC. The attached patch updates the documentation to describe the new system. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/643> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac November 2011