[Users] Einstein Toolkit Meeting Reminder

[Frank Loeffler]

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#.

In addition to anything that might be brought up at the meeting, the
primary issue at the moment is to get the code ready for a new release
in May, with the planned schedule shown below. At the moment this means
to test, test and test. Bugs and smallish new features might still go
in, but larger additions (like new thorns) are already 'out'.

Last week a number of maintainers agreed to test machines. So far, only
four are in:

  https://docs.einsteintoolkit.org/et-docs/Release_Details

We currently miss:

Ian: datura
Erik: bluewaters, hopper, orca, surveyor, vesta
Roland: kraken, zwicky
Peter: pandora, queenbee, tezpur
Frank: philip (speed problems)
Tanja: stampede
Bruno: tresles

plus a couple of private machines. Please update the results, or the
wiki indicating if you cannot do the tests on a particular machine.

The currently very scarce results indicate, that at least on one machine
(spine - a Debian workstation, using gcc 4.7) all tests pass. On others
quite some number fail (e.g. supermuc). Common problems seem to be one
Exact testsuite, and some GRHydro suites, especially the new WENO test
stuite. Symmetry thorns also fail some of their tests on more than one
of the four machines.

As always: failure don't necessarily mean that something is wrong.
Sometimes, the tolerances are just too strict for the underlying code,
and CPUs, different compilers or compiler flags then show these
differences. 

So, in short: the good news is that at least one machine doesn't show
test suite failures, something that was often not the case in the past.
Now we 'only' need to figure out what needs to be done with tests that
fail on some of the machines - especially the large production clusters.


We also mentioned possibilities for the new release name last time. The
current list is on the wiki as well. Please add other names if you like:

  https://docs.einsteintoolkit.org/et-docs/Release_Details

- ET_2013_05 schedule
    - Apr 08: No new major additions to the ET until unfreeze
    - May 01: feature freeze of /trunk, extensive testing begins
              (test-suites on all relevant machines)
    - May 10: release branches are created trunk unfrozen again
              release-branch code in only-important-bugs-freeze bug-fixing
              primarily in release branch
    - May 21: complete freeze, to prepare tar-balls, add tags ect.
    - May 23: target release date (or earlier if all bugs are fixed)

Frank Löffler

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
Url : http://lists.einsteintoolkit.org/pipermail/users/attachments/20130428/7b0c30b4/attachment.bin