Present: Roland, Antoni Ramos Buades, Eloisa, Erik, Ian, Jim, Sam, Steve, Peter, Yosef, Bhavesh, Bill, Carlos, Gabrielle, Muricia Suarez, Roberto de Pietri, Qian, two anonymous callers
Invitation to join cosmo working groups * if interested, please join the mailing list as outlined in the email by Helvi at: http://lists.einsteintoolkit.org/pipermail/users/2018-January/006021.html
Failing tests in PITTNullCode: * Yosef tracked it down to a compiler bug. The only affected code is the test, regular code in the thorn does not use the failing combination of operations. A bug report has been filed with the gcc developers * would like to find out which versions are affected * will follow Yosef's suggestion and remove the test
Release status: * test are in the process of running on clusters * have to find out (again) how to populate http://einsteintoolkit.org/testsuite_results/index.php * had release status meeting on Friday and could clarify most issues * details are here: https://docs.einsteintoolkit.org/et-docs/Release_Details * Ian created tickets for the otustanding tasks (marked with the milestone) in the trac system * code name "Tesla"
OpenMP scaling: * Jim ran openmp-tasks version on Stamped2 Skylake * running on larger number of cores (~24 nodes) one sees an improved runspeed using the task based prolongation compared to either the old code or the new code with the options turned off * this test used 11 reflevels and fairly high resolution * Erik points out the importance of thread binding in Cactus which requires the SystemTopology thorn. Jim will re-run with that thorn active (~256 iterations is enough). Should also post the stdout files where Carpet lists thread binding results
ET US meeting at GT: * dates have still to be finalized
Yours, Roland
Hello all,
Release status:
- test are in the process of running on clusters
- have to find out (again) how to populate
The repo is helpfully listed on top of the status page: http://einsteintoolkit.org/testsuite_results/index.php namely it is https://bitbucket.org/einsteintoolkit/testsuite_results
I have also updated the wiki with this information.
The good new is that there are (so far) no disastrous failures. QueenBee had trouble compiling this morning and I was compiling manually to get more readable error output. The two MPG machines (hydar and draco) should run, but I remember that at least for one I had to do tricks to get the testsuite runs to start due to restrictions on runtime and the number of nodes one can use (or maybe that was edison&cori). Golub is NCSA local, the hex numbers are my laptops.
So it would be good if Roberto could again test the Italian machines and if Steve, Peter, Frank could give the LSU ones (other than qb which I can test though if you were to also update its machine files and make it compile again, that would be great) a try.
Yours, Roland
users@lists.einsteintoolkit.org