From trac-noreply at einsteintoolkit.org Fri Jan 12 16:18:00 2024 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Fri, 12 Jan 2024 22:18:00 +0000 Subject: [ET Trac] #2755: bugs in POWER code Message-ID: #2755: bugs in POWER code Reporter: Anuj Kankani Status: open Milestone: Version: Type: bug Priority: major Component: Other Changes (by Roland Haas): status: open (was resolved) Comment (by Roland Haas): The applied fix was incorrect (would set angular momentum to 0 all the time...). Fixed in master in [bbcc63e](https://git.ncsa.illinois.edu/elihu/Gravitational_Waveform_Extractor/commits/bbcc63ea64be72c997871d28e7d047d6c230a19d) "POWER: correct expression for angular momentum once more" of [Gravitational_Waveform_Extractor](https://git.ncsa.illinois.edu/elihu/Gravitational_Waveform_Extractor). Should be backported. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2755/bugs-in-power-code -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri Jan 12 23:29:51 2024 From: trac-noreply at einsteintoolkit.org (tootle) Date: Sat, 13 Jan 2024 05:29:51 +0000 Subject: [ET Trac] #2772: Issues link against Kadath thorns and Intel MKL due to link ordering Message-ID: #2772: Issues link against Kadath thorns and Intel MKL due to link ordering Reporter: tootle Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn A recurring issue that keeps coming up with the KadathThorn/Importer is centered around linking when using intel MKL.? It is worth noting that this is not restricted to the ETK, but I had not been able to reproduce the error myself until now. The problem is resolved if I specify all of the dependencies of Kadath in a specific order in the final build command that outputs the cactus executable. e.g, adding the following directly after -lkadath: ``` -lgsl -lgslcblas -lfftw3 -L${MKLROOT}/lib/ -Wl,--start-group -lmkl_intel_lp64 -lmkl_sequential -lmkl_core -lmkl_blacs_intelmpi_lp64 -Wl,--end-group -lgomp -lpthread -lmkl_scalapack_lp64 -lm -ldl ``` results in a working executable on the local HPC in Idaho. Excluding this link order or adding it somewhere else in the command other than directly after -lkadath will result in an executable that yields undefined behavior. Note: the undefined behavior leads to a crash during ID import from all known cases \(in and out of the ETK\) where this problem has come up. Solution: 1. Ability to specify a controlled link order in the options.cfg file \(LDFLAGS does not work\) 2. Ability to specify a controlled link order during the build script of KadathThorn ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2772/issues-link-against-kadath-thorns-and -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed Jan 17 12:19:10 2024 From: trac-noreply at einsteintoolkit.org (tootle) Date: Wed, 17 Jan 2024 18:19:10 +0000 Subject: [ET Trac] #2772: Issues link against Kadath thorns and Intel MKL due to link ordering Message-ID: #2772: Issues link against Kadath thorns and Intel MKL due to link ordering Reporter: tootle Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by tootle): @{557058:56049c54-f8c2-4b6c-9b88-ab697c967495} @{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} Do you have ideas for either solution? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2772/issues-link-against-kadath-thorns-and -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed Jan 17 12:36:35 2024 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 17 Jan 2024 18:36:35 +0000 Subject: [ET Trac] #2772: Issues link against Kadath thorns and Intel MKL due to link ordering Message-ID: #2772: Issues link against Kadath thorns and Intel MKL due to link ordering Reporter: tootle Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Is dislike both :-\) But, as @{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} , will be happy to confirm, that is my default answer and may well change. Let me think about this a bit. I would have hoped using `LDFLAGS` would have worked, but this does not seem to be the case for you. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2772/issues-link-against-kadath-thorns-and -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Jan 18 09:14:18 2024 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 18 Jan 2024 15:14:18 +0000 Subject: [ET Trac] #2755: bugs in POWER code Message-ID: #2755: bugs in POWER code Reporter: Anuj Kankani Status: open Milestone: Version: Type: bug Priority: major Component: Other Comment (by Roland Haas): Pull request to backport is [https://github.com/NCSAGravity/Gravitational\_Waveform\_Extractor/pull/2](https://github.com/NCSAGravity/Gravitational_Waveform_Extractor/pull/2): -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2755/bugs-in-power-code -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Jan 18 09:14:29 2024 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 18 Jan 2024 15:14:29 +0000 Subject: [ET Trac] #2755: bugs in POWER code Message-ID: #2755: bugs in POWER code Reporter: Anuj Kankani Status: open Milestone: Version: Type: bug Priority: major Component: Other Comment (by Roland Haas): Please review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2755/bugs-in-power-code -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Jan 18 09:32:10 2024 From: trac-noreply at einsteintoolkit.org (Steven R. Brandt) Date: Thu, 18 Jan 2024 15:32:10 +0000 Subject: [ET Trac] #2772: Issues link against Kadath thorns and Intel MKL due to link ordering Message-ID: #2772: Issues link against Kadath thorns and Intel MKL due to link ordering Reporter: tootle Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Steven R. Brandt): I?ve had trouble controlling the linking process on multiple occasions. It would be nice to have more control over it. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2772/issues-link-against-kadath-thorns-and -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Jan 18 14:42:06 2024 From: trac-noreply at einsteintoolkit.org (Anuj Kankani) Date: Thu, 18 Jan 2024 20:42:06 +0000 Subject: [ET Trac] #2755: bugs in POWER code Message-ID: #2755: bugs in POWER code Reporter: Anuj Kankani Status: open Milestone: Version: Type: bug Priority: major Component: Other Comment (by Anuj Kankani): looks good, sorry for not catching it the first time. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2755/bugs-in-power-code -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed Jan 31 15:56:25 2024 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 31 Jan 2024 21:56:25 +0000 Subject: [ET Trac] #2773: make CarpetX-ThornDoc is confused in InterLatex.pl Message-ID: #2773: make CarpetX-ThornDoc is confused in InterLatex.pl Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus Running `make CarpetX-ThornDoc` I find warnings \(among others?\) in `LOG_INTERLATEX_MSGS`: ``` ekohaes8: .../cactus/CarpetXCPU$ less doc/ThornDoc/CarpetX/CarpetX/LOG_INTERLATEX_MSGS CarpetX Parsing interface for CarpetX Initialized thorn structure for CarpetX Implements: CarpetX Inherits: IO 2 Public, 0 Protected, 0 Private variable groups Walking ancestors for CarpetX --> Confused: [global_type] = [HASH(0x560e5bfd79e8)] Finished. ``` which is due to a hash membmer `global_type` \(a bareword\) in the `interface_db`. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2773/make-carpetx-thorndoc-is-confused-in -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed Jan 31 15:56:33 2024 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 31 Jan 2024 21:56:33 +0000 Subject: [ET Trac] #2773: make CarpetX-ThornDoc is confused in InterLatex.pl Message-ID: #2773: make CarpetX-ThornDoc is confused in InterLatex.pl Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: minor Component: Cactus Changes (by Roland Haas): status: open (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2773/make-carpetx-thorndoc-is-confused-in -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed Jan 31 15:57:02 2024 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 31 Jan 2024 21:57:02 +0000 Subject: [ET Trac] #2773: make CarpetX-ThornDoc is confused in InterLatex.pl Message-ID: #2773: make CarpetX-ThornDoc is confused in InterLatex.pl Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: minor Component: Cactus Changes (by Roland Haas): responsible: [] (was ) assignee: Steven R. Brandt (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2773/make-carpetx-thorndoc-is-confused-in -------------- next part -------------- An HTML attachment was scrubbed... URL: