Users

users@lists.einsteintoolkit.org

3 participants
3983 discussions

FW: Cactus compilation question
by Babiuc-Hamilton, Maria 25 May '10

25 May '10

________________________________________ From: Babiuc-Hamilton, Maria Sent: Monday, May 24, 2010 12:36 PM To: Erik Schnetter Subject: Cactus compilation question Hello, I have problems compiling Cactus on a macbook pro i7 snow-leopard. The configuration I am using is: ___________________ PP = cpp-mp-4.3 FPP = cpp-mp-4.3 CC = gcc-mp-4.3 CXX = g++-mp-4.3 F77 = gfortran-mp-4.3 F90 = gfortran-mp-4.3 HDF5 = yes HDF5_DIR = /opt/local LIBSZ_DIR = /opt/local LIBZ_DIR = /opt/local MPI=MPICH MPICH_DIR=/opt/local #MPI = OpenMPI #OPENMPI_DIR = /opt/local BLAS_DIR = /System/Library/Frameworks/vecLib.framework LAPACK_DIR = /System/Library/Frameworks/vecLib.framework FFTW_DIR = /opt/local GSL_DIR = /opt/local PETSC_DIR = /opt/local/lib/petsc X_LIB_DIR = /usr/X11R6/lib The wavetoy compiled, but with my thorns, there were errors like this: Undefined symbols: "__gfortran_size1" "__gfortran_transfer_complex" "__gfortran_minloc0_4_r8" "MPI::Win::Set_errhandler(MPI::Errhandler const&)" "__gfortran_string_trim" "__gfortran_st_close" thanks, Maria

1 0

fix d3tensor in TwoPunctures/src/TP_utilities.c
by Roland Haas 24 May '10

24 May '10

Hello all, my original commit to remove NR from d3tensor in TwoPunctures contained a bug in d3tensor. Since the routine is never called by stock TP this did not show up. Attached is a corrected version (which was actually used). Ok to commit? 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

Re: [Users] still cannot update CVS repositories from outside LSU ISSUE=925 PROJ=20
by CCT IT Support 18 May '10

18 May '10

When replying, type your text above this line. ---------------------------------------------- Notification of Incident Change The following changes have been made to this Incident: Appended a Description. Project: CCT Help Desk Incident: Re: [Users] still cannot update CVS repositories from outside LSU Incident Number: 925 Priority: Medium Status: Open Date: 05/18/2010 Time: 12:27:12 Creation Date: 05/18/2010 Creation Time: 08:47:32 Created By: roland.haas(a)physics.gatech.edu View Incident in Browser: https://itservice.lsu.edu/MRcgi/MRlogin.pl?DL=925DA20 Description: Entered on 05/18/2010 at 12:27:12 CDT (GMT-0500) by Dilip Somavarapu: Hi Roland, Sorry I was thinking you were trying to checkin some files into the repository. This repository has read permissions for the cvs_anon and I will be looking into the issue. Thanks Dilip Entered on 05/18/2010 at 10:41:08 CDT (GMT-0500) by roland.haas(a)physics.gatech.edu: Dear Dilip, > I see you using cvs_anon username for update, which will have only read > access for any repository. > Please use your cvs username and password for update the cvs repository. It hangs as well if I use: cvs -d:pserver:rhaas@cvs.cct.lsu.edu/numrel login <Enter rhaas CVS password> cvs -d:pserver:rhaas@cvs.cct.lsu.edu/numrel update Also I checked the repository out using cvs_anon so am surprised that I cannot update my local copy using cvs_anon as well. This repository is used to distribute a Cactus thorn (QuasiLocalMeasures) for the EinsteinToolkit. The aim is to make the thorn (module) available to the general public, who will not have cct CVS accounts. So if a CVS account is needed then users will not be able to update the code even though they could delete their current copy and checkout the newest version again. 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. Entered on 05/18/2010 at 10:29:15 CDT (GMT-0500) by Dilip Somavarapu: Hi Roland, I see you using cvs_anon username for update, which will have only read access for any repository. Please use your cvs username and password for update the cvs repository. Thanks Dilip Entered on 05/18/2010 at 08:47:31 CDT (GMT-0500) by roland.haas(a)physics.gatech.edu: Dear Sir or Madam, > On Tue, May 18, 2010 at 08:55:06AM -0400, Roland Haas wrote: >> I am still unable to *update* CVS repositories from outside LSU (works >> from is.cct.lsu.edu). > > Can you please get in contact with ccthelpdesk(a)lsu.edu to resolve this? > I have spoken with them about this, but couldn't show anything because > it worked for me. > > thanks, Frank I am having trouble *updating* cvs repositories hosted at asylum.cct.lsu.edu from outside of the LSU network. The initial checkout works fine and if I log into say is.cct.lsu.edu I can also update. These are the steps that allow me to reproduce the problem: [rhaas3@phys44230 tmp]$ cvs -d:pserver:cvs_anon@cvs.cct.lsu.edu/numrel login <Enter: anon as password> [rhaas3@phys44230 tmp]$ cvs -d:pserver:cvs_anon@cvs.cct.lsu.edu/numrel co LSUThorns/QuasiLocalMeasures [rhaas3@phys44230 tmp]$ cd LSUThorns/QuasiLocalMeasures/ [rhaas3@phys44230 QuasiLocalMeasures]$ cvs update ... stalls ... With 'strace cvs update' I get as one of the last few lines: mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b773e4c6000 lseek(4, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek) write(3, "BEGIN AUTH REQUEST\n/numrel\ncvs_a"..., 59) = 59 cvs [update aborted]: received termination signal where the termination signal is I pressing CTRL-C. This happens on both my workstation (Gergia Tech) and on TACC Ranger but not from is.cct.lsu.edu. I also see: [rhaas3@phys44230 m]$ netstat --tcp -p | grep cvs (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 59 phys44230.physics.gat:47852 asylum.cct.lsu.e:cvspserver ESTABLISHED 9837/cvs The CVS version at GT is 1.11.22 on Ranger 1.11.17 and on is.cct.lsu.edu 1.11.22. This is rather baffling. 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. Current Assignees: Dilip Somavarapu Contact Information: Email Address: roland.haas(a)physics.gatech.edu Attachments: signature_20100518084731.asc signature_20100518104108.asc

1 0

Re: [Users] still cannot update CVS repositories from outside LSU ISSUE=925 PROJ=20
by CCT IT Support 18 May '10

18 May '10

When replying, type your text above this line. ---------------------------------------------- Notification of Incident Change The following changes have been made to this Incident: Appended a Description, Incoming mail: From: roland.haas(a)physics.gatech.edu; To: ccthelpdesk(a)lsu.edu, Added Attachment. Project: CCT Help Desk Incident: Re: [Users] still cannot update CVS repositories from outside LSU Incident Number: 925 Priority: Medium Status: Open Date: 05/18/2010 Time: 10:41:08 Creation Date: 05/18/2010 Creation Time: 08:47:32 Created By: roland.haas(a)physics.gatech.edu View Incident in Browser: https://itservice.lsu.edu/MRcgi/MRlogin.pl?DL=925DA20 Description: Entered on 05/18/2010 at 10:41:08 CDT (GMT-0500) by roland.haas(a)physics.gatech.edu: Dear Dilip, > I see you using cvs_anon username for update, which will have only read > access for any repository. > Please use your cvs username and password for update the cvs repository. It hangs as well if I use: cvs -d:pserver:rhaas@cvs.cct.lsu.edu/numrel login <Enter rhaas CVS password> cvs -d:pserver:rhaas@cvs.cct.lsu.edu/numrel update Also I checked the repository out using cvs_anon so am surprised that I cannot update my local copy using cvs_anon as well. This repository is used to distribute a Cactus thorn (QuasiLocalMeasures) for the EinsteinToolkit. The aim is to make the thorn (module) available to the general public, who will not have cct CVS accounts. So if a CVS account is needed then users will not be able to update the code even though they could delete their current copy and checkout the newest version again. 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. Entered on 05/18/2010 at 10:29:15 CDT (GMT-0500) by Dilip Somavarapu: Hi Roland, I see you using cvs_anon username for update, which will have only read access for any repository. Please use your cvs username and password for update the cvs repository. Thanks Dilip Entered on 05/18/2010 at 08:47:31 CDT (GMT-0500) by roland.haas(a)physics.gatech.edu: Dear Sir or Madam, > On Tue, May 18, 2010 at 08:55:06AM -0400, Roland Haas wrote: >> I am still unable to *update* CVS repositories from outside LSU (works >> from is.cct.lsu.edu). > > Can you please get in contact with ccthelpdesk(a)lsu.edu to resolve this? > I have spoken with them about this, but couldn't show anything because > it worked for me. > > thanks, Frank I am having trouble *updating* cvs repositories hosted at asylum.cct.lsu.edu from outside of the LSU network. The initial checkout works fine and if I log into say is.cct.lsu.edu I can also update. These are the steps that allow me to reproduce the problem: [rhaas3@phys44230 tmp]$ cvs -d:pserver:cvs_anon@cvs.cct.lsu.edu/numrel login <Enter: anon as password> [rhaas3@phys44230 tmp]$ cvs -d:pserver:cvs_anon@cvs.cct.lsu.edu/numrel co LSUThorns/QuasiLocalMeasures [rhaas3@phys44230 tmp]$ cd LSUThorns/QuasiLocalMeasures/ [rhaas3@phys44230 QuasiLocalMeasures]$ cvs update ... stalls ... With 'strace cvs update' I get as one of the last few lines: mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b773e4c6000 lseek(4, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek) write(3, "BEGIN AUTH REQUEST\n/numrel\ncvs_a"..., 59) = 59 cvs [update aborted]: received termination signal where the termination signal is I pressing CTRL-C. This happens on both my workstation (Gergia Tech) and on TACC Ranger but not from is.cct.lsu.edu. I also see: [rhaas3@phys44230 m]$ netstat --tcp -p | grep cvs (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 59 phys44230.physics.gat:47852 asylum.cct.lsu.e:cvspserver ESTABLISHED 9837/cvs The CVS version at GT is 1.11.22 on Ranger 1.11.17 and on is.cct.lsu.edu 1.11.22. This is rather baffling. 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. Current Assignees: Dilip Somavarapu Contact Information: Email Address: roland.haas(a)physics.gatech.edu Attachments: signature_20100518084731.asc signature_20100518104108.asc

1 0

Re: [Users] still cannot update CVS repositories from outside LSU ISSUE=925 PROJ=20
by CCT IT Support 18 May '10

18 May '10

When replying, type your text above this line. ---------------------------------------------- Notification of Incident Change The following changes have been made to this Incident: Changed Status to Open from Request, Set Issue Category to Issue 1 ,Set Start Date to 20100518 ,Set Due Date to 20100525 , Appended a Description, Added Assignee : Dilip Somavarapu, Changed Incident data or Contact data. Project: CCT Help Desk Incident: Re: [Users] still cannot update CVS repositories from outside LSU Incident Number: 925 Priority: Medium Status: Open Date: 05/18/2010 Time: 10:29:15 Creation Date: 05/18/2010 Creation Time: 08:47:32 Created By: roland.haas(a)physics.gatech.edu View Incident in Browser: https://itservice.lsu.edu/MRcgi/MRlogin.pl?DL=925DA20 Description: Entered on 05/18/2010 at 10:29:15 CDT (GMT-0500) by Dilip Somavarapu: Hi Roland, I see you using cvs_anon username for update, which will have only read access for any repository. Please use your cvs username and password for update the cvs repository. Thanks Dilip Entered on 05/18/2010 at 08:47:31 CDT (GMT-0500) by roland.haas(a)physics.gatech.edu: Dear Sir or Madam, > On Tue, May 18, 2010 at 08:55:06AM -0400, Roland Haas wrote: >> I am still unable to *update* CVS repositories from outside LSU (works >> from is.cct.lsu.edu). > > Can you please get in contact with ccthelpdesk(a)lsu.edu to resolve this? > I have spoken with them about this, but couldn't show anything because > it worked for me. > > thanks, Frank I am having trouble *updating* cvs repositories hosted at asylum.cct.lsu.edu from outside of the LSU network. The initial checkout works fine and if I log into say is.cct.lsu.edu I can also update. These are the steps that allow me to reproduce the problem: [rhaas3@phys44230 tmp]$ cvs -d:pserver:cvs_anon@cvs.cct.lsu.edu/numrel login <Enter: anon as password> [rhaas3@phys44230 tmp]$ cvs -d:pserver:cvs_anon@cvs.cct.lsu.edu/numrel co LSUThorns/QuasiLocalMeasures [rhaas3@phys44230 tmp]$ cd LSUThorns/QuasiLocalMeasures/ [rhaas3@phys44230 QuasiLocalMeasures]$ cvs update ... stalls ... With 'strace cvs update' I get as one of the last few lines: mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b773e4c6000 lseek(4, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek) write(3, "BEGIN AUTH REQUEST\n/numrel\ncvs_a"..., 59) = 59 cvs [update aborted]: received termination signal where the termination signal is I pressing CTRL-C. This happens on both my workstation (Gergia Tech) and on TACC Ranger but not from is.cct.lsu.edu. I also see: [rhaas3@phys44230 m]$ netstat --tcp -p | grep cvs (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 59 phys44230.physics.gat:47852 asylum.cct.lsu.e:cvspserver ESTABLISHED 9837/cvs The CVS version at GT is 1.11.22 on Ranger 1.11.17 and on is.cct.lsu.edu 1.11.22. This is rather baffling. 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. Current Assignees: Dilip Somavarapu Contact Information: Email Address: roland.haas(a)physics.gatech.edu Attachments: signature_20100518084731.asc

1 0

still cannot update CVS repositories from outside LSU
by Roland Haas 18 May '10

18 May '10

Hello all, I am still unable to *update* CVS repositories from outside LSU (works from is.cct.lsu.edu). Bruno: since you are also "outside LSU", could you confirm this (cvs update in arrangements/LSUThorns/QuasiLocalMeasures), please? Just to make sure it is not a GT issue. 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.

3 3

Re: [Users] still cannot update CVS repositories from outside LSU ISSUE=925 PROJ=20
by CCT IT Support 18 May '10

18 May '10

When replying, type your text above this line. ---------------------------------------------- Notification of Incident Registration Project: CCT Help Desk Incident: Re: [Users] still cannot update CVS repositories from outside LSU Incident Number: 925 Priority: Medium Status: Request Date: 05/18/2010 Time: 08:47:31 Created By: roland.haas(a)physics.gatech.edu View Incident in Browser: https://itservice.lsu.edu/MRcgi/MRlogin.pl?DL=925DA20 Description: Entered on 05/18/2010 at 08:47:31 CDT (GMT-0500) by roland.haas(a)physics.gatech.edu: Dear Sir or Madam, > On Tue, May 18, 2010 at 08:55:06AM -0400, Roland Haas wrote: >> I am still unable to *update* CVS repositories from outside LSU (works >> from is.cct.lsu.edu). > > Can you please get in contact with ccthelpdesk(a)lsu.edu to resolve this? > I have spoken with them about this, but couldn't show anything because > it worked for me. > > thanks, Frank I am having trouble *updating* cvs repositories hosted at asylum.cct.lsu.edu from outside of the LSU network. The initial checkout works fine and if I log into say is.cct.lsu.edu I can also update. These are the steps that allow me to reproduce the problem: [rhaas3@phys44230 tmp]$ cvs -d:pserver:cvs_anon@cvs.cct.lsu.edu/numrel login <Enter: anon as password> [rhaas3@phys44230 tmp]$ cvs -d:pserver:cvs_anon@cvs.cct.lsu.edu/numrel co LSUThorns/QuasiLocalMeasures [rhaas3@phys44230 tmp]$ cd LSUThorns/QuasiLocalMeasures/ [rhaas3@phys44230 QuasiLocalMeasures]$ cvs update ... stalls ... With 'strace cvs update' I get as one of the last few lines: mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b773e4c6000 lseek(4, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek) write(3, "BEGIN AUTH REQUEST\n/numrel\ncvs_a"..., 59) = 59 cvs [update aborted]: received termination signal where the termination signal is I pressing CTRL-C. This happens on both my workstation (Gergia Tech) and on TACC Ranger but not from is.cct.lsu.edu. I also see: [rhaas3@phys44230 m]$ netstat --tcp -p | grep cvs (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 59 phys44230.physics.gat:47852 asylum.cct.lsu.e:cvspserver ESTABLISHED 9837/cvs The CVS version at GT is 1.11.22 on Ranger 1.11.17 and on is.cct.lsu.edu 1.11.22. This is rather baffling. 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. Current Assignees: Contact Information: Email Address: roland.haas(a)physics.gatech.edu Attachments: signature_20100518084731.asc

1 0

Patch for TwoPunctures
by Barry Wardell 14 May '10

14 May '10

Hi, The attached patch fixes a couple of minor problems in the TwoPunctures thorn: 1) When the bare masses are not given as parameters (give_bare_mass=no), they are calculated at double precision, but the par_m_plus and par_m_minus parameters are then only set at single precision. 2) When the bare masses have been calculated, they are printed to stdout. In some cases, the initial guess for the bare mass is printed rather than the final calculated bare mass. Regards, Barry Wardell

2 4

Einstein Toolkit talk at GR19
by Erik Schnetter 13 May '10

13 May '10

I have just submitted an abstract for a talk at GR19 <http://www.gr19.com/ > in the session B2 Numerical Relativity and Astrophysical Applications. This talk will advertise the Einstein Toolkit to the community. Title: The Einstein Toolkit Authors: Erik Schnetter for the Einstein Toolkit Consortium Abstract: We introduce the Einstein Toolkit, a collection of software components and tools for simulating and analyzing general relativistic astrophysical systems. Such systems include gravitational wave space-times, collisions of compact objects such as black holes or neutron stars, accretion onto compact objects, core collapse supernovae and Gamma-Ray Bursts. This toolkit is developed as open software for relativistic astrophysics. Our aim is to provide the core computational tools that can enable new science, broaden our community, facilitate interdisciplinary research and take advantage of emerging petascale computers and advanced cyberinfrastructure. We believe that this toolkit can also be constructively used in teaching numerical relativity courses, and can help "getting started" in numerical relativity research. The Einstein Toolkit builds on numerous software efforts in the numerical relativity community including CactusEinstein, Whisky, and Carpet. The Einstein Toolkit currently uses the Cactus Framework as the underlying computational infrastructure that provides large-scale parallelization, general computational components, and a model for collaborative, portable code development. We give a brief overview over the toolkit, its goals, and its current state, and show examples of scientific results obtained by various research groups employing this toolkit as basis of their research codes. -- Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.cct.lsu.edu/~eschnett/

5 14

Commit rights and policy
by Frank Loeffler 10 May '10

10 May '10

Hi, As discussed today I have given everyone currently listed as maintainer on http://einsteintoolkit.org/about/developers/ commit rights to the whole toolkit. This excludes the admin repository where the permissions for all the other repositories are stored, as is information about email addresses and such (for proper From: addresses in commit emails). Only four people do have read/write rights there currently: Colby (computer support), Gab, Erik and myself. Given that privacy-related information is stored there (like email addresses), we decided to keep this repository private, in contrast to everything else in the project. Another issue besides commit rights are some commit guidelines (you could call it policies if you want). We currently do not have this spelled out on the web pages, but we would like to get to that point in the future. We should take the experience with what we will try now as basis for that: Changes should be reviewed by at least one (other) maintainer. We should come up with a table of thorns and their 'maintainers' within the toolkit and ideally these persons should approve (or decline) a patch. However, the announcement of patches and the corresponding discussion should happen on the users mailing list to give everyone the opportunity to speak up and also to prepare for this change. There have to be exceptions to make this practical, but there cannot be strict rules about direct commits without discussions. Use common sense to decide about that. Nobody will shout at you if you get it wrong (at least not it's not too often). Good examples which don't need a discussion are: - Trivial changes (like typos) in documentation or comments, or extension thereof (always welcome) - Obvious bugs which fix problems like a compiler error or a file which was left out of a previous commit - Code cleanup which is not expected to change any result (like a formating change) Although you might _want_ to have a second look if this is a bigger change. If you would like to make such a change but you are not a maintainer, please simply send it to the users list regardless. Frank

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users