Users June 2010

users@lists.einsteintoolkit.org

19 participants
61 discussions

Re: [Users] [Commits] [svn:einsteintoolkit] manifest/ (Rev. 19)
by Erik Schnetter 08 Jun '10

08 Jun '10

On Jun 8, 2010, at 9:24 , roland.haas(a)physics.gatech.edu wrote: > User: rhaas > Date: 2010/06/08 09:24 AM > > Modified: > / > einsteintoolkit.th > > Log: > remove extraneous '!CHECKOUT = ' since GetComponents uses only the > last > CHECKOUT statement for each TARGET ignoring previous ones > > File Changes: > > Directory: / > ============ > > File [modified]: einsteintoolkit.th > Delta lines: +4 -4 > =================================================================== > --- einsteintoolkit.th 2010-06-08 14:09:42 UTC (rev 18) > +++ einsteintoolkit.th 2010-06-08 14:24:58 UTC (rev 19) > @@ -224,9 +224,9 @@ > McLachlan/ML_BSSN_O2_Helper > McLachlan/ML_ADMConstraints > McLachlan/ML_ADMQuantities > -!CHECKOUT = McLachlan/doc > -!CHECKOUT = McLachlan/m > -!CHECKOUT = McLachlan/par > +McLachlan/doc > +McLachlan/m > +McLachlan/par This does not work, since it treats "doc" etc. as thorns, leading to build errors. I have reverted both patches, will discuss this before doing anything. -erik -- Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.cct.lsu.edu/~eschnett/

1 0

Re: [Users] [Maintainers] Fwd: [Commits] [svn:einsteintoolkit] www/about/members/ (Rev. 180)
by Roland Haas 08 Jun '10

08 Jun '10

Hello Gabrielle, > This page is showing quite right for me in Safari, I assume you mean "not quite right"? > Humin Zhang from > Washington University has disappeared (his name is in the html file), > and the little circles for the items are partly trimmed. I could just > remove the item lists for the names to see if that fixes the circles, > but wondering if anyone has a real fix? This is most likely caused by me adding <ul class="column"> to the list of members (it looks fine with Firefox 3.0.1 under Linux with Humin Zhang present at the end of the list). Do you have the same problem with the credits page (also: what browser are you using)? Or with http://www.prism.gatech.edu/~rhaas3/etk/credits.html This seems to have worked at one time at least for Safari (on 2010-05-27 for Erik, could you try again please in case something changed [I added a css style for IE column-width: 30%]). I only have access to Linux based browsers unfortunately. Yours, Roland -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://keys.gnupg.net.

2 1

Kerr ID
by Scott Noble 07 Jun '10

07 Jun '10

Hello Users, I believe I found a minor typo in EinsteinInitialData/IDAnalyticBH/src/Kerr.c of the ET. Just a missing term in the denominator of the shift vector, so it will not likely affect many users. I have attached a patch. cheers, -- scott n.

1 0

Einstein_Toolkit compiling problem on abe
by Hui-Min Zhang 04 Jun '10

04 Jun '10

Hi, I try to compile the Einstein Toolkit on abe, with the ThornList 'einsteintoolkit.th' and config file ' simfactory/optionlists/abe-mvapich2.cfg', the compiling crashed in LORENE with error message ------------- /usr/local/intel/10.1.008/bin/icpc -c -g -debug all -inline-debug-info -traceback -align -restrict -I/u/ac/zhanghm/carpet/Cactus/configs/mycarpet/scratch/build-Lorene/Lorene/C++/Include -I/u/ac/zhanghm/carpet/Cactus/configs/mycarpet/scratch/build-Lorene/Lorene/C++/Include_extra sol_elliptic_sin_zec.C sol_elliptic_sin_zec.C(56): catastrophic error: could not open source file "gsl/gsl_sf_bessel.h" #include <gsl/gsl_sf_bessel.h> ^ compilation aborted for sol_elliptic_sin_zec.C (code 4) -------------- any suggestion on how to fix this ? Thanks. Hui-Min Zhang

2 1

SVN history
by Ian Hinder 04 Jun '10

04 Jun '10

Hi, I have just added some documentation for the Multipole thorn in EinsteinAnalysis. I checked out the thorn using the GetComponents script, and I notice that apart from my commit, and one from Frank, there is no other history information when I type "svn log". Was the history information discarded when the thorn was imported into SVN, or has GetComponents done some type of checkout which doesn't let me view the full history? The same is true of WeylScal4, in which I can only see commits since March. -- Ian Hinder ian.hinder(a)aei.mpg.de

3 3

Re: [Users] Meudon_Bin_BH compilation error
by azebrowski＠cct.lsu.edu 04 Jun '10

04 Jun '10

Hello, find -name bin_bh.h brings up nothing. My options aren't very fancy, I just have some pointers to MPICH2 modelled after some options I found in SimFactory: MPI=CUSTOM MPICH_DIR=/usr/lib64/mpich2/ MPI_INC_DIRS=/usr/include/mpich2-x86_64/ MPI_LIBS = mpich mpichf90 mpichcxx My full build log is at http://cct.lsu.edu/~azebrowski/build.log, but I took out the two parts for LORENE (looks OK) and where it fails below: Here is my build log for LORENE: make[2]: Entering directory `/home/ashley/Einstein/Cactus/configs/sample/build/LORENE' if [ ! -d ./ ] ; then mkdir -p ./ ; fi cd ./ ; make CCTK_TARGET=make.checked TOP=/home/ashley/Einstein/Cactus/configs/sample CONFIG=/home/ashley/Einstein/Cactus/configs/sample/config-data SRCDIR=/home/ashley/Einstein/Cactus/arrangements/ExternalLibraries/LORENE/src THORN=LORENE USESTHORNS="BLAS GSL LAPACK" -f /home/ashley/Einstein/Cactus/lib/make/make.subdir make[3]: Entering directory `/home/ashley/Einstein/Cactus/configs/sample/build/LORENE' make[3]: `make.checked' is up to date. make[3]: Leaving directory `/home/ashley/Einstein/Cactus/configs/sample/build/LORENE' cd cctk_Bindings; make CCTK_TARGET=make.checked TOP=/home/ashley/Einstein/Cactus/configs/sample CONFIG=/home/ashley/Einstein/Cactus/configs/sample/config-data SRCDIR=/home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE THORN=LORENE USESTHORNS="BLAS GSL LAPACK" -f /home/ashley/Einstein/Cactus/lib/make/make.subdir make[3]: Entering directory `/home/ashley/Einstein/Cactus/configs/sample/build/LORENE/cctk_Bindings' gcc -E -M /home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE/cctk_ThornBindings.c -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/gsl-1.12/include" -I"/usr/include/mpich2-x86_64/" -I"/usr/include/mpich2-x86_64/" -I"/home/ashley/Einstein/Cactus/arrangements/ExternalLibraries/LORENE/src" -I"/home/ashley/Einstein/Cactus/arrangements/ExternalLibraries/LORENE/src/include" -I"/home/ashley/Einstein/Cactus/configs/sample/config-data" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/include" -I"/home/ashley/Einstein/Cactus/src/include" -I"/home/ashley/Einstein/Cactus/arrangements" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/Configuration/Thorns" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/gsl-1.12/include" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE/include" -DTHORN_IS_LORENE -DCCODE > cctk_ThornBindings.c.d perl -pi -e "s,([^:]*),cctk_ThornBindings.c.o cctk_ThornBindings.c.d, if(m/: /); s:\s+\S*[/\\\](cctk_Functions\.h|CParameterStructNames\.h|cctk_Arguments\.h|definethisthorn\.h|FParameters.h|CParameters\.h)\b::g" cctk_ThornBindings.c.d make[3]: Leaving directory `/home/ashley/Einstein/Cactus/configs/sample/build/LORENE/cctk_Bindings' make[3]: Entering directory `/home/ashley/Einstein/Cactus/configs/sample/build/LORENE/cctk_Bindings' Preprocessing /home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE/cctk_ThornBindings.c { if test no = 'yes'; then echo '#line 1 "'/home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE/cctk_ThornBindings.c'"'; fi; cat /home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE/cctk_ThornBindings.c; } | perl -s /home/ashley/Einstein/Cactus/lib/sbin/c_file_processor.pl -line_directives=no -source_file_name=/home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE/cctk_ThornBindings.c /home/ashley/Einstein/Cactus/configs/sample/config-data > cctk_ThornBindings.c Compiling /home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE/cctk_ThornBindings.c current_wd=`pwd` ; cd /home/ashley/Einstein/Cactus/configs/sample/scratch ; gcc -pipe -std=gnu99 -O3 -c -o $current_wd/cctk_ThornBindings.c.o $current_wd/cctk_ThornBindings.c -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/gsl-1.12/include" -I"/usr/include/mpich2-x86_64/" -I"/usr/include/mpich2-x86_64/" -I"/home/ashley/Einstein/Cactus/arrangements/ExternalLibraries/LORENE/src" -I"/home/ashley/Einstein/Cactus/arrangements/ExternalLibraries/LORENE/src/include" -I"/home/ashley/Einstein/Cactus/configs/sample/config-data" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/include" -I"/home/ashley/Einstein/Cactus/src/include" -I"/home/ashley/Einstein/Cactus/arrangements" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/Configuration/Thorns" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/gsl-1.12/include" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE/include" -DTHORN_IS_LORENE -DCCODE Postprocessing /home/ashley/Einstein/Cactus/configs/sample/bindings/build/LORENE/cctk_ThornBindings.c ________________________________________________________________________ echo "" > make.checked make[3]: Leaving directory `/home/ashley/Einstein/Cactus/configs/sample/build/LORENE/cctk_Bindings' if [ -r /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a ] ; then echo Updating /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a ; else echo Creating /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a ; fi Creating /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a if [ -r /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a ] ; then rm -f /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a ; fi make -f /home/ashley/Einstein/Cactus/lib/make/make.thornlib /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a.objectlist make[3]: Entering directory `/home/ashley/Einstein/Cactus/configs/sample/build/LORENE' echo cctk_Bindings//cctk_ThornBindings.c.o > /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a.objectlist make[3]: Leaving directory `/home/ashley/Einstein/Cactus/configs/sample/build/LORENE' xargs -n 10000 ar rucs /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a < /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a.objectlist rm -f /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a.objectlist if test "xno" = "xyes" ; then ranlib -cs /home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_LORENE.a ; fi ________________________________________________________________________ make[2]: Leaving directory `/home/ashley/Einstein/Cactus/configs/sample/build/LORENE' Here is where it fails: Checking status of thorn Meudon_Bin_BH ________________________________________________________________________ make[2]: Entering directory `/home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH' if [ ! -d ./ ] ; then mkdir -p ./ ; fi cd ./ ; make CCTK_TARGET=make.checked TOP=/home/ashley/Einstein/Cactus/configs/sample CONFIG=/home/ashley/Einstein/Cactus/configs/sample/config-data SRCDIR=/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src THORN=Meudon_Bin_BH USESTHORNS="LORENE" -f /home/ashley/Einstein/Cactus/lib/make/make.subdir make[3]: Entering directory `/home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH' c++ -E -M /home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/check_parameters.cc -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/Export/C++/Include" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/C++/Include" -I"/usr/include/mpich2-x86_64/" -I"/usr/include/mpich2-x86_64/" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/include" -I"/home/ashley/Einstein/Cactus/configs/sample/config-data" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/include" -I"/home/ashley/Einstein/Cactus/src/include" -I"/home/ashley/Einstein/Cactus/arrangements" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/Configuration/Thorns" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/Export/C++/Include" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/C++/Include" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/include" -DTHORN_IS_Meudon_Bin_BH -DCCODE > check_parameters.cc.d perl -pi -e "s,([^:]*),check_parameters.cc.o check_parameters.cc.d, if(m/: /); s:\s+\S*[/\\\](cctk_Functions\.h|CParameterStructNames\.h|cctk_Arguments\.h|definethisthorn\.h|FParameters.h|CParameters\.h)\b::g" check_parameters.cc.d c++ -E -M /home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/Export/C++/Include" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/C++/Include" -I"/usr/include/mpich2-x86_64/" -I"/usr/include/mpich2-x86_64/" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/include" -I"/home/ashley/Einstein/Cactus/configs/sample/config-data" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/include" -I"/home/ashley/Einstein/Cactus/src/include" -I"/home/ashley/Einstein/Cactus/arrangements" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/Configuration/Thorns" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/Export/C++/Include" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/C++/Include" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/include" -DTHORN_IS_Meudon_Bin_BH -DCCODE > Bin_BH.cc.d /home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc:10:20: error: bin_bh.h: No such file or directory make[3]: Leaving directory `/home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH' make[3]: Entering directory `/home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH' Preprocessing /home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc { if test no = 'yes'; then echo '#line 1 "'/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc'"'; fi; cat /home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc; } | perl -s /home/ashley/Einstein/Cactus/lib/sbin/c_file_processor.pl -line_directives=no -source_file_name=/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc /home/ashley/Einstein/Cactus/configs/sample/config-data > Bin_BH.cc Compiling /home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc current_wd=`pwd` ; cd /home/ashley/Einstein/Cactus/configs/sample/scratch ; c++ -pipe -O3 -c -o $current_wd/Bin_BH.cc.o $current_wd/Bin_BH.cc -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/Export/C++/Include" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/C++/Include" -I"/usr/include/mpich2-x86_64/" -I"/usr/include/mpich2-x86_64/" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/include" -I"/home/ashley/Einstein/Cactus/configs/sample/config-data" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/include" -I"/home/ashley/Einstein/Cactus/src/include" -I"/home/ashley/Einstein/Cactus/arrangements" -I"/home/ashley/Einstein/Cactus/configs/sample/bindings/Configuration/Thorns" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/Export/C++/Include" -I"/home/ashley/Einstein/Cactus/configs/sample/scratch/build-Lorene/Lorene/C++/Include" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src" -I"/home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/include" -DTHORN_IS_Meudon_Bin_BH -DCCODE /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:10:20: error: bin_bh.h: No such file or directory /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc: In function ?void ID_Bin_BH_initialise(cGH*)?: /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:66: error: ?Bin_BH? was not declared in this scope /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:66: error: expected ?;? before ?bin_bh? /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:68: error: ?bin_bh? was not declared in this scope make[3]: *** [Bin_BH.cc.o] Error 1 make[3]: Leaving directory `/home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH' make[2]: *** [make.checked] Error 2 make[2]: Leaving directory `/home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH' make[1]: *** [/home/ashley/Einstein/Cactus/configs/sample/lib/libthorn_Meudon_Bin_BH.a] Error 2 make[1]: Leaving directory `/home/ashley/Einstein/Cactus' make: *** [sample] Error 2 Quoting Erik Schnetter <schnetter(a)cct.lsu.edu>: > On Jun 3, 2010, at 17:25 , azebrowski(a)cct.lsu.edu wrote: > >> Hello, >> >> I just checked out a copy of the EinsteinToolkit repos, but get the >> following error when compiling. It looks like it's looking for >> bin_bh.h, which I don't see anywhere in my Cactus tree. Does anyone >> have any idea how to fix this? >> >> Here's the error, >> >> Preprocessing >> /home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc >> Compiling >> /home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc >> /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:10:20: error: bin_bh.h: No such file >> or >> directory >> /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc: >> In >> function ?void ID_Bin_BH_initialise(cGH*)?: >> /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:66: >> error: ?Bin_BH? was not declared in this scope >> /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:66: >> error: expected ?;? before ?bin_bh? >> /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:68: >> error: ?bin_bh? was not declared in this scope > > > The file bin_bh.h is provided by the thorn LORENE. Can you send your > configuration options? Can you compile this thorn with SILENT=no and > make the output available? > > -erik > > -- > Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.cct.lsu.edu/~eschnett/

2 1

kranc checkout, GetComponents and GitHub repository
by Bruno Coutinho Mundim 03 Jun '10

03 Jun '10

Hi, when trying a fresh checkout of einsteintoolkit, I found the following error message: ----------------------------------------------------------------- Checking out module: KrancNumericalTools/GenericFD from repository: http://github.com/ianhinder/Kranc.git into: Cactus/arrangements cwd = /home/bruno/tmp/test git clone --depth 1 http://github.com/ianhinder/Kranc.git Cactus/git-repos/Kranc shallow over http or ftp not supported ----------------------------------------------------------------- ... Unable to process KrancNumericalTools/GenericFD. The option --depth 1 is not accepted by GitHub. I was able to clone it without a problem otherwise. Do we really need this option in GetComponents? Thanks, Bruno.

3 5

Meudon_Bin_BH compilation error
by azebrowski＠cct.lsu.edu 03 Jun '10

03 Jun '10

Hello, I just checked out a copy of the EinsteinToolkit repos, but get the following error when compiling. It looks like it's looking for bin_bh.h, which I don't see anywhere in my Cactus tree. Does anyone have any idea how to fix this? Here's the error, Preprocessing /home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc Compiling /home/ashley/Einstein/Cactus/arrangements/EinsteinInitialData/Meudon_Bin_BH/src/Bin_BH.cc /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:10:20: error: bin_bh.h: No such file or directory /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc: In function ?void ID_Bin_BH_initialise(cGH*)?: /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:66: error: ?Bin_BH? was not declared in this scope /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:66: error: expected ?;? before ?bin_bh? /home/ashley/Einstein/Cactus/configs/sample/build/Meudon_Bin_BH/Bin_BH.cc:68: error: ?bin_bh? was not declared in this scope Thank you for your help, -Ashley Zebrowski

