[Developers] Contents of Developers Digest
Erik Schnetter
schnetter at cct.lsu.edu
Sun Jul 8 14:03:30 CDT 2007
Hi Claudo,
congratulations. That is good to hear.
-erik
On Jul 4, 2007, at 17:46:48, claudio at das.inpe.br wrote:
> Hi, Erik.
>
> I have good news. When I sent that message, the executable file
> wasn't been
> generated. That situation hadn't solution with my old linux
> distribution and its
> problems !! ... So, I've decided to install Fedora Core 6 in my
> machine, and I
> did it. By now, my system works very well. I can compile Cactus
> making:
>
> claudiob> gmake Bench_BSSN_PUGH_single F90=gfotran
>
> The Result is the executable is generated and works correctly.
>
> Thank you for your suport.
> My best regards,
>
> Claudio.
>
>
>
>
>> Today's Topics:
>>
>> 1. Bugs ?? -- config file. (claudio at das.inpe.br)
>> 2. Re: Bugs ?? (Erik Schnetter)
>> 3. ADMMacros, syntax errors in C version (Frank L?ffler)
>> 4. Re: ADMMacros, syntax errors in C version (Erik Schnetter)
>> 5. Re: ADMMacros, syntax errors in C version (Denis Pollney)
>> 6. Re: ADMMacros, syntax errors in C version (Frank L?ffler)
>> 7. Re: ADMMacros, syntax errors in C version (Erik Schnetter)
>> 8. Re: ADMMacros, syntax errors in C version (Frank L?ffler)
>>
>>
>> ---------------------------------------------------------------------
>> -
>>
>> Message: 1
>> Date: Mon, 18 Jun 2007 14:11:24 -0300
>> From: claudio at das.inpe.br
>> Subject: [Developers] Bugs ?? -- config file.
>> To: developers at cactuscode.org
>> Message-ID: <1182186684.4676bcbc3ef6d at webmail.inpe.br>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>>
>> My configuration file ...
>> _____________________________________________________________________
>> ___
>> Cactus - version: 4.0.b16
>> if test ! -r
>>
> "/home/claudiob/DOUTORADO/CACTUS/Cactus/configs/
> Bench_BSSN_PUGH_single/config-info";
>> then \
>> echo ""; \
>> echo "Error reconfiguring 'Bench_BSSN_PUGH_single':
>> configuration is
>> incomplete."; \
>> echo "Use 'gmake Bench_BSSN_PUGH_single-reconfig' to configure the
>> configuration."; \
>> exit 2; \
>> elif ! head -n 1
>> /home/claudiob/DOUTORADO/CACTUS/Cactus/configs/
>> Bench_BSSN_PUGH_single/config-info
>> | grep -q '# CONFIGURATION'; then \
>> echo "Error reconfiguring 'Bench_BSSN_PUGH_single': unrecognized
>> config-info
>> file format" ; \
>> echo "This probably means that the Cactus config-info file
>> format has
>> changed"; \
>> echo "since this configuration was last configured. You will
>> have to
>> freshly"; \
>> echo "configure the configuration with"; \
>> echo " gmake Bench_BSSN_PUGH_single-config OPTION1=VALUE1
>> OPTION2=VALUE2
>> ..."; \
>> echo "Note that this will overwrite all of this configuration's
>> current";
>> \
>> echo "configuration options. See the config-info file"; \
>> echo "
>>
> /home/claudiob/DOUTORADO/CACTUS/Cactus/configs/
> Bench_BSSN_PUGH_single/config-info";
>> \
>> echo "to see what these are."; \
>> exit 2; \
>> fi; \
>> if ( perl -s lib/make/setup_configuration.pl
>>
> -config_file=/home/claudiob/DOUTORADO/CACTUS/Cactus/configs/
> Bench_BSSN_PUGH_single/config-info
>> Bench_BSSN_PUGH_single) ; then : ; else \
>> echo
>> "" ; \
>> echo "Error reconfiguring Bench_BSSN_PUGH_single-
>> reconfig" ;
>>
>> \
>> rm -f
>>
> "/home/claudiob/DOUTORADO/CACTUS/Cactus/configs/
> Bench_BSSN_PUGH_single/config-data/cctk_Config.h";\
>> exit
>> 2 ; \
>>
>> fi ; \
>> echo
>> _____________________________________________________________________
>> ___ ; \
>> if test "x"yes"" = "xno" ; then \
>> gmake Bench_BSSN_PUGH_single WARN=; \
>> else \
>> echo Use 'gmake Bench_BSSN_PUGH_single' to build the
>> configuration. ; \
>> fi
>> Reconfiguring Bench_BSSN_PUGH_single.
>> Adding configuration options from
>>
> '/home/claudiob/DOUTORADO/CACTUS/Cactus/configs/
> Bench_BSSN_PUGH_single/config-info'...
>> End of options from
>>
> '/home/claudiob/DOUTORADO/CACTUS/Cactus/configs/
> Bench_BSSN_PUGH_single/config-info'.
>> creating cache ./config.cache
>> checking host system type... x86_64-unknown-linux-gnu
>> Setting FPP to /lib/cpp
>> Setting FPPFLAGS to -traditional
>> checking whether make sets ${MAKE}... yes
>> checking for gcc... gcc
>> checking whether the C compiler (gcc ) works... yes
>> checking whether the C compiler (gcc ) is a cross-compiler... no
>> checking whether we are using GNU C... yes
>> checking for c++... c++
>> checking whether the C++ compiler (c++ ) works... yes
>> checking whether the C++ compiler (c++ ) is a cross-compiler... no
>> checking whether we are using GNU C++... yes
>> checking for ranlib... ranlib
>> checking for cpp... /lib/cpp
>> checking for perl... perl
>> checking for f90... f90
>> checking for f77... f77
>> checking for ar... ar
>> checking for mkdir... mkdir
>> Setting CACHELINE_BYTES to 64
>> Setting CACHE_SIZE to 2048*1024 bytes
>> checking how to run the C preprocessor... /lib/cpp
>> checking for ANSI C header files... yes
>> checking whether byte ordering is bigendian... no
>> checking size of long long... 8
>> checking size of long int... 8
>> checking size of int... 4
>> checking size of short int... 2
>> checking size of long double... 16
>> checking size of double... 8
>> checking size of float... 4
>> checking size of char *... 8
>> checking for the null device... /dev/null
>> checking for gethostbyname... yes
>> checking if mode_t is defined... yes
>> checking for availability of gettimeofday timing... yes
>> checking if gettimeofday needs timezone... yes
>> checking for availability of getrusage timing... yes
>> checking for availability of _ftime timing... no
>> checking for time.h... yes
>> checking for sys/time.h... yes
>> checking for sys/types.h... yes
>> checking for unistd.h... yes
>> checking for string.h... yes
>> checking for assert.h... yes
>> checking for sys/stat.h... yes
>> checking for getopt.h... yes
>> checking for dirent.h... yes
>> checking for regex.h... yes
>> checking for sys/filio.h... no
>> checking for sys/ioctl.h... yes
>> checking for sys/socket.h... yes
>> checking for netinet/in.h... yes
>> checking for netdb.h... yes
>> checking for arpa/inet.h... yes
>> checking for winsock2.h... no
>> checking for crypt.h... yes
>> checking for signal.h... yes
>> checking whether time.h and sys/time.h may both be included... yes
>> checking if socklen_t is defined... yes
>> checking if SOCKET is defined... no
>> checking if __int64 is defined... no
>> checking for vector... yes
>> checking for vector.h... yes
>> checking for getopt_long_only... yes
>> checking for working const... yes
>> checking for inline... inline
>> checking for C restrict... __restrict__
>> checking for C++ restrict... __restrict__
>> checking for C bool... no
>> checking for CXX bool... yes
>> checking for crypt... no
>> checking for crypt in library crypt... yes
>> checking for finite... yes
>> checking for isnan... yes
>> checking for mkstemp... yes
>> checking for va_copy... yes
>> creating cctk_Archdefs.h
>> creating make.arch.defn
>> creating cctk_Extradefs.h
>> creating make.extra.defn
>> cctk_Archdefs.h is unchanged
>> make.arch.defn is unchanged
>> cctk_Extradefs.h is unchanged
>> make.extra.defn is unchanged
>> updating cache ./config.cache
>> creating ./config.status
>> creating make.config.defn
>> creating make.config.deps
>> creating make.config.rules
>> creating cctk_Config.h
>> cctk_Config.h is unchanged
>> Determining number of fortran underscores...
>> Compiling test file with f90 -align -w95 ...
>> Lowercase - One trailing underscore
>> Compiling test file with f90 -align -w95 ...
>> Lowercase - One trailing underscore
>> _____________________________________________________________________
>> ___
>> Use gmake Bench_BSSN_PUGH_single to build the configuration.
>> _____________________________________________________________________
>> ___
>>
>>
>> -------------------------------------------------
>> This mail sent through IMP: http://horde.org/imp/
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sat, 23 Jun 2007 14:37:31 -0500
>> From: Erik Schnetter <schnetter at cct.lsu.edu>
>> Subject: Re: [Developers] Bugs ??
>> To: developers at cactuscode.org
>> Message-ID: <B09A905D-08A6-448B-8930-8C34EE62A877 at cct.lsu.edu>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> On Jun 18, 2007, at 11:53:12, claudio at das.inpe.br wrote:
>>
>>> c++ -o
>>> "/home/claudiob/DOUTORADO/CACTUS/Cactus/exe/
>>> cactus_Bench_BSSN_PUGH_single" -Qy
>>> /usr/lib/icrt.link
>>> "/home/claudiob/DOUTORADO/CACTUS/Cactus/configs/
>>> Bench_BSSN_PUGH_single/datestamp.o"
>>> -L/home/claudiob/DOUTORADO/CACTUS/Cactus/configs/
>>> Bench_BSSN_PUGH_single/lib
>>> -lthorn_Cactus -lthorn_CactusBindings -lthorn_BSSN_MoL -
>>> lthorn_StaticConformal
>>> -lthorn_SpaceMask -lthorn_ADMBase -lthorn_CartGrid3D -lthorn_MoL
>>> -lthorn_NaNChecker -lthorn_PUGHReduce -lthorn_PUGHInterp -
>>> lthorn_IOBasic
>>> -lthorn_Time -lthorn_SymBase -lthorn_IOUtil -lthorn_CoordGauge -
>>> lthorn_CoordBase
>>> -lthorn_Boundary -lthorn_ADMMacros -lthorn_ADMCoupling -
>>> lthorn_PUGHSlab
>>> -lthorn_PUGH -lthorn_Cactus -lthorn_CactusBindings -L/usr/lib -
>>> lcrypt -lifcore
>>> -limf -lsvml -lm
>>> gmake[1]: Leaving directory `/home/claudiob/DOUTORADO/CACTUS/Cactus'
>>
>> Claudio,
>>
>> this output looks as if the executable has been successfully
>> generated. At least I do not see the error message any more which
>> you showed in your first email. Do you have an executable in the
>> "exe" directory?
>>
>> -erik
>>
>> --
>> Erik Schnetter <schnetter at cct.lsu.edu>
>>
>> My email is as private as my paper mail. I therefore support
>> encrypting
>> and signing email messages. Get my PGP key from www.keyserver.net.
>>
>>
>>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: PGP.sig
>> Type: application/pgp-signature
>> Size: 186 bytes
>> Desc: This is a digitally signed message part
>> Url :
>>
> http://www.cactuscode.org/pipermail/developers/attachments/
> 20070623/43490d99/attachment-0001.bin
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Wed, 4 Jul 2007 09:48:31 +0200
>> From: Frank L?ffler <frank.loeffler at aei.mpg.de>
>> Subject: [Developers] ADMMacros, syntax errors in C version
>> To: patches at cactuscode.org
>> Message-ID: <20070704074831.GJ12161 at peterpan.ap.op.sissa.it>
>> Content-Type: text/plain; charset=utf-8
>>
>> Hi,
>>
>> this patch fixes two missing ";" in the C version.
>>
>> Frank
>>
>>
>> Index: ADMMacros/src/macro/HAMADM_guts.h
>> ===================================================================
>> RCS file: /cactusdevcvs/CactusEinstein/ADMMacros/src/macro/
>> HAMADM_guts.h,v
>> retrieving revision 1.7
>> diff -u -r1.7 HAMADM_guts.h
>> --- ADMMacros/src/macro/HAMADM_guts.h 18 Nov 2004 14:18:24 -0000 1.7
>> +++ ADMMacros/src/macro/HAMADM_guts.h 4 Jul 2007 07:38:35 -0000
>> @@ -27,9 +27,9 @@
>>
>> #ifdef CCODE
>>
>> - HAMADM_HAMADM = TRRICCI_TRRICCI - TRKK_TRKK + TRK_TRK*TRK_TRK
>> + HAMADM_HAMADM = TRRICCI_TRRICCI - TRKK_TRKK + TRK_TRK*TRK_TRK;
>> HAMADM_HAMADMABS = fabs(TRRICCI_TRRICCI) + fabs(TRKK_TRKK) +
>> - TRK_TRK*TRK_TRK
>> + TRK_TRK*TRK_TRK;
>>
>> #endif
>>
>>
>>
>> --- StripMime Report -- processed MIME parts ---
>> multipart/mixed
>> text/plain (text body -- kept)
>> text/plain (text body -- kept)
>> ---
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Wed, 4 Jul 2007 10:16:34 +0200
>> From: Erik Schnetter <schnetter at cct.lsu.edu>
>> Subject: Re: [Developers] ADMMacros, syntax errors in C version
>> To: developers at cactuscode.org
>> Message-ID: <26C6F3DA-9774-4EC5-9544-85813F3F999B at cct.lsu.edu>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> On Jul 4, 2007, at 09:48:31, Frank L?ffler wrote:
>>
>>> Hi,
>>>
>>> this patch fixes two missing ";" in the C version.
>>
>> Frank,
>>
>> thanks for the correction. I have applied your patch.
>>
>> The fact that this code did not compile before indicates that the C
>> version of the macros has not yet been thoroughly tested. You should
>> be very careful if you want to use it. Historically, only the
>> Fortran version has of ADMMacros been used.
>>
>> The code in ADMMacros is hand-written and therefore tends to contain
>> errors. These days, many people autogenerate code using a variety of
>> systems based on Maple or Mathematica; I'm sure you know Kranc
>> <http://numrel.aei.mpg.de/Research/Kranc/>, and there are other,
>> similar systems. We (the LSU group) recently implemented our
>> harmonic formulation of the Einstein equations using Maple directly.
>>
>> Generating code automatically also has certain other advantages. For
>> example, one can perform high-level optimisations of the code
>> depending on the machine for which one generates code. This may
>> become important in the future as machines have more processors
>> (cores) and/or less memory per node. With hand-written code these
>> optimisations need to be applied manually, while a code-generation
>> system can generate the corresponding optimisations automatically.
>>
>> If one wanted e.g. to use or to experiment with multi-threading or
>> OpenMP, which can potentially save a significant amount of memory,
>> one would have to change only a few lines of Kranc to generate the
>> corresponding directives. This will allow much faster experiments
>> than manually annotating all existing loops in a production code,
>> probably protected by #ifdef statements to be able to switch forth
>> and back.
>>
>> -erik
>>
>> --
>> Erik Schnetter <schnetter at cct.lsu.edu>
>>
>> My email is as private as my paper mail. I therefore support
>> encrypting
>> and signing email messages. Get my PGP key from www.keyserver.net.
>>
>>
>>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: PGP.sig
>> Type: application/pgp-signature
>> Size: 186 bytes
>> Desc: This is a digitally signed message part
>> Url :
>>
> http://www.cactuscode.org/pipermail/developers/attachments/20070704/
> b2914631/attachment-0001.bin
>>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Wed, 04 Jul 2007 10:31:20 +0200
>> From: Denis Pollney <denis.pollney at aei.mpg.de>
>> Subject: Re: [Developers] ADMMacros, syntax errors in C version
>> To: developers at cactuscode.org
>> Message-ID: <1183537880.30972.36.camel at x41>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> On Wed, 2007-07-04 at 10:16 +0200, Erik Schnetter wrote:
>>> On Jul 4, 2007, at 09:48:31, Frank L?ffler wrote:
>>>
>>>> Hi,
>>>>
>>>> this patch fixes two missing ";" in the C version.
>>>
>>> Frank,
>>>
>>> thanks for the correction. I have applied your patch.
>>>
>>> The fact that this code did not compile before indicates that the C
>>> version of the macros has not yet been thoroughly tested. You
>>> should
>>> be very careful if you want to use it. Historically, only the
>>> Fortran version has of ADMMacros been used.
>>
>> There are a couple of places where the C versions of the macros are
>> simply wrong. I have the impression that at some point in the very
>> early history of the code, when they were experimenting with things
>> like how to finite difference the advection terms and how the
>> constraints are added into the BSSN, they stopped maintaining both
>> versions of the macros simultaneously.
>>
>> If you really need C macros, I agree with Erik that it's probably
>> easier to start from scratch than to go through each macro and
>> check that the C and Fortran versions are compatible.
>>
>> Denis.
>>
>> --
>> ---------------------------------------------------------------------
>> -
>> Denis Pollney <Denis.Pollney at aei.mpg.de> office:
>> +49-331-567-7623
>> Max-Planck-Institut fuer Gravitationsphysik mobile:
>> +49-170-302-3132
>> Albert-Einstein-Institut, Am Muehlenberg 1, D-14476, Golm, Germany
>>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: not available
>> Type: application/pgp-signature
>> Size: 189 bytes
>> Desc: This is a digitally signed message part
>> Url :
>>
> http://www.cactuscode.org/pipermail/developers/attachments/20070704/
> f6a97ccc/attachment-0001.bin
>>
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Wed, 4 Jul 2007 11:15:25 +0200
>> From: Frank L?ffler <frank.loeffler at aei.mpg.de>
>> Subject: Re: [Developers] ADMMacros, syntax errors in C version
>> To: developers at cactuscode.org
>> Message-ID: <20070704091524.GP12161 at peterpan.ap.op.sissa.it>
>> Content-Type: text/plain; charset=utf-8
>>
>> On Wed, Jul 04, 2007 at 10:31:20AM +0200, Denis Pollney wrote:
>>> There are a couple of places where the C versions of the macros are
>>> simply wrong.
>>
>> I know that those errors mean that nobody used them at all yet. I
>> would
>> only use them to debug some things, but maybe I am really better
>> off by
>> using Fortran code for that.
>> On the other hand, _some_ of the macros are used, also by C code.
>>
>> What can we do to improve the situation? We could
>> a) remove the code, which is wrong
>> b) correct the wrong code
>> c) rething the whole Macros
>>
>> c) might be the best for the long term, but for a) and b) we have to
>> identify the wrong code first. Can you point at some places?
>>
>> Frank
>>
>>
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Wed, 4 Jul 2007 11:42:49 +0200
>> From: Erik Schnetter <schnetter at cct.lsu.edu>
>> Subject: Re: [Developers] ADMMacros, syntax errors in C version
>> To: developers at cactuscode.org
>> Message-ID: <7A2B2288-DB6F-4487-AA82-F002D1647247 at cct.lsu.edu>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> On Jul 4, 2007, at 11:15:25, Frank L?ffler wrote:
>>
>>> On Wed, Jul 04, 2007 at 10:31:20AM +0200, Denis Pollney wrote:
>>>> There are a couple of places where the C versions of the macros are
>>>> simply wrong.
>>>
>>> I know that those errors mean that nobody used them at all yet. I
>>> would
>>> only use them to debug some things, but maybe I am really better
>>> off by
>>> using Fortran code for that.
>>> On the other hand, _some_ of the macros are used, also by C code.
>>
>> Where is that? That is, which C thorn uses these macros?
>>
>> -erik
>>
>> --
>> Erik Schnetter <schnetter at cct.lsu.edu>
>>
>> My email is as private as my paper mail. I therefore support
>> encrypting
>> and signing email messages. Get my PGP key from www.keyserver.net.
>>
>>
>>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: PGP.sig
>> Type: application/pgp-signature
>> Size: 186 bytes
>> Desc: This is a digitally signed message part
>> Url :
>>
> http://www.cactuscode.org/pipermail/developers/attachments/
> 20070704/29329a16/attachment-0001.bin
>>
>>
>> ------------------------------
>>
>> Message: 8
>> Date: Wed, 4 Jul 2007 11:56:28 +0200
>> From: Frank L?ffler <frank.loeffler at aei.mpg.de>
>> Subject: Re: [Developers] ADMMacros, syntax errors in C version
>> To: developers at cactuscode.org
>> Message-ID: <20070704095628.GU12161 at peterpan.ap.op.sissa.it>
>> Content-Type: text/plain; charset=utf-8
>>
>> On Wed, Jul 04, 2007 at 11:42:49AM +0200, Erik Schnetter wrote:
>>> Where is that? That is, which C thorn uses these macros?
>>
>> at least:
>>
>> AEIDevelopment/ADMMass
>> CactusEinstein/ADMAnalysis
>> Whisky_Dev/Whisky_SSIVP
>>
>> Frank
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> Developers mailing list
>> Developers at cactuscode.org
>> http://www.cactuscode.org/mailman/listinfo/developers
>>
>>
>> End of Developers Digest, Vol 45, Issue 1
>> *****************************************
>>
>
>
>
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
> _______________________________________________
> Developers mailing list
> Developers at cactuscode.org
> http://www.cactuscode.org/mailman/listinfo/developers
>
--
Erik Schnetter <schnetter at cct.lsu.edu>
My email is as private as my paper mail. I therefore support encrypting
and signing email messages. Get my PGP key from www.keyserver.net.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.cactuscode.org/pipermail/developers/attachments/20070708/a1b1f606/attachment.bin
More information about the Developers
mailing list