Users April 2011

users@lists.einsteintoolkit.org

16 participants
24 discussions

"No Einstein Toolkit Meeting" Reminder
by Frank Loeffler 04 Jul '11

04 Jul '11

Hi There will be no Einstein Toolkit meeting today. The next Monday-meeting will happen in two weeks: May 9th at 10am US central time. Frank Loeffler

2 1

Carpet Mercurial
by Frank Loeffler 01 May '11

01 May '11

Hi, With the new release out of the way, the mercurial(hg)-version of Carpet will replace the git-version in the development version of the Einstein Toolkit. Write access will be provided as was in the past: using ssh keys. Ask Erik to get access. Anonymous read access is available via the following URL, both to be used for cloning, and for browsing the repository if you so like. http://www.carpetcode.org/hg/carpet/ We will change the thornlist of the development version of the Einstein toolkit to use the hg version - please be aware of this when you update your configuration. Frank Loeffler

4 5

TOVSolver
by Frank Loeffler 28 Apr '11

28 Apr '11

Hi, I propose to change the TOVSolver parameters. - Some of the parameters can be given individually for each star, and I would like to change that to only one global parameter, valid for each star: TOV_Gamma[] -> TOV_Gamma TOV_K[] -> TOV_K - TOV_Solve_for_TOVs -> remove (depreciated already) - TOV_Fast_Interpolation -> remove (no reason to not use the default) Those changes could be done right away. After that, we should also: - Don't let TOVSolver set the conserved variables - Don't set an atmosphere (let GRHydro handle that) - Remove dependency on GRHydro (is blocked by previous two points) Thoughts about this? Frank

2 1

Maintaining old releases
by Ian Hinder 24 Apr '11

24 Apr '11

Hi, The Einstein Toolkit has releases every six months or so which are tested and tagged so that people can download a working version. However, some things change (for example machine configurations and directory locations) which mean that the old releases don't work any more. How should we solve this problem? One proposal would be to check every commit and decide if it needs to be backported to old releases. This would only happen if the old release would no longer work without the commit (or maybe if the bug was very important?). How many releases should be backported to? Just the last one? This issue is probably only really applicable to simfactory machine configurations and optionlists. -- Ian Hinder ian.hinder(a)aei.mpg.de

3 2

Age of TRAC tickets
by Erik Schnetter 22 Apr '11

22 Apr '11

I took the liberty of adding a column "time" to the default TRAC display options, showing the age of the ticket. This is especially useful if you follow the "View all open tickets (only pending review)" link. There are 12 tickets that have patched attached, ready to be committed if someone invests the time examining these patches. These tickets are between 3 weeks and 5 months old. I encourage all Einstein Toolkit users to have a look, and if you find you are interested in one of these patches, do not hesitate to leave a comment there. -erik -- Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.cct.lsu.edu/~eschnett/

1 0

Code freeze
by Frank Loeffler 21 Apr '11

21 Apr '11

Hi, The Einstein Toolkit [1] prepares for a new release this week, and in the process all repositories which are part of the ET are from now on frozen. That means nobody should commit any change anymore, unless it a) fixes an important bug _and_ b) is approved by myself. This is not enforced technically, but don't abuse it. The freeze won't last for long. The current plan is: Mon Apr 18th: freeze Wed Apr 20th: release-branches created Thu Apr 21th: new release, thaw The new release will be announced here, as well as any changes to this plan. Frank [1] http://einsteintoolkit.org/

1 2

Einstein Toolkit Release
by Frank Loeffler 21 Apr '11

21 Apr '11

We are pleased to announce the second release (code name "Curie") of the Einstein Toolkit, an open, community developed software infrastructure for relativistic astrophysics. This release changed the equation of state interface from two competing (EOS_Base and EOSG_Base, also known as the old and the general EOS interface), to a completely new interface called EOS_Omni, also adding support for tabulated, microphysical EOSs in the process. In addition, bug fixes accumulated since the previous release in November 2010 have been included, and the testsuites have been checked also using OpenMP. The Einstein Toolkit is a collection of software components and tools for simulating and analyzing general relativistic astrophysical systems that builds on numerous software efforts in the numerical relativity community including CactusEinstein, the Carpet AMR infrastructure and the relativistic hydrodynamics code GRHydro (an updated and extended version of the public release of the Whisky code). The Cactus Framework is used as the underlying computational infrastructure providing large-scale parallelization, general computational components, and a model for collaborative, portable code development. The toolkit includes modules to build complete codes for simulating black hole spacetimes as well as systems governed by relativistic hydrodynamics. Current development in the consortium is targeted at providing additional infrastructure for general relativistic magnetohydrodynamics. The Einstein Toolkit uses a distributed software model and its different modules are developed, distributed, and supported either by the core team of Einstein Toolkit Maintainers, or by individual groups. Where modules are provided by external groups, the Einstein Toolkit Maintainers provide quality control for modules for inclusion in the toolkit and help coordinate support. The Einstein Toolkit Maintainers currently involve postdocs and faculty from five different institutions, and host weekly meetings that are open for anyone to join in. Guiding principles for the design and implementation of the toolkit include: open, community-driven software development; well thought out and stable interfaces; separation of physics software from computational science infrastructure; provision of complete working production code; training and education for a new generation of researchers. For more information about using or contributing to the Einstein Toolkit, or to join the Einstein Toolkit Consortium, please visit our web pages at <http://einsteintoolkit.org>. Detailed information about this release can be found here: <http://einsteintoolkit.org/about/releases/ET_2011_05_announcement.php>. The Einstein Toolkit is primarily supported by NSF 0903973/0903782/0904015 (CIGR), and also by NSF 0701566/0855892 (XiRel), 0721915 (Alpaca), 0905046/0941653 (PetaCactus) and 0710874 (LONI Grid). The "Curie" Release Team on behalf of the Einstein Toolkit Consortium (2011-04-21)

1 1

release status
by Frank Loeffler 20 Apr '11

20 Apr '11

Hi, I created a new release branch in all repositories within the thornlist, except three: Kranc, PunctureTracker and Systemstatistics. I lack write permissions to those, admins are notified. Unfortunately this means that a complete test cannot be run right now and has to wait until this is resolved, holding up the release. Despite the creation of the new branches, the freeze is still in effect to be able to more easily roll-back in case of not expected problems. We lack updated testsuite information for some machines, I assume this is because of jobs waiting in the queue. It would be nice to get that information in before the release. With the exception of the new machine pandora (still in friendly-user mode), all updated machines now pass all testsuites using one and two MPI processes and one and two threads. I wouldn't be surprised if some of the missing machines still fail a few tests though. However, we never had this few failing tests before to the best of my knowledge - a big thanks for all the people involved in tracking these issues down. With respect to the name the current status is: Name Count Curie 5 Dirac 4 Noether 4 Einstein 1 I will take the status tomorrow morning and simply decide for number one, because I think that all are good candidates. So, you still got a bit of time to (re-)decide. Frank

1 0

Release name
by Frank Loeffler 20 Apr '11

20 Apr '11

Hi, Something totally unimportant (is it?) I forgot to bring up at today's call is a name for the new release. We already had ET_2010_06 aka Bohr ET_2010_11 aka Chandrasekhar The new release will be ET_2011_05, and we cannot just yet use "Maxwell" - hopefully next release for obvious reasons. The suggestion of office LSU J202 (Peter and Frank) is following our "tradition" of choosing physicists, we could relate it to one of the larger changes this release, plus it comes next in the alphabet: Dirac Any comments, or other suggestions? Frank

12 13

ET testsuite rerun
by Frank Loeffler 20 Apr '11

20 Apr '11

Hi, for all of you who are running parts of the testsuite collection at http://einsteintoolkit.org/release-info/parse_testsuite_results.php : Please do a fresh checkout again and redo the tests, hopefully the last time before the relase. thanks, Frank

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users April 2011