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#.
Besides any development issues that might have come up last week I would like to brainstorm about the future direction of the toolkit. This is a good time to look back because officially the original grant will end soon. In no particular order and certainly not complete, think about topics of the following kind:
- If you were the single person to change something within the ET, what would it be? - Funding for the next three years will be much less than what the project had so far, thus we need to concentrate on the most important things. What do you consider most important? - Are the weekly calls your tool of choice to coordinate development? - Are the services the toolkit provides sufficient? Should something in particular be changed / improved? - Should the toolkit have 'own' user profiles (not using the CCT logins)? - Should we investigate in non-svn repos at ET.org (specifically git)? - Should the web page stay plain html, editable by every developer?
Some of these questions might be fast to answer, others maybe not and you might have some of your own. This is not meant to decide anything, but to get community input on what is needed/expected/wanted and we do this deliberately at the public call so that everyone can have a voice. Of course we would like to see emails as well in case you prefer that or you cannot join the call.
Last week was busy: 16 Issues have been changed and are still open but 20 have been closed, e.g.: - The default relative tolerance of testsuites has been changed from 0 to 1.e-12 - The rsync option '-C' isn't used by simfactory anymore since it excluded copying some things users did in fact want to copy. - SummationByParts got improved OpenMP parallelization for Intel Compilers (because they still cannot handle workshares as they should). - LocalInterp got some OpenMP improvements. - Cactus now better enforces that arrangement and thorn names only contain characters from a whitelist. This is necessary because these names are used inside C code. - Carpet could in some cases interpolate data from buffer regions. This was now fixed.
9 Tickets are waiting for review at the moment [1]. Please see if you can help.
Frank Loeffler
[1] https://trac.einsteintoolkit.org/query?status=review&group=component&...
_______________________________________________ Users mailing list Users@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users
users@lists.einsteintoolkit.org