Users January 2013

users@lists.einsteintoolkit.org

14 participants
25 discussions

Einstein Toolkit Meeting Reminder
by Frank Loeffler 14 May '15

14 May '15

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]! - Hotel booking - Release planning - release date: Mon Oct 24 2011 - freeze date: Mon Sep 26 - the day of the call! - branch name: ET_2011_10 - List of release-concerning bugs [2] - ET paper: proposed "freeze" by Oct 3rd (Mon after this call) 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&…

10 31

McLachlan BSSN
by Erik Schnetter 18 Feb '13

18 Feb '13

Please keep all discussion on the McLachlan BSSN code on this mailing list. This ensures that everybody knows about everything that is going on, and avoid duplicate work. At the moment, we seem to have approximately three different versions of the BSSN code that seem to be incompatible: - the (official) trunk version - a version (potentially faster and more accurate) by Jim van Meter - a more flexible version (regarding gauge conditions) by Peter Diener I would suggest that we discuss things on this list before we proceed. John, Peter, could you describe your changes here? -erik -- Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.perimeterinstitute.ca/personal/eschnetter/

4 6

question about ET on Stampede (TACC)
by Bruno Giacomazzo 07 Feb '13

07 Feb '13

Hi, I'd like to compile and run ET on the new TACC cluster Stampede. Did anybody run ET on stampede? I see that there are already simfactory scripts for stampede in the ET development version, but I'm not sure if they have been already fully tested (I see that there are comments about job submission not having been tested yet). I'm also curious to know if you think that the hybrid approach can be of any use for ET/GRHydro (or ET/Whisky) on that machine. I'm not very familiar with the Intel Phi coprocessor and MIC programming (but it seems similar to GPU, except for being much easier to use). Thanks, Bruno Dr. Bruno Giacomazzo JILA - University of Colorado 440 UCB Boulder, CO 80309 USA Tel. : +1 303-492-5170 Fax : +1 303-492-5235 email : bruno.giacomazzo(a)jila.colorado.edu web: http://www.brunogiacomazzo.org ---------------------------------------------------------------------- There are only 10 types of people in the world: Those who understand binary, and those who don't ----------------------------------------------------------------------

3 9

Einstein Toolkit Seminar
by Roland Haas 04 Feb '13

04 Feb '13

Hi Please consider joining the Einstein Toolkit Seminar next week Monday, February 4h, at 10 am US central time. We will use the Einstein Toolkit Meeting venue for this, and will use a Webex seminar. Details on Webex (system requirements, how to connect, phone in numbers) will be provided in a separate email soon. Details (and eventually link to the slides) can be found at http://einsteintoolkit.org/seminars/2013_02_04/ Next weeks presenter will be Christian Reisswig from the Caltech, talking about "Three-Dimensional General-Relativistic Hydrodynamic Simulations of Binary Neutron Star Coalescence and Stellar Collapse with Multipatch Grids". Roland Haas

3 6

Using Cactus HDF5 Vector Data in Visit 2.6.0
by Brian Taylor 30 Jan '13

30 Jan '13

I am trying to use vector data in Visit 2.6.0. Each component of the data that I have is separated into three scalar quantities. I want to know how to combine these scalars into one vector quantity that can be used in visit. So far, I have tried to do this using HDF5 data organized two ways: one where all the data for each component is in one file (for example - Bx.h5, By.h5 etc.), the other way involved having the data separated by refinement grids in 32 files per component (so, Bx_file_*.h5 where "*" is from 0 to 31). With both methods I have run into issues when trying to draw vector or streamline plots. For the single file component data, I first loaded each component into its own database. Then I used the database comparison wizard to setup an evaluation of type "Between meshes in two separate databases" for my y and z component. The target database was Bx.h5 and the target mesh was "Carpet AMR-grid" while the donor database was By.h5 and Bz.h5 respectively with donor field "MHD_EVOLVE--By" and "MHD_EVOLVE--Bz." I tried both connectivity and position based CMFE. Neither seemed to make a difference. And I just chose placed the donor field on the target mesh. I then made a database correlation based on time between my three databases. Then in the expressions editor, I made a vector mesh variable defined by {<MHD_EVOLVE--Bx>,By_comp,Bz_comp} where By_comp and Bz_comp were the resultant expressions from the database comparison wizard. <MHD_EVOLVE--Bx> is the component in the active database. I then went to add a vector plot using the vector expression. When I would click draw on the vector plot I would get the following error: Vector: (InvalidExpressionException) viewer: The expression was invalid: The expression parser encountered an unexpected token: conn_cmfe(</home/projects/By.h5:MHD_EVOLVE--By>, Carpet AMR-grid) ^^^ I don't know if this matters but in the visit window, the three carets are under "AMR" Before that, I also tried pretty much the same steps with the component files containing 32 files. I then got a similar error: Vector: (InvalidExpressionException) viewer: The expression was invalid: The expression parser encountered an unexpected token: conn_cmfe(</home/projects/B5/3d_data_201207012347/By.file_* database:MHD_EVOLVE--By>, Carpet AMR-grid) ^^^ Again, the three carets are under "AMR" I should note that I am having no trouble drawing scalar quantities with volumes plots for example. The components individually will draw properly. Has anyone successfully loaded and drawn cactus vector data either by combining three scalars in visit or by using another form of data? Thanks, Brian Taylor