2 1

Failing AHFinderDirect test cases.
by Peter Diener 02 Jun '10

02 Jun '10

Hi, I have been looking at why some of AHFinderDirect test cases fail. First I checked the tests running on 1 processor and found that the cause of the failing test cases was a bug fix made in 2005 where the tests had not been updated afterwards. For those tests I regenerated the output. One additional test failed by not producing output because it didn't converge to the specified tolerance. I wasn't able to find a version of the code (after the date that the test case had been created) that I was able to compile and that passed the test. For that reason (after discussing with Erik) I disabled that test by renaming the parameter file to someting not ending in .par. After that I realized that a lot of the tests failed when running on 2 procs. After some investigating, I realized that the cause was to be find in Exact. When going from 1 to 2 procs, the coordinates setup by CoordBase and CartGrid3d can differ at the roundoff level. In the particular case I was looking at in one case the y-coordinate was -3.3999999999999999 while in the other it was: -3.4000000000000004 so a difference only in the last digit. This introduced a difference of the computed 4-metric in the 2 last digits. Now Exact uses 2nd order finite differencing with an epsilon of 1.e-6 to calculate time derivatives of the 3-metric and and the spatial derivatives of the shift that is needed to calculate the extrinsic curvature. In this process there is a significant cancelletion of digits leading to a loss of 6-7 digits so the extrinsic curvature only agreed to 9-10 digits. In other grid points the coordinates were identical and so was the extrinsic curvature. So essentially the process of constructing the extrinsic curvature iteself lead to some arbitrary noise at the 9-10 digit level. When this was fed into AHFinderDirect the differences were amplified even more leading to differences in the mass at the 6th digit level. Currently Erik is working on improving this (by using higher order finite differencing with a larger epsilon), but the main conclusion is that we have to be very careful when making tests based on initial data from the current version of Exact and may have to reduce the accuracy criteria for pass/fail significantly. Cheers, Peter

