Users

users@lists.einsteintoolkit.org

3 participants
3984 discussions

Einstein Toolkit Meeting Reminder
by Frank Loeffler 03 Oct '11

03 Oct '11

On Sun, Sep 25, 2011 at 10:38:13PM -0500, Frank Loeffler wrote: Hi Please consider joining the weekly Einstein Toolkit phone call at 10 am US central time on Mondays. As usual, you can find instructions how to join on the following web site: http://einsteintoolkit.org/community/support/ I short: the number is (+1) 225-578-4942 or (+1) 866-573-0359 and the conference id is 118682#. Todays agenda contains: - Release planning - release date: Mon Oct 24 2011 - remember: we are in freeze - List of release-concerning bugs [1]: 19 open, of which 3 are 'pending review' - Blocker for hg-version of Carpet: https://trac.einsteintoolkit.org/ticket/499 (Prolongation fails with vectorisation enabled) - Question: ok to make this non-blocker given the available workaround? - ET paper - "freeze": no major changes/additions after today midnight - "smoothing": - two people (at least) reading through everything until We, pointing out problems with general flow, definition order, definition consistency, ect. - one person looking at generating (most) plots using same tool, or at least making them look alike (style, line widths, fonts, colors) - _all_ data used to generate plots has to be in repository, including scripts to generate plots - for examples: also provide parameter files (although not used for the paper) - one person looking at references - references.bib in manifest - lookout for duplicate references - sections to talk about at call - two sections 'spacetime evolution code' - Relativity tools: too short, merge with other section (hydro?) - cosmetics: subsubsection headlines (e.g. in 5.7.x) don't stand out As always: feel free to add to the agenda. Frank Loeffler [1] https://trac.einsteintoolkit.org/query?status=!closed&milestone=ET_2011_11&…

1 0

spring meeting
by Frank Loeffler 29 Sep '11

29 Sep '11

Hi, We decided to have a spring ET workshop, targeted at a larger audience, and either directly before or after the APS meeting in Atlanta. We should decide soon about whether we target the before or after, to coordinate with other meetings. Please just shortly state whether you prefer either of the two, or whether you don't care. thanks, Frank

3 3

compiler warning for McLachlan
by Frank Loeffler 27 Sep '11

27 Sep '11

Hi, I just checked out a new copy of the Einstein Toolkit and compiled, and got this (and a lot of similar messages): An internal threshold was exceeded for routine _Z20ML_BSSN_O2_RHS2_BodyPK4_cGHiiPKdS3_S3_PKiS5_iPrKPd and optimization level may be reduced. See http://software.intel.com/en-us/articles/internal-threshold-was-exceeded for more information and advice. In addition, McLachlan seems to compile for a very long time and uses a lot of memory (several GB per compiler process), for the Intel compiler. Did I miss this in the past or did something change in McLachlan which could trigger this? Frank

4 20

Einstein Toolkit installaton problems
by ciambridge 26 Sep '11

26 Sep '11

Hello, my name is Vassili, i just started my PhD under the supervision of Toni font in Valencia. I am going to work with the Einstein Toolkit to do numerical simulations. I tried installing the toolkit as described in the simplified tutorial for new users and got the following error messages when trying to compile: Error: Unclassifiable statement at (1) /home/vass/Cactus/configs/firsttry/build/Extract/Extract.f:971.72: GOTO 404 1 Error: Label 404 referenced at (1) is never defined /home/vass/Cactus/configs/firsttry/build/Extract/Extract.f:1393.6: 101 format(a1,a14) 1 Error: Bad continuation line at (1) /home/vass/Cactus/configs/firsttry/build/Extract/Extract.f:1393.6: 101 format(a1,a14) 1 Error: Unclassifiable statement at (1) /home/vass/Cactus/configs/firsttry/build/Extract/Extract.f:1392.29: write(filehandle,101) char(34),filename 1 Error: FORMAT label 101 at (1) not defined /home/vass/Cactus/configs/firsttry/build/Extract/Extract.f:1694.6: 101 format(a1,a14) 1 Error: Bad continuation line at (1) /home/vass/Cactus/configs/firsttry/build/Extract/Extract.f:1694.6: 101 format(a1,a14) 1 Error: Unclassifiable statement at (1) /home/vass/Cactus/configs/firsttry/build/Extract/Extract.f:1693.22: write(444,101) char(34),filename 1 Error: FORMAT label 101 at (1) not defined /home/vass/Cactus/configs/firsttry/build/Extract/Extract.f:1998.6: 101 format(a1,a14) 1 Error: Bad continuation line at (1) /home/vass/Cactus/configs/firsttry/build/Extract/Extract.f:1998.6: 101 format(a1,a14) 1 Error: Unclassifiable statement at (1) /home/vass/Cactus/configs/firsttry/build/Extract/Extract.f:1997.22: write(444,101) char(34),filename 1 Error: FORMAT label 101 at (1) not defined make[3]: *** [Extract.F.o] Error 1 make[3]: *** Waiting for unfinished jobs.... Postprocessing /home/vass/Cactus/arrangements/EinsteinAnalysis/Extract/src/unphysical_to_physical.F ________________________________________________________________________ make[2]: *** [make.checked] Error 2 make[1]: *** [/home/vass/Cactus/configs/firsttry/lib/libthorn_Extract.a] Error 2 make: *** [firsttry] Error 2 vass@vass-Studio-1557:~/Cactus$ ./simfactory/bin/sim build firsttry --thornlist=manifest/einsteintoolkit.th--optionlist=/home/vass/.cactus/config this is not exhaustive, it goes on for much longer...basically the fortran F77 files are not compiled properly...i am using ubuntu 11.04 and gfortran, but also installed g77 from the ubuntu 8.04 archives to see whether this would remove the problems...as suggested in the web, i have also used the ffppflags= -traditional option in my config file... before, there were also other files affected by this, like the distortedBHIVP.f file.... don't know what to do, it would be great if you could point me into a direction!! best wishes, Vassili

3 3

Meeting minutes
by Roland Haas 19 Sep '11

19 Sep '11

Present were: Frank, Roland, Ian, Eloisa, Christian, Tanja, Yosef, Peter, Steve, Josh, Bruno MHD status: * code (and maybe paper) should be ready for the release next month. Currently performing gauge wave and Bondi flow tests * are optimistic to get everything ready before the workshop * try to submit paper in conjunction with ET release ET release: * want to release before the workshop, aim for Oct. 25th * branch name: 2011_10, code name: Maxwell * PLEASE go ahead and fix outstanding bugs: https://trac.einsteintoolkit.org/query?status=!closed&milestone=ET_2011_11&… * fix failing testsuites ** WeylScal4 (Hg): try if increasing grid size helps, if so use as fix * will use simfactory/python for release instead of simfactory/perl * no more major changes after next Monday (Sept. 26th) * announce major changes on mailing list before release, Ian has prepared list of commit messages on wiki: https://docs.einsteintoolkit.org/et-docs/Release_Details CCE: * will be included in release * Peter will to testing this week Carpet/Hg: * vectorization still fails on some machines using some compiler and some parameter options * Ian, Barry and Erik will discuss the off-line * blocker for release otherwise ! 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

simfactory (python): small requests
by Luca Baiotti 19 Sep '11

19 Sep '11

Hello I have some other small questions and requests on simfactory. 1) I would like the name of the simulation and the output directory to be different. (The name of the simulation should be short in order to be meaningful (visible in the queueing system) while the name of the output directory can be long, in order to properly describe its content.) Is this possible? 2) I would like to have a single file containing both sdtout and stderr from the job. I tried to insert #$ -j y into simfactory/mdb/submitscripts/ranger-intel11.sub (which is what I am using) and to remove the lines #$ -o @RUNDIR@/@SIMULATION_NAME@.out #$ -e @RUNDIR@/@SIMULATION_NAME@.err but this didn't sort the wanted effect (i.e. the stdout and stderr are still in separate files). How can I achieve this? 3) How can one change the default warning level in the cactus run (the simfactory default is -L 3)? 4) For some reason (maximum core count exceeded), my job was rejected from the queueing system, so it never started and I received no notification email, and I was wondering what happened. Then I realised that actually the line "Submit finished, job id is 212....." was not printed by simfactory. Instead of simply not printing the final line, could simfactory print an error message in this case? Best, Luca

2 2

Re: [Users] simfactory (python) small issue
by Luca Baiotti 19 Sep '11

19 Sep '11

Thanks, I have updated parts of the wiki. Maybe someone who knows simfactory well could update other parts, if necessary? Some issues remain: > 1) I tried the command > > simfactory/bin/sim list-machines ranger > > and the result is the whole list of machines. Shouldn't it output only > the data for ranger? > > > The list-machines command currently lists all machines in the machine > database. It should also probably either: > > a) complain if you give it a machine name as an extra command. > b) only list machines which match the pattern of the name you give. Can some one fix this? > 2) The command print-machine seem non-existent: > > Cactus> simfactory/bin/sim print-machine > Error: unknown command print-machine > Aborting Simfactory. > > > You probably want print-mdb-entry. No, I meant print-machine, as explained on the wiki. > 3) If I say: > > simfactory/bin/sim --remote-machine=ranger execute ls > > the reply is: > > sim.py: error: no such option: --remote-machine > > > Try: > > simfactory/bin/sim --remote ranger execute ls > > 4) What is the version of the command: > > simfactory/bin/sim list-configurations > > that lists the available configurations on a remote machine? > > > simfactory/bin/sim --remote ranger list-configurations > > 5) What is the version of the command: > > simfactory/bin/sim build [<configurationname>] --thornlist=<thornlist> > > that lists the available configurations on a remote machine? > > > I'm not sure what you mean by this, but assuming you want to build on a > remote machine: > > simfactory/bin/sim --remote ranger build [configuration] OK. Luca

2 2

GRHydro Multipatch announcement
by Roland Haas 19 Sep '11

19 Sep '11

Dear all, as already mentioned in the meeting minutes and discussed in last week's CIGR call, Christian Reisswig has been working on adding Llama Multipatch compatibility to GRHydro. For those of you not familiar with Llama, this is the description from the Llama website (www.llamacode.org): --8<-- The Llama code is a 3-dimensional multiblock infrastructure with adaptive mesh-refinement for Cactus based on Carpet. It provides different patch systems that cover the simulation domain by a set of overlapping patches. Each of these patches has local cooordinates with a well defined relation to global Cartesian coordinates. However, all computations are carried out using a global Cartesian tensor basis such that involved tensor transformations between patch systems can be avoided. Information between the different patches is communicated via interpolation in the overlap zones. --8<-- We would like to incorporate these changes into the public development version of GRHydro. Right now multipatch support is functional for pure hydro simulations but still incomplete (eg. only the HLLE solver is supported, others will currently fail with multipatch enabled). No (serious) attempt has been made to incorporate MP into MHD, though the changes required should be straightforward. The proposed patch is backward compatible in that old parameter files will continue to work without change. However the patch touches a large number of code lines since all references to vector/tensor components have to be replaced with references to tensor components in a local tensor basis. In practice this means that all occurances of gxx, betax, vel[i] etc. have to be replaced by gaa, betaa, lvlel[i]. On top of that, the requirement to stay backwards compatible (and to not use extra memory) with old parameter files when MP is not actually employed adds another layer so that in the end gxx is replaced by g11 etc. This is all rather straightforward, but unfortunately tedious and makes for a large patch. We have tested that the code runs the old GRHydro testsuites and passes the same testsuites that a current vanilla checkout passes. We will begin adding multipatch support during the day. Yours, Christian R., Christian O. and 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 3

Einstein Toolkit Meeting Reminder
by Frank Loeffler 18 Sep '11

18 Sep '11

On Sun, Sep 11, 2011 at 11:55:28PM -0500, Frank Loeffler wrote: Hi Please consider joining the weekly Einstein Toolkit phone call at 10 am US central time on Mondays. As usual, you can find instructions how to join on the following web site: http://einsteintoolkit.org/community/support/ I short: the number is (+1) 225-578-4942 or (+1) 866-573-0359 and the conference id is 118682#. My agenda contains: - Fall workshop - PLEASE let us know if you come [1]! - MHD and CCE status - Release planning - proposed release date: Mon Oct 24 2011 - Name? Maxwell? - branch name: ET_2011_11 - List of release-concerning bugs [2] As always: feel free to add to this list. Frank Loeffler [1] https://docs.einsteintoolkit.org/et-docs/ET_Workshop_Fall_2011#Fall_Einstei… [2] https://trac.einsteintoolkit.org/query?status=!closed&milestone=ET_2011_11&…

1 0

simfactory build and submit
by Luca Baiotti 18 Sep '11

18 Sep '11

Hello, in addition to editing the optionlist files or creating new ones, are there other ways (e.g. a command-line option) to customise configurations? In particular I need to add the LORENE directory (because I have local changes) while leaving all other settings unchanged. Then, the wiki says that this shorthand syntax is available for submitting jobs: simfactory/bin/sim submit [<simulationname>] <parfile> <walltime> <procs> How does one specify which configuration should be used? Ciao, Luca

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users