Hi
Please consider joining the weekly Einstein Toolkit phone call at 9:30 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/
We use a Google hangout, with an URL announced on this list before the meeting.
Likely topics are potential problems that might have surfaced after the release, and what to expect to change soon within the development version.
Frank Löffler
On Sun, Jan 08, 2017 at 07:00:03PM -0600, Frank Loeffler wrote:
We use a Google hangout, with an URL announced on this list before the meeting.
https://hangouts.google.com/hangouts/_/p5qtz45rbnhutnp4i7qrzw6n24e?authuser=...
Frank
Minutes for this week:
Present were: Erik, Frank, Ian, Steven, Vassili and Yosef.
Some issues with the last release will be backported, all of which are slight changes to machine options in simfactory, see ticket https://trac.einsteintoolkit.org/ticket/1997 After those have been backported, a new release tag will be generated (but as with all tags, should not be used for checkouts; pull within the simfactory repository instead).
PITTNUllCode/SphericalHarmonicRecon apparently uses functions only available to the HDF5 version 1.8 API, while the rest of the toolkit so far only required version 1.6. It was agreed that requiring version 1.8 for the toolkit would be the best solution, as this has now been around for quite a while, and should be supported on almost all machines. Where it might not yet be supported, the bundled version can be used.
The McLachlan constraint test failures with some versions of the Intel compilers are still an unsolved issue.
The piraha_everywhere branch will be merged with master very soon.
Erik proposed to move the calculation of the RHS to PostStep. While this would change scheduling, this change should be transparent to most thorns. Exceptions are infrastructure thorns like Poison, or possibly thorns that don't use MoL in the intended way (but we don't know of any such thorns).
The creation of a very brief McLachlan gauge condition cheat sheet was discussed, to be able to point to that in case of questions about the meaning of each parameter, or to prevent those questions in the first place. However, the general consensus seems to be that a cleanup should be in-order first. Volunteers for this are welcome.
Now is the time to make larger changes to the Einstein Toolkit, so expect possible breakages of the development version. Don't use it for production.
This is also the time to think about release goals for the spring release. Please collect some thoughts, and share them at the next Einstein Toolkit meeting. We do want to avoid duplication of effort.
Unless otherwise announced, there will be *no Einstein Toolkit meeting next week*. The next call will be on Jan 23, at the usual time.
Happy new year, Frank
Hi
Please consider joining the weekly Einstein Toolkit phone call at 9:30 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/
We use a Google hangout, with an URL announced on this list before the meeting.
Topics discussed tomorrow include release and development plans for the spring.
Frank Löffler
On Sun, Jan 22, 2017 at 08:16:09PM -0600, Frank Loeffler wrote:
We use a Google hangout, with an URL announced on this list before the meeting.
https://hangouts.google.com/call/bsf6nd2ajzdbfdh3tvachz7qgye
Frank Loeffler
users@lists.einsteintoolkit.org
-
Frank Loeffler