From d.rideout at imperial.ac.uk Wed Jun 6 11:04:20 2007 From: d.rideout at imperial.ac.uk (David Rideout) Date: Wed, 6 Jun 2007 17:04:20 +0100 Subject: [Developers] eliminating scheduling ambiguities Message-ID: <200706061704.20778.d.rideout@imperial.ac.uk> I propose to modify the specification of Cactus slightly, to state that the relative order of scheduled routines, beyond that specified by before & after requests in thorns' schedule.ccl, is fixed in some arbitrary way (say alphabetically). I believe that currently it is unspecified. The reason for this proposal is described in detail below. This is a request for comment. Currently the Cactus flesh computes a 'topological sort' of scheduled routines, based upon what thorns request in their schedule.ccl. This simply means some linear ordering of the routines which is compatible with all before and after requests in the schedule.ccl files. (In the language of partial order relations, the before / after requests impose a partial order on the set of scheduled routines, and the flesh computes a linear extension of this order.) In general there will be many routines whose relative order is unspecified by before / after requests. e.g. schedule routineA in CCTK_EVOL ... schedule routineB in CCTK_EVOL ... Now consider a computation which uses a pseudorandom number generator (RNG). This is a (deterministic) function which, each time it is called, returns an approximately random number, based upon its previous value. The initial value is initialized as a seed. Thus for a given seed, the RNG produces a fixed sequence of pseudorandom numbers. Now a problem arises, as follows. If we imagine fixing the seed in a parameter file, then one may expect to get a fixed unique output from that parameter file. Such behavior is needed for a testsuite, for example. However, two different builds of Cactus may differ in the relative order of routineA and routineB. If both of these routines contain calls to the RNG, then the output from Cactus will differ, even though each build runs the same parameter file. A simple fix is to (arbitrarily) specify this unspecified aspect of the scheduler as described above. Note that the actual choice of ordering makes no difference, it only matters that the order of routines is fixed for a given collection of compiled thorns and parameter settings. One can dream up many more complicated solutions, but I believe this simple resolution can be extremely easy to implement (e.g. just by sorting the thornlist before processing!). Thanks, David From schnetter at cct.lsu.edu Wed Jun 6 12:15:41 2007 From: schnetter at cct.lsu.edu (Erik Schnetter) Date: Wed, 6 Jun 2007 13:15:41 -0400 Subject: [Developers] eliminating scheduling ambiguities In-Reply-To: <200706061704.20778.d.rideout@imperial.ac.uk> References: <200706061704.20778.d.rideout@imperial.ac.uk> Message-ID: <9B2FEE30-7916-4EBF-A4C0-A50C1E837BD2@cct.lsu.edu> On Jun 6, 2007, at 12:04:20, David Rideout wrote: > I propose to modify the specification of Cactus slightly, to state > that the > relative order of scheduled routines, beyond that specified by > before & after > requests in thorns' schedule.ccl, is fixed in some arbitrary way (say > alphabetically). I believe that currently it is unspecified. Although unspecified, the routines are sorted alphabetically. Thus your test suites should already work. For the test suites to work, it is not necessary that Cactus specifies a specific order. It suffices if Cactus guarantees that there will be an order, such that the same parameter file always leads to the same execution order. As a side points, there are routines called "zzz_Whatever", ensuring that they will be executed "last". -erik -- Erik Schnetter 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/20070606/f8cefa30/attachment.bin From Ankush.Gupta at Sun.COM Mon Jun 11 01:12:05 2007 From: Ankush.Gupta at Sun.COM (Ankush Gupta) Date: Mon, 11 Jun 2007 11:42:05 +0530 Subject: [Developers] Cactus on network.com Message-ID: <466CE7B5.9090706@sun.com> Hi All I have ported Cactus on Solaris 10 and have mailed the changes to the cactus maintain team. Also I would like to make the cactus available on network.com ( grid running on Solaris x86 machines ) . So that people could make best use of it. They could run cactus on the grid for large scientific applications which require huge computing power. So how do you want me to put it on it. I meant along with some thorns or as a flesh. Could someone help me in getting a good use case of the same. Thanks Ankush From claudio at das.inpe.br Fri Jun 15 17:19:45 2007 From: claudio at das.inpe.br (claudio at das.inpe.br) Date: Fri, 15 Jun 2007 19:19:45 -0300 Subject: [Developers] Bugs ?? Message-ID: <1181945985.46731081add7b@webmail.inpe.br> Cactus Team, I've found a (probabily) mistake when I compile the Bench_BSSN_PUGH_single. My machine has Suse 10.2 x86_64 and I'm using gcc, g77 and intel Fortran compiler. The compiling result is : claudiob at graviton:Cactus> gmake Bench_BSSN_PUGH_single ________________________________________________________________________ Cactus - version: 4.0.b16 Building configuration Bench_BSSN_PUGH_single ________________________________________________________________________ Checking status of thorn CoordBase ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn CartGrid3D ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn ADMBase ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn ADMCoupling ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn ADMMacros ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn BSSN_MoL ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn Boundary ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn CoordGauge ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn IOUtil ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn IOBasic ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn NaNChecker ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn MoL ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn PUGH ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn PUGHInterp ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn PUGHReduce ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn PUGHSlab ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn SpaceMask ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn StaticConformal ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn SymBase ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn Time ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn Cactus ________________________________________________________________________ ________________________________________________________________________ Checking status of thorn CactusBindings ________________________________________________________________________ ________________________________________________________________________ Creating cactus_Bench_BSSN_PUGH_single in /home/claudiob/DOUTORADO/CACTUS/Cactus/exe from CactusEinstein/ADMBase CactusEinstein/ADMCoupling CactusEinstein/ADMMacros AEIThorns/BSSN_MoL CactusBase/Boundary CactusBase/CartGrid3D CactusBase/CoordBase CactusEinstein/CoordGauge CactusBase/IOBasic CactusBase/IOUtil CactusBase/MoL CactusUtils/NaNChecker CactusPUGH/PUGH CactusPUGH/PUGHInterp CactusPUGH/PUGHReduce CactusPUGH/PUGHSlab CactusEinstein/SpaceMask CactusEinstein/StaticConformal CactusBase/SymBase CactusBase/Time /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: skipping incompatible /home/claudiob/DOUTORADO/CACTUS/Cactus/configs/Bench_BSSN_PUGH_single/lib/libthorn_BSSN_MoL.a when searching for -lthorn_BSSN_MoL /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: cannot find -lthorn_BSSN_MoL collect2: ld returned 1 exit status make[1]: *** [/home/claudiob/DOUTORADO/CACTUS/Cactus/exe/cactus_Bench_BSSN_PUGH_single] Error 1 make: *** [Bench_BSSN_PUGH_single] Error 2 =================================================================== And I don't know why this problem appears. My best Regards, Claudio. ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ From schnetter at cct.lsu.edu Fri Jun 15 17:28:45 2007 From: schnetter at cct.lsu.edu (Erik Schnetter) Date: Fri, 15 Jun 2007 17:28:45 -0500 Subject: [Developers] Bugs ?? In-Reply-To: <1181945985.46731081add7b@webmail.inpe.br> References: <1181945985.46731081add7b@webmail.inpe.br> Message-ID: On Jun 15, 2007, at 17:19:45, claudio at das.inpe.br wrote: > /usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse- > linux/bin/ld: > skipping incompatible > /home/claudiob/DOUTORADO/CACTUS/Cactus/configs/ > Bench_BSSN_PUGH_single/lib/libthorn_BSSN_MoL.a > when searching for -lthorn_BSSN_MoL Hi Claudio, an incompatible library looks as if the different compilers you used (for C and Fortran) are maybe incompatible. It could e.g. be that one of them was set to produce 32 bit code, while the other produced 64 bit code. What compilers are used etc. is printed to the screen when you configure. Also, if you pass the option "SILENT=no" to make, you see what commands are invoked to build the libraries. Can you post the relevant output here? If you change your configuration options, it can also be that the build is in an inconsistent state. A "make Bench_BSSN_PUGH_single- realclean" should remedy this. -erik -- Erik Schnetter 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/20070615/74a18407/attachment.bin From claudio at das.inpe.br Mon Jun 18 11:36:28 2007 From: claudio at das.inpe.br (claudio at das.inpe.br) Date: Mon, 18 Jun 2007 13:36:28 -0300 Subject: [Developers] Bugs ?? Message-ID: <1182184588.4676b48c72d9a@webmail.inpe.br> Here is the full output in attachments ... This file has 3027 lines ... Cheers. C. ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ -------------- next part -------------- A non-text attachment was scrubbed... Name: output Type: application/octet-stream Size: 0 bytes Desc: not available Url : http://www.cactuscode.org/pipermail/developers/attachments/20070618/1431e9b4/attachment.obj From claudio at das.inpe.br Mon Jun 18 11:43:10 2007 From: claudio at das.inpe.br (claudio at das.inpe.br) Date: Mon, 18 Jun 2007 13:43:10 -0300 Subject: [Developers] Bugs ?? Message-ID: <1182184990.4676b61e0cc87@webmail.inpe.br> It seems that the attachments hasn't worked well ... I 'll try again ... ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: output.txt Url: http://www.cactuscode.org/pipermail/developers/attachments/20070618/6cf54545/attachment.txt From claudio at das.inpe.br Mon Jun 18 11:53:12 2007 From: claudio at das.inpe.br (claudio at das.inpe.br) Date: Mon, 18 Jun 2007 13:53:12 -0300 Subject: [Developers] Bugs ?? Message-ID: <1182185592.4676b878cfa20@webmail.inpe.br> Well, here is the last lines of output file ... I can't attach files in maillist ... make[2]: Leaving directory `/home/claudiob/DOUTORADO/CACTUS/Cactus/configs/Bench_BSSN_PUGH_single/build/CactusBindings' ________________________________________________________________________ Creating cactus_Bench_BSSN_PUGH_single in /home/claudiob/DOUTORADO/CACTUS/Cactus/exe from CactusEinstein/ADMBase CactusEinstein/ADMCoupling CactusEinstein/ADMMacros AEIThorns/BSSN_MoL CactusBase/Boundary CactusBase/CartGrid3D CactusBase/CoordBase CactusEinstein/CoordGauge CactusBase/IOBasic CactusBase/IOUtil CactusBase/MoL CactusUtils/NaNChecker CactusPUGH/PUGH CactusPUGH/PUGHInterp CactusPUGH/PUGHReduce CactusPUGH/PUGHSlab CactusEinstein/SpaceMask CactusEinstein/StaticConformal CactusBase/SymBase CactusBase/Time gcc -pipe -O3 -c -o "/home/claudiob/DOUTORADO/CACTUS/Cactus/configs/Bench_BSSN_PUGH_single/datestamp.o" -I"/home/claudiob/DOUTORADO/CACTUS/Cactus/src/include" -I"/home/claudiob/DOUTORADO/CACTUS/Cactus/configs/Bench_BSSN_PUGH_single/config-data" "/home/claudiob/DOUTORADO/CACTUS/Cactus/src/datestamp.c" if [ ! -d /home/claudiob/DOUTORADO/CACTUS/Cactus/exe ]; then mkdir -p /home/claudiob/DOUTORADO/CACTUS/Cactus/exe ; fi 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' ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ From claudio at das.inpe.br Mon Jun 18 12:11:24 2007 From: claudio at das.inpe.br (claudio at das.inpe.br) Date: Mon, 18 Jun 2007 14:11:24 -0300 Subject: [Developers] Bugs ?? -- config file. Message-ID: <1182186684.4676bcbc3ef6d@webmail.inpe.br> 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/ From schnetter at cct.lsu.edu Sat Jun 23 14:37:31 2007 From: schnetter at cct.lsu.edu (Erik Schnetter) Date: Sat, 23 Jun 2007 14:37:31 -0500 Subject: [Developers] Bugs ?? In-Reply-To: <1182185592.4676b878cfa20@webmail.inpe.br> References: <1182185592.4676b878cfa20@webmail.inpe.br> Message-ID: 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 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.bin