From trac-noreply at einsteintoolkit.org Sat Mar 1 15:47:59 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sat, 01 Mar 2025 21:47:59 +0000 Subject: [ET Trac] #2633: SummationByPart's Diff_gv aliased function does ont document which part of the grid the computed derivative is valid Message-ID: #2633: SummationByPart's Diff_gv aliased function does ont document which part of the grid the computed derivative is valid Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Comment (by Roland Haas): @{557058:f7fd5133-6eee-4385-a5e5-3e03342a0b24} an updates on this? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2633/summationbyparts-diff_gv-aliased-function -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Sat Mar 1 15:48:52 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sat, 01 Mar 2025 21:48:52 +0000 Subject: [ET Trac] #2308: SummationByParts: Use centred stencils on multipatch symmetry boundaries Message-ID: #2308: SummationByParts: Use centred stencils on multipatch symmetry boundaries Reporter: Roland Haas Status: open Milestone: Version: Type: enhancement Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): @{557058:ae98ab72-3754-49e1-9230-5c814d4c790b} is this still relevant? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2308/summationbyparts-use-centred-stencils-on -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Sat Mar 1 15:51:30 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sat, 01 Mar 2025 21:51:30 +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): Applied as git hash [985f7556](https://bitbucket.org/cactuscode/cactus/commits/985f7556a19660cda28f373188652e450a9d2951) "Cactus: use CCTK\_ERROR to report user errors instead of assert" of [cactus](https://bitbucket.org/cactuscode/cactus) on 2023-05-02 -- 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 Sat Mar 1 19:00:54 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sun, 02 Mar 2025 01:00:54 +0000 Subject: [ET Trac] #2860: Don't call the optimized 4th order second derivative operators. Message-ID: #2860: Don't call the optimized 4th order second derivative operators. Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn As the optimized 4th order second derivative operators have been proven to cause instabilities, simply call the minimal bandwidth operators regardless of parameter choices. Note: The 4-2 second derivative operator was the only one to have an optimized variant. I suspect that it was never tested before. This makes the 4-2 second derivative operator behave like the -3 and 8-4 operators. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2860/dont-call-the-optimized-4th-order-second -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Sat Mar 1 19:02:17 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sun, 02 Mar 2025 01:02:17 +0000 Subject: [ET Trac] #2860: Don't call the optimized 4th order second derivative operators. Message-ID: #2860: Don't call the optimized 4th order second derivative operators. Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Pull request is here: [https://bitbucket.org/cactuscode/cactusnumerical/pull-requests/13](https://bitbucket.org/cactuscode/cactusnumerical/pull-requests/13) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2860/dont-call-the-optimized-4th-order-second -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Sat Mar 1 19:04:37 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sun, 02 Mar 2025 01:04:37 +0000 Subject: [ET Trac] #2625: CarpetMask should not be scheduled before SphericalSurface_Set Message-ID: #2625: CarpetMask should not be scheduled before SphericalSurface_Set Reporter: Gabriele Bozzola Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Please review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2625/carpetmask-should-not-be-scheduled-before -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Sat Mar 1 19:06:15 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sun, 02 Mar 2025 01:06:15 +0000 Subject: [ET Trac] #2860: Don't call the optimized 4th order second derivative operators. Message-ID: #2860: Don't call the optimized 4th order second derivative operators. Reporter: Roland Haas Status: new Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): responsible: [] (was ) assignee: Peter Diener (was ) Comment (by Roland Haas): Assign to @{557058:f7fd5133-6eee-4385-a5e5-3e03342a0b24} who created the original pull request. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2860/dont-call-the-optimized-4th-order-second -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Sat Mar 1 19:06:38 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sun, 02 Mar 2025 01:06:38 +0000 Subject: [ET Trac] #2860: Don't call the optimized 4th order second derivative operators. Message-ID: #2860: Don't call the optimized 4th order second derivative operators. Reporter: Roland Haas Status: open Milestone: Version: development version Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: open (was new) Comment (by Roland Haas): Please review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2860/dont-call-the-optimized-4th-order-second -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Sat Mar 1 19:19:48 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sun, 02 Mar 2025 01:19:48 +0000 Subject: [ET Trac] #2857: Compiling CarpetX with OpenPMD Message-ID: #2857: Compiling CarpetX with OpenPMD Reporter: Alejandra Gonzalez Status: open Milestone: ET_2024_11 Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Pull request is here: [https://github.com/EinsteinToolkit/ExternalLibraries-openPMD/pull/1](https://github.com/EinsteinToolkit/ExternalLibraries-openPMD/pull/1) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2857/compiling-carpetx-with-openpmd -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Sat Mar 1 19:20:12 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sun, 02 Mar 2025 01:20:12 +0000 Subject: [ET Trac] #2857: Compiling CarpetX with OpenPMD Message-ID: #2857: Compiling CarpetX with OpenPMD Reporter: Alejandra Gonzalez Status: open Milestone: ET_2024_11 Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Please review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2857/compiling-carpetx-with-openpmd -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 3 05:44:34 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Mon, 03 Mar 2025 11:44:34 +0000 Subject: [ET Trac] #2857: Compiling CarpetX with OpenPMD Message-ID: #2857: Compiling CarpetX with OpenPMD Reporter: Alejandra Gonzalez Status: open Milestone: ET_2024_11 Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Alejandra Gonzalez): The new commits from the PR seem to compile openPMD without issues -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2857/compiling-carpetx-with-openpmd -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 3 09:53:40 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 03 Mar 2025 15:53:40 +0000 Subject: [ET Trac] #2857: Compiling CarpetX with OpenPMD Message-ID: #2857: Compiling CarpetX with OpenPMD Reporter: Alejandra Gonzalez Status: open Milestone: ET_2024_11 Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Thank you for the feedback. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2857/compiling-carpetx-with-openpmd -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 3 09:53:55 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 03 Mar 2025 15:53:55 +0000 Subject: [ET Trac] #2857: Compiling CarpetX with OpenPMD Message-ID: #2857: Compiling CarpetX with OpenPMD Reporter: Alejandra Gonzalez Status: open Milestone: ET_2024_11 Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Applied as git hash [e0cb63d](https://github.com/EinsteinToolkit/ExternalLibraries-openPMD/commits/e0cb63d402e25e916e1d553769c5a874b98bb3c0) "openPMD: include nlohmann\_json and toml11tar file" of [ExternalLibraries-openPMD](https://github.com/EinsteinToolkit/ExternalLibraries-openPMD) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2857/compiling-carpetx-with-openpmd -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 3 09:54:08 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 03 Mar 2025 15:54:08 +0000 Subject: [ET Trac] #2857: Compiling CarpetX with OpenPMD Message-ID: #2857: Compiling CarpetX with OpenPMD Reporter: Alejandra Gonzalez Status: resolved Milestone: ET_2024_11 Version: Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2857/compiling-carpetx-with-openpmd -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 08:09:50 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Thu, 06 Mar 2025 14:09:50 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: submitted Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn I?m currently testing CarpetX in the new MareNostrum 5 and attempted to run the parfiles here: [https://github.com/EinsteinToolkit/SpacetimeX/tree/main/Punctures/par](https://github.com/EinsteinToolkit/SpacetimeX/tree/main/Punctures/par) specifically `qc0` and `qc0-unigrid`. However I get the following error right at initialization \(for both\): ``` INFO (Formaline): Writing tarballs with the Cactus sources into the directory "qc0/cactus-source" INFO (CarpetX): Setting initial values for max_grid_size values for all levels INFO (CarpetX): Setting up initial conditions... INFO (CarpetX): Iteration: 0 time: 0 delta_time: 0.25 INFO (CarpetX): Patch 0: INFO (CarpetX): Grid extent: INFO (CarpetX): gsh=[67,67,67] INFO (CarpetX): blocking_factor=[8,8,8] INFO (CarpetX): max_grid_size=[32,32,32] INFO (CarpetX): max_tile_size=[1024000,16,32] INFO (CarpetX): Domain extent: INFO (CarpetX): xmin=[-16,-16,-16] INFO (CarpetX): xmax=[16,16,16] INFO (CarpetX): base dx=[0.5,0.5,0.5] INFO (CarpetX): Initializing level 0... INFO (Punctures): Nonlinear iteration #1 ERROR from host as06r1b22 process 0 in thorn CarpetX, file /gpfs/home/uib/uib416720/ETK2024/CarpetX/Cactus/configs/sim_cx/build/CarpetX/valid.cxx:461: -> CallFunction iteration 0 Punctures_solve1: Punctures::Punctures_rhs checking output: Grid function "PUNCTURES::urhs" contains nans, infinities, or poison; expected valid The interior is valid because: CallFunction iteration 0 Punctures_solve1: Punctures::Punctures_rhs: Mark output variables as valid. The outer boundary is valid because: CallFunction iteration 0 Punctures_solve1: Punctures::Punctures_rhs: Mark output variables as valid. The ghost zones are valid because: CallFunction iteration 0 Punctures_solve1: Punctures::Punctures_rhs: Mark output variables as valid. ``` My questions here are: 1. Should I be using these specific parfiles or is there a more updated \(previously tested\) somewhere else? 2. I?m confused with the thorns I should be using, is `Punctures` the way to go for BBH or should I use something else? e.g. `TwoPuncturesX` 3. Could the error have to do with the way I?m setting up the MPI/OMP/GPU devices with slurm? Thanks in advance for your help. ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 08:14:53 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Thu, 06 Mar 2025 14:14:53 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: submitted Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Alejandra Gonzalez): I?m currently testing CarpetX in the new MareNostrum 5 and attempted to run the parfiles here: [https://github.com/EinsteinToolkit/SpacetimeX/tree/main/Punctures/par](https://github.com/EinsteinToolkit/SpacetimeX/tree/main/Punctures/par) specifically `qc0` and `qc0-unigrid`. However I get the following error right at initialization \(for both\): ``` INFO (Formaline): Writing tarballs with the Cactus sources into the directory "qc0/cactus-source" INFO (CarpetX): Setting initial values for max_grid_size values for all levels INFO (CarpetX): Setting up initial conditions... INFO (CarpetX): Iteration: 0 time: 0 delta_time: 0.25 INFO (CarpetX): Patch 0: INFO (CarpetX): Grid extent: INFO (CarpetX): gsh=[67,67,67] INFO (CarpetX): blocking_factor=[8,8,8] INFO (CarpetX): max_grid_size=[32,32,32] INFO (CarpetX): max_tile_size=[1024000,16,32] INFO (CarpetX): Domain extent: INFO (CarpetX): xmin=[-16,-16,-16] INFO (CarpetX): xmax=[16,16,16] INFO (CarpetX): base dx=[0.5,0.5,0.5] INFO (CarpetX): Initializing level 0... INFO (Punctures): Nonlinear iteration #1 ERROR from host as06r1b22 process 0 in thorn CarpetX, file /gpfs/home/uib/uib416720/ETK2024/CarpetX/Cactus/configs/sim_cx/build/CarpetX/valid.cxx:461: -> CallFunction iteration 0 Punctures_solve1: Punctures::Punctures_rhs checking output: Grid function "PUNCTURES::urhs" contains nans, infinities, or poison; expected valid The interior is valid because: CallFunction iteration 0 Punctures_solve1: Punctures::Punctures_rhs: Mark output variables as valid. The outer boundary is valid because: CallFunction iteration 0 Punctures_solve1: Punctures::Punctures_rhs: Mark output variables as valid. The ghost zones are valid because: CallFunction iteration 0 Punctures_solve1: Punctures::Punctures_rhs: Mark output variables as valid. ``` My questions here are: 1. Should I be using these specific parfiles or is there a more updated \(previously tested\) somewhere else? 2. I?m confused with the thorns I should be using, is `Punctures` the way to go for BBH or should I use something else? e.g. `TwoPuncturesX` 3. Could the error have to do with the way I?m setting up the MPI/OMP/GPU devices with slurm? Thanks in advance for your help. PS. For the record, I tested `benchmark-carpetx` and `benchmark-z4c` from [https://github.com/EinsteinToolkit/CarpetX/tree/main/BenchX/par](https://github.com/EinsteinToolkit/CarpetX/tree/main/BenchX/par) and both worked well. ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 08:54:31 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 14:54:31 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: open (was submitted) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:05:45 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 06 Mar 2025 16:05:45 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Lucas Timotheo Sanches): responsible: [] (was ) assignee: Lucas Timotheo Sanches (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:15:50 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 16:15:50 +0000 Subject: [ET Trac] #2839: look for multiple flavors of hdf5 library names Message-ID: #2839: look for multiple flavors of hdf5 library names Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): @{5bae587b96242d2e2b6110a4} \(private communication\) reports that this fixes issues on his macOS setup. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2839/look-for-multiple-flavors-of-hdf5-library -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:16:07 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 16:16:07 +0000 Subject: [ET Trac] #2839: look for multiple flavors of hdf5 library names Message-ID: #2839: look for multiple flavors of hdf5 library names Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Applied as git hash [af17e67](https://github.com/EinsteinToolkit/ExternalLibraries-HDF5/commits/af17e67b3919f587c8a207585031ba64c628b706) "HDF5: look for multiple flavors of hdf5 library names" of [ExternalLibraries-HDF5](https://github.com/EinsteinToolkit/ExternalLibraries-HDF5) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2839/look-for-multiple-flavors-of-hdf5-library -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:16:29 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 16:16:29 +0000 Subject: [ET Trac] #2839: look for multiple flavors of hdf5 library names Message-ID: #2839: look for multiple flavors of hdf5 library names Reporter: Roland Haas Status: resolved Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2839/look-for-multiple-flavors-of-hdf5-library -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:17:49 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 16:17:49 +0000 Subject: [ET Trac] #2840: supplement rather than supercede auto-guessed data with gsl-config Message-ID: #2840: supplement rather than supercede auto-guessed data with gsl-config Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): Applied as git hash [84143cb](https://github.com/EinsteinToolkit/ExternalLibraries-GSL/commits/84143cb3ccf42e5c780fbdd59fa5185970e1632a) "GSL: supplement rather than supercese auto-guessed data with gsl-config" of [ExternalLibraries-GSL](https://github.com/EinsteinToolkit/ExternalLibraries-GSL) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2840/supplement-rather-than-supercede-auto -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:18:06 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 16:18:06 +0000 Subject: [ET Trac] #2840: supplement rather than supercede auto-guessed data with gsl-config Message-ID: #2840: supplement rather than supercede auto-guessed data with gsl-config Reporter: Roland Haas Status: resolved Milestone: Version: Type: bug Priority: minor Component: EinsteinToolkit thorn Changes (by Roland Haas): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2840/supplement-rather-than-supercede-auto -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:22:41 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 06 Mar 2025 16:22:41 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): Hello Alejandra. I suspect that the issue you are facing is indeed due to out of date parameter files / thorns. I?m investigating the status of `Punctures` and its example parameter files. I will update you as soon as I have news. In the meantime, I recommend using `TwoPuncturesX` for setting up initial data. This thorn is a port of the original `TwoPunctures` thorn and I can confirm it works well in practice. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:25:56 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 16:25:56 +0000 Subject: [ET Trac] #2838: supplement pkg-config information by h5cc Message-ID: #2838: supplement pkg-config information by h5cc Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Applied as git hash [8ce1523](https://github.com/EinsteinToolkit/ExternalLibraries-HDF5/commits/8ce1523d210300f6e5ac4a1f10ecdfc8023c378a) "HDF5: attempt to get missing LIBDIRS from h5cc" of [ExternalLibraries-HDF5](https://github.com/EinsteinToolkit/ExternalLibraries-HDF5) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2838/supplement-pkg-config-information-by-h5cc -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:26:15 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 16:26:15 +0000 Subject: [ET Trac] #2838: supplement pkg-config information by h5cc Message-ID: #2838: supplement pkg-config information by h5cc Reporter: Roland Haas Status: resolved Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2838/supplement-pkg-config-information-by-h5cc -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:29:01 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 06 Mar 2025 16:29:01 +0000 Subject: [ET Trac] #2862: Update `SpacetimeX/Z4c` robust stability paramete file Message-ID: #2862: Update `SpacetimeX/Z4c` robust stability paramete file Reporter: Lucas Timotheo Sanches Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn The current robust stability test parameter files in [SpacetimeX/Z4c](https://github.com/EinsteinToolkit/SpacetimeX/blob/main/Z4c/par/robust-stability.par) is out of date and does not work out of the box. The pull request [here](https://github.com/EinsteinToolkit/SpacetimeX/pull/56) addresses several issues preventing it from working correctly. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2862/update-spacetimex-z4c-robust-stability -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:29:29 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 06 Mar 2025 16:29:29 +0000 Subject: [ET Trac] #2862: Update `SpacetimeX/Z4c` robust stability paramete file Message-ID: #2862: Update `SpacetimeX/Z4c` robust stability paramete file Reporter: Lucas Timotheo Sanches Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): Pull request is [here](https://github.com/EinsteinToolkit/SpacetimeX/pull/56) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2862/update-spacetimex-z4c-robust-stability -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:29:40 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 06 Mar 2025 16:29:40 +0000 Subject: [ET Trac] #2862: Update `SpacetimeX/Z4c` robust stability paramete file Message-ID: #2862: Update `SpacetimeX/Z4c` robust stability paramete file Reporter: Lucas Timotheo Sanches Status: new Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): Please review -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2862/update-spacetimex-z4c-robust-stability -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 10:30:24 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 16:30:24 +0000 Subject: [ET Trac] #2862: Update `SpacetimeX/Z4c` robust stability paramete file Message-ID: #2862: Update `SpacetimeX/Z4c` robust stability paramete file Reporter: Lucas Timotheo Sanches Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: open (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2862/update-spacetimex-z4c-robust-stability -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 17:14:42 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 23:14:42 +0000 Subject: [ET Trac] #2863: simfactory does not correctly handle non existing files Message-ID: #2863: simfactory does not correctly handle non existing files Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: major Component: SimFactory mostly it just silently returns empty strings instead of reporting a failure -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2863/simfactory-does-not-correctly-handle-non -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 17:15:04 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 23:15:04 +0000 Subject: [ET Trac] #2863: simfactory does not correctly handle non existing files Message-ID: #2863: simfactory does not correctly handle non existing files Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: major Component: SimFactory Comment (by Roland Haas): Pull request is here: [https://bitbucket.org/simfactory/simfactory2/pull-requests/72](https://bitbucket.org/simfactory/simfactory2/pull-requests/72) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2863/simfactory-does-not-correctly-handle-non -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 6 17:17:08 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 06 Mar 2025 23:17:08 +0000 Subject: [ET Trac] #2863: simfactory does not correctly handle non existing files Message-ID: #2863: simfactory does not correctly handle non existing files Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: major Component: SimFactory Changes (by Roland Haas): status: open (was new) Comment (by Roland Haas): Please review -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2863/simfactory-does-not-correctly-handle-non -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri Mar 7 15:48:25 2025 From: trac-noreply at einsteintoolkit.org (Peter Diener) Date: Fri, 07 Mar 2025 21:48:25 +0000 Subject: [ET Trac] #2633: SummationByPart's Diff_gv aliased function does ont document which part of the grid the computed derivative is valid Message-ID: #2633: SummationByPart's Diff_gv aliased function does ont document which part of the grid the computed derivative is valid Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Comment (by Peter Diener): I suggest adding the following to the end of section 3.4: In both cases, the derivatives are not calculated in ghost zones of inter-processor or symmetry boundaries, i.e. the returned derivatives are undefined in ghost zones and will require synchronization of either the derivatives or the evolved fields depending on the scheme used. It would be wrong to switch to use one sided derivatives in ghost zones as, for most operators, the region, where one sided derivatives would be calculated, is larger than the ghost region. Hence some cells where centered finite differences could be calculated would contain one sided derivatives and the result would depend on the number of processors used. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2633/summationbyparts-diff_gv-aliased-function -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 10 05:45:12 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Mon, 10 Mar 2025 10:45:12 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Alejandra Gonzalez): Hello Lucas, thank you. For the record I was able to run `qc0` with the thorns: ``` ActiveThorns = " ADMBaseX CarpetX CoordinatesX ErrorEstimator Formaline IOUtil TwoPuncturesX " ``` with the following output: ``` INFO (Formaline): Writing tarballs with the Cactus sources into the directory "qc0/cactus-source" INFO (CarpetX): Setting initial values for max_grid_size values for all levels INFO (CarpetX): Setting up initial conditions... INFO (CarpetX): Iteration: 0 time: 0 delta_time: 0.25 INFO (CarpetX): Patch 0: INFO (CarpetX): Grid extent: INFO (CarpetX): gsh=[67,67,67] INFO (CarpetX): blocking_factor=[8,8,8] INFO (CarpetX): max_grid_size=[32,32,32] INFO (CarpetX): max_tile_size=[1024000,16,32] INFO (CarpetX): Domain extent: INFO (CarpetX): xmin=[-16,-16,-16] INFO (CarpetX): xmax=[16,16,16] INFO (CarpetX): base dx=[0.5,0.5,0.5] INFO (CarpetX): Initializing level 0... INFO (CarpetX): Regridding... INFO (CarpetX): level 0: 8 boxes, 262144 cells (100%) INFO (CarpetX): Initialized 1 levels INFO (CarpetX): OutputGH: iteration 0, time 0.000000, run time 5 s INFO (CarpetX): OutputSilo... Results from timer "OutputSilo": gettimeofday: 0.102 secs Results from timer "OutputSilo": getrusage: 0.085 secs INFO (CarpetX): OutputGH done. INFO (CarpetX): Starting evolution... INFO (CarpetX): Shutting down... Total GPU global memory (MB) spread across MPI: [64952 ... 64952] Free GPU global memory (MB) spread across MPI: [64165 ... 64165] [The Arena] space (MB) allocated spread across MPI: [48714 ... 48714] [The Arena] space (MB) used spread across MPI: [0 ... 0] [The Device Arena] space (MB) allocated spread across MPI: [8 ... 8] [The Device Arena] space (MB) used spread across MPI: [0 ... 0] [The Pinned Arena] space (MB) allocated spread across MPI: [8 ... 8] [The Pinned Arena] space (MB) used spread across MPI: [0 ... 0] AMReX (24.10) finalized -------------------------------------------------------------------------------- Done. ``` I would like to know if this is the expected verbose and if you have any suggestions about the type of output I should use \(openpmd, silo, etc\) while running with carpetx or if it?s irrelevant. ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 13 09:01:09 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 13 Mar 2025 14:01:09 +0000 Subject: [ET Trac] #2864: Spectre CCE exporter Message-ID: #2864: Spectre CCE exporter Reporter: Roland Haas Status: new Milestone: ET_2025_05 Version: Type: enhancement Priority: major Component: EinsteinToolkit thorn Include CCE exporter for [Spectre CCE code](https://spectre-code.org/tutorial_cce.html). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2864/spectre-cce-exporter -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 13 09:02:14 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 13 Mar 2025 14:02:14 +0000 Subject: [ET Trac] #2864: Spectre CCE exporter Message-ID: #2864: Spectre CCE exporter Reporter: Roland Haas Status: new Milestone: ET_2025_05 Version: Type: enhancement Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): @{5f2f18c8e8c45600229698f5} will review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2864/spectre-cce-exporter -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 13 09:02:36 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Thu, 13 Mar 2025 14:02:36 +0000 Subject: [ET Trac] #2864: Spectre CCE exporter Message-ID: #2864: Spectre CCE exporter Reporter: Roland Haas Status: open Milestone: ET_2025_05 Version: Type: enhancement Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: open (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2864/spectre-cce-exporter -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 13 10:51:27 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 13 Mar 2025 15:51:27 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): Hi Alejandra. I was unable to make `Punctures` work by simply modifying parameters, which suggests that the thorn has a more fundamental issue. This will need to be further investigated at another opportune moment. Regardless, as you noted `TwoPuncturesX` is the preferred option for initial data and should be used instead. Yes, your output seems to indicate that your execution of the parameter file was successful. As you may have noticed, this example parameter file only runs for a single iteration, which is probably not very useful for your needs. As for output formats, here?s an abbreviated guideline - Whenever you intend to visualize 3D data, use the `Silo` format. The `Silo` format can be used natively with [LLNL?s VisIt](https://visit-dav.github.io/visit-website/index.html). This is probably the easiest way to visualize `CarpetX` data, as it allows you to simply read the files and create plots by using a GUI. The `OpenPMD` file is also an option for visualization, but you may have to write custom Python scripts for it. - Whenever you wish to store data, in Checkpoints, for instance, the `ADIOS2` and `OpenPMD` files are adequate. - `TSV` data, which is plain text, not recommended for storage, in general. It is more of a debug format, where you can look at grid function values in a human readable manner. `TSV` data is also adequate for storing the multipolar extractions of the Weyl scalar and the location of the punctures throughout the simulation. I have compiled a more complex `qc0` parameter file, which uses `TwoPunctureX` for initial data, but also performs Apparent Horizon finding, puncture tracking and multipole extractions of the Psi4 Weyl scalar. This example should give you a good idea on what production run looks like and may be useful to your applications. ``` # Settings ################################# $itlast = 1000000000 $final_time = 200 $max_runtime = 23 * 60 # In minutes $xmin = -120.0 $xmax = +120.0 $ncells = 120 $nlevels = 7 $time_stepper = "RK4" $dtfac = 0.25 $error_threshold = 0.9 $out_every = 32 $out_silo_every = 64 * 8 $wave_extract_every = 32 ################################# ActiveThorns = " ADMBaseX AEILocalInterp AHFinderDirect BoxInBox CarpetX CoordinatesX IOUtil Multipole NewRadX ODESolvers PunctureTracker SphericalSurface TimerReport TmunuBaseX TwoPuncturesX WeylScal4 Z4c " # Driver Cactus::cctk_show_schedule = yes Cactus::presync_mode = "mixed-error" CarpetX::verbose = no CarpetX::poison_undefined_values = no # Run Termination Cactus::terminate = "any" Cactus::cctk_itlast = $itlast Cactus::cctk_final_time = $final_time Cactus::max_runtime = $max_runtime # Grid setup CarpetX::xmin = $xmin CarpetX::ymin = $xmin CarpetX::zmin = $xmin CarpetX::xmax = $xmax CarpetX::ymax = $xmax CarpetX::zmax = $xmax CarpetX::ncells_x = $ncells CarpetX::ncells_y = $ncells CarpetX::ncells_z = $ncells CarpetX::ghost_size = 3 CarpetX::interpolation_order = 3 CarpetX::prolongation_type = "ddf" CarpetX::prolongation_order = 5 # Boundary conditions CarpetX::boundary_x = "linear extrapolation" CarpetX::boundary_y = "linear extrapolation" CarpetX::boundary_z = "linear extrapolation" CarpetX::boundary_upper_x = "linear extrapolation" CarpetX::boundary_upper_y = "linear extrapolation" CarpetX::boundary_upper_z = "linear extrapolation" # Mesh refinement CarpetX::max_num_levels = $nlevels CarpetX::regrid_every = 128 CarpetX::regrid_error_threshold = $error_threshold BoxInBox::num_regions = 2 # Region 1 BoxInBox::shape_1 = "cube" BoxInBox::num_levels_1 = $nlevels BoxInBox::position_x_1 = +1.168642873 BoxInBox::radius_1 = [-1., 64., 16., 8., 4., 2., 1.] # Region 2 BoxInBox::shape_2 = "cube" BoxInBox::num_levels_2 = $nlevels BoxInBox::position_x_2 = -1.168642873 BoxInBox::radius_2 = [-1., 64., 16., 8., 4., 2., 1.] # Initial data ADMBaseX::initial_data = "TwoPunctures" ADMBaseX::initial_lapse = "TwoPunctures-averaged" TwoPuncturesX::verbose = yes TwoPuncturesX::par_b = 1.168642873 TwoPuncturesX::par_m_plus = 0.453 TwoPuncturesX::par_m_minus = 0.453 TwoPuncturesX::par_P_plus [1] = +0.3331917498 TwoPuncturesX::par_P_minus[1] = -0.3331917498 TwoPuncturesX::grid_setup_method = "evaluation" TwoPuncturesX::TP_epsilon = 1.0e-2 TwoPuncturesX::TP_Tiny = 1.0e-2 # Time Integration CarpetX::dtfac = $dtfac ODESolvers::verbose = no ODESolvers::method = $time_stepper # Spacetime evolution Z4c::calc_ADM_vars = yes #Required for computing the Weyl scalar Z4c::calc_ADMRHS_vars = yes #Required for computing the Weyl scalar Z4c::calc_constraints = yes Z4c::chi_floor = 1.0e-6 Z4c::alphaG_floor = 1.0e-8 Z4c::epsdiss = 0.32 Z4C::boundary_conditions = "NewRadX" # Spherical surfaces SphericalSurface::nsurfaces = 5 SphericalSurface::maxntheta = 39 SphericalSurface::maxnphi = 76 SphericalSurface::verbose = no # Surfaces 0 and 1 are used by PunctureTracker # Tracker 1 SphericalSurface::ntheta [0] = 39 SphericalSurface::nphi [0] = 76 SphericalSurface::nghoststheta [0] = 2 SphericalSurface::nghostsphi [0] = 2 # Tracker 2 SphericalSurface::ntheta [1] = 39 SphericalSurface::nphi [1] = 76 SphericalSurface::nghoststheta [1] = 2 SphericalSurface::nghostsphi [1] = 2 # Surfaces 2, 3, 4 are used by AHFinderDirect and QuasiLocalMeasures # Horizon 1 SphericalSurface::ntheta [2] = 39 SphericalSurface::nphi [2] = 76 SphericalSurface::nghoststheta [2] = 2 SphericalSurface::nghostsphi [2] = 2 # Horizon 2 SphericalSurface::ntheta [3] = 39 SphericalSurface::nphi [3] = 76 SphericalSurface::nghoststheta [3] = 2 SphericalSurface::nghostsphi [3] = 2 # Horizon 3 SphericalSurface::ntheta [4] = 39 SphericalSurface::nphi [4] = 76 SphericalSurface::nghoststheta [4] = 2 SphericalSurface::nghostsphi [4] = 2 # Puncture tracking PunctureTracker::verbose = no PunctureTracker::track_boxes = yes PunctureTracker::interp_order = 3 PunctureTracker::track [0] = yes PunctureTracker::initial_x [0] = +1.168642873 PunctureTracker::track [1] = yes PunctureTracker::initial_x [1] = -1.168642873 # Apparent horizons AHFinderDirect::find_every = $wave_extract_every AHFinderDirect::verbose_level = "physics details" AHFinderDirect::output_BH_diagnostics = "true" AHFinderDirect::run_at_CCTK_POST_RECOVER_VARIABLES = no AHFinderDirect::output_h_every = 0 # Turn off horizon shape output AHFinderDirect::max_Newton_iterations__initial = 50 AHFinderDirect::max_Newton_iterations__subsequent = 50 AHFinderDirect::max_allowable_Theta_growth_iterations = 10 AHFinderDirect::max_allowable_Theta_nonshrink_iterations = 10 AHFinderDirect::geometry_interpolator_name = "CarpetX" AHFinderDirect::geometry_interpolator_pars = "order=3 boundary_off_centering_tolerance={1.0e-10 1.0e-10 1.0e-10 1.0e-10 1.0e-10 1.0e-10} boundary_extrapolation_tolerance={0.0 0.0 0.0 0.0 0.0 0.0}" AHFinderDirect::surface_interpolator_name = "Lagrange polynomial interpolation" AHFinderDirect::surface_interpolator_pars = "order=3" AHFinderDirect::move_origins = yes AHFinderDirect::reshape_while_moving = yes AHFinderDirect::predict_origin_movement = yes AHFinderDirect::N_horizons = 3 AHFinderDirect::origin_x [1] = +1.168642873 AHFinderDirect::origin_y [1] = 0 AHFinderDirect::origin_z [1] = 0 AHFinderDirect::initial_guess_method [1] = "coordinate sphere" AHFinderDirect::initial_guess__coord_sphere__x_center[1] = +1.168642873 AHFinderDirect::initial_guess__coord_sphere__y_center[1] = 0 AHFinderDirect::initial_guess__coord_sphere__z_center[1] = 0 AHFinderDirect::initial_guess__coord_sphere__radius [1] = 0.25 AHFinderDirect::which_surface_to_store_info [1] = 2 AHFinderDirect::set_mask_for_individual_horizon [1] = no AHFinderDirect::reset_horizon_after_not_finding [1] = no AHFinderDirect::dont_find_after_individual_time [1] = 30.0 AHFinderDirect::origin_x [2] = -1.168642873 AHFinderDirect::origin_y [2] = 0 AHFinderDirect::origin_z [2] = 0 AHFinderDirect::initial_guess_method [2] = "coordinate sphere" AHFinderDirect::initial_guess__coord_sphere__x_center[2] = -1.168642873 AHFinderDirect::initial_guess__coord_sphere__y_center[2] = 0 AHFinderDirect::initial_guess__coord_sphere__z_center[2] = 0 AHFinderDirect::initial_guess__coord_sphere__radius [2] = 0.25 AHFinderDirect::which_surface_to_store_info [2] = 3 AHFinderDirect::reset_horizon_after_not_finding [2] = no AHFinderDirect::dont_find_after_individual_time [2] = 30.0 AHFinderDirect::origin_x [3] = 0.0 AHFinderDirect::origin_y [3] = 0 AHFinderDirect::origin_z [3] = 0 AHFinderDirect::initial_guess_method [3] = "coordinate sphere" AHFinderDirect::initial_guess__coord_sphere__x_center[3] = 0.0 AHFinderDirect::initial_guess__coord_sphere__y_center[3] = 0 AHFinderDirect::initial_guess__coord_sphere__z_center[3] = 0 AHFinderDirect::initial_guess__coord_sphere__radius [3] = 0.6 AHFinderDirect::which_surface_to_store_info [3] = 4 AHFinderDirect::find_after_individual_time [3] = 0.0 # Wave extraction WeylScal4::WeylScal4_psi4_calc_4th_calc_every = $wave_extract_every Multipole::verbose = no Multipole::nradii = 8 Multipole::radius[0] = 15 Multipole::radius[1] = 30 Multipole::radius[2] = 40 Multipole::radius[3] = 50 Multipole::radius[4] = 60 Multipole::radius[5] = 70 Multipole::radius[6] = 80 Multipole::radius[7] = 90 Multipole::ntheta = 120 Multipole::nphi = 240 Multipole::variables = " WeylScal4::Psi4r{sw=-2 cmplx='WeylScal4::Psi4i' name='Psi4'} " Multipole::out_every = $wave_extract_every Multipole::l_max = 4 Multipole::interpolator_pars = "order=3" # Checkpoint and recovery IO::out_dir = $parfile IO::out_every = $out_every IO::parfile_write = no IO::checkpoint_dir = "checkpoints_$parfile" IO::recover_dir = "checkpoints_$parfile" IO::checkpoint_ID = no IO::checkpoint_every_walltime_hours = 6 IO::checkpoint_on_terminate = yes IO::recover = "autoprobe" CarpetX::checkpoint_method = "openpmd" CarpetX::recover_method = "openpmd" # Output TimerReport::out_every = $out_every TimerReport::out_filename = "TimerReport" TimerReport::output_schedule_timers = no TimerReport::n_top_timers = 100 # Norm and reduction output CarpetX::out_norm_vars = "all" CarpetX::out_norm_omit_unstable = yes # 1D output CarpetX::out_tsv_vars = " PunctureTracker::pt_loc PunctureTracker::pt_vel " # 3D output CarpetX::out_silo_every = $out_silo_every CarpetX::out_silo_vars = " ADMBaseX::alp " ``` ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 13 10:58:33 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 13 Mar 2025 15:58:33 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): Hi Alejandra. I was unable to make `Punctures` work by simply modifying parameters, which suggests that the thorn has a more fundamental issue. This will need to be further investigated at another opportune moment. Regardless, as you noted `TwoPuncturesX` is the preferred option for initial data and should be used instead. Yes, your output seems to indicate that your execution of the parameter file was successful. As you may have noticed, this example parameter file only runs for a single iteration, which is probably not very useful for your needs. As for output formats, here?s an abbreviated guideline * Whenever you intend to visualize 3D data, use the `Silo` format. The `Silo` format can be used natively with [LLNL?s VisIt](https://visit-dav.github.io/visit-website/index.html). This is probably the easiest way to visualize `CarpetX` data, as it allows you to simply read the files and create plots by using a GUI. The `OpenPMD` file is also an option for visualization, but you may have to write custom Python scripts for it. * Whenever you wish to store data, in Checkpoints, for instance, the `ADIOS2` and `OpenPMD` files are adequate. * `TSV` data, which is plain text, not recommended for storage, in general. It is more of a debug format, where you can look at grid function values in a human readable manner. `TSV` data is also adequate for storing the multipolar extractions of the Weyl scalar and the location of the punctures throughout the simulation. ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 13 11:00:31 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 13 Mar 2025 16:00:31 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 13 11:04:25 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 13 Mar 2025 16:04:25 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): I have attached a more complex `qc0` parameter file, which uses `TwoPunctureX` for initial data, but also performs Apparent Horizon finding, puncture tracking and multipole extractions of the Psi4 Weyl scalar. This example should give you a good idea on what production run looks like and may be useful to your applications. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri Mar 14 05:56:57 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Fri, 14 Mar 2025 10:56:57 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Alejandra Gonzalez): Hi Lucas, Thank you very much. Just one more question regarding the parfile you are sharing: Where can I find the thorn \`AEILocalInterp\`? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri Mar 14 11:36:56 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Fri, 14 Mar 2025 16:36:56 +0000 Subject: [ET Trac] #2848: updates to FLRWSolver Message-ID: #2848: updates to FLRWSolver Reporter: Roland Haas Status: new Milestone: ET_2025_05 Version: Type: enhancement Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): @{557058:8bc23f2a-45c0-477d-8ac4-a5a16c734278} may be able to review. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2848/updates-to-flrwsolver -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue Mar 18 06:40:15 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Tue, 18 Mar 2025 11:40:15 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Alejandra Gonzalez): Hi Lucas, thank you so much for the information and the parfile. To run it I had to download some additional thorns, i.e. \`Multipole PunctureTracker AEILocalInterp WeylScal4 ?\` that I didn?t have before. But now I get a weird error in the HDF5 thorn: ``` libtool: compile: gfortran -I. -I../../src -std=f2008 -pedantic -Wall -Wextra -Wunderflow -Wimplicit-interface -Wsurprising -Waliasing -Wcharacter-truncation -Warray-temporaries -Wintrinsics-std -Wimplicit-procedure -Wreal-q-constant -Wfunction-elimination -Wrealloc-lhs -Wrealloc-lhs-all -Wno-c-binding-type -Wuse-without-only -Winteger-division -Wfrontend-loop-interchange -fcheck=all -g -Og -I../../src -I../../fortran/src -g -fcray-pointer -ffixed-line-length-none -O2 -fopenmp -c H5VLff.F90 -o H5VLff.o H5VLff.F90:40:7: 40 | USE H5GLOBAL | 1 Warning: USE statement at (1) has no ONLY qualifier [-Wuse-without-only] H5VLff.F90:41:7: 41 | USE H5fortkit | 1 Warning: USE statement at (1) has no ONLY qualifier [-Wuse-without-only] H5VLff.F90:41:7: Fatal Error: Cannot open module file ?h5fortkit.mod? for reading at (1): No such file or directory compilation terminated. ``` which I didn?t have before while compiling CarpetX with cuda. I attach my thornlist. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue Mar 18 06:40:44 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Tue, 18 Mar 2025 11:40:44 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Alejandra Gonzalez): thornlist being used -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue Mar 18 06:48:37 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Tue, 18 Mar 2025 11:48:37 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Alejandra Gonzalez): The thornlist being shared on the CarpetX wiki is this one: [https://bitbucket.org/einsteintoolkit/manifest/raw/master/einsteintoolkit.th](https://bitbucket.org/einsteintoolkit/manifest/raw/master/einsteintoolkit.th) However it doesn?t include TwoPuncturesX and many of the SpacetimeX thorns ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed Mar 19 09:07:28 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 19 Mar 2025 14:07:28 +0000 Subject: [ET Trac] #2839: look for multiple flavors of hdf5 library names Message-ID: #2839: look for multiple flavors of hdf5 library names Reporter: Roland Haas Status: resolved Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Additional fixes applied as git hash [1d69db0](https://github.com/EinsteinToolkit/ExternalLibraries-HDF5/commits/1d69db0c278105676c69ecd2865ae34dd021086d) "HDF5: correctly handle error return from find\_lib" of [ExternalLibraries-HDF5](https://github.com/EinsteinToolkit/ExternalLibraries-HDF5) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2839/look-for-multiple-flavors-of-hdf5-library -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed Mar 19 09:10:44 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Wed, 19 Mar 2025 14:10:44 +0000 Subject: [ET Trac] #2838: supplement pkg-config information by h5cc Message-ID: #2838: supplement pkg-config information by h5cc Reporter: Roland Haas Status: resolved Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Additional fixes as git hash [b5451d1](https://github.com/EinsteinToolkit/ExternalLibraries-HDF5/commits/b5451d17917704dd873c5c288c10ebc35d536971) "HDF5: add support for different sorts of h5cc" of [ExternalLibraries-HDF5](https://github.com/EinsteinToolkit/ExternalLibraries-HDF5) since `h5cc` provided on macOS is different from that on Linux and accepts different options. Still does not fix issues on homebrew where the pkg-config entry is not just missing information but returns incorrect library names `-lz -llibname-NOTFOUND -llibname-NOTFOUND` -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2838/supplement-pkg-config-information-by-h5cc -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed Mar 19 23:03:45 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 20 Mar 2025 04:03:45 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed Mar 19 23:09:44 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Thu, 20 Mar 2025 04:09:44 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): Hello Alejandra. ? Indeed, as you pointed out, the official Thornlists that include `CarpetX` don?t include `SpacetimeX`. This is because the thorns there are not yet part of the Einstein Toolkit. `Z4c` will probably be included in the next release, scheduled for May, but that is not yet certain. ? This means that this arrangement is still under active development and testing, but that should not stop you from using and exploring the thorns in there. ? Given the lack of official Thornlisists, I have attached to the issue the `spacetimex.th` file, which is the Thornlist that I personally use when interacting with these codes. I recommend that you do a clean checkout \(via `GetComponents`\) and a clean build of Cactus using this Thornlist. This will hopefully clear up your HDF5 problems -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri Mar 21 04:03:06 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Fri, 21 Mar 2025 09:03:06 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Alejandra Gonzalez): Hi Lucas, I am trying now to compile a clean Cactus directory from your thornlist \(which it seems that it solved now the HDF5 issue\) but the problem now is that it is trying to clone an external repository and the cluster I?m trying to compile it in has no internet access: ``` [ 11%] Creating directories for 'cmocka-populate' [ 22%] Performing download step (git clone) for 'cmocka-populate' Cloning into 'cmocka-src'... fatal: unable to access 'https://gitlab.com/cmocka/cmocka.git/': Failed to connect to gitlab.com port 443: Connection timed out Cloning into 'cmocka-src'... fatal: unable to access 'https://gitlab.com/cmocka/cmocka.git/': Failed to connect to gitlab.com port 443: Connection timed out Cloning into 'cmocka-src'... fatal: unable to access 'https://gitlab.com/cmocka/cmocka.git/': Failed to connect to gitlab.com port 443: Connection timed out Had to git clone more than once: 3 times. CMake Error at cmocka-subbuild/cmocka-populate-prefix/tmp/cmocka-populate-gitclone.cmake:50 (message): Failed to clone repository: 'https://gitlab.com/cmocka/cmocka.git' ``` this is similar to what happened to me before with openPMD \(here is the [ticket](https://bitbucket.org/einsteintoolkit/tickets/issues/2857/compiling-carpetx-with-openpmd)\) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri Mar 21 04:13:10 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Fri, 21 Mar 2025 09:13:10 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Alejandra Gonzalez): The associated thorn is \`ExternalLibraries-ssht\` -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri Mar 21 19:33:01 2025 From: trac-noreply at einsteintoolkit.org (Jose Eduardo Jaimes Barrera) Date: Sat, 22 Mar 2025 00:33:01 +0000 Subject: [ET Trac] #2865: Inquiry About Service Downtime Message-ID: #2865: Inquiry About Service Downtime Reporter: Jose Eduardo Jaimes Barrera Status: submitted Milestone: Version: Type: bug Priority: blocker Component: Hello Support Team, I would like to request information regarding the current status of Bitbucket's service, as we have been experiencing availability issues. 1. What is the cause of the current downtime? ? 2. Do you have an estimated time for the service to return to normal? ? 3. Given the impact this has had on our operations, is there any compensation or credit available for the service disruption? ? ? I appreciate your prompt response and any updates you can provide. attachment: Image.jfif (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2865/attachments/Image.jfif) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2865/inquiry-about-service-downtime -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri Mar 21 20:51:41 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sat, 22 Mar 2025 01:51:41 +0000 Subject: [ET Trac] #2865: Inquiry About Service Downtime Message-ID: #2865: Inquiry About Service Downtime Reporter: Jose Eduardo Jaimes Barrera Status: submitted Milestone: Version: Type: bug Priority: blocker Component: Changes (by Roland Haas): responsible: [] (was ) assignee: Roland Haas (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2865/inquiry-about-service-downtime -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri Mar 21 20:55:55 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sat, 22 Mar 2025 01:55:55 +0000 Subject: [ET Trac] #2865: Inquiry About Service Downtime Message-ID: #2865: Inquiry About Service Downtime Reporter: Jose Eduardo Jaimes Barrera Status: submitted Milestone: Version: Type: bug Priority: blocker Component: Comment (by Roland Haas): Hello Jose, unfortunately the ET maintainers have no more insight into the Bitbucket issue than you, since we just use the public services. Looking at the status page \(linked in the yellow banner on top of the screen\): [https://bitbucket.status.atlassian.com/incidents/6lzhx12yy2bt](https://bitbucket.status.atlassian.com/incidents/6lzhx12yy2bt) Atlassian says the issue has been resolved and indeed it seems to work fine for me right now. Downdetector [https://downdetector.com/status/bitbucket/](https://downdetector.com/status/bitbucket/) also seems to show that things are back to normal. Please try downloading again, and hopefully things will work. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2865/inquiry-about-service-downtime -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Fri Mar 21 20:56:09 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Sat, 22 Mar 2025 01:56:09 +0000 Subject: [ET Trac] #2865: Inquiry About Service Downtime Message-ID: #2865: Inquiry About Service Downtime Reporter: Jose Eduardo Jaimes Barrera Status: open Milestone: Version: Type: bug Priority: blocker Component: Changes (by Roland Haas): status: open (was submitted) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2865/inquiry-about-service-downtime -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 24 08:21:25 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 24 Mar 2025 13:21:25 +0000 Subject: [ET Trac] #2865: Inquiry About Service Downtime Message-ID: #2865: Inquiry About Service Downtime Reporter: Jose Eduardo Jaimes Barrera Status: resolved Milestone: Version: Type: bug Priority: blocker Component: Changes (by Roland Haas): status: resolved (was open) Comment (by Roland Haas): Bitbucket is back online. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2865/inquiry-about-service-downtime -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 24 08:35:37 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 24 Mar 2025 13:35:37 +0000 Subject: [ET Trac] #2848: updates to FLRWSolver Message-ID: #2848: updates to FLRWSolver Reporter: Roland Haas Status: new Milestone: ET_2025_05 Version: Type: enhancement Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): This currently \(as for [2c80c39](https://github.com/hayleyjm/FLRWSolver_public/commits/2c80c39bd726441dbb5a6d6343644c40a1af5db0) "updates to documentation and README" of [FLRWSolver\_public](https://github.com/hayleyjm/FLRWSolver_public)\) causes a test failure in test \`FLRW\_powerspec\_exact\_test\` [https://einsteintoolkit.github.io/tests/build\_1120.html](https://einsteintoolkit.github.io/tests/build_1120.html) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2848/updates-to-flrwsolver -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 24 08:37:42 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 24 Mar 2025 13:37:42 +0000 Subject: [ET Trac] #2848: updates to FLRWSolver Message-ID: #2848: updates to FLRWSolver Reporter: Roland Haas Status: open Milestone: ET_2025_05 Version: Type: enhancement Priority: major Component: EinsteinToolkit thorn Changes (by Roland Haas): status: open (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2848/updates-to-flrwsolver -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Tue Mar 25 10:36:37 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Tue, 25 Mar 2025 15:36:37 +0000 Subject: [ET Trac] #2864: Spectre CCE exporter Message-ID: #2864: Spectre CCE exporter Reporter: Roland Haas Status: open Milestone: ET_2025_05 Version: Type: enhancement Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Are there any updates on this \(review or code status wise\)? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2864/spectre-cce-exporter -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Wed Mar 26 11:27:09 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Wed, 26 Mar 2025 16:27:09 +0000 Subject: [ET Trac] #2864: Spectre CCE exporter Message-ID: #2864: Spectre CCE exporter Reporter: Roland Haas Status: open Milestone: ET_2025_05 Version: Type: enhancement Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): I have received access to the code and began reviewing it today \(03/26/2025\) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2864/spectre-cce-exporter -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Thu Mar 27 22:34:02 2025 From: trac-noreply at einsteintoolkit.org (Lucas Timotheo Sanches) Date: Fri, 28 Mar 2025 03:34:02 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Lucas Timotheo Sanches): @{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} May be better suited than me to help you out with these specific issues -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 31 07:42:11 2025 From: trac-noreply at einsteintoolkit.org (Alejandra Gonzalez) Date: Mon, 31 Mar 2025 12:42:11 +0000 Subject: [ET Trac] #2861: Running qc0 with CarpetX Message-ID: #2861: Running qc0 with CarpetX Reporter: Alejandra Gonzalez Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Alejandra Gonzalez): Thanks again Lucas. I?m now running the parfile you sent earlier without issues. I will let you know if I encounter some other issue :\) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 31 07:58:29 2025 From: trac-noreply at einsteintoolkit.org (Cadrante de estrelas) Date: Mon, 31 Mar 2025 12:58:29 +0000 Subject: [ET Trac] #2866: Problem while building the ET on MN5: OpenCL Message-ID: #2866: Problem while building the ET on MN5: OpenCL Reporter: Cadrante de estrelas Status: submitted Milestone: Version: Type: bug Priority: blocker Component: Cactus Hello again: while building the toolkit on the cluster Marenostrum 5 I obtain the following error related with the absence of a particular file in the OpenCL folder: ? _COMPILING ExternalLibraries/OpenCL/src/info.c_ _**/gpfs/projects/uib104/local/etoolkit2/Cactus/configs/sim/build/OpenCL/info.c:13:10: fatal error:** CL/cl.h: No such file or directory_ ?? _13 | #include ****_ ? ? ? _|? ? ? ? ? **^~~~~~~~~**_ _compilation terminated._ _make\[3\]: \*\*\* \[/gpfs/projects/uib104/local/etoolkit2/Cactus/configs/sim/config-data/make.config.rules:267: info.c.o\] Error 1_ _make\[2\]: \*\*\* \[/gpfs/projects/uib104/local/etoolkit2/Cactus/lib/make/make.thornlib:113: make.checked\] Error 2_ _make\[1\]: \*\*\* \[/gpfs/projects/uib104/local/etoolkit2/Cactus/lib/make/make.configuration:179: /gpfs/projects/uib104/local/etoolkit2/Cactus/configs/sim/lib/libthorn\_OpenCL.a\] Error 2_ _make: \*\*\* \[Makefile:265: sim\] Error 2_ ? I am really stuck at this point? I am using the same cfg file as other members of my research group, the only difference is that I am not using CUDA, so I commented every line related to. I have attached it to this message just in case is necessary. ? Thanks! ? attachment: marenostrum5.cfg (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2866/attachments/marenostrum5.cfg) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2866/problem-while-building-the-et-on-mn5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 31 09:26:55 2025 From: trac-noreply at einsteintoolkit.org (Roland Haas) Date: Mon, 31 Mar 2025 14:26:55 +0000 Subject: [ET Trac] #2866: Problem while building the ET on MN5: OpenCL Message-ID: #2866: Problem while building the ET on MN5: OpenCL Reporter: Samuel G?mez Status: submitted Milestone: Version: Type: bug Priority: blocker Component: Cactus Comment (by Roland Haas): If you don?t need OpenCL I?d disable ExternalLibraries/OpenCL -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2866/problem-while-building-the-et-on-mn5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 31 15:34:23 2025 From: trac-noreply at einsteintoolkit.org (Keith Dow) Date: Mon, 31 Mar 2025 20:34:23 +0000 Subject: [ET Trac] #2867: WaveToyX examples, HDF5 output error in all three examples. Message-ID: #2867: WaveToyX examples, HDF5 output error in all three examples. Reporter: Keith Dow Status: submitted Milestone: ET_2024_11 Version: ET_2024_05 Type: bug Priority: minor Component: EinsteinToolkit thorn ?evict\_on\_close\(\)? is currently not supported in parallel HDF5 -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2867/wavetoyx-examples-hdf5-output-error-in-all -------------- next part -------------- An HTML attachment was scrubbed... URL: From trac-noreply at einsteintoolkit.org Mon Mar 31 15:35:18 2025 From: trac-noreply at einsteintoolkit.org (Keith Dow) Date: Mon, 31 Mar 2025 20:35:18 +0000 Subject: [ET Trac] #2867: WaveToyX examples, HDF5 output error in all three examples. Message-ID: #2867: WaveToyX examples, HDF5 output error in all three examples. Reporter: Keith Dow Status: submitted Milestone: ET_2024_11 Version: ET_2024_05 Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Keith Dow): I am not sure if this effects Kuibit working. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2867/wavetoyx-examples-hdf5-output-error-in-all -------------- next part -------------- An HTML attachment was scrubbed... URL: