Users

users@lists.einsteintoolkit.org

3 participants
3984 discussions

new release delayed a few days
by Frank Loeffler 14 Nov '14

14 Nov '14

Hi, A short update on the upcoming release: Mainly due to projects at LSU that were more time-consuming than foreseen, the Einstein Toolkit release was delayed a few days. Originally we planned to release this week, but we now look at next week. On the bright side, due to the mentioned project, the ET will be part of a demo at a major supercomputing conference in the US (SC14) next week, running a (simple) neutron star simulation on 32 nodes of a Raspberry-Pi cluster. I am sorry for the inconvenience. Frank Loeffler

1 0

How to submit patches to the Einstein Toolkit
by Erik Schnetter 10 Nov '14

10 Nov '14

When using Subversion, there are two classes of people: Those with write access to the repository, which can make changes or create branches for development, and those without, who are forced to send patches or tarballs by email or by attaching them to a bug report. The latter is really quite inconvenient, both for the people preparing them, and also for the people who have to apply them. When using a git repository hosted at Bitbucket (or Github etc.), things are much easier for all parties. There is no need to send around patches or tarballs any more. Instead, you do the following. Bear with me -- the instructions are lengthy only because I'm explaining things, but each of these steps really corresponds just to a mouse click or two. (1) Create an account at Bitbucket. Obviously, you do this only once. (2) Fork the repository on Bitbucket. This creates a copy of the repository on Bitbucket which belongs to you, and where you can commit changes. I see the "fork" menu entry hidden behind the three horizontal dots in the top-left corner of the original repository's web pages. That's "fork", and not "clone" -- clone would make a copy on your laptop, which isn't quite enough. The difference is that you can later allow others to look at your forked repository, and thus pick up the changes you made. (3) Clone the forked repository, or -- if you already have a clone of the original repository -- add a new "remote" to it. That's straightforward if you use a GUI, on the command line you'll have to follow instructions that are posted on Google. All the steps until here are necessary only once per repository. (Unfortunately, the ET uses a gazillion of repositories -- in hindsight I'm not quite sure why, it certainly doesn't make things easier.) (4) Make your changes, commit them, etc. I usually create a new branch for every patch. (5) Push your changes (i.e. the branch) to the forked repository. They are now visible to the world; people can look at them and comment them. (6) Tell others about your changes and where to find them. The easiest way is to create a "pull request" on Bitbucket. I see the "create pull request" menu entry near the "fork" menu entry. A "pull request" is essentially a ticket (on Bitbucket) that allows others -- those with write access to the repository -- to merge ("pull") your changes with the click of a button. Those with write access like this, because it's very convenient. They don't even have to clone your branch -- it's all visible right there in the web browser, and reviewing and accepting a patch takes less than a minute. As an added bonus, since you created the commit, your name will be associated with the change and bring you fame. And as a side note, my (egoistic) willingness to look at a patch depends on how much trouble I have to go through for this. Clicking on a link that immediately shows me a nice commit message in a web browser together with a colour-coded diff is about as easy as it gets for me. -erik -- Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.perimeterinstitute.ca/personal/eschnetter/

1 1

Einstein Toolkit Meeting Reminder
by Frank Loeffler 10 Nov '14

10 Nov '14

1 0

Build server fails
by Erik Schnetter 10 Nov '14

10 Nov '14

I see that the ET build server is failing for the past two commits. I can only access the commit messages on the build server's web pages, and they point to unrelated Simfactory MDB changes. Is there a way to get a complete diff between the last succeeding and the first failing version? The error message points to PETSc and how it configures MPI. -erik -- Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.perimeterinstitute.ca/personal/eschnetter/

4 4

LSU servers partially down
by Frank Loeffler 07 Nov '14

07 Nov '14

Hi, Some of our servers were hit by a power outage tonight. They are gradually brought up again now, but that process has not finished yet. Frank

1 0

Meeting Minutes for 2014-11-03
by Roland Haas 06 Nov '14

