Trac September 2014

trac@lists.einsteintoolkit.org

1 participants
133 discussions

[Einstein Toolkit] #816: include SphericalHarmonicReconASCII from incoming in PITTNULLCode
by Einstein Toolkit 04 Aug '15

04 Aug '15

#816: include SphericalHarmonicReconASCII from incoming in PITTNULLCode -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- Christian Reisswig provided a copy of SphericalHarmonicReconASCII and alternative thorn that reads in CCE boundary data (similar SphericalHarmonicRecon) but supporting a wider variety of input file formats (HDF5 among them, irrespective of the name). Used by SpEC and Llama. There are no docs or test cases as of now. Test data would be welcome (SpEC, Llama or Cactus provided, I don't think it makes a difference). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/816> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 17

[Einstein Toolkit] #1637: MoL should automatically allocate storage for sufficient timelevels of evolved variables
by Einstein Toolkit 24 Jul '15

24 Jul '15

#1637: MoL should automatically allocate storage for sufficient timelevels of evolved variables -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: MoL | -------------------------+-------------------------------------------------- The MoL thorn requires that all evolved variables have at least two timelevels of data, even if the integration method (e.g. RK4) does not need any past timelevels. It uses one of these timelevels as scratch space, potentially in addition to any other scratch space variables. In the case where at least two timelevels are needed for other reasons, this is more efficient than allocating an extra scratch space variable. Rather than requiring the evolution thorn to allocate at least two timelevels of storage for these variables, MoL should ensure sufficient timelevels via the flesh API. A related issue is that using timelevels for this purpose is wasteful in situations where the timelevel is not used for any other purpose, since the timelevel will be checkpointed even though it is only being used for temporary storage. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1637> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #1377: GRHydro_Bondi.c and GRHydro_BondiM.c use M_PI
by Einstein Toolkit 16 Jun '15

16 Jun '15

#1377: GRHydro_Bondi.c and GRHydro_BondiM.c use M_PI -----------------------------------+---------------------------------------- Reporter: sbrandt | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: GRHydro M_PI | -----------------------------------+---------------------------------------- GRHydro_Bondi.c and GRHydro_BondiM.c use M_PI. This was a problem on Tianhe-1A. I'd suggest adding the following to both files: #ifndef M_PI #define M_PI 3.141592653589793 #endif -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1377> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #1252: Thorn configuration scripts should not be run if there are missing thorns
by Einstein Toolkit 09 Jun '15

09 Jun '15

#1252: Thorn configuration scripts should not be run if there are missing thorns -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- If there are thorns present in the thornlist which are not present in the source tree, Cactus currently displays the corresponding error message, and then runs the rest of the CST including thorn configuration scripts. Since these can build large external libraries (e.g. LORENE), it can be a long time before the user notices that the build has failed. I would prefer if Cactus aborted before running the CST scripts. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1252> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #796: Support https for einsteintoolkit.org
by Einstein Toolkit 22 May '15

22 May '15

#796: Support https for einsteintoolkit.org -------------------------------------+-------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit website | Version: Keywords: | -------------------------------------+-------------------------------------- To show our commitment to privacy and IT safety, we should enable https support for our web site. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/796> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #1506: compiling Cactus on Windows
by Einstein Toolkit 17 May '15

17 May '15

