From trac-noreply at einsteintoolkit.org Mon May 1 10:11:59 2023 From: trac-noreply at einsteintoolkit.org (Zach Etienne) Date: Mon, 01 May 2023 15:11:59 +0000 Subject: [ET Trac] #2581: Vectors test fails on AMD Ryzen 9 4900HS Message-ID: #2581: Vectors test fails on AMD Ryzen 9 4900HS Reporter: Zach Etienne Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Zach Etienne): I just recompiled with the latest version of the ET on that machine. It compiled without any issues, and was able to run a few parfiles that use `Vectors` . Marking the ticket as Resolved. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2581/vectors-test-fails-on-amd-ryzen-9-4900hs -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 1 10:12:22 2023 From: trac-noreply at einsteintoolkit.org (Zach Etienne) Date: Mon, 01 May 2023 15:12:22 +0000 Subject: [ET Trac] #2581: Vectors test fails on AMD Ryzen 9 4900HS Message-ID: #2581: Vectors test fails on AMD Ryzen 9 4900HS Reporter: Zach Etienne Status: resolved Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Zach Etienne): status: resolved (was new) Comment (by Zach Etienne): I can no longer reproduce the issue seen, with the latest ET. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2581/vectors-test-fails-on-amd-ryzen-9-4900hs -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 1 10:42:49 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 01 May 2023 15:42:49 +0000 Subject: [ET Trac] #2581: Vectors test fails on AMD Ryzen 9 4900HS Message-ID: #2581: Vectors test fails on AMD Ryzen 9 4900HS Reporter: Zach Etienne Status: resolved Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): @{557058:8bc23f2a-45c0-477d-8ac4-a5a16c734278} you say you can compile without issues. However looking at the issue description the problem was never a compile time problem but a runtime failure. Can you try and run the code? Just the testsuite for thorn Vectors should do. Something like: ``` make sim-testsuite PROMPT=no CCTK_TESTSUITE_RUN_TESTS=Vectors/vectors ``` should do. Or you can leave out the `PROMPT` and `CCTK_TESTSUITE_RUN_TESTS` options and use the interactive menu to select which tests to run. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2581/vectors-test-fails-on-amd-ryzen-9-4900hs -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 1 10:46:17 2023 From: trac-noreply at einsteintoolkit.org (Zach Etienne) Date: Mon, 01 May 2023 15:46:17 +0000 Subject: [ET Trac] #2581: Vectors test fails on AMD Ryzen 9 4900HS Message-ID: #2581: Vectors test fails on AMD Ryzen 9 4900HS Reporter: Zach Etienne Status: resolved Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Zach Etienne): Sorry forgot to report that I ran the Vectors tests from the testsuite as well. Again no failures. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2581/vectors-test-fails-on-amd-ryzen-9-4900hs -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 1 10:55:55 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 01 May 2023 15:55:55 +0000 Subject: [ET Trac] #2581: Vectors test fails on AMD Ryzen 9 4900HS Message-ID: #2581: Vectors test fails on AMD Ryzen 9 4900HS Reporter: Zach Etienne Status: resolved Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): RIght. Actually you did report that you could run parfiles ?and was able to run a few parfiles that use `Vectors` ? which would have been good enough \(the testsuite just runs the same self-tests for all possible architectures\) but I missed that part of the sentence, sorry. ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2581/vectors-test-fails-on-amd-ryzen-9-4900hs -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 1 12:01:56 2023 From: trac-noreply at einsteintoolkit.org (Steven R. Brandt) Date: Mon, 01 May 2023 17:01:56 +0000 Subject: [ET Trac] #2052: piraha assumes that assert(false) always aborts Message-ID: #2052: piraha assumes that assert(false) always aborts Reporter: Roland Haas Status: open Milestone: Version: development version Type: bug Priority: minor Component: Cactus Comment (by Steven R. Brandt): Add PR [https://bitbucket.org/cactuscode/cactus/pull-requests/154/fix-for-ticket-2052-replace-calls-to](https://bitbucket.org/cactuscode/cactus/pull-requests/154/fix-for-ticket-2052-replace-calls-to) which replaces calls to assert\(false\) with CCTK\_Error. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2052/piraha-assumes-that-assert-false-always -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 1 16:23:58 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Mon, 01 May 2023 21:23:58 +0000 Subject: [ET Trac] #2692: Inclusion of FUKA importer thorns Message-ID: #2692: Inclusion of FUKA importer thorns Reporter: tootle Status: new Milestone: ET_2023_05 Version: ET_2023_05 Type: proposal Priority: major Component: EinsteinToolkit thorn Comment (by Samuel Cupp): It?s fine if you make the branch, though we will be making branches for all the repos we have access to. If you don?t want it to be from master/main, it might be best if you handle it, but we can always do it as well. The branches aren?t scheduled to be made till 5-17, so there?s still a few weeks before we generate all the new release branches. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2692/inclusion-of-fuka-importer-thorns -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 1 18:17:05 2023 From: trac-noreply at einsteintoolkit.org (Vikram Manikantan) Date: Mon, 01 May 2023 23:17:05 +0000 Subject: [ET Trac] #2723: No boundary conditions registered for variables in group LEANBSSNMOL Message-ID: #2723: No boundary conditions registered for variables in group LEANBSSNMOL Reporter: Vikram Manikantan Status: submitted Milestone: ET_2023_05 Version: ET_2022_11 Type: bug Priority: major Component: EinsteinToolkit thorn I am running the latest version of ET, using the parameter file `Lean_inspiral_d06_mres.par` in the lean\_public par folder, I added this line: ``` Cactus::presync_mode?= "mixed-warn" ``` Now, I am getting these warnings \(one example of hundreds in the .out file\): ``` -> No boundary conditions registered for variables in group LEANBSSNMOL::GAMMAT. The unregistered variable(s) is(are) LEANBSSNMOL::gammatx, LEANBSSNMOL::gammaty, LEANBSSNMOL::gammatz. ``` This is related to [Issue #2651](https://bitbucket.org/einsteintoolkit/tickets/issues/2651/new-warning-message-for-missing-boundary). Is this a concern? Thanks! Vikram -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2723/no-boundary-conditions-registered-for -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 2 04:32:34 2023 From: trac-noreply at einsteintoolkit.org (tootle) Date: Tue, 02 May 2023 09:32:34 +0000 Subject: [ET Trac] #2692: Inclusion of FUKA importer thorns Message-ID: #2692: Inclusion of FUKA importer thorns Reporter: tootle Status: new Milestone: ET_2023_05 Version: ET_2023_05 Type: proposal Priority: major Component: EinsteinToolkit thorn Comment (by tootle): @{557058:088051f9-5b94-4b5e-bfbe-71137030b9c1} I took care of the branches and tags this morning for all three repos. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2692/inclusion-of-fuka-importer-thorns -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 2 11:21:08 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 02 May 2023 16:21:08 +0000 Subject: [ET Trac] #2052: piraha assumes that assert(false) always aborts Message-ID: #2052: piraha assumes that assert(false) always aborts Reporter: Roland Haas Status: open Milestone: Version: development version Type: bug Priority: minor Component: Cactus Comment (by Roland Haas): Please apply. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2052/piraha-assumes-that-assert-false-always -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 2 14:40:10 2023 From: trac-noreply at einsteintoolkit.org (Steven R. Brandt) Date: Tue, 02 May 2023 19:40:10 +0000 Subject: [ET Trac] #2592: TOV_ET tutorial Segfaults when running in Windows 10 WSL Message-ID: #2592: TOV_ET tutorial Segfaults when running in Windows 10 WSL Reporter: Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: SimFactory Comment (by Steven R. Brandt): I did not. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2592/tov_et-tutorial-segfaults-when-running-in -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 2 15:42:34 2023 From: trac-noreply at einsteintoolkit.org (Sam) Date: Tue, 02 May 2023 20:42:34 +0000 Subject: [ET Trac] #2592: TOV_ET tutorial Segfaults when running in Windows 10 WSL Message-ID: #2592: TOV_ET tutorial Segfaults when running in Windows 10 WSL Reporter: Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: SimFactory Comment (by Sam): Hi, i was the OP of this thread. At the time i managed to solve it by deactivating the anaconda environment before running, I do not really know the reason why that was the problem. Either way, I eventually switched to linux completely and i built ET without issues on the same device, so problem solved. Thank you for the help. Regards, Samuel -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2592/tov_et-tutorial-segfaults-when-running-in -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 2 16:29:52 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 02 May 2023 21:29:52 +0000 Subject: [ET Trac] #2592: TOV_ET tutorial Segfaults when running in Windows 10 WSL Message-ID: #2592: TOV_ET tutorial Segfaults when running in Windows 10 WSL Reporter: Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: SimFactory Comment (by Roland Haas): Ok. My best guess would be some interaction between anaconda and the system libraries. I will close as ?invalid? in that it could not be reproduced. Thank you for the update. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2592/tov_et-tutorial-segfaults-when-running-in -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 2 16:30:25 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 02 May 2023 21:30:25 +0000 Subject: [ET Trac] #2592: TOV_ET tutorial Segfaults when running in Windows 10 WSL Message-ID: #2592: TOV_ET tutorial Segfaults when running in Windows 10 WSL Reporter: Status: invalid Milestone: Version: ET_2021_11 Type: bug Priority: major Component: SimFactory Changes (by Roland Haas): status: invalid (was new) Comment (by Roland Haas): Could not be reproduced, might be due to Anaconda interaction with system libs. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2592/tov_et-tutorial-segfaults-when-running-in -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:24:48 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:24:48 +0000 Subject: [ET Trac] #2176: Test "Binary neutron star" example Message-ID: #2176: Test "Binary neutron star" example Reporter: Roland Haas Status: open Milestone: ET_2022_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): status: open (was resolved) Comment (by Roland Haas): I will test this for ET_2023_05. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2176/test-binary-neutron-star-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:25:14 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:25:14 +0000 Subject: [ET Trac] #2176: Test "Binary neutron star" example Message-ID: #2176: Test "Binary neutron star" example Reporter: Roland Haas Status: open Milestone: ET_2022_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Roland Haas): Applied as git hash [40309d5](https://bitbucket.org/einsteintoolkit/www/commits/40309d540440c52d36c75cddce5c08e0f1ab9271) "BNS: udpate date for 2023-05 release" of [www](https://bitbucket.org/einsteintoolkit/www) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2176/test-binary-neutron-star-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:25:42 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:25:42 +0000 Subject: [ET Trac] #2176: Test "Binary neutron star" example Message-ID: #2176: Test "Binary neutron star" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): milestone: ET_2023_05 (was ET_2022_11) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2176/test-binary-neutron-star-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:25:56 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:25:56 +0000 Subject: [ET Trac] #2176: Test "Binary neutron star" example Message-ID: #2176: Test "Binary neutron star" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): responsible: [] (was ) assignee: Roland Haas (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2176/test-binary-neutron-star-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:29:34 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:29:34 +0000 Subject: [ET Trac] #2172: Test "Binary black hole GW150914" example Message-ID: #2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: resolved Milestone: ET_2022_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): responsible: [] (was []) assignee: Steven R. Brandt (was Allen Wen) Comment (by Roland Haas): @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} will \(may\) handle this for ET\_2023\_05. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black-hole-gw150914-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:32:07 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:32:07 +0000 Subject: [ET Trac] #2175: Test "Single, stable neutron star" example Message-ID: #2175: Test "Single, stable neutron star" example Reporter: Roland Haas Status: resolved Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): responsible: [] (was []) milestone: ET_2023_05 (was ET_2022_11) assignee: Peter Diener (was Leung, Lisa Jing) Comment (by Roland Haas): @{557058:f7fd5133-6eee-4385-a5e5-3e03342a0b24} will handle this for ET\_2023\_05 -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2175/test-single-stable-neutron-star-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:32:45 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:32:45 +0000 Subject: [ET Trac] #2172: Test "Binary black hole GW150914" example Message-ID: #2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: resolved Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): milestone: ET_2023_05 (was ET_2022_11) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black-hole-gw150914-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:36:59 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:36:59 +0000 Subject: [ET Trac] #2174: Test "Multi Patch Scalar Wave Equation" example Message-ID: #2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: resolved Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): responsible: [] (was []) milestone: ET_2023_05 (was ET_2022_11) assignee: Bing-Jyun Tsao (was Kalyanaraman, Hrishikesh) Comment (by Roland Haas): @{62e2dce03aaeedcae75675a2} will handle this for ET\_2023\_05 -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-scalar-wave-equation -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:37:09 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:37:09 +0000 Subject: [ET Trac] #2174: Test "Multi Patch Scalar Wave Equation" example Message-ID: #2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): status: open (was resolved) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-scalar-wave-equation -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:37:17 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:37:17 +0000 Subject: [ET Trac] #2175: Test "Single, stable neutron star" example Message-ID: #2175: Test "Single, stable neutron star" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): status: open (was resolved) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2175/test-single-stable-neutron-star-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 12:37:44 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 03 May 2023 17:37:44 +0000 Subject: [ET Trac] #2172: Test "Binary black hole GW150914" example Message-ID: #2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): status: open (was resolved) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black-hole-gw150914-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 3 19:06:20 2023 From: trac-noreply at einsteintoolkit.org (Gabriele Bozzola) Date: Thu, 04 May 2023 00:06:20 +0000 Subject: [ET Trac] #2724: Update download page Message-ID: #2724: Update download page Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: enhancement Priority: minor Component: EinsteinToolkit website The [download](http://einsteintoolkit.org/download.html) page: * reports a warning regarding a 11 years old version of OpenSSL, * is not very specific in the requirements, * could make a use of a link to the more specific packages needed as in the [tutorial notebook](https://github.com/nds-org/jupyter-et/blob/master/tutorial-server/notebooks/CactusTutorial.ipynb) In particular, I noticed that the instruction to install kuibit would not work out of the box for some distributions \(e.g., Debian 12, Ubuntu 23.04, macOS\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2724/update-download-page -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 4 12:11:29 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 04 May 2023 17:11:29 +0000 Subject: [ET Trac] #2722: GetComponents places KadathThorn inside repos/KadathThorn instead of Cactus/repos/KadathThorn Message-ID: #2722: GetComponents places KadathThorn inside repos/KadathThorn instead of Cactus/repos/KadathThorn Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: major Component: GetComponents Comment (by Roland Haas): Tested on OSX and Linux and seems to work ok there. This should cover all relevant OS \(only other that would come to mind might be Windows with mingw but that is not really workable anyway due to failing to compile the code for other reasons\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2722/getcomponents-places-kadaththorn-inside -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 8 10:33:10 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 08 May 2023 15:33:10 +0000 Subject: [ET Trac] #2722: GetComponents places KadathThorn inside repos/KadathThorn instead of Cactus/repos/KadathThorn Message-ID: #2722: GetComponents places KadathThorn inside repos/KadathThorn instead of Cactus/repos/KadathThorn Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: major Component: GetComponents Comment (by Roland Haas): If someone could review this, please? This is urgent and would block the release. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2722/getcomponents-places-kadaththorn-inside -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 8 10:34:02 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 08 May 2023 15:34:02 +0000 Subject: [ET Trac] #2722: GetComponents places KadathThorn inside repos/KadathThorn instead of Cactus/repos/KadathThorn Message-ID: #2722: GetComponents places KadathThorn inside repos/KadathThorn instead of Cactus/repos/KadathThorn Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: major Component: GetComponents Comment (by Roland Haas): @{557058:088051f9-5b94-4b5e-bfbe-71137030b9c1} @{5bae587b96242d2e2b6110a4} @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} could you take a look, please? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2722/getcomponents-places-kadaththorn-inside -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 8 11:55:55 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 08 May 2023 16:55:55 +0000 Subject: [ET Trac] #2721: Cactus does not detect `gettimeofday` timer Message-ID: #2721: Cactus does not detect `gettimeofday` timer Reporter: Erik Schnetter Status: open Milestone: Version: Type: bug Priority: major Component: Comment (by Roland Haas): Applied as git hash [8a5bfc47](https://bitbucket.org/cactuscode/cactus/commits/8a5bfc479e04548f4ef9fdc5cce05cfc348631bb) "Cactus: Regenerate configure" of [cactus](https://bitbucket.org/cactuscode/cactus) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2721/cactus-does-not-detect-gettimeofday-timer -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 8 11:57:12 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 08 May 2023 16:57:12 +0000 Subject: [ET Trac] #2721: Cactus does not detect `gettimeofday` timer Message-ID: #2721: Cactus does not detect `gettimeofday` timer Reporter: Erik Schnetter Status: resolved Milestone: Version: Type: bug Priority: major Component: Changes (by Roland Haas): status: resolved (was open) Comment (by Roland Haas): Thank you for the patch. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2721/cactus-does-not-detect-gettimeofday-timer -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 8 15:42:57 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 08 May 2023 20:42:57 +0000 Subject: [ET Trac] #2722: GetComponents places KadathThorn inside repos/KadathThorn instead of Cactus/repos/KadathThorn Message-ID: #2722: GetComponents places KadathThorn inside repos/KadathThorn instead of Cactus/repos/KadathThorn Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: major Component: GetComponents Comment (by Roland Haas): @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} says ?Please apply? in pull request. Applied as git hash [b870f78](https://github.com/gridaphobe/CRL/commits/b870f784bec5933473e0db651079820835ea2365) "GetComponents: construct relative paths based on physical location" of [CRL](https://github.com/gridaphobe/CRL) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2722/getcomponents-places-kadaththorn-inside -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 8 15:43:11 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 08 May 2023 20:43:11 +0000 Subject: [ET Trac] #2722: GetComponents places KadathThorn inside repos/KadathThorn instead of Cactus/repos/KadathThorn Message-ID: #2722: GetComponents places KadathThorn inside repos/KadathThorn instead of Cactus/repos/KadathThorn Reporter: Zach Etienne Status: resolved Milestone: Version: Type: bug Priority: major Component: GetComponents Changes (by Roland Haas): status: resolved (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2722/getcomponents-places-kadaththorn-inside -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 8 20:40:30 2023 From: trac-noreply at einsteintoolkit.org (Leonardo Werneck) Date: Tue, 09 May 2023 01:40:30 +0000 Subject: [ET Trac] #2174: Test "Multi Patch Scalar Wave Equation" example Message-ID: #2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Leonardo Werneck): I don?t know how to change the assignee. @{62e2dce03aaeedcae75675a2} does Jake have a Bitbucket account? I couldn?t find him based on his email address. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-scalar-wave-equation -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 8 20:42:43 2023 From: trac-noreply at einsteintoolkit.org (Leonardo Werneck) Date: Tue, 09 May 2023 01:42:43 +0000 Subject: [ET Trac] #2173: Test "Poisson equation" example Message-ID: #2173: Test "Poisson equation" example Reporter: Roland Haas Status: resolved Milestone: ET_2022_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Leonardo Werneck): @{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} could you please change this milestone to ET\_2023\_05 and assign it to @{62e2dce03aaeedcae75675a2} ? I don?t know how to change the assignee. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equation-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 10:09:55 2023 From: trac-noreply at einsteintoolkit.org (Matthew Cerep) Date: Tue, 09 May 2023 15:09:55 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: submitted Milestone: Version: Type: bug Priority: trivial Component: SimFactory Whenever I submit a job, the walltime gets set to 24 hours. Even if I hardcode a max\_walltime for TerminationTrigger as some value, when I look at the parfile it outputs in the simulation directory the value gets overwritten to 24. I went into the submitScript file and hardcoded the walltime there to my desired walltime as well, but that doesn?t help. The parfile and log.txt file \(attached is the log file\) says the walltime is 24 hours, but running qstat -u says it?s the desired walltime. I believe the issue is with SimFactory, but I?m not sure what?s going on or how to fix it. attachment: log.txt (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2725/attachments/log.txt) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 10:39:49 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 15:39:49 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: submitted Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Roland Haas): Not sure if this is a bug or just unexpected behaviour. Most clusters have a maximum allowed walltime \(often 24 or 48 hours\). Simfactory is aware of the limit \(via the maxwalltime setting in the machine.ini file\) and will automatically split up longer jobs into chained segments of at most maxwalltime length. You seem to be on the thornyflat cluster where maxwalltime is 168 hours \(see [https://bitbucket.org/simfactory/simfactory2/src/master/mdb/machines/thornyflat.ini#lines-57](https://bitbucket.org/simfactory/simfactory2/src/master/mdb/machines/thornyflat.ini#lines-57)\), so that should actually not limit the walltime to 24 hours Second, simfactory contains hard-coded, historic, unfortunate, code that will reset the right hand side of the \`TerminationTrigger::max\_walltime\` parameter to the walltime that simfactory was given in its submit command \(or the default value for walltime, which I do not recall on top of my head\). As far as I know this cannot be turned off \(though I may well be wrong\). Could you provide the exact simfactory command that you entered, please? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 10:57:36 2023 From: trac-noreply at einsteintoolkit.org (Matthew Cerep) Date: Tue, 09 May 2023 15:57:36 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: submitted Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Matthew Cerep): Yes, I?m on thornyflat in a queue that should allow for a maximum walltime of 168 hours, which is why I?m confused that it's being set to 24 hours. Here?s the command I entered. ? ./simfactory/bin/sim create-submit insp08\_final\_small\_2 --parfile par/charged\_binary\_inspiral\_final.rpar --walltime 168:00:00 --queue comm\_small\_week --cores 80 --ppn 40 --num-threads 1 --machine thornyflat ? The rparfile just uses the python package jhuki to generate the parfile, I tested it with the a regular parfile as well and the issue persists. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 11:05:12 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 16:05:12 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: submitted Milestone: Version: Type: bug Priority: trivial Component: SimFactory Changes (by Roland Haas): responsible: [] (was ) assignee: Roland Haas (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 11:16:21 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 16:16:21 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: submitted Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Roland Haas): Hmm. I am very puzzled. In your log file \(thank you for including it\) you have the lines: ```text [LOG:2023-05-07 21:19:25] self.submit(submitScript)::No previous walltime available to be used, using walltime 168:00:00 [LOG:2023-05-07 21:19:25] self.submit(submitScript)::Defined substituion properties for submission [LOG:2023-05-07 21:19:25] self.submit(submitScript)::{'SOURCEDIR': '/users/mtc00017/scratch/EToolKitNew/Cactus', 'SIMULATION_NAME': 'insp08_final_small_2', 'SHORT_SIMULATION_NAME': 'insp08_final_sm', 'SIMULATION_ID': 'simulation-insp08_final_small_2-thornyflat-tf.hpc.wvu.edu-mtc00017-2023.05.07-21.19.25-2587', 'RESTART_ID': 0, 'RUNDIR': '/users/mtc00017/scratch/simulations/insp08_final_small_2/output-0000', 'SCRIPTFILE': '/users/mtc00017/scratch/simulations/insp08_final_small_2/output-0000/SIMFACTORY/SubmitScript', 'EXECUTABLE': '/users/mtc00017/scratch/simulations/insp08_final_small_2/SIMFACTORY/exe/cactus_sim', 'PARFILE': '/users/mtc00017/scratch/simulations/insp08_final_small_2/output-0000/charged_binary_inspiral_final.rpar', 'HOSTNAME': 'tf.hpc.wvu.edu', 'USER': 'mtc00017', 'NODES': 2, 'PROCS_REQUESTED': 80, 'PPN': 40, 'NUM_PROCS': 80, 'NODE_PROCS': 40, 'PROCS': 80, 'NUM_THREADS': 1, 'PPN_USED': 40, 'NUM_SMT': 1, 'MEMORY': '98304', 'CPUFREQ': '2.10', 'ALLOCATION': 'NOALLOCATION', 'QUEUE': 'comm_small_week', 'EMAIL': 'mtc00017', 'WALLTIME': '24:00:00', 'WALLTIME_HH': '24', 'WALLTIME_MM': '00', 'WALLTIME_SS': '00', 'WALLTIME_SECONDS': 86400, 'WALLTIME_MINUTES': 1440.0, 'WALLTIME_HOURS': 24.0, 'SIMFACTORY': '/gpfs20/scratch/mtc00017/EToolKitNew/Cactus/repos/simfactory2/bin/sim', 'SUBMITSCRIPT': '/users/mtc00017/scratch/simulations/insp08_final_small_2/output-0000/SIMFACTORY/SubmitScript', 'CONFIGURATION': 'sim', 'FROM_RESTART_COMMAND': '', 'CHAINED_JOB_ID': ''} ``` So the walltime was 168 hours at one point \(the ?`No previous walltime available?` really just means that this is `output-0000`\) but then switched to 24hrs just afterwards. Looking at the Python code in `lib/simrestart.py` I cannot see how it could change to 24hrs. ```python # import walltime if no --walltime is specified. if existingProperties is not None and not simenv.OptionsManager.HasOption('walltime') and existingProperties.HasProperty('walltime'): Walltime = restartlib.WallTime(existingProperties.GetProperty("walltime")) self.SimulationLog.Write("Using walltime %s from previous restart %s" % (existingProperties.GetProperty("walltime"), self.MaxRestartID)) else: self.SimulationLog.Write("No previous walltime available to be used, using walltime %s" % Walltime.Walltime) [..stuff that does not touch Walltime...] walltt = Walltime # always restrict our walltime to maxwalltime if requested walltime # is too large. if MaxWalltime.walltime_seconds < Walltime.walltime_seconds: walltt = MaxWalltime # okay, our walltime requested was too large # find out if we should use automatic job chaining. if chainedJobId is None: UseChaining = True # TODO: i don't understand the job chaining logic. a # restart should be presubmitted (instead of # submitted) if there is a restart currently running. # yet there is no check for this. new_properties['WALLTIME'] = walltt.Walltime ``` Worse, if I try to mimic thornyflat \(I have no account\) on my workstation using ``` [thornyflat] submit = cat @SCRIPTFILE@ >/dev/tty basedir = /data/rhaas/simulations sourcebasedir = /data/@USER@ envsetup = true ``` and running: ```shell ./simfactory/bin/sim create-submit --machine thornyflat --parfile par/tov_ET.par --cores 1 foobar ``` I do not see any such change in walltime myself. Could you run, on thornyflat, this command, please: ``` ./simfactory/bin/sim print-mdb-entry thornyflat | grep maxwalltime ``` which should output what simfactory thinks the maximum allowed walltime is \(this is not output to the log, the 168 that you see comes from your command line option for walltime\). You could also add some `print("maxwalltime is ", MaxWalltime,Walltime)` debug statements to `lib/simrestart.py`'s `submit` function to print out the value. Though as said, I am not sure what is going on. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 12:12:30 2023 From: trac-noreply at einsteintoolkit.org (Matthew Cerep) Date: Tue, 09 May 2023 17:12:30 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: submitted Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Matthew Cerep): I just ran that command, and it output `maxwalltime ? ? = 24:00:00` , so simfactory does think the max walltime is 24 hours. I?ll take a look at `lib/simrestart.py` and see if I find anything odd. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 12:20:20 2023 From: trac-noreply at einsteintoolkit.org (Matthew Cerep) Date: Tue, 09 May 2023 17:20:20 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: submitted Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Matthew Cerep):
-- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 12:21:32 2023 From: trac-noreply at einsteintoolkit.org (Matthew Cerep) Date: Tue, 09 May 2023 17:21:32 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: submitted Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Matthew Cerep): I just attached the log file for a job that?s currently running and at 24:43. What?s weird is that the log file seems to suggest simfactory still thinks the walltime is 24. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 12:25:43 2023 From: trac-noreply at einsteintoolkit.org (Matthew Cerep) Date: Tue, 09 May 2023 17:25:43 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: submitted Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Matthew Cerep): Sorry, I forgot to note that the only difference in this job?s parfile is that I commented out the lines having to do with TerminationTrigger. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 12:32:44 2023 From: trac-noreply at einsteintoolkit.org (Matthew Cerep) Date: Tue, 09 May 2023 17:32:44 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: submitted Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Matthew Cerep): That?s actually the wrong job \(sorry, I ran a lot of test jobs yesterday!\), but the correct log file still says it thinks that walltime is 24 hours. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 12:41:24 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 17:41:24 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: open Milestone: Version: Type: bug Priority: trivial Component: SimFactory Changes (by Roland Haas): status: open (was submitted) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 12:43:54 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 17:43:54 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: open Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Roland Haas): Before digging into the Python code, maybe it would be good to check both your `simfactory/etc/defs.local.ini` and `simfactory/mdb/machines/thornyflat.ini` to check if any of those sets a rogue `maxwalltime` for `thornyflat`. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 12:54:39 2023 From: trac-noreply at einsteintoolkit.org (Steven R. Brandt) Date: Tue, 09 May 2023 17:54:39 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: open Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Steven R. Brandt): Maybe this shouldn?t happen silently. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 12:58:28 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 17:58:28 +0000 Subject: [ET Trac] #420: newest revision of simfactory 2.0 submit three instead of one job Message-ID: #420: newest revision of simfactory 2.0 submit three instead of one job Reporter: anonymous Status: closed Milestone: Version: ET_2010_11 Type: bug Priority: minor Component: SimFactory Changes (by Roland Haas): responsible: (was []) assignee: (was anonymous) I am submitting a simulation using simfactory with the command: \[snip\] simfactory/bin/sim submit test-whisky-openmp --configuration test-whisky-openmp --parfile=whisky-openmp-test-ali.par --verbose --walltime=48:00:00 --procs=16 --ppn=4 --num-threads=4 --machine=damiana --queue=intel.q \[snip\] sim then comes with the messages: ```text [snip] Info: Simfactory command: simfactory/bin/../lib/sim.py "submit" "test-whisky-openmp" "--configuration" "test-whisky-openmp" "--parfile=whisky-openmp-test-ali.par" "--verbose" "--walltime=48:00:00" "--procs=16" "--ppn=4" "--num-threads=4" "--machine=damiana" "--queue=intel.q" Info: Version 1331M The Simulation Factory: Manage Cactus simulations Info: defs: /home/alibeck/programme/Cactus-Luca/Cactus/simfactory/etc/defs.ini Info: defs.local: /home/alibeck/programme/Cactus-Luca/Cactus/simfactory/etc/defs.local.ini Info: Cactus Directory: /home/alibeck/programme/Cactus-Luca/Cactus Info: simenv.COMMAND: submit Info: Executing command: submit Info: Assigned restart_id of: 0002 Info: Found the following restart_ids: [0, 1] Info: Maximum restart id determined to be: 0001 Assigned restart id: 2 Info: Simulation is inactive: submitting Info: Job allocation information: Info: System: nodes=170 cores/node=4 threads/process=4 Info: Requested: nodes=4 cores=16 cores/node=4 Info: Run: processes=4 threads=16 threads/process=4 Info: Distribution: processes/node=1 threads/node=4 Info: Ratio: threads/core=1.000 cores/thread=1.000 Info: writing to internalDir: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0002/SIMFACTORY Info: saving substituted submitscript contents to: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0002/SIMFACTORY/SubmitScript Executing submit command: qsub /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0002/SIMFACTORY/SubmitScript Submit finished, job id is 259460 Info: Restart 2 is active Info: Assigned restart_id of: 0003 Info: Found the following restart_ids: [0, 1, 2, 2] Info: Maximum restart id determined to be: 0002 Assigned restart id: 3 Info: Simulation is active: presubmitting Info: Job allocation information: Info: System: nodes=170 cores/node=4 threads/process=4 Info: Requested: nodes=4 cores=16 cores/node=4 Info: Run: processes=4 threads=16 threads/process=4 Info: Distribution: processes/node=1 threads/node=4 Info: Ratio: threads/core=1.000 cores/thread=1.000 Info: writing to internalDir: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0003/SIMFACTORY Info: saving substituted submitscript contents to: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0003/SIMFACTORY/SubmitScript Executing submit command: qsub /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0003/SIMFACTORY/SubmitScript Submit finished, job id is 259461 Info: Restart 2 is active Info: Assigned restart_id of: 0004 Info: Found the following restart_ids: [0, 1, 2, 2, 3] Info: Maximum restart id determined to be: 0003 Assigned restart id: 4 Info: Simulation is active: presubmitting Info: Job allocation information: Info: System: nodes=170 cores/node=4 threads/process=4 Info: Requested: nodes=4 cores=16 cores/node=4 Info: Run: processes=4 threads=16 threads/process=4 Info: Distribution: processes/node=1 threads/node=4 Info: Ratio: threads/core=1.000 cores/thread=1.000 Info: writing to internalDir: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0004/SIMFACTORY Info: saving substituted submitscript contents to: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0004/SIMFACTORY/SubmitScript Executing submit command: qsub /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0004/SIMFACTORY/SubmitScript Submit finished, job id is 259462 [snip] ``` As a result three jobs are queued. ```text [snip] qstat job-ID prior name user state submit/start at queue slots ja-task-ID 259460 0.00000 test-whisk alibeck qw 04/29/2011 10:26:55 16 259461 0.00000 test-whisk alibeck hqw 04/29/2011 10:26:56 16 259462 0.00000 test-whisk alibeck hqw 04/29/2011 10:26:56 16 [snip] ``` What is going wrong here? **Keyword:** -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/420/newest-revision-of-simfactory-20-submit -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 12:59:10 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 17:59:10 +0000 Subject: [ET Trac] #420: newest revision of simfactory 2.0 submit three instead of one job Message-ID: #420: newest revision of simfactory 2.0 submit three instead of one job Reporter: anonymous Status: closed Milestone: Version: ET_2010_11 Type: bug Priority: minor Component: SimFactory Changes (by Roland Haas): I am submitting a simulation using simfactory with the command: ``` [snip] simfactory/bin/sim submit test-whisky-openmp --configuration test-whisky-openmp --parfile=whisky-openmp-test-ali.par --verbose --walltime=48:00:00 --procs=16 --ppn=4 --num-threads=4 --machine=damiana --queue=intel.q [snip] ``` sim then comes with the messages: ```text [snip] Info: Simfactory command: simfactory/bin/../lib/sim.py "submit" "test-whisky-openmp" "--configuration" "test-whisky-openmp" "--parfile=whisky-openmp-test-ali.par" "--verbose" "--walltime=48:00:00" "--procs=16" "--ppn=4" "--num-threads=4" "--machine=damiana" "--queue=intel.q" Info: Version 1331M The Simulation Factory: Manage Cactus simulations Info: defs: /home/alibeck/programme/Cactus-Luca/Cactus/simfactory/etc/defs.ini Info: defs.local: /home/alibeck/programme/Cactus-Luca/Cactus/simfactory/etc/defs.local.ini Info: Cactus Directory: /home/alibeck/programme/Cactus-Luca/Cactus Info: simenv.COMMAND: submit Info: Executing command: submit Info: Assigned restart_id of: 0002 Info: Found the following restart_ids: [0, 1] Info: Maximum restart id determined to be: 0001 Assigned restart id: 2 Info: Simulation is inactive: submitting Info: Job allocation information: Info: System: nodes=170 cores/node=4 threads/process=4 Info: Requested: nodes=4 cores=16 cores/node=4 Info: Run: processes=4 threads=16 threads/process=4 Info: Distribution: processes/node=1 threads/node=4 Info: Ratio: threads/core=1.000 cores/thread=1.000 Info: writing to internalDir: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0002/SIMFACTORY Info: saving substituted submitscript contents to: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0002/SIMFACTORY/SubmitScript Executing submit command: qsub /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0002/SIMFACTORY/SubmitScript Submit finished, job id is 259460 Info: Restart 2 is active Info: Assigned restart_id of: 0003 Info: Found the following restart_ids: [0, 1, 2, 2] Info: Maximum restart id determined to be: 0002 Assigned restart id: 3 Info: Simulation is active: presubmitting Info: Job allocation information: Info: System: nodes=170 cores/node=4 threads/process=4 Info: Requested: nodes=4 cores=16 cores/node=4 Info: Run: processes=4 threads=16 threads/process=4 Info: Distribution: processes/node=1 threads/node=4 Info: Ratio: threads/core=1.000 cores/thread=1.000 Info: writing to internalDir: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0003/SIMFACTORY Info: saving substituted submitscript contents to: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0003/SIMFACTORY/SubmitScript Executing submit command: qsub /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0003/SIMFACTORY/SubmitScript Submit finished, job id is 259461 Info: Restart 2 is active Info: Assigned restart_id of: 0004 Info: Found the following restart_ids: [0, 1, 2, 2, 3] Info: Maximum restart id determined to be: 0003 Assigned restart id: 4 Info: Simulation is active: presubmitting Info: Job allocation information: Info: System: nodes=170 cores/node=4 threads/process=4 Info: Requested: nodes=4 cores=16 cores/node=4 Info: Run: processes=4 threads=16 threads/process=4 Info: Distribution: processes/node=1 threads/node=4 Info: Ratio: threads/core=1.000 cores/thread=1.000 Info: writing to internalDir: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0004/SIMFACTORY Info: saving substituted submitscript contents to: /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0004/SIMFACTORY/SubmitScript Executing submit command: qsub /lustre/AEI/alibeck/simulations/test-whisky-openmp/output-0004/SIMFACTORY/SubmitScript Submit finished, job id is 259462 [snip] ``` As a result three jobs are queued. ```text [snip] qstat job-ID prior name user state submit/start at queue slots ja-task-ID 259460 0.00000 test-whisk alibeck qw 04/29/2011 10:26:55 16 259461 0.00000 test-whisk alibeck hqw 04/29/2011 10:26:56 16 259462 0.00000 test-whisk alibeck hqw 04/29/2011 10:26:56 16 [snip] ``` What is going wrong here? **Keyword:** -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/420/newest-revision-of-simfactory-20-submit -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 13:10:01 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 18:10:01 +0000 Subject: [ET Trac] #2723: No boundary conditions registered for variables in group LEANBSSNMOL Message-ID: #2723: No boundary conditions registered for variables in group LEANBSSNMOL Reporter: Vikram Manikantan Status: new Milestone: ET_2023_05 Version: ET_2022_11 Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: new (was submitted) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2723/no-boundary-conditions-registered-for -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 13:12:22 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 18:12:22 +0000 Subject: [ET Trac] #2723: No boundary conditions registered for variables in group LEANBSSNMOL Message-ID: #2723: No boundary conditions registered for variables in group LEANBSSNMOL Reporter: Vikram Manikantan Status: new Milestone: ET_2023_05 Version: ET_2022_11 Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): responsible: [] (was ) assignee: helvi witek (was ) Comment (by Roland Haas): @{557058:a2800088-fc6e-4fbe-9a1e-663271f736bd} @{557058:65c5f18c-c3ad-4126-bb2b-be0e766b31ef} could you take a look, please? You are listed as LeanBSSNMoL maintainers \(according to the README file\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2723/no-boundary-conditions-registered-for -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 13:17:49 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 18:17:49 +0000 Subject: [ET Trac] #2726: no documentation for Lean codes Message-ID: #2726: no documentation for Lean codes Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit thorn Neither LeanBSSNMoL nor NPScalars have a documentation file. The arrangement they are in \(Lean\) also has none. A documentation file should \(must\) be present for all thorns in the ET. It also serves to advertise the thorns presence via the documentation web-page: [http://einsteintoolkit.org/documentation/ThornGuide.php](http://einsteintoolkit.org/documentation/ThornGuide.php) which will not list it if it has no documentation. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2726/no-documentation-for-lean-codes -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 13:19:19 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 18:19:19 +0000 Subject: [ET Trac] #2726: no documentation for Lean codes Message-ID: #2726: no documentation for Lean codes Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): @{557058:a2800088-fc6e-4fbe-9a1e-663271f736bd} @{557058:65c5f18c-c3ad-4126-bb2b-be0e766b31ef} you are both listed as Lean maintainers in the README file, and I have assigned the ticket to the first one listed. If you would like to change that assignment you should be able to do so via the ?Edit? button of the ticket. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2726/no-documentation-for-lean-codes -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 13:51:39 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Tue, 09 May 2023 18:51:39 +0000 Subject: [ET Trac] #2173: Test "Poisson equation" example Message-ID: #2173: Test "Poisson equation" example Reporter: Roland Haas Status: resolved Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Samuel Cupp): responsible: [] (was []) milestone: ET_2023_05 (was ET_2022_11) assignee: Bing-Jyun Tsao (was Nadine Kuo) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equation-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 13:52:05 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Tue, 09 May 2023 18:52:05 +0000 Subject: [ET Trac] #2173: Test "Poisson equation" example Message-ID: #2173: Test "Poisson equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Samuel Cupp): status: open (was resolved) Comment (by Samuel Cupp): Rerun test for ET_2023_05 release -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equation-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 14:15:44 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 19:15:44 +0000 Subject: [ET Trac] #2726: no documentation for Lean codes Message-ID: #2726: no documentation for Lean codes Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit thorn Changes (by Roland Haas): Neither LeanBSSNMoL nor NPScalars have a documentation file. The arrangement they are in \(Lean\) also has none. A documentation file should \(must\) be present for all thorns in the ET. It also serves to advertise the thorns presense via the documentation web-page: [http://einsteintoolkit.org/documentation/ThornGuide.php](http://einsteintoolkit.org/documentation/ThornGuide.php) which will not list it if it has no documentation. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2726/no-documentation-for-lean-codes -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 14:24:38 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 19:24:38 +0000 Subject: [ET Trac] #2174: Test "Multi Patch Scalar Wave Equation" example Message-ID: #2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): responsible: (was []) assignee: (was Bing-Jyun Tsao) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-scalar-wave-equation -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 16:01:56 2023 From: trac-noreply at einsteintoolkit.org (Matthew Cerep) Date: Tue, 09 May 2023 21:01:56 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: open Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Matthew Cerep): I found it! `simfactory/mdb/machines/thornyflat.ini` set `maxwalltime = 24:00:00` for some reason. Changing that fixed it! Thank you! -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 16:08:59 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 21:08:59 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: open Milestone: Version: Type: bug Priority: trivial Component: SimFactory Comment (by Roland Haas): Glad to have been able to help. I will close this ticket and create a new one for Steve?s suggestion. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 16:09:25 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 21:09:25 +0000 Subject: [ET Trac] #2725: Walltime being overwritten to 24 hours Message-ID: #2725: Walltime being overwritten to 24 hours Reporter: Matthew Cerep Status: wontfix Milestone: Version: Type: bug Priority: trivial Component: SimFactory Changes (by Roland Haas): status: wontfix (was open) Comment (by Roland Haas): No bug in simfactory, somehow ini files got changed on the system. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2725/walltime-being-overwritten-to-24-hours -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 9 16:11:49 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 09 May 2023 21:11:49 +0000 Subject: [ET Trac] #2727: be more verbose when auto-splitting jobs Message-ID: #2727: be more verbose when auto-splitting jobs Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: minor Component: SimFactory When requesting a walltime large than `maxwalltime` simfactory will automatically split up the requested walltime into `maxwalltime` \(or smaller\) chunks and submit a set of chained runs. Right now, this does not seem to produce any diagnostic output to screen. In #2725 @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} suggests that it should be more verbose when this happens. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2727/be-more-verbose-when-auto-splitting-jobs -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 10 04:19:10 2023 From: trac-noreply at einsteintoolkit.org (Miguel Zilhão) Date: Wed, 10 May 2023 09:19:10 +0000 Subject: [ET Trac] #2726: no documentation for Lean codes Message-ID: #2726: no documentation for Lean codes Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit thorn Changes (by Miguel Zilh?o): responsible: [] (was []) assignee: Miguel Zilh?o (was helvi witek) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2726/no-documentation-for-lean-codes -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 10 04:20:37 2023 From: trac-noreply at einsteintoolkit.org (Miguel Zilhão) Date: Wed, 10 May 2023 09:20:37 +0000 Subject: [ET Trac] #2726: no documentation for Lean codes Message-ID: #2726: no documentation for Lean codes Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Miguel Zilh?o): I?ve assigned this one to me since I?m also assigned to the documentation ticket in the scalar thorn. I?ll try to take care of both issues during this month. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2726/no-documentation-for-lean-codes -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 10 04:34:48 2023 From: trac-noreply at einsteintoolkit.org (Miguel Zilhão) Date: Wed, 10 May 2023 09:34:48 +0000 Subject: [ET Trac] #2723: No boundary conditions registered for variables in group LEANBSSNMOL Message-ID: #2723: No boundary conditions registered for variables in group LEANBSSNMOL Reporter: Vikram Manikantan Status: new Milestone: ET_2023_05 Version: ET_2022_11 Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Miguel Zilh?o): Can you check if this issue is also present in the current development branch of `LeanBSSNMoL`? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2723/no-boundary-conditions-registered-for -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 10 17:49:12 2023 From: trac-noreply at einsteintoolkit.org (Bing-Jyun Tsao) Date: Wed, 10 May 2023 22:49:12 +0000 Subject: [ET Trac] #2173: Test "Poisson equation" example Message-ID: #2173: Test "Poisson equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Bing-Jyun Tsao): 2023\_05 test Ran with 1 thread and 1 node for 72 minutes, or 8 threads and 1 node for 10 minutes. Machine uses Intel\(R\) Xeon\(R\) Gold 6226R CPU @ 2.90GH. RAM is 64GB. Both error plot and 3D psi plot are consistent with previous tests. Visualized with Visit3.2.1, change source path from `psi2.session` and saved as `psi4.session`: ``` "ct_analytic-ct_testc0.file_* database" "ct_multilevel-psi.file_* database" ``` Note for future testers using just 1 thread: h5 files will only be saved in `ct_analytic-ct_testc0.h5` and `ct_multilevel-psi.h5` so the path above will need to be changed accordingly. ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equation-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 10 21:19:22 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Thu, 11 May 2023 02:19:22 +0000 Subject: [ET Trac] #2173: Test "Poisson equation" example Message-ID: #2173: Test "Poisson equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Samuel Cupp): Thanks! @{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} Do we need to do anything with the data? Or just change the ?last tested? line on the website? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equation-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 11 08:37:15 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 11 May 2023 13:37:15 +0000 Subject: [ET Trac] #2173: Test "Poisson equation" example Message-ID: #2173: Test "Poisson equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Roland Haas): What to do is likely spelled out \(somewhere\) in this long ticket. To simplify matters I wrote, couple of days ago, a wiki entry with the steps: [https://docs.einsteintoolkit.org/et-docs/Release\_Process#add\_gallery\_runners](https://docs.einsteintoolkit.org/et-docs/Release_Process#add_gallery_runners) ? which may help. In principle all can \(and should\) be done by the runners themselves. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equation-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 11 08:51:42 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 11 May 2023 13:51:42 +0000 Subject: [ET Trac] #2174: Test "Multi Patch Scalar Wave Equation" example Message-ID: #2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): responsible: [] (was ) assignee: jakedoherty (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-scalar-wave-equation -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 11 08:52:32 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 11 May 2023 13:52:32 +0000 Subject: [ET Trac] #2174: Test "Multi Patch Scalar Wave Equation" example Message-ID: #2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Roland Haas): I wrote up some notes explaining the steps required including how to upload files: [https://docs.einsteintoolkit.org/et-docs/Release\_Process#add\_gallery\_runners](https://docs.einsteintoolkit.org/et-docs/Release_Process#add_gallery_runners) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-scalar-wave-equation -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 11 09:00:02 2023 From: trac-noreply at einsteintoolkit.org (Leonardo Rosa Werneck) Date: Thu, 11 May 2023 14:00:02 +0000 Subject: [ET Trac] #2497: IllinoisGRMHD is incompatible with setting TmunuBase::stress_energy_at_RHS = "no" Message-ID: #2497: IllinoisGRMHD is incompatible with setting TmunuBase::stress_energy_at_RHS = "no" Reporter: Gabriele Bozzola Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Leonardo Rosa Werneck): I will fix this for the upcoming release. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2497/illinoisgrmhd-is-incompatible-with-setting -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 11 13:02:57 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 11 May 2023 18:02:57 +0000 Subject: [ET Trac] #2728: not all configuration options are documented Message-ID: #2728: not all configuration options are documented Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus No all configuration options seem to be documented. Right now `git grep 'CXX.*OPENMP'` finds noting in the TeX files. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2728/not-all-configuration-options-are -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 11 13:13:09 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 11 May 2023 18:13:09 +0000 Subject: [ET Trac] #1674: Switch to OpenBLAS Message-ID: #1674: Switch to OpenBLAS Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: enhancement Priority: minor Component: Other Comment (by Roland Haas): This ticket has been around for a while. I would still think that since OpenBLAS is x86 specific and even on x86 machines fails to compile if the processor is too new \(or old I guess\), I would not want it to be the default. Instead clusters where indeed we could compile BLAS and LAPACK libs from scratch can use simfactory?s `enabled-thorns` and `disable-thorns` options to enable OpenBLAS. If we do not compile, which is the usual case on clusters, then there is no difference between using BLAS/LAPACK externallibraries and OpenBLAS. That leaves the case of user workstations and unknown clusters. On a user workstation, with automated setup, speed should not matter so I would strongly advocate to use the ?compiles everywhere? BLAS and LAPACK even if they are slow. In particular since the ET as a whole doe not depend on those for speed. On clusters, speed does matter, but setting up on a cluster requires some expertise anyway and we should be able to expect that those doing so will be able to set the correct LAPACK\_DIR and BLAS\_DIR variables to point to the system installed good BLAS / LAPACK library. If there are indeed HPC clusters where those libraries are not provide, then those clusters may be best avoided. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1674/switch-to-openblas -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 11 13:13:38 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 11 May 2023 18:13:38 +0000 Subject: [ET Trac] #1674: Switch to OpenBLAS Message-ID: #1674: Switch to OpenBLAS Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: enhancement Priority: minor Component: Other Comment (by Roland Haas): So I would like to close this ticket as `wontfix`. @{557058:56049c54-f8c2-4b6c-9b88-ab697c967495} ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1674/switch-to-openblas -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri May 12 08:16:53 2023 From: trac-noreply at einsteintoolkit.org (Erik Schnetter) Date: Fri, 12 May 2023 13:16:53 +0000 Subject: [ET Trac] #1674: Switch to OpenBLAS Message-ID: #1674: Switch to OpenBLAS Reporter: Erik Schnetter Status: open Milestone: Version: development version Type: enhancement Priority: minor Component: Other Comment (by Erik Schnetter): I concur. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1674/switch-to-openblas -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri May 12 10:00:58 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Fri, 12 May 2023 15:00:58 +0000 Subject: [ET Trac] #1674: Switch to OpenBLAS Message-ID: #1674: Switch to OpenBLAS Reporter: Erik Schnetter Status: wontfix Milestone: Version: development version Type: enhancement Priority: minor Component: Other Changes (by Roland Haas): status: wontfix (was open) OpenBLAS is a BLAS and LAPACK library that is significantly more efficient that the standard ("reference") BLAS. I suggest we switch the ET thorn list to ExternalLibraries/OpenBLAS instead of ExternalLibraries/BLAS and ExternalLibraris/LAPACK. **Keyword:** Comment (by Roland Haas): One more ticket down! -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1674/switch-to-openblas -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 15 09:32:34 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 15 May 2023 14:32:34 +0000 Subject: [ET Trac] #2729: ET server uptime monitor does not send emails and does not show correct status Message-ID: #2729: ET server uptime monitor does not send emails and does not show correct status Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit website The uptime monitor at [https://einsteintoolkit.github.io/uptime](https://einsteintoolkit.github.io/uptime) does not show the correct summary or send out emails \(or the emails are eaten by the mail server which in fact may be the service that is down\). The only indication on the main page of a failure is the red bar next to the mailing list server row. Since the server that is down is the mail server this also means that no email about this could have been sent. So a secondary delivery mechanism is needed. Either a second, directly accessible email address or maybe posting to the ET chat on Gitter using GitHub credentials \(of the workflow user\). ? attachment: 2023-05-15T094828.png (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2729/attachments/2023-05-15T094828.png) attachment: 2023-05-15T094839.png (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2729/attachments/2023-05-15T094839.png) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2729/et-server-uptime-monitor-does-not-send -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon May 15 14:41:01 2023 From: trac-noreply at einsteintoolkit.org (Bing-Jyun Tsao) Date: Mon, 15 May 2023 19:41:01 +0000 Subject: [ET Trac] #2173: Test "Poisson equation" example Message-ID: #2173: Test "Poisson equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Bing-Jyun Tsao): Gallery test run poisson-20230510 is completed and updated. The link for the thornlist is pointed to [https://bitbucket.org/einsteintoolkit/manifest/raw/ET\_2023\_05/einsteintoolkit.th](https://bitbucket.org/einsteintoolkit/manifest/raw/ET_2023_05/einsteintoolkit.th) which does not exist yet. A new visit session file `psi4.session` is needed for either cases of running with 1 thread or 8 threads with VisIt 3.2.1, and the session file is included in the compressed folder `poisson-20230510.tar.gz` in downloads. ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equation-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 16 16:15:02 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 16 May 2023 21:15:02 +0000 Subject: [ET Trac] #2730: Cactus wikpedia page flagged for plagiarism Message-ID: #2730: Cactus wikpedia page flagged for plagiarism Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus website The Cactus wikipedia page has been tagged as containing large copied sections \(from [cactuscode.org](http://cactuscode.org) one assumes\). ? ![](https://bitbucket.org/repo/8zBLME5/images/2421563016-image.png) ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2730/cactus-wikpedia-page-flagged-for -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 16 16:33:39 2023 From: trac-noreply at einsteintoolkit.org (jakedoherty) Date: Tue, 16 May 2023 21:33:39 +0000 Subject: [ET Trac] #2174: Test "Multi Patch Scalar Wave Equation" example Message-ID: #2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by jakedoherty): I?ve pushed the changes for 2023 May Release and I got the exact same results using 56 cores on Frontera in a little over a minute. I generated my own session files for visualization. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-scalar-wave-equation -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 16 17:15:59 2023 From: trac-noreply at einsteintoolkit.org (Leonardo Werneck) Date: Tue, 16 May 2023 22:15:59 +0000 Subject: [ET Trac] #2497: IllinoisGRMHD is incompatible with setting TmunuBase::stress_energy_at_RHS = "no" Message-ID: #2497: IllinoisGRMHD is incompatible with setting TmunuBase::stress_energy_at_RHS = "no" Reporter: Gabriele Bozzola Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Leonardo Werneck): After reviewing the issue more carefully, I think it is more prudent to fix it for the November release, as there won?t be enough time to fully test the code in time for this release. One possible solution is to modify IllinoisGRMHD?s `schedule.ccl` to add the con2prim function to the `HydroBase_Con2Prim` bin when `TmunuBase::stress_energy_at_RHS="no"`, e.g., ``` if(stress_energy_at_RHS) { schedule IllinoisGRMHD_conserv_to_prims in AddToTmunu after compute_B_and_Bstagger_from_A { LANG: C } "Compute primitive variables from conservatives. This is non-trivial, requiring a Newton-Raphson root-finder." schedule IllinoisGRMHD_outer_boundaries_on_P_rho_b_vx_vy_vz in AddToTmunu after IllinoisGRMHD_conserv_to_prims { # We must sync {P,rho_b,vx,vy,vz} here. SYNC: grmhd_primitives_allbutBi LANG: C } "Apply outflow-only, flat BCs on {P,rho_b,vx,vy,vz}. Outflow only == velocities pointed inward from outer boundary are set to zero." } else { schedule IllinoisGRMHD_conserv_to_prims in HydroBase_Con2Prim after compute_B_and_Bstagger_from_A { LANG: C } "Compute primitive variables from conservatives. This is non-trivial, requiring a Newton-Raphson root-finder." schedule IllinoisGRMHD_outer_boundaries_on_P_rho_b_vx_vy_vz in HydroBase_Con2Prim after IllinoisGRMHD_conserv_to_prims { # We must sync {P,rho_b,vx,vy,vz} here. SYNC: grmhd_primitives_allbutBi LANG: C } "Apply outflow-only, flat BCs on {P,rho_b,vx,vy,vz}. Outflow only == velocities pointed inward from outer boundary are set to zero." } ``` This fixes the scheduling problem, but the code will still keep adding to `Tmunu` unless one also sets `IllinoisGRMHD::update_tmunu = "no"` in the parfile. Could you please test this to see if it provides the functionality that you seek @{557058:4b0c8315-696b-4d2e-92da-2da5fea9e8d4} ? If I misunderstood something, please let me know. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2497/illinoisgrmhd-is-incompatible-with-setting -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 17 13:15:45 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 17 May 2023 18:15:45 +0000 Subject: [ET Trac] #2731: check for incomplete perl install when use requests parallel checkout Message-ID: #2731: check for incomplete perl install when use requests parallel checkout Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: GetComponents **Panagiotis Iosif** in [https://lists.einsteintoolkit.org/pipermail/users/2023-May/008923.html](https://lists.einsteintoolkit.org/pipermail/users/2023-May/008923.html) encountered and issue when passed `--parallel` to GetComponents on a cluster where the Perl installation is very minimal and lacks Perl?s standard Thread package. This has happened before in some Docker image as well \(so that now we include Perl as one of the packages to install with apt/yum/dnf\). Since this is apparently also an issue on clusters, pull request [https://github.com/gridaphobe/CRL/pull/13](https://github.com/gridaphobe/CRL/pull/13) provides an error message when this happens. Leaving out the explicit `--parallel` option lets one download the ET. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2731/check-for-incomplete-perl-install-when-use -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 17 13:16:14 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 17 May 2023 18:16:14 +0000 Subject: [ET Trac] #2731: check for incomplete perl install when use requests parallel checkout Message-ID: #2731: check for incomplete perl install when use requests parallel checkout Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: GetComponents Comment (by Roland Haas): Please review. After the 2023\_05 release. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2731/check-for-incomplete-perl-install-when-use -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 18 08:45:31 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 18 May 2023 13:45:31 +0000 Subject: [ET Trac] #2176: Test "Binary neutron star" example Message-ID: #2176: Test "Binary neutron star" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Roland Haas): I updated the website and the data. The gallery example now uses higher resolution. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2176/test-binary-neutron-star-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 18 13:16:50 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 18 May 2023 18:16:50 +0000 Subject: [ET Trac] #2663: add an notice about minimum Intel / GCC version required to configure output Message-ID: #2663: add an notice about minimum Intel / GCC version required to configure output Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: major Component: Comment (by Roland Haas): @{557058:8bc23f2a-45c0-477d-8ac4-a5a16c734278} would you be interested to review? Pull request is earlier in this ticket and also, for convenience, here: [https://bitbucket.org/cactuscode/cactus/pull-requests/152](https://bitbucket.org/cactuscode/cactus/pull-requests/152) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2663/add-an-notice-about-minimum-intel-gcc -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 18 13:20:40 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 18 May 2023 18:20:40 +0000 Subject: [ET Trac] #2731: check for incomplete perl install when use requests parallel checkout Message-ID: #2731: check for incomplete perl install when use requests parallel checkout Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: GetComponents Changes (by Roland Haas): responsible: [] (was []) assignee: Steven R. Brandt (was Roland Haas) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2731/check-for-incomplete-perl-install-when-use -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 18 13:22:29 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 18 May 2023 18:22:29 +0000 Subject: [ET Trac] #2731: check for incomplete perl install when use requests parallel checkout Message-ID: #2731: check for incomplete perl install when use requests parallel checkout Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: GetComponents Comment (by Roland Haas): @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} could I ask you to review this one for the weekly review, please? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2731/check-for-incomplete-perl-install-when-use -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 23 16:13:04 2023 From: trac-noreply at einsteintoolkit.org (Peter Diener) Date: Tue, 23 May 2023 21:13:04 +0000 Subject: [ET Trac] #2175: Test "Single, stable neutron star" example Message-ID: #2175: Test "Single, stable neutron star" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Peter Diener): I have rerun the gallery simulation and found no difference between the new results and the old ones. I also ran at three higher resolutions and have added that data to the new plot. I have also added a convergence plot using the three highest resolutions. The Kuibit script has been update to produce both the density and the convergence plots. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2175/test-single-stable-neutron-star-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:15:26 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Thu, 25 May 2023 14:15:26 +0000 Subject: [ET Trac] #2692: Inclusion of FUKA importer thorns Message-ID: #2692: Inclusion of FUKA importer thorns Reporter: tootle Status: resolved Milestone: ET_2023_05 Version: ET_2023_05 Type: proposal Priority: major Component: EinsteinToolkit thorn Changes (by Samuel Cupp): status: resolved (was new) Comment (by Samuel Cupp): These thorns are now included as part of the Toolkit in the ET_2023_05 release. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2692/inclusion-of-fuka-importer-thorns -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:16:29 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Thu, 25 May 2023 14:16:29 +0000 Subject: [ET Trac] #2176: Test "Binary neutron star" example Message-ID: #2176: Test "Binary neutron star" example Reporter: Roland Haas Status: resolved Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Samuel Cupp): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2176/test-binary-neutron-star-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:17:03 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Thu, 25 May 2023 14:17:03 +0000 Subject: [ET Trac] #2173: Test "Poisson equation" example Message-ID: #2173: Test "Poisson equation" example Reporter: Roland Haas Status: resolved Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Samuel Cupp): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equation-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:17:28 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Thu, 25 May 2023 14:17:28 +0000 Subject: [ET Trac] #2174: Test "Multi Patch Scalar Wave Equation" example Message-ID: #2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: resolved Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Samuel Cupp): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-scalar-wave-equation -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:19:29 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Thu, 25 May 2023 14:19:29 +0000 Subject: [ET Trac] #2172: Test "Binary black hole GW150914" example Message-ID: #2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Samuel Cupp): @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} Has this been completed? The website hasn?t been updated if it has. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black-hole-gw150914-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:20:22 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Thu, 25 May 2023 14:20:22 +0000 Subject: [ET Trac] #2175: Test "Single, stable neutron star" example Message-ID: #2175: Test "Single, stable neutron star" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Samuel Cupp): @{557058:f7fd5133-6eee-4385-a5e5-3e03342a0b24} Can you close this ticket once you?ve uploaded the new data and updated the website? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2175/test-single-stable-neutron-star-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:22:20 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Thu, 25 May 2023 14:22:20 +0000 Subject: [ET Trac] #2712: KadathThorn build script contains GNUisms Message-ID: #2712: KadathThorn build script contains GNUisms Reporter: Roland Haas Status: new Milestone: ET_2023_05 Version: Type: bug Priority: major Component: Comment (by Samuel Cupp): @{5e5fc4216e8fdd0cd81720ad} @{634afd8853df3c01232121fd} is this ticket safe to close? Or is there still a problem? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2712/kadaththorn-build-script-contains-gnuisms -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:23:15 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Thu, 25 May 2023 14:23:15 +0000 Subject: [ET Trac] #2697: Include BBH+scalar field initial data code from Canuda in ET Message-ID: #2697: Include BBH+scalar field initial data code from Canuda in ET Reporter: Cheng-Hsin Cheng Status: resolved Milestone: Version: Type: enhancement Priority: major Component: Changes (by Samuel Cupp): status: resolved (was new) Comment (by Samuel Cupp): These new features are now included as part of the Toolkit in the ET_2023_05 release. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2697/include-bbh-scalar-field-initial-data-code -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:25:58 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Thu, 25 May 2023 14:25:58 +0000 Subject: [ET Trac] #2693: Adding read/write support to Baikal and BaikalVacuum Message-ID: #2693: Adding read/write support to Baikal and BaikalVacuum Reporter: Samuel Cupp Status: resolved Milestone: ET_2023_05 Version: Type: enhancement Priority: minor Component: EinsteinToolkit thorn Changes (by Samuel Cupp): status: resolved (was new) Comment (by Samuel Cupp): This enhancement is now included as part of the Toolkit in the ET_2023_05 release. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2693/adding-read-write-support-to-baikal-and -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:35:09 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 25 May 2023 14:35:09 +0000 Subject: [ET Trac] #2712: KadathThorn build script contains GNUisms Message-ID: #2712: KadathThorn build script contains GNUisms Reporter: Roland Haas Status: new Milestone: ET_2023_05 Version: Type: bug Priority: major Component: Comment (by Roland Haas): I did not explicitly check, but Samuel claims to have removed the GNUisms, which is good enough for me. We can open a new ticket if more or the same issues are found again. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2712/kadaththorn-build-script-contains-gnuisms -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:37:24 2023 From: trac-noreply at einsteintoolkit.org (Steven R. Brandt) Date: Thu, 25 May 2023 14:37:24 +0000 Subject: [ET Trac] #2172: Test "Binary black hole GW150914" example Message-ID: #2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: open Milestone: ET_2023_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Steven R. Brandt): I did the create-submit, now I need to follow up with more submits. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black-hole-gw150914-example -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 09:54:10 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 25 May 2023 14:54:10 +0000 Subject: [ET Trac] #2731: check for incomplete perl install when use requests parallel checkout Message-ID: #2731: check for incomplete perl install when use requests parallel checkout Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: GetComponents Comment (by Roland Haas): Steve says: please apply \(in pull request\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2731/check-for-incomplete-perl-install-when-use -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 10:00:37 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 25 May 2023 15:00:37 +0000 Subject: [ET Trac] #2731: check for incomplete perl install when use requests parallel checkout Message-ID: #2731: check for incomplete perl install when use requests parallel checkout Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: GetComponents Comment (by Roland Haas): Applied as git hash [172d861](https://github.com/gridaphobe/CRL/commits/172d861bc4f96816c43183bcea76990dbe23e4d5) "GetComponents: abort if --parallel is passed but Perl has no threads" of [CRL](https://github.com/gridaphobe/CRL) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2731/check-for-incomplete-perl-install-when-use -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 10:02:52 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 25 May 2023 15:02:52 +0000 Subject: [ET Trac] #2731: check for incomplete perl install when use requests parallel checkout Message-ID: #2731: check for incomplete perl install when use requests parallel checkout Reporter: Roland Haas Status: resolved Milestone: Version: Type: bug Priority: minor Component: GetComponents Changes (by Roland Haas): status: resolved (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2731/check-for-incomplete-perl-install-when-use -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu May 25 10:46:26 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 25 May 2023 15:46:26 +0000 Subject: [ET Trac] #2732: leftover reverences to nds-org docker image and files in ET tutorial Message-ID: #2732: leftover reverences to nds-org docker image and files in ET tutorial Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit website For the ET\_2023\_05 release we moved the repository hosting the ET notebook tutorial files \(jupyter notebooks, images, docker files\) from nds-org?s GitHub repo to einsteintoolkit/jupyter-et to simplify granting write access to ET developers. Currently there is at least one leftover reference to nds-org in the tutorial files. In CactusTutorial.ipynb it says: > This notebook is intended to be used online on the Einstein Toolkit tutorial server, offline as a read-only document, as a jupyter notebook that you can download and also in your own docker container using `nds-org/jupyter-et`. To make all of these work some setting need to be tweaked, which we do in the next cell. ? and there is no obvious docker image candidate in the einsteintoolkit dockerhub org to replace that with. The ones available are: ![](https://bitbucket.org/repo/8zBLME5/images/1886879992-image.png) ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2732/leftover-reverences-to-nds-org-docker -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri May 26 13:35:10 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Fri, 26 May 2023 18:35:10 +0000 Subject: [ET Trac] #2387: move CactusCode.org to be hosted by github pages Message-ID: #2387: move CactusCode.org to be hosted by github pages Reporter: Roland Haas Status: open Milestone: Version: Type: task Priority: major Component: Cactus website Comment (by Roland Haas): [http://www.cactuscode.org](http://www.cactuscode.org) moved to github pages in 2020 \(see [https://github.com/EinsteinToolkit/www.cactuscode.org/issues/19](https://github.com/EinsteinToolkit/www.cactuscode.org/issues/19)\). Git hash [e825525d](https://bitbucket.org/cactuscode/cactus/commits/e825525d1866fda1ec708802f18355edd5a3c50b) "Cactus: remove link to removed wavetoy demo server" of [cactus](https://bitbucket.org/cactuscode/cactus) removes the now dead link. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2387/move-cactuscodeorg-to-be-hosted-by-github -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri May 26 13:35:23 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Fri, 26 May 2023 18:35:23 +0000 Subject: [ET Trac] #2387: move CactusCode.org to be hosted by github pages Message-ID: #2387: move CactusCode.org to be hosted by github pages Reporter: Roland Haas Status: resolved Milestone: Version: Type: task Priority: major Component: Cactus website Changes (by Roland Haas): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2387/move-cactuscodeorg-to-be-hosted-by-github -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue May 30 08:56:08 2023 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 30 May 2023 13:56:08 +0000 Subject: [ET Trac] #2733: TwoPunctures contains globally visible symbols not prefixed by thorn name Message-ID: #2733: TwoPunctures contains globally visible symbols not prefixed by thorn name Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: TwoPunctures contains a number of functions \(and possibly global variables\) that are not prefixed by the thorn name and thus cause name clashes. This is most obvious when one compares the derived codes `TwoPunctures_BBHSF` and `TwoPunctures_KerrProca` to `TwoPunctures` \(eg using `diff -ur`\) since the derived codes already added the prefixes. This should however also be fixed in `TwoPunctures` since some of the names are very generic \(eg `Index()` and `interpol`\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2733/twopunctures-contains-globally-visible -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 31 14:37:13 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Wed, 31 May 2023 19:37:13 +0000 Subject: [ET Trac] #2723: No boundary conditions registered for variables in group LEANBSSNMOL Message-ID: #2723: No boundary conditions registered for variables in group LEANBSSNMOL Reporter: Vikram Manikantan Status: new Milestone: ET_2023_05 Version: ET_2022_11 Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Samuel Cupp): I?ve never used this thorn, but I can hazard a guess. On the master branch, the function `LeanBSSN_Boundaries` doesn?t run until ``` schedule LeanBSSN_Boundaries in MoL_PostStep { LANG: Fortran OPTIONS: LEVEL SYNC: ADMBase::lapse SYNC: ADMBase::shift SYNC: LeanBSSNMoL::conf_fac SYNC: LeanBSSNMoL::hmetric SYNC: LeanBSSNMoL::hcurv SYNC: LeanBSSNMoL::trk SYNC: LeanBSSNMoL::gammat } "MoL boundary enforcement" ``` In the old approach, boundary conditions and ghost zone synchronization were completely independent. Now, we simply do both at the same time. Hence, scheduling like ``` schedule LeanBSSN_adm2bssn at CCTK_INITIAL after ADMBase_PostInitial { LANG: Fortran OPTIONS: Local SYNC: gammat } "Convert initial data into BSSN variables" ``` will naturally trigger warnings if there are no BCs yet. Additionally, the old method didn?t make it clear that the ApplyBCs scheduled at CCTK\_INITIAL was an empty call that did nothing. Since the registered BCs look to be `none`, it doesn't actually matter. I thought this was resolved in [Issue #2648](https://bitbucket.org/einsteintoolkit/tickets/issues/2723/no-boundary-conditions-registered-for). However, the changes aren?t in master. This ticket changed ``` schedule LeanBSSN_adm2bssn at CCTK_INITIAL after ADMBase_PostInitial { LANG: Fortran OPTIONS: Local SYNC: gammat } "Convert initial data into BSSN variables" schedule GROUP ApplyBCs as LeanBSSN_ApplyBCs at CCTK_INITIAL after LeanBSSN_adm2bssn { } "Apply boundary conditions" ``` to ``` schedule LeanBSSN_adm2bssn at CCTK_INITIAL after ADMBase_PostInitial { LANG: Fortran OPTIONS: Local } "Convert initial data into BSSN variables" schedule LeanBSSN_Boundaries at CCTK_INITIAL after LeanBSSN_adm2bssn { LANG: Fortran OPTIONS: LEVEL SYNC: LeanBSSNMoL::gammat } "Boundary enforcement" schedule GROUP ApplyBCs as LeanBSSN_ApplyBCs at CCTK_INITIAL after LeanBSSN_adm2bssn { } "Apply boundary conditions" ``` It looks like this change **is** in the development branch. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2723/no-boundary-conditions-registered-for -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 31 14:39:23 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Wed, 31 May 2023 19:39:23 +0000 Subject: [ET Trac] #2723: No boundary conditions registered for variables in group LEANBSSNMOL Message-ID: #2723: No boundary conditions registered for variables in group LEANBSSNMOL Reporter: Vikram Manikantan Status: new Milestone: ET_2023_05 Version: ET_2022_11 Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Samuel Cupp): So, in answer to the original question, you can try changing the schedule.ccl to what I posted above and see if that resolves the errors or not. I haven?t run with mixed-warning much, so there might be some other cases that could trigger it that I haven?t thought of. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2723/no-boundary-conditions-registered-for -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed May 31 14:56:34 2023 From: trac-noreply at einsteintoolkit.org (Samuel Cupp) Date: Wed, 31 May 2023 19:56:34 +0000 Subject: [ET Trac] #2734: Consider adding if statement functionality to read/write declarations Message-ID: #2734: Consider adding if statement functionality to read/write declarations Reporter: Samuel Cupp Status: new Milestone: Version: Type: enhancement Priority: minor Component: Cactus Currently, the read/write declarations are a compile-time setting. This is usually fine. For a function that is scheduled in multiple places with different rd/wr, Cactus takes a union of all declarations for generating the function-specific macros. However, one case can lead to additional complications in scheduling. If a function has many different _if_ statements inside it controlling behavior at runtime \(see e.g. GRHydro for the worst case scenario of this type of runtime-dependent scheduling\), then properly setting the rd/wr declarations will require either ignoring the actual behavior of the code and hoping for the best **or** having all of those _if_ statements reproduced inside the schedule.ccl. The former can bypass some safety checks and enforcement of good code behavior, while the latter causes excessive bloat in the schedule.ccl. ? A preferable alternative would be to allow rd/wr declarations to have runtime tags/conditionals/something that can turn them on/off depending on parameters. An easy example is `IllinoisGRMHD`'s conserv\_to\_prims function, which writes the primitives, conservatives, and \(if update\_Tmunu\) the stress-energy tensor. Right now, the only way to explicitly give this data dependency would be \(focusing on the WRITES declarations\) ``` if (update_Tmunu) { schedule IllinoisGRMHD_conserv_to_prims { LANG: C READS: stuff WRITES: prims, cons, Tmunu } "" } else { schedule IllinoisGRMHD_conserv_to_prims { LANG: C READS: stuff WRITES: prims, cons } "" } ``` Instead, it would be convenient to say ``` schedule IllinoisGRMHD_conserv_to_prims { LANG: C READS: stuff WRITES: prims, cons WRITES: Tmunu if update_Tmunu } "" ``` or something equivalent. This not only gives the ability to more accurately state the data dependencies, it also allows for more compact scheduling of complicated functions while still allowing for them to be controlled using runtime parameters. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2734/consider-adding-if-statement-functionality -------------- next part -------------- An HTML attachment was scrubbed... URL: