Users November 2013

users@lists.einsteintoolkit.org

12 participants
26 discussions

Einstein Toolkit Meeting Reminder
by Frank Loeffler 10 Nov '13

10 Nov '13

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#. I expect us to talk primarily about the upcoming release, but any other topic is of course welcome, and will be discussed first. Frank Löffler

1 0

Testing Simfactory for release
by Erik Schnetter 07 Nov '13

07 Nov '13

I have updated the option lists in Simfactory for several machines. This is to ensure that these option lists and machine descriptions are current, so that these machines can be used easily. I have tested that the test suites can be run, but not whether they succeed. According to my tests, these option lists now allow syncing, building, submitting, and running on the following systems without problems: - Bethe, Blue Waters, Gordon, Hopper, Kraken, Lonestar, Mike, Nvidia, Orca, Philip, Queen Bee, Redshift, Stampede, Stampede-MIC, Titan, Trestles, Zwicky There are problems on the following systems: - Carver, Pandora, Surveyor (job submission) - Vesta (running test suite) I did not test the following systems: - Datura, GPC, Loewe, Supermuc As mentioned above, I did not check the results of running the test cases; I assume that some test cases are failing on some of these systems. I think we should address the problems on Pandora, Datura, and Vesta, and maybe Loewe. I volunteer for Vesta. I am using the "distribute" script that comes with Simfactory for this. To use it: - Check out the Einstein Toolkit - run e.g. ./sim/bin/distribute --no-benchmark queenbee - this will sync, and then remotely build, submit a simple test job, run the test cases, and then test checkpoint/recovery/presubmission - high-level output: tail -f log/queenbee.results - verbose output: tail -f log/queenbee.out Since this works remotely, this requires keeping a network connection from your machine to the machine being tested. I thus run this from a workstation, not from my laptop. If you run this on Queen Bee directly, you obviously don't need to keep a network connection since the tests will run locally. Other important options for "distribute": - --no-clean: don't rebuild from scratch - --no-recover: don't test checkpoint/recovery; this step will fail without a queueing system (e.g. on a workstation) -erik -- Erik Schnetter <schnetter(a)cct.lsu.edu> http://www.perimeterinstitute.ca/personal/eschnetter/ My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://pgp.mit.edu/.

3 2

Re: [Users] coverage tests
by Roland Haas 05 Nov '13

05 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Steve, > Just saw this email today. See utils/GcovAnalysis.pl, and comments > at the top of the file. Very nice. Thank you. Yours, Roland - -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://keys.gnupg.net. - -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://keys.gnupg.net. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlJ5ZRsACgkQTiFSTN7SboUbVACgr0exLzk6pgnEC85NVNewjHQK aZgAoI2IL/1W6lgZHTB06G3WBwxW5Pu2 =cF7E -----END PGP SIGNATURE-----

1 0

Evolving grid arrays using MoL
by Ian Hinder 04 Nov '13

04 Nov '13

Hi, What is the current situation with evolving grid arrays with MoL? Over the past 7 years, this topic has come up repeatedly on the mailing lists, and some of the old information is probably out of date. Is there a way to do this without using any hacks, or are hacks still necessary? Is there an example somewhere of how to do this, or does someone have an example they would be willing to share? -- Ian Hinder http://numrel.aei.mpg.de/people/hinder

7 17

No Einstein Toolkit Meeting
by Frank Loeffler 04 Nov '13

04 Nov '13

Hi I am sorry about the late notice, but there won't be an Einstein Toolkit call today. Release issues should be communicated on the users mailing list. Most issues have been dealt with already last week, with only a few things remaining to be fixed. I would like to urge everyone not to commit any larger changes right now, but wait until after the release with those. The next Einstein Toolkit call will happen next Monday, at the usual time. Frank Loeffler

1 0

coverage tests
by Roland Haas 31 Oct '13

31 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Steve, all, do I remember correctly that you managed to run a coverage analysis of the ET code at the last developer's meeting and had a nice way of visualizing the results? Do you have instructions anywhere on how to run this analysis? This would be useful to verify that all parts of the code (that I currently care about and am thus likely to write tests for...) are actually tested? Yours, Roland - -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://keys.gnupg.net. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlJzCiMACgkQTiFSTN7SboWGwACdHm9IVbjF+Oniqs/F3xciIDqL HBkAoNVjEjtrL8tEfOmD14Geq82a/dxG =hSw9 -----END PGP SIGNATURE-----

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users November 2013