2 1

Releases and backporting
by Ian Hinder 30 Jan '13

30 Jan '13

Hi, Recently, the issue of backporting fixes to the released version of the Einstein Toolkit has come up. When the code is obviously wrong in the released version, especially when this is a newly-introduced problem, we have committed the fix both to the trunk and to the release branch. There have been a small number of these commits. Now that I think about it, I see that this approach has some problems. 1. If someone says in a paper that they are using "the release" of the ET, there is no way to know which version they are using if "the release" refers to the branch (which can point to different versions as people commit occasional fixes). 2. There is no way to easily test the "proposed re-released version" before moving the release branches, at which point new users will be downloading the untested version. Version control systems have both branches and tags. Branches point to "lines of development" and tags point to specific versions. In order to identify specific releases of the code, we should use tags, for example ET_2012_11.1, ET_2012_11.2 etc. Once created, these never change. Perhaps we want the following: * Branch for trunk, as currently; * Branch for "backports"; this would be things which people think should be backported and which can then be checked out and tested easily; * Tags for tested, released versions (ET_2012_11.N) * Branch for the latest tagged version (ET_2012_11) (?) The important thing is that people know (and can state in papers) what version of the code they are using. One way to ensure this is to ask people to check out the release from a specific tag, and then to check it out again from the new tag when there is a new version. An alternative would be to always check out from the release branch, but to provide a GetComponents mechanism for upgrading from one version to the next, and for verifying that the currently checked-out code is all from the same tag. I don't want to overcomplicate things, but issue (1) listed above is important. Does anyone have some better suggestions? -- Ian Hinder http://numrel.aei.mpg.de/people/hinder

3 3

Re: [Users] [Einstein Toolkit] #590: McLachlan should allow other thorns to set the gauge
by Einstein Toolkit 29 Jan '13

29 Jan '13

#590: McLachlan should allow other thorns to set the gauge ------------------------------------+--------------------------------------- Reporter: bmundim | Owner: diener Type: defect | Status: assigned Priority: major | Milestone: ET_2013_05 Component: EinsteinToolkit thorn | Version: Resolution: | Keywords: ------------------------------------+--------------------------------------- Comment (by diener): I took a quick look at the version of McLachlan provided in Ticket #963. As far as I can see the proposed changes there are orthogonal to this patch, i.e. they mainly change the RHS calculation, which I don't touch. John mentioned that he recently merged Jim's version with the release version. Maybe starting from that it would not be so difficult to produce a patch that can be applied to the development version. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/590#comment:16> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

Re: [Users] [Einstein Toolkit] #590: McLachlan should allow other thorns to set the gauge
by Einstein Toolkit 29 Jan '13

29 Jan '13

#590: McLachlan should allow other thorns to set the gauge ------------------------------------+--------------------------------------- Reporter: bmundim | Owner: diener Type: defect | Status: assigned Priority: major | Milestone: ET_2013_05 Component: EinsteinToolkit thorn | Version: Resolution: | Keywords: ------------------------------------+--------------------------------------- Changes (by knarf): * cc: users@… (added) Comment: Testing adding the ET users mailing list as CC to this ticket. But for that to work out in trac neatly would mean to respond in trac, not on the mailing list. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/590#comment:15> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

Meeting Minutes
by Roland Haas 28 Jan '13

28 Jan '13

Present were: Frank, Steve, Peter, Roland, Ian, Philip, Tanja, Erik ET spring workshop: * will announce ET workshop together with Caltech school on astrophysics gravitational waves [1] Site is currently under construction so content may change. * the new user workshop will be *one day*, Friday July 26th * the summer school before should cover the theory part, eg. BSSN and astrophycis and gravitational wave theory * preliminary program outline is on wiki [2] * old meeting notes on user workshop: > * next new users workshop will be attached to Caltech summer > school on astrophysics. School runs July 22nd - July 26th (incl.). > * students of summer school housed in dorms, extra attendants will need > to book hotel rooms (dorms would need to know how many rooms in advance > [now]). > * will have 1 day intensive program on Friday (from past experience; we > want to offer an early bird setup session the day before or before the > workshop starts, we do not want to loose time on this.) > * program suggestions: > - gear towards astrophysics (less binary black holes) > - consider other components than Cactus, eg. GR1D > - generic computational methods: OpenMP, OpenCL, CUDA, (since new > clusters with accelerator architectures will be online by then) > * a wiki page for the workshop will be created > (https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Summer…), > please list yourself if you want to volunteer for a section of the workshop > > * attach developers workshop after new users workshop, ie. on Saturday, > Sunday and Monday > * pick one topic for developers workshop, prepare this in advance, focus > on this during workshop * suggestions for the hands on coding are to write a simple center of mass routine (not the more fancy one we tried before, just one that produces output to disk). * developer's workshop right afterwards on Saturday and Sunday. Need goal for this workshop. GRhydroMP presentation: * current plan is to use webex. Instructions on how to use are to follow. * Erik will be host * date: next week Feb 5th Yours, Roland [1] http://www.cgwas.org [2] https://docs.einsteintoolkit.org/et-docs/ET_Workshop_Summer_2013

1 0

Einstein Toolkit Meeting
by Frank Loeffler 27 Jan '13

27 Jan '13

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users January 2013