#1506: compiling Cactus on Windows --------------------------------+------------------------------------------- Reporter: jtao | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: compiling, windows | --------------------------------+------------------------------------------- Hi, In the process to create the cactusBSSN benchmark for SPEC, I worked with Mat from PGI(now NVIDIA) to help resolve some compilation issues on Windows. I don't have patches for each one of them, but attemptive solutions could be found in the email below. These are not critical issues but it would be good to be resolved to help future windows users if there is any. Regards, Jian Mathew COLGROVE wrote: > Hi Jian, > > I've been working on porting cactusBSSN to Windows. After working through some header file configuration, I encountered several undefined references. I've been able to work around some of them, but a few others I need some help with. > > 1) "STDOUT_FILENO" and "STDERR_FILENO" in Cactus/main/Warnlevel.c > These symbols are found in "unistd.h" which is not available on Windows. I just commented these lines out since I don't think this section is executed. Though, the proper fix would be to define then in > the cctk_Config.h file if not "HAVE_UNISTD_H" is not. The function isatty is defined in unistd.h. A conditional macro will be necessary for that function as well in this case. #if HAVE_UNISTD_H if (!isatty (STDOUT_FILENO)) val = ""; #endif > 2) "hypot" and "copysign" in Cactus/main/Complex.c > > Windows does support "hypot" and "copysign", however they spell them "_hypot" and "_copysign". To work around, I created two versions of each macro that use these symbols. I will probably do the same. > 3) "regexec", "regfree", and "regcomp" in Cactus/main/Parameters.c and Cactus/utils/misc.c > > Windows does not support these functions. We may be able to integrate a port from glibc into the benchmark but I would rather not. Since previous versions of Cactus did not used these symbols, can we use an older version other these files? As a matter of fact, Cactus includes files from the src of the GNU C library. You can find them under Your_Cactus/src/gnu. It is likely that you pre-configured Cactus on a linux box or other systems which provide the library. Cactus will then use the system default instead. To compiler regex.c getopt.c distributed with Cactus, you need to go to Your_Cactus/configs/spec/config-data/ and set both BUILD_GETOPT BUILD_REGEX to yes. # GNU stuff BUILD_GETOPT = yes BUILD_REGEX = yes This will solve #4 below as well. > 4) "getopt_long_only", "optarg", and "optind" in Cactus/main/ProcessCommandLine.c > > Again, there is no Windows equivalent for these symbols. We may be able to integrate something from http://gnuwin32.sourceforge.net/packages/libgw32c.htm, but I would rather not. Since previous versions of Cactus did not used these symbols, can we use an older version other this file? > > 5) "gethostname" and "gethostbyname" in Cactus/utils/Network.c > > Windows does have these functions but we'd need to link with a DLL which I'd rather not have to do (the user should have the option on how to link). Though, I think we'd be safe to remove these functions. Yes, the prototypes of gethostname and gethostbyname can be found in winsock2.h, and Cactus knows how to deal with them on Windows. --------------------------------------- Network.c : ... #elif defined HAVE_WINSOCK2_H #include <winsock2.h> #endif /* HAVE_WINSOCK2_H */ ... --------------------------------------- If linking DLL will be an issue, I would suggest you keep Util_GetHostName but make it a dummy function since Util_GetHostName serves as the interface to gethostname for Cactus. Regards, Jian -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1506> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #1211: CarpetIOScalar should write file info for restart files
by Einstein Toolkit 22 Apr '15

22 Apr '15

#1211: CarpetIOScalar should write file info for restart files --------------------+------------------------------------------------------- Reporter: knarf | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: Carpet | Version: Keywords: | --------------------+------------------------------------------------------- Currently Carpet doesn't write file info for files created by a restarted simulation (from a checkpoint, writing into a new file). It should instead write the header if it created the file - which means it need to check whether it appends or created the file new. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1211> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1282: Enable HDF5 compression by default in Carpet
by Einstein Toolkit 22 Apr '15

22 Apr '15

#1282: Enable HDF5 compression by default in Carpet -------------------------+-------------------------------------------------- Reporter: hinder | Owner: eschnett Type: enhancement | Status: new Priority: major | Milestone: Component: Carpet | Version: Keywords: | -------------------------+-------------------------------------------------- The current default for CarpetIOHDF5::compression_level is 0 (no compression). I have been using compression in most of my HDF5 files for years, and have never run into any problem. CPUs are typically much faster than storage nowadays. I propose that the compression level should default to 9. This would affect output and checkpoint files, and could lead to huge space savings. Apart from the checkpoint files being written and read quicker and taking less disk space, the user should not notice, as the HDF5 library handles compression transparently. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1282> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 8

[Einstein Toolkit] #1617: Calls to Accelerator_NotifyDataModified should be paired with calls to Accelerator_RequireInvalidData
by Einstein Toolkit 25 Mar '15

25 Mar '15

#1617: Calls to Accelerator_NotifyDataModified should be paired with calls to Accelerator_RequireInvalidData -----------------------------------+---------------------------------------- Reporter: sbrandt | Owner: Type: defect | Status: new Priority: minor | Milestone: Cactus_4.3.0 Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- Calls to Accelerator_NotifyDataModified should be paired with calls to Accelerator_RequireInvalidData, otherwise there's a risk of seg fault in Accelerator_NotifyDataModified due to a missing accelerator data structure. MoL fails to do this in Operators.c. Patch attached. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1617> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1612: reace condition when building Cactus utilities
by Einstein Toolkit 24 Mar '15

24 Mar '15

#1612: reace condition when building Cactus utilities --------------------+------------------------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: | --------------------+------------------------------------------------------- I just compiled on bluewaters and received output {{{ Done creating cactus_simO3. All done ! Building utilities for simO3 Building utilities for simO3 ... Creating hdf5_recombiner in /mnt/a/u/sciteam/rhaas/ET_trunk/exe/simO3 from /mnt/a/u/sciteam/rhaas/ET_trunk/configs/simO3/build/CarpetIOHDF5/hdf5_recombiner.o mkdir: cannot create directory `/tmp/1399318629': File exists mkdir: cannot create directory `/tmp/1399318629': File exists }}} with the full (last part of) the log in the attached file. So it seems as if we have a race condition in the make system that causes it to try and build the utilities twice (in parallel). On bluewaters simfactory (which I used) builds Cactus using 16 processes. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1612> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

← Newer
1
...
5
6
7
8
9
10
11
...
14
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac September 2014