Present: Roland, Steve, Sam, Bill, Chris, Zach, Helvi, Antoni,
Future of svn.cactuscode.org [SB] - suggest to check access log - only thing hosted there that we know to be still in use is website source for cactuscode.org and CarpetHDF5 visit reader - repositories should / must be moved to some other hosting service before
ET release planning [RH] * release team - Steve - Roland - Helvi - Peter - Sam * release goals ** BNS gallery example - no update ** WVU_Analysis / WVU_Diagnostics status - Zach has been adding missing pieces to thorn - Add thorns to master thornlist of manifest repo - Tests are still missing, Zach is trying to obtain tiny ID dataset, most thorns could use more generic data though - Zach is looking for a place to put example parfiles ** Proca / Lean status - Lean has example parfiles that could go to Cactus/par - thorns are in thornlist - removed SIMD vectorization which caused issues with Intel 17 / 18 compilers on Stampede2. See https://bitbucket.org/einsteintoolkit/tickets/issues/2101/ ** release relevant tickets https://bitbucket.org/einsteintoolkit/tickets/issues?milestone=ET_2019_02&am... - sqrt() issue on AVX512 https://bitbucket.org/einsteintoolkit/tickets/issues/2219/fix-sqrt-for-avx51... should be fixed. The pull request contains more than just the bugfix. Bugfix commit is here: https://bitbucket.org/cactuscode/cactusutils/commits/5dea378d702207d771e6442...
Stale example parfiles * suggestion to at least run the example parfiles through cactus_sim -S to test that the parfile are at least parsable * could be made part of the jenkins tests
Workshop at RIT - no updates
unanswered question on mailing list / open tickets sorted by update time - no unanswered question on mailing list
Yours, Roland
On 21 Feb 2019, at 15:42, Haas, Roland <rhaas@illinois.edumailto:rhaas@illinois.edu> wrote:
Stale example parfiles * suggestion to at least run the example parfiles through cactus_sim -S to test that the parfile are at least parsable * could be made part of the jenkins tests
Hi,
I did a little bit of work on testing the example parameter files at one of the ET workshops. There are notes at
https://docs.einsteintoolkit.org/et-docs/Fixing_examples
See also https://bitbucket.org/einsteintoolkit/tickets/issues/641/parameter-files-and..., where this is discussed. Unfortunately, the web page with the results that this page points to no longer exists. I have looked briefly for the script I wrote to do this test, and sadly cannot find it.
Probably the suggestion to do this in Jenkins is a good one. Most of the parameter files don't need much memory or CPU time. We probably would need to blacklist those that do.
PS: there are broken links to trac tickets on the wiki. It would be good if trac.einsteintoolkit.orghttp://trac.einsteintoolkit.org redirected a link such as
https://trac.einsteintoolkit.org/ticket/641
to the relevant BitBucket ticket.
-- Ian Hinder Research Software Engineer University of Manchester, UK
Hello Ian, all,
I did a little bit of work on testing the example parameter files at one of the ET workshops. There are notes at
That is good start. Some of the new ones may take more memory than is available in Jenkins so we may have to resort to just running cactus_sim -S or cactus_sim -P on them (the latter requires memory for reflevel 0). Looking at your page, that will only catch a small fraction of the broken parfiles :-( .
PS: there are broken links to trac tickets on the wiki. It would be good if trac.einsteintoolkit.orghttp://trac.einsteintoolkit.org redirected a link such as
https://trac.einsteintoolkit.org/ticket/641
to the relevant BitBucket ticket.
That should be doable with an apache mod_rewrite rule https://httpd.apache.org/docs/2.4/rewrite/remapping.html#movehomedirs
Eg:
RedirectMatch "^/tickets/([^/]*)" "https://bitbucket.org/einsteintoolkit/tickets/issues/$1"
Yours, Roland
users@lists.einsteintoolkit.org
-
Haas, Roland -
Ian Hinder