3 2

Meeting Notes Jun 1st
by Frank Loeffler 01 Jun '10

01 Jun '10

Hi, here are the notes of today's meeting: The main topic was how the future development of the ET should happen. First, Erik explained what the current (not yet that old) policy states: 1 There will be stable branches from time to time 2 There is one development branch for most of the development 3 There might be extra branches if wished for. Commits to 1 and 2 have to have a review, unless they are trivial, development in 3 is up to the maintainer of that branch. Christian and Roland (?) said they thought the reviews only apply to 1, not also 2. Frank suggested to go with Christians email-suggestion, which would: - try to avoid branches, but might have - have stable branches - have (almost) free development in /trunk Frank noted that in order to achieve stable branches, a more or less regular freeze of /trunk would be necessary: no further development, only bug fixes. One of Christian's arguments against a lot of branches was that keeping them in sync with the main development branch takes a lot of time which could be better spent. This often leads to diverging branches which are never really merged. Ian Hinder generally does not mind to handle multiple branches. Roland Haas suggested to maybe add one more level: in addition to stable and development there could be an experimental branch which would be free for any type of development while the development branch is only updated from the experimental branch from time to time, as the stable branch is from the development branch. This didn't find another supporter. Erik noted that with free development inside /trunk (the development branch) it would not be stable enough to be used for production - anything might break after an update. This means there have to be regular updates of the stable versions from the development version to be able to take advantage of new features. Erik asked what a good time for such a cycle would be and suggested 3-6 months. Nobody objected. Everyone was requested to voice her/his opinion about this topic, and everyone on the call (except Pablo, who had dropped off) agreed on Christian's suggestion (with a few additions from todays meeting): 1 There will be stable branches from time to time, targeting at about every 3-6 months. Commits to these branches needs a code review unless trivial. 2 Most of the development will happen in the development branch, which is /trunk. No special policy for commit is in place there, common sense rules. 3 There will be a freeze from time to time to move changes in the development branch to a new stable branch. When and how long such a freeze happens will be discussed. 4 There might be extra branches with their maintainers being responsible to enforce any policy they like. Erik suggested to start with a freeze to get a first stable release before starting to implement MHD into GRHydro. He estimated the time to 1-2 weeks. Christian agreed that this delay wouldn't be a problem for the MHD development. Christian asked if there is a tutorial of how to create a good testsuite, but nobody could name something like that apart from a small part of the Cactus documentation. Everybody agreed that this should be improved, but nobody volunteered to be responsible for this. So: everyone is invited to see if she/he could add tips to the Cactus documentation. It was also noted that most discussions should happen on the users@einsteintoolkit mailing list and only the "boring administrative stuff" should be sent to the maintainers list. Last but not least, the main topic for next week's meeting will be how MHD will be implemented in GRHydro: figuring out who does what and probably also how and when. Next week's meeting will take place at it's usual time: Mon, Jun 7th at 10am CDT, with the usual phone information: Each participant of the teleconference will call 578-4942 (225-578-4942 from off-campus or 866-573-0359 toll free). Participants will press 118682# for Conference Line one. Frank

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users June 2010