06 Nov '14

Present: Frank, Peter, Steve, Matt, Roland, Ian, Elo, Erik, Jonah, Josh, Zach, Philipp Tickets: * intel compiler miscompiles NewRad ** intel 15 fixes this again ** Steve will try and write an autoconf test for this * use after free in IOUtil's parameter recovery routine ** Frank to fix * IllinoisGRMHD: ** suggest to use custom thornlist based on release thornlist but using different branches for HydroBase and Carpet Upcoming release: ** Send out announcement of upcoming release timeline to mailing list ** Elo has new simfactory files for new machine, will test and we will include machine in release announcement if tests pass * Frank to make people do what they promise to do * GRHydro failing tests on stampede: Roland to check what is going on and to fix Yours, Roland

3 6

ET test failures on Stampede
by Erik Schnetter 05 Nov '14

05 Nov '14

I've begun to run the automated tests for the ET on our production machines. Things look very good almost everywhere, except on Stampede, one of the machines that is most important to us. It seems that there are many test failures for GRHydro, and these seem to be caused by segfaults. Does anybody volunteer to investigate? -erik -- Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.perimeterinstitute.ca/personal/eschnetter/

3 13

Building on stampede
by Ian Hinder 05 Nov '14

05 Nov '14

Hi, When I try a fresh build of the current ET trunk on stampede, I get > CST error 1: > -> Thorn 'LORENE' requires the capability 'LAPACK'. > Please add a thorn that provides 'LAPACK' to your ThornList or remove 'LORENE' from it ! > > > CST error 2: > -> Thorn 'LORENE' requires the capability 'BLAS'. > Please add a thorn that provides 'BLAS' to your ThornList or remove 'LORENE' from it ! > > > CST error 3: > -> Thorn 'TGRtensor' requires the capability 'LAPACK'. > Please add a thorn that provides 'LAPACK' to your ThornList or remove 'TGRtensor' from it ! > Did something get forgotten in the latest BLAS/LAPACK/OpenBLAS changes? -- Ian Hinder http://numrel.aei.mpg.de/people/hinder

2 2

Release plans
by Frank Loeffler 03 Nov '14

03 Nov '14

Hi, A new Einstein toolkit release is being prepared right now. In order to make this happen, the current code base is largely "frozen", with only small changes allowed to be made (bug fixes, documentation updates and the like). This will be followed by a complete freeze next Monday (Nov 10th), until the release a few days later. One suggestion for a release name (thanks Peter) is: Yvonne Choquet-Bruhat http://en.wikipedia.org/wiki/Yvonne_Choquet-Bruhat Yvonne Choquet-Bruhat (born 29 December 1923 in Lille) is a French mathematician and physicist. She was the first woman to be elected to the Académie des Sciences Française ("French Academy of Sciences") and is a Grand Officier of the Légion d'honneur. <snip> From 1951-1952 she worked at the Institute for Advanced Study in Princeton where she proved the local existence and uniqueness of solutions to the vacuum Einstein Equations. <snip> At the Universite Pierre et Marie Curie she continued to make significant contributions to mathematical physics, notably in general relativity, supergravity, and the non-Abelian gauge theories of the standard model. Please let us know if you disapprove, and/or if you want to nominate someone else. Frank

4 3

Einstein Toolkit Meeting Reminder
by Frank Loeffler 03 Nov '14

03 Nov '14

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/ In short: the number is (+1) 225-578-4942 or (+1) 866-573-0359 and the conference id is 118682#. Notice that "summer time" ended in the US, which means that the meeting time might be different for you right now compared to "usually". However, a lot of countries already changed previously as well (like Germany), so time might be "in sync" now again. (Some) noteworthy tickets: - 1276: Intel Compiler and __restrict__ : is new blacklist known? - 1685: use of a freed pointer within Cactus With beginning of today, no larger changes should go into the ET before the release. What didn't make it in until now should be able to wait for 1-2 weeks (unless discussed, of course). Frank Loeffler

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users