From users at einsteintoolkit.org Mon Jun 1 15:18:01 2026 From: users at einsteintoolkit.org (users at einsteintoolkit.org) Date: Mon, 01 Jun 2026 15:18:01 -0500 Subject: [Users] Agenda for Thursday's Meeting Message-ID: <6a1de8f9.63eMowCatAXhe2pI%users@einsteintoolkit.org> Please update the Wiki with agenda items for Thursday's meeting. Thanks! https://docs.einsteintoolkit.org/et-docs/meeting_agenda --The Maintainers From users at einsteintoolkit.org Wed Jun 3 17:15:02 2026 From: users at einsteintoolkit.org (users at einsteintoolkit.org) Date: Wed, 03 Jun 2026 17:15:02 -0500 Subject: [Users] Einstein Toolkit Meeting Reminder Message-ID: <6a20a766.DbX1XOzNJj44aQiC%users@einsteintoolkit.org> Hello, Please consider joining the weekly Einstein Toolkit phone call at 9:00 am US central time on Thursdays. For details on how to connect and what agenda items are to be discussed, use the link below. https://docs.einsteintoolkit.org/et-docs/Main_Page#Weekly_Users_Call --The Maintainers From jnicoules at ua.pt Thu Jun 4 08:31:37 2026 From: jnicoules at ua.pt (Jordan Nicoules) Date: Thu, 4 Jun 2026 13:31:37 +0000 Subject: [Users] Automatic termination trigger mid-run Message-ID: <325e4562ebd24b16b0c5e943b171fa12@ua.pt> Dear all, I was wondering if there was a built-in way to trigger the termination of a simulation when something specific happens, along the lines of what Trigger does to steer quantities. From what I understand, Trigger does not offer that possibility, and TerminationTrigger checks either a file or a time limit. What I'm considering would be more along the lines of "an apparent horizon is found so trigger termination", in order to steer some parameters at recovery. If there's no such explicit way, I'm happy to try to implement that in Trigger. I actually have ideas of other small improvements to Trigger that I could try contributing as well (namely, increase the maximum number of triggers and allow one trigger to have multiple consequences at once). Unfortunately I won't be able to join the weekly call today to discuss this directly. Best, Jordan -------------- next part -------------- An HTML attachment was scrubbed... URL: From schnetter at gmail.com Thu Jun 4 08:57:49 2026 From: schnetter at gmail.com (Erik Schnetter) Date: Thu, 4 Jun 2026 09:57:49 -0400 Subject: [Users] Automatic termination trigger mid-run In-Reply-To: <325e4562ebd24b16b0c5e943b171fa12@ua.pt> References: <325e4562ebd24b16b0c5e943b171fa12@ua.pt> Message-ID: <219D6265-660E-47DB-9D77-864EB5D32167@gmail.com> You can call the function `CCTK_TerminateNext`, which will stop the simulation gracefully after the current iteration finishes. This is built-in, you do not need a special thorn for this. This is how TerminationTrigger is implemented: It calls this function when a certain file is created. -erik > On Jun 4, 2026, at 09:31, Jordan Nicoules via Users wrote: > > Dear all, > > I was wondering if there was a built-in way to trigger the termination of a simulation when something specific happens, along the lines of what Trigger does to steer quantities. From what I understand, Trigger does not offer that possibility, and TerminationTrigger checks either a file or a time limit. What I'm considering would be more along the lines of "an apparent horizon is found so trigger termination", in order to steer some parameters at recovery. > > If there's no such explicit way, I'm happy to try to implement that in Trigger. I actually have ideas of other small improvements to Trigger that I could try contributing as well (namely, increase the maximum number of triggers and allow one trigger to have multiple consequences at once). > > Unfortunately I won't be able to join the weekly call today to discuss this directly. > > Best, > > Jordan > _______________________________________________ > Users mailing list > Users at einsteintoolkit.org > http://lists.einsteintoolkit.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From jnicoules at ua.pt Thu Jun 4 09:19:40 2026 From: jnicoules at ua.pt (Jordan Nicoules) Date: Thu, 4 Jun 2026 14:19:40 +0000 Subject: [Users] Automatic termination trigger mid-run In-Reply-To: <219D6265-660E-47DB-9D77-864EB5D32167@gmail.com> References: <325e4562ebd24b16b0c5e943b171fa12@ua.pt>, <219D6265-660E-47DB-9D77-864EB5D32167@gmail.com> Message-ID: <381626e0f1244b41af2d31e28bfb3d17@ua.pt> Hi Erik, Thank you for your reply! I know of CCTK_TerminateNext, I actually use it in one of my thorns (so I could hack it to achieve what I want). In fact, a call to this function is what I would add to Trigger. My point is more: with the existing thorns, is there a way to terminate a simulation while it's running (and before its expected end based on final time/iteration), with a parfile directive, without: - manually editing the termination file - reaching walltime - having NaNs - and such edge cases. Something that would be like: ``` Trigger::Trigger_Checked_Variable [0] = "ADMBase::lapse" Trigger::Trigger_Reduction [0] = "minimum" Trigger::Trigger_Relation [0] = "<" Trigger::Trigger_Checked_Value [0] = 0.2 Trigger::Trigger_Reaction [0] = "terminate" # <-- This doesn't exist as far as I understand ``` Thanks, Jordan ________________________________ From: Users on behalf of Erik Schnetter via Users Sent: Thursday, June 4, 2026 14:57 To: users at einsteintoolkit.org Subject: Re: [Users] Automatic termination trigger mid-run CUIDADO: Email de um sistema externo. Cuidado com links, anexos e pedidos de dados/senhas. CAUTION: Email from an external system. Be careful with links, attachments, and requests for data/passwords. You can call the function `CCTK_TerminateNext`, which will stop the simulation gracefully after the current iteration finishes. This is built-in, you do not need a special thorn for this. This is how TerminationTrigger is implemented: It calls this function when a certain file is created. -erik On Jun 4, 2026, at 09:31, Jordan Nicoules via Users wrote: Dear all, I was wondering if there was a built-in way to trigger the termination of a simulation when something specific happens, along the lines of what Trigger does to steer quantities. From what I understand, Trigger does not offer that possibility, and TerminationTrigger checks either a file or a time limit. What I'm considering would be more along the lines of "an apparent horizon is found so trigger termination", in order to steer some parameters at recovery. If there's no such explicit way, I'm happy to try to implement that in Trigger. I actually have ideas of other small improvements to Trigger that I could try contributing as well (namely, increase the maximum number of triggers and allow one trigger to have multiple consequences at once). Unfortunately I won't be able to join the weekly call today to discuss this directly. Best, Jordan _______________________________________________ Users mailing list Users at einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From lucas.t.s.carneiro at gmail.com Thu Jun 4 10:13:31 2026 From: lucas.t.s.carneiro at gmail.com (Lucas Timotheo Sanches) Date: Thu, 4 Jun 2026 10:13:31 -0500 Subject: [Users] Meeting Minutes for 2026-06-04 Message-ID: Attendees: Lucas (minutes), Peter Diener, Roland Hass (chair), Beyhanm, Deborah Ferguson, Johnny Tsao, Maxwell Rizzo, Nikolai Wallin, Noora Ghadiri, Zach Etienne # ET_2026_05 release ## Gallery runs - Debporah's run: Something is wrong with the stampede build, her student ran and the trajectories were off. She's also having trouble with the derivatives - Johnny is encountering a difference when running his (Poisson equation). He says if he uses the number of processes Steve used he gets different results, if he uses 1 he gets the same results. He sees a left to right shift. Roland says that if the thing gets shifted to the right its OK, its taking a couple of iterations longer to converge. - Noora reports having some allocation issues but promises to have it done by next week. ## Test suite runners - Deborah is debuging on stampede 3. No luck yet. Will report back. - Cottonmouth fails on sunrise and cosma, but the info is outdated, thorns have had updates. The test runners will try again. - Noora reports all tests passing on frontera, but have not updated the webpage yet. - McLachlan fails on delta, queen bee and sunrise. Peter concludes it was a tolerance issue, he will update the tests and the test page. - Checkpoint failing on delta, anvil and expense. Roland asks for log files for this specific failure and will look at them. - TwoPuncturesX fails on delta. Cheng-Hsin is defending, so Lucas and Noora will coordinate to see who has more time and try to run there. ## Thorn Reviews - Bhahaha: Will have a vote next weeks for final inclusion. - CanudaX: vote in 2 weeks or after. - Cottonmouth: Zach is reviewing the Einstein Engine repo, he will have a list of updated issues soon. - Boost: Its in, some people have been using it already, no issues so far. Up for vote next week. - TwoPuncturesX: Approved, up for vote next week, # ET Workshop at UIUC - Its happening! - Total participant numbers is about 100 people, with 50 in person and 50 online - The tutorial server boss (Steve) is away so for now you are on your own. # Mailing list questions - Jordan asks about termination functionality. Roland will respond to him on the mailing list. # Tickets 2916: New issues for Cottonmouth Review. 2952: 2950: We can't do point 3 before doing point 1, because we don't have conditional storage yet. 2944: Roland suggests splitting up the issue list in more than one ticket. Because this thorn is very close to Multipole, many of the issues pointed out here should also be fixed on that thorn. 2949: C23 reserves the bool keyword, and the flesh requires some changes. 2948: Requires conditional storage. From schnetter at gmail.com Thu Jun 4 10:23:57 2026 From: schnetter at gmail.com (Erik Schnetter) Date: Thu, 4 Jun 2026 11:23:57 -0400 Subject: [Users] Automatic termination trigger mid-run In-Reply-To: <381626e0f1244b41af2d31e28bfb3d17@ua.pt> References: <325e4562ebd24b16b0c5e943b171fa12@ua.pt> <219D6265-660E-47DB-9D77-864EB5D32167@gmail.com> <381626e0f1244b41af2d31e28bfb3d17@ua.pt> Message-ID: Ooh, you are using the "Trigger" thorn. I thought you were using "TerminationTrigger". So that's an option -- use that thorn instead. Otherwise, if you find your requested feature convenient, then please go ahead and implement it! It would be a nice addition to Cactus. -erik > On Jun 4, 2026, at 10:19, Jordan Nicoules wrote: > > Hi Erik, > > Thank you for your reply! I know of CCTK_TerminateNext, I actually use it in one of my thorns (so I could hack it to achieve what I want). In fact, a call to this function is what I would add to Trigger. > > My point is more: with the existing thorns, is there a way to terminate a simulation while it's running (and before its expected end based on final time/iteration), with a parfile directive, without: > - manually editing the termination file > - reaching walltime > - having NaNs > - and such edge cases. > > Something that would be like: > ``` > Trigger::Trigger_Checked_Variable [0] = "ADMBase::lapse" > Trigger::Trigger_Reduction [0] = "minimum" > Trigger::Trigger_Relation [0] = "<" > Trigger::Trigger_Checked_Value [0] = 0.2 > Trigger::Trigger_Reaction [0] = "terminate" # <-- This doesn't exist as far as I understand > ``` > > Thanks, > > Jordan > > From: Users > on behalf of Erik Schnetter via Users > > Sent: Thursday, June 4, 2026 14:57 > To: users at einsteintoolkit.org > Subject: Re: [Users] Automatic termination trigger mid-run > > > CUIDADO: Email de um sistema externo. Cuidado com links, anexos e pedidos de dados/senhas. > CAUTION: Email from an external system. Be careful with links, attachments, and requests for data/passwords. > You can call the function `CCTK_TerminateNext`, which will stop the simulation gracefully after the current iteration finishes. This is built-in, you do not need a special thorn for this. > > This is how TerminationTrigger is implemented: It calls this function when a certain file is created. > > -erik > >> On Jun 4, 2026, at 09:31, Jordan Nicoules via Users wrote: >> >> Dear all, >> >> I was wondering if there was a built-in way to trigger the termination of a simulation when something specific happens, along the lines of what Trigger does to steer quantities. From what I understand, Trigger does not offer that possibility, and TerminationTrigger checks either a file or a time limit. What I'm considering would be more along the lines of "an apparent horizon is found so trigger termination", in order to steer some parameters at recovery. >> >> If there's no such explicit way, I'm happy to try to implement that in Trigger. I actually have ideas of other small improvements to Trigger that I could try contributing as well (namely, increase the maximum number of triggers and allow one trigger to have multiple consequences at once). >> >> Unfortunately I won't be able to join the weekly call today to discuss this directly. >> >> Best, >> >> Jordan >> _______________________________________________ >> Users mailing list >> Users at einsteintoolkit.org >> http://lists.einsteintoolkit.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhaas at mail.ubc.ca Thu Jun 4 10:27:40 2026 From: rhaas at mail.ubc.ca (Roland Haas) Date: Thu, 4 Jun 2026 08:27:40 -0700 Subject: [Users] Automatic termination trigger mid-run In-Reply-To: References: <325e4562ebd24b16b0c5e943b171fa12@ua.pt> <219D6265-660E-47DB-9D77-864EB5D32167@gmail.com> <381626e0f1244b41af2d31e28bfb3d17@ua.pt> Message-ID: <20260604082740.7282573a@haengie2.phas.ubc.ca> Hello all, Trigger can set parameters and there's a Cactus::terminate_next parameter (src/param.ccl) that you can set. You may need to then add `Cactus::terminate_next = no`) into your parfile (so that when the checkpoint recovers the steered value of terminate_next is overwritten). Yours, Roland > [CAUTION: Non-UBC Email] > > Ooh, you are using the "Trigger" thorn. I thought you were using "TerminationTrigger". So that's an option -- use that thorn instead. > > Otherwise, if you find your requested feature convenient, then please go ahead and implement it! It would be a nice addition to Cactus. > > -erik > > > On Jun 4, 2026, at 10:19, Jordan Nicoules wrote: > > > > Hi Erik, > > > > Thank you for your reply! I know of CCTK_TerminateNext, I actually use it in one of my thorns (so I could hack it to achieve what I want). In fact, a call to this function is what I would add to Trigger. > > > > My point is more: with the existing thorns, is there a way to terminate a simulation while it's running (and before its expected end based on final time/iteration), with a parfile directive, without: > > - manually editing the termination file > > - reaching walltime > > - having NaNs > > - and such edge cases. > > > > Something that would be like: > > ``` > > Trigger::Trigger_Checked_Variable [0] = "ADMBase::lapse" > > Trigger::Trigger_Reduction [0] = "minimum" > > Trigger::Trigger_Relation [0] = "<" > > Trigger::Trigger_Checked_Value [0] = 0.2 > > Trigger::Trigger_Reaction [0] = "terminate" # <-- This doesn't exist as far as I understand > > ``` > > > > Thanks, > > > > Jordan > > > > From: Users > on behalf of Erik Schnetter via Users > > > Sent: Thursday, June 4, 2026 14:57 > > To: users at einsteintoolkit.org > > Subject: Re: [Users] Automatic termination trigger mid-run > > > > > > CUIDADO: Email de um sistema externo. Cuidado com links, anexos e pedidos de dados/senhas. > > CAUTION: Email from an external system. Be careful with links, attachments, and requests for data/passwords. > > You can call the function `CCTK_TerminateNext`, which will stop the simulation gracefully after the current iteration finishes. This is built-in, you do not need a special thorn for this. > > > > This is how TerminationTrigger is implemented: It calls this function when a certain file is created. > > > > -erik > > > >> On Jun 4, 2026, at 09:31, Jordan Nicoules via Users wrote: > >> > >> Dear all, > >> > >> I was wondering if there was a built-in way to trigger the termination of a simulation when something specific happens, along the lines of what Trigger does to steer quantities. From what I understand, Trigger does not offer that possibility, and TerminationTrigger checks either a file or a time limit. What I'm considering would be more along the lines of "an apparent horizon is found so trigger termination", in order to steer some parameters at recovery. > >> > >> If there's no such explicit way, I'm happy to try to implement that in Trigger. I actually have ideas of other small improvements to Trigger that I could try contributing as well (namely, increase the maximum number of triggers and allow one trigger to have multiple consequences at once). > >> > >> Unfortunately I won't be able to join the weekly call today to discuss this directly. > >> > >> Best, > >> > >> Jordan > >> _______________________________________________ > >> Users mailing list > >> Users at einsteintoolkit.org > >> http://lists.einsteintoolkit.org/mailman/listinfo/users > -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://pgp.mit.edu . From skylar2kaisa at gmail.com Mon Jun 1 16:38:32 2026 From: skylar2kaisa at gmail.com (Rodney) Date: Mon, 1 Jun 2026 23:38:32 +0200 Subject: [Users] =?utf-8?q?Code_Submission_/_Project_Showcase=3A_NOVA-?= =?utf-8?q?=CE=A9_Lightweight_Relativistic_Accretion_Engine?= Message-ID: I wanted to share a lightweight, self-contained Python numerical simulation framework I have developed called NOVA-?. The project consists of two distinct 2D orbital simulation engines rendered in real-time via a highly optimized, flicker-free cell-buffer terminal matrix utilizing DEC 2026 synchronized output: 1. An Advection-Diffusion Variant: Utilizing a direct radial-velocity decay model ($\frac{dr}{dt} \propto -r^{-2}$) designed for fluid-like particle ring visualization. 2. A Dynamical Relativistic Variant: Integrating a true Schwarzschild-limit effective potential force calculation containing the strong-field correction term ($-3GL^2 / r^4$). This engine features continuous orbital energy dissipation via a localized distance-scaled drag gradient and successfully models the conservation of angular momentum by dynamically scaling the central singularity?s global spin metric ($\Omega $) upon event horizon ingestion. The entire framework is written in pure Python without heavy external dependencies, allowing it to execute deep strong-field physics calculations and multi-body boundary transformations in a fraction of a millisecond per frame. I believe this could serve as an excellent, lightweight educational tool, a visual toy-model for testing non-vacuum binary perturbations, or an inspiring example of optimizing terminal-based physics rendering. The public repository containing the codebases can be found here: https://github.com/skylar2kaisa-gif/NOVA--A-2D-Fluid-Velocity-Approximation-Engine-for-Accretion-Dynamics/tree/main I would love to hear your thoughts, feedback, or any potential paths for integration into community educational resources. Best regards, Rodney de Rijk Lead Developer, NOVA-? Project -------------- next part -------------- An HTML attachment was scrubbed... URL: From skylar2kaisa at gmail.com Mon Jun 1 17:39:12 2026 From: skylar2kaisa at gmail.com (Rodney) Date: Tue, 2 Jun 2026 00:39:12 +0200 Subject: [Users] =?utf-8?q?Code_Submission_/_Project_Showcase=3A_NOVA-?= =?utf-8?q?=CE=A9_Lightweight_Relativistic_Accretion_Engine?= In-Reply-To: References: Message-ID: To summarize: Subject: External Tool Announcement: NOVA-? 2D Fluid Velocity Approximation Engine *Hello Einstein Toolkit Community,* *I want to share an open-source tool I've developed called NOVA-?. It is a standalone, self-contained Python framework designed for 2D fluid velocity approximations and accretion kinematics, featuring effective relativistic potentials (Schwarzschild strong-field corrections).* *While it is not written as a Cactus thorn, it serves as a lightweight, interactive tool (rendering directly to an ANSI terminal) that can be useful for students or researchers looking for rapid prototyping of accretion behaviors before launching heavy numerical relativity simulations.* *You can check out the repository here: * https://github.com/skylar2kaisa-gif/NOVA--A-2D-Fluid-Velocity-Approximation-Engine-for-Accretion-Dynamics *Feedback is highly appreciated!* On Mon, Jun 1, 2026 at 11:38?PM Rodney wrote: > I wanted to share a lightweight, self-contained Python numerical > simulation framework I have developed called NOVA-?. > The project consists of two distinct 2D orbital simulation engines > rendered in real-time via a highly optimized, flicker-free cell-buffer > terminal matrix utilizing DEC 2026 synchronized output: > > 1. An Advection-Diffusion Variant: Utilizing a direct radial-velocity > decay model ($\frac{dr}{dt} \propto -r^{-2}$) designed for fluid-like > particle ring visualization. > 2. A Dynamical Relativistic Variant: Integrating a true > Schwarzschild-limit effective potential force calculation containing the > strong-field correction term ($-3GL^2 / r^4$). This engine features > continuous orbital energy dissipation via a localized distance-scaled drag > gradient and successfully models the conservation of angular momentum by > dynamically scaling the central singularity?s global spin metric ($\Omega > $) upon event horizon ingestion. > > The entire framework is written in pure Python without heavy external > dependencies, allowing it to execute deep strong-field physics calculations > and multi-body boundary transformations in a fraction of a millisecond per > frame. > I believe this could serve as an excellent, lightweight educational tool, > a visual toy-model for testing non-vacuum binary perturbations, or an > inspiring example of optimizing terminal-based physics rendering. > The public repository containing the codebases can be found here: > https://github.com/skylar2kaisa-gif/NOVA--A-2D-Fluid-Velocity-Approximation-Engine-for-Accretion-Dynamics/tree/main > I would love to hear your thoughts, feedback, or any potential paths for > integration into community educational resources. > Best regards, > Rodney de Rijk > Lead Developer, NOVA-? Project > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jorge.mio at correo.nucleares.unam.mx Tue Jun 2 12:17:18 2026 From: jorge.mio at correo.nucleares.unam.mx (Jorge Yahir Mio) Date: Tue, 2 Jun 2026 11:17:18 -0600 Subject: [Users] Question about restarting a simulation from checkpoint data Message-ID: Dear Einstein Toolkit users, I am currently working with the Einstein Toolkit and trying to use checkpoint/restart functionality to recover simulations. I understand the parameters that must be included in the parameter file, but I am not sure how I should correctly restart a simulation from existing checkpoint data. So far, I have been launching simulations with commands such as ./simfactory/bin/sim run ProcaStar -workstation-parfile=par/ProcaStar.par and the simulation runs correctly and generates checkpoint files. However, when I try to restart from the checkpoint data, I am unsure what the correct procedure should be. I do not know whether I should use a different SimFactory command, modify the submission procedure, or provide additional options. The checkpoint-related parameters in my parameter file are: CarpetIOHDF5::checkpoint = yes IOUtil::checkpoint_every_walltime_hours = 0.1 IOUtil::checkpoint_dir = "checkpoints_prueba" IOUtil::checkpoint_keep = 1 IOUtil::checkpoint_ID = no IOUtil::checkpoint_on_terminate = yes IOUtil::recover = "autoprobe" IOUtil::recover_dir = "checkpoints_prueba" IOUtil::abort_on_io_errors = yes CarpetIOHDF5::open_one_input_file_at_a_time = yes Could someone please clarify the recommended procedure for restarting a simulation from existing checkpoint files? In particular: 1. Which SimFactory command should be used to restart a simulation? 2. Is it necessary to create a new run or continue the existing one? 3. Are there any additional parameters or directory requirements for recovery to work correctly? My environment is: Einstein Toolkit version: ET_2025_05 Operating system: Linux Ubuntu 22.04.5 LTS Cluster/machine: Local Thank you very much for your help. Best regards, Yahir Mio -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhaas at mail.ubc.ca Thu Jun 4 10:44:31 2026 From: rhaas at mail.ubc.ca (Roland Haas) Date: Thu, 4 Jun 2026 08:44:31 -0700 Subject: [Users] Question about restarting a simulation from checkpoint data In-Reply-To: References: Message-ID: <20260604084431.778515db@haengie2.phas.ubc.ca> Hello all, This is also addressed in the chat: https://matrix.to/#/%21mYSgqyShRCoThqmUmY%3Agitter.im/%24GoGyO7PMmaXQPBip5Jjk5T5dycsBi-o6_JlF8kI2zPQ?via=gitter.im&via=matrix.org where the most recent issue is --8<-- /home/jorge/simulations/ProcaStar6/SIMFACTORY/exe/cactus_sim -L 3 /home/jorge/simulations/ProcaStar6/output-0000/ProcaStar.par cactus_sim: /home/jorge/Einstein-Toolkit/Cactus/arrangements/Carpet/CarpetLib/src/th.hh:70: CCTK_REAL8 CarpetLib::th::get_time(int, int, int) const: Assertion `tl >= 0 and tl < timelevels' failed. Rank 0 with PID 57937 received signal 6 --8<-- Yours, Roland > [CAUTION: Non-UBC Email] > > Dear Einstein Toolkit users, > > I am currently working with the Einstein Toolkit and trying to use > checkpoint/restart functionality to recover simulations. > > I understand the parameters that must be included in the parameter file, > but I am not sure how I should correctly restart a simulation from existing > checkpoint data. > > So far, I have been launching simulations with commands such as > > ./simfactory/bin/sim run ProcaStar -workstation-parfile=par/ProcaStar.par > > and the simulation runs correctly and generates checkpoint files. However, > when I try to restart from the checkpoint data, I am unsure what the > correct procedure should be. I do not know whether I should use a different > SimFactory command, modify the submission procedure, or provide additional > options. > > The checkpoint-related parameters in my parameter file are: > > CarpetIOHDF5::checkpoint = yes > IOUtil::checkpoint_every_walltime_hours = 0.1 > IOUtil::checkpoint_dir = "checkpoints_prueba" > IOUtil::checkpoint_keep = 1 > IOUtil::checkpoint_ID = no > IOUtil::checkpoint_on_terminate = yes > IOUtil::recover = "autoprobe" > IOUtil::recover_dir = "checkpoints_prueba" > IOUtil::abort_on_io_errors = yes > CarpetIOHDF5::open_one_input_file_at_a_time = yes > > Could someone please clarify the recommended procedure for restarting a > simulation from existing checkpoint files? In particular: > > 1. > > Which SimFactory command should be used to restart a simulation? > 2. > > Is it necessary to create a new run or continue the existing one? > 3. > > Are there any additional parameters or directory requirements for > recovery to work correctly? > > My environment is: > Einstein Toolkit version: ET_2025_05 > Operating system: Linux Ubuntu 22.04.5 LTS > Cluster/machine: Local > > Thank you very much for your help. > > Best regards, > Yahir Mio -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://pgp.mit.edu . From jnicoules at ua.pt Thu Jun 4 10:47:35 2026 From: jnicoules at ua.pt (Jordan Nicoules) Date: Thu, 4 Jun 2026 15:47:35 +0000 Subject: [Users] Automatic termination trigger mid-run In-Reply-To: <20260604082740.7282573a@haengie2.phas.ubc.ca> References: <325e4562ebd24b16b0c5e943b171fa12@ua.pt> <219D6265-660E-47DB-9D77-864EB5D32167@gmail.com> <381626e0f1244b41af2d31e28bfb3d17@ua.pt> , <20260604082740.7282573a@haengie2.phas.ubc.ca> Message-ID: Hi, Thanks, this Cactus parameter was exactly the piece I was missing! Best, Jordan ________________________________ From: Users on behalf of Roland Haas via Users Sent: Thursday, June 4, 2026 4:27:40 PM To: Erik Schnetter via Users Subject: Re: [Users] Automatic termination trigger mid-run CUIDADO: Email de um sistema externo. Cuidado com links, anexos e pedidos de dados/senhas. CAUTION: Email from an external system. Be careful with links, attachments, and requests for data/passwords. Hello all, Trigger can set parameters and there's a Cactus::terminate_next parameter (src/param.ccl) that you can set. You may need to then add `Cactus::terminate_next = no`) into your parfile (so that when the checkpoint recovers the steered value of terminate_next is overwritten). Yours, Roland > [CAUTION: Non-UBC Email] > > Ooh, you are using the "Trigger" thorn. I thought you were using "TerminationTrigger". So that's an option -- use that thorn instead. > > Otherwise, if you find your requested feature convenient, then please go ahead and implement it! It would be a nice addition to Cactus. > > -erik > > > On Jun 4, 2026, at 10:19, Jordan Nicoules wrote: > > > > Hi Erik, > > > > Thank you for your reply! I know of CCTK_TerminateNext, I actually use it in one of my thorns (so I could hack it to achieve what I want). In fact, a call to this function is what I would add to Trigger. > > > > My point is more: with the existing thorns, is there a way to terminate a simulation while it's running (and before its expected end based on final time/iteration), with a parfile directive, without: > > - manually editing the termination file > > - reaching walltime > > - having NaNs > > - and such edge cases. > > > > Something that would be like: > > ``` > > Trigger::Trigger_Checked_Variable [0] = "ADMBase::lapse" > > Trigger::Trigger_Reduction [0] = "minimum" > > Trigger::Trigger_Relation [0] = "<" > > Trigger::Trigger_Checked_Value [0] = 0.2 > > Trigger::Trigger_Reaction [0] = "terminate" # <-- This doesn't exist as far as I understand > > ``` > > > > Thanks, > > > > Jordan > > > > From: Users > on behalf of Erik Schnetter via Users > > > Sent: Thursday, June 4, 2026 14:57 > > To: users at einsteintoolkit.org > > Subject: Re: [Users] Automatic termination trigger mid-run > > > > > > CUIDADO: Email de um sistema externo. Cuidado com links, anexos e pedidos de dados/senhas. > > CAUTION: Email from an external system. Be careful with links, attachments, and requests for data/passwords. > > You can call the function `CCTK_TerminateNext`, which will stop the simulation gracefully after the current iteration finishes. This is built-in, you do not need a special thorn for this. > > > > This is how TerminationTrigger is implemented: It calls this function when a certain file is created. > > > > -erik > > > >> On Jun 4, 2026, at 09:31, Jordan Nicoules via Users wrote: > >> > >> Dear all, > >> > >> I was wondering if there was a built-in way to trigger the termination of a simulation when something specific happens, along the lines of what Trigger does to steer quantities. From what I understand, Trigger does not offer that possibility, and TerminationTrigger checks either a file or a time limit. What I'm considering would be more along the lines of "an apparent horizon is found so trigger termination", in order to steer some parameters at recovery. > >> > >> If there's no such explicit way, I'm happy to try to implement that in Trigger. I actually have ideas of other small improvements to Trigger that I could try contributing as well (namely, increase the maximum number of triggers and allow one trigger to have multiple consequences at once). > >> > >> Unfortunately I won't be able to join the weekly call today to discuss this directly. > >> > >> Best, > >> > >> Jordan > >> _______________________________________________ > >> Users mailing list > >> Users at einsteintoolkit.org > >> http://lists.einsteintoolkit.org/mailman/listinfo/users > -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://pgp.mit.edu . _______________________________________________ Users mailing list Users at einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From jnicoules at ua.pt Fri Jun 5 14:06:50 2026 From: jnicoules at ua.pt (Jordan Nicoules) Date: Fri, 5 Jun 2026 19:06:50 +0000 Subject: [Users] Question about schedule options Message-ID: <625d852e73554f18900ff1995cc5a704@ua.pt> Hi all, I have a question about scheduling routines in the analysis bin, more particularly about the options you can provide. Is there any downside in scheduling a function as "global-early loop-local", compared to the default "local"? Like a loss of performance, for instance if there end up being multiple such functions without non-trivial order? My issue is, Trigger::Trigger_Check is scheduled as global-early, but I would like to compute GFs before (and reductions, but that is not the problematic part). The "before" directive seems to only properly apply if I make my routine "global-early loop-local", which I can understand. If there's no additional overhead, I don't mind changing the options of my routine. If it may turn out to have impact on performance, I may prefer to introduce conditional statements or find other workarounds. Best, Jordan -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhaas at mail.ubc.ca Fri Jun 5 16:22:02 2026 From: rhaas at mail.ubc.ca (Roland Haas) Date: Fri, 5 Jun 2026 14:22:02 -0700 Subject: [Users] Question about schedule options In-Reply-To: <625d852e73554f18900ff1995cc5a704@ua.pt> References: <625d852e73554f18900ff1995cc5a704@ua.pt> Message-ID: <20260605142202.7e1e8fde@haengie2.phas.ubc.ca> Hello Jordan, Scheduling in Carpet with subcycling in time involved is quite tricky. Let me try and give rundown. * first to realize is that the schedule that you see printed out to screen is somewhat of a fiction * second to realize is that Carpet will execute the schedule for each bin (eg ANALYSIS) level-by-level. It will not however always execute all levels it can in one bin before executing the next bin (namely that only happens beween EVOL and POSTEP and at some points between INITIAL and POSTPOSTINITIAL [and EVOL]). Details in `Carpet/Carpet/src/Evolve.cc` or https://github.com/EinsteinToolkit/Carpet/blob/master/doc/scheduling.pdf pg 8 * a GLOBAL-EARLY routine will be executed along with the regular routines when the FIRST refinement level is processed (whichever one that may be) * a GLOBAL-LATE routine will be executed along with the regular routines when the LAST refinement is processed (whichever one that may be) * BEFORE / AFTER statements are only effective within a single schedule pass. So a routine A that is GLOBAL-EARLY and is AFTER a LOCAL routine B *will* execute after routine B in that FIRST refinement level. But *will* have executed BEFORE any instance of routine B on later level (it won't execute more than once though) * the LOOP-LOCAL option (which can only be used with GLOBAL, SINGLEMAP or LEVEL routines) means that Carpet will insert an extra loop over all the refinement levels and will call the scheduled routine on *all* levels, all the time. Even if a LOCAL routine at that iteration would not be. So it is somewhat more expensive than a LOCAL routine. If you want to compute something for Trigger to use, I would suggest to compute it in POSTSTEP rather than ANALYSIS (ANALYSIS is not supposed to compute anything that is used by others, really, only analyze data for output). Note that you will have to compute the quantity all the time, not just in iterations that say you want to use it (b/c the output may use data on refinement levels that would have been computed and that you skipped). Yours, Roland > [CAUTION: Non-UBC Email] > > Hi all, > > > I have a question about scheduling routines in the analysis bin, more > particularly about the options you can provide. Is there any downside > in scheduling a function as "global-early loop-local", compared to > the default "local"? Like a loss of performance, for instance if > there end up being multiple such functions without non-trivial order? > > > My issue is, Trigger::Trigger_Check is scheduled as global-early, but > I would like to compute GFs before (and reductions, but that is not > the problematic part). The "before" directive seems to only properly > apply if I make my routine "global-early loop-local", which I can > understand. If there's no additional overhead, I don't mind changing > the options of my routine. If it may turn out to have impact on > performance, I may prefer to introduce conditional statements or find > other workarounds. > > > Best, > > > Jordan Yours, Roland -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://pgp.mit.edu . From users at einsteintoolkit.org Mon Jun 8 15:18:01 2026 From: users at einsteintoolkit.org (users at einsteintoolkit.org) Date: Mon, 08 Jun 2026 15:18:01 -0500 Subject: [Users] Agenda for Thursday's Meeting Message-ID: <6a272379.Y5cTb92ZUD6ubOjV%users@einsteintoolkit.org> Please update the Wiki with agenda items for Thursday's meeting. Thanks! https://docs.einsteintoolkit.org/et-docs/meeting_agenda --The Maintainers From wernecklr at gmail.com Tue Jun 9 13:54:42 2026 From: wernecklr at gmail.com (Leonardo Werneck) Date: Tue, 9 Jun 2026 11:54:42 -0700 Subject: [Users] Silo Compilation Error Message-ID: Hi all, I've been trying to improve GRHayL's CI, and while trying to build the Einstein Toolkit's master thornlist in a container image, I got the following error: ``` #11 1164.3 ../../../tools/silock/silock.c: In function ?updateProgress?: 29704 #11 1164.3 ../../../tools/silock/silock.c:183:20: error: storage size of ?timeZone? isn?t known 29705 #11 1164.3 183 | struct timezone timeZone; 29706 #11 1164.3 | ^~~~~~~~ 29707 #11 1164.3 make[7]: *** [Makefile:540: silock.o] Error 1 29708 #11 1164.3 make[6]: *** [Makefile:486: all-recursive] Error 1 29709 #11 1164.3 make[5]: *** [Makefile:545: all-recursive] Error 1 29710 #11 1164.3 make[4]: *** [Makefile:477: all] Error 2 29711 #11 1164.3 make[3]: *** No rule to make target '/opt/et-build/et-gcc/configs/sim/scratch/done/Silo', needed by 'silo.cxx.o'. Stop. 29712 #11 1164.3 make[2]: *** [/opt/et-build/et-gcc/lib/make/make.thornlib:113: make.checked] Error 2 29713 #11 1164.3 make[1]: *** [/opt/et-build/et-gcc/lib/make/make.configuration:179: /opt/et-build/et-gcc/configs/sim/lib/libthorn_Silo.a] Error 2 29714 #11 1164.3 make[1]: *** Waiting for unfinished jobs.... ``` It appears that `struct timezone` is legacy C. Has anyone encountered this before and/or know how to deal with it? I've been using the latest gcc on Ubuntu 24.04, for completeness. Thanks! Leo -------------- next part -------------- An HTML attachment was scrubbed... URL: From wernecklr at gmail.com Tue Jun 9 16:44:08 2026 From: wernecklr at gmail.com (Leonardo Werneck) Date: Tue, 9 Jun 2026 14:44:08 -0700 Subject: [Users] Silo Compilation Error In-Reply-To: References: Message-ID: I figured out the issue, never mind. It was a stale `-std=c99` flag in my cfg file. Best, Leo On Tue, Jun 9, 2026 at 11:54?AM Leonardo Werneck wrote: > Hi all, > > I've been trying to improve GRHayL's CI, and while trying to build the > Einstein Toolkit's master thornlist in a container image, I got the > following error: > ``` > #11 1164.3 ../../../tools/silock/silock.c: In function ?updateProgress?: > 29704 > #11 1164.3 ../../../tools/silock/silock.c:183:20: error: storage size of > ?timeZone? isn?t known > 29705 > #11 1164.3 183 | struct timezone timeZone; > 29706 > #11 1164.3 | ^~~~~~~~ > 29707 > #11 1164.3 make[7]: *** [Makefile:540: silock.o] Error 1 > 29708 > #11 1164.3 make[6]: *** [Makefile:486: all-recursive] Error 1 > 29709 > #11 1164.3 make[5]: *** [Makefile:545: all-recursive] Error 1 > 29710 > #11 1164.3 make[4]: *** [Makefile:477: all] Error 2 > 29711 > #11 1164.3 make[3]: *** No rule to make target > '/opt/et-build/et-gcc/configs/sim/scratch/done/Silo', needed by > 'silo.cxx.o'. Stop. > 29712 > #11 1164.3 make[2]: *** [/opt/et-build/et-gcc/lib/make/make.thornlib:113: > make.checked] Error 2 > 29713 > #11 1164.3 make[1]: *** > [/opt/et-build/et-gcc/lib/make/make.configuration:179: > /opt/et-build/et-gcc/configs/sim/lib/libthorn_Silo.a] Error 2 > 29714 > #11 1164.3 make[1]: *** Waiting for unfinished jobs.... > ``` > > It appears that `struct timezone` is legacy C. Has anyone encountered this > before and/or know how to deal with it? I've been using the latest gcc on > Ubuntu 24.04, for completeness. > > Thanks! > Leo > -------------- next part -------------- An HTML attachment was scrubbed... URL: From users at einsteintoolkit.org Wed Jun 10 17:15:01 2026 From: users at einsteintoolkit.org (users at einsteintoolkit.org) Date: Wed, 10 Jun 2026 17:15:01 -0500 Subject: [Users] Einstein Toolkit Meeting Reminder Message-ID: <6a29e1e5.O1ddHtmix8DEePoi%users@einsteintoolkit.org> Hello, Please consider joining the weekly Einstein Toolkit phone call at 9:00 am US central time on Thursdays. For details on how to connect and what agenda items are to be discussed, use the link below. https://docs.einsteintoolkit.org/et-docs/Main_Page#Weekly_Users_Call --The Maintainers From rhaas at mail.ubc.ca Thu Jun 11 10:24:56 2026 From: rhaas at mail.ubc.ca (Roland Haas) Date: Thu, 11 Jun 2026 08:24:56 -0700 Subject: [Users] meeting minutes for 2026-06-11 Message-ID: <20260611082456.0e1e63ff@haengie2.phas.ubc.ca> Present: Roland, Steve, Peter, Max, Deborah, Noora, Yuvraj, Zach Chair: Deborah Minutes: Roland ET release ========== * timeline * gallery ** BBH test gives large CoM drift on either Stampede3 or Unity ** needs to be checked, would be critical for release ** suggest to try 2025 version of TwoPunctures * Noora is running axidilaton gallery example now * testsuites ** Derivs tests fail with error code 255, finds NaN but only for order 4 and higher * sunrise failures, may be due to postprocessing code. Seems fixable by removing a line of code ** CanudaX has significant differences ** SpherePUGH has differences * votes for final inclusion next meeting: CanudaX, Cottonmouth, Boost, TwoPuncturesX (post investigation of BBH gallery issues) * votes for inclusion that passed: Bhahaha, BHNS gallery example ET summer school and workshop ============================= * If presenting a tutorial, please send any notebooks / data you would like to use to Steve ASAP, by uploading to the tutorial server and pointing him to the location * data files can be hosted in your $HOME, make sure to set permissions, `chmod -R ugo+rX $HOME` Yours, Roland -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://pgp.mit.edu . From makino.taiki.g6 at s.mail.nagoya-u.ac.jp Mon Jun 15 19:00:00 2026 From: makino.taiki.g6 at s.mail.nagoya-u.ac.jp (MAKINO Taiki) Date: Tue, 16 Jun 2026 00:00:00 +0000 Subject: [Users] ET Simulation Error Message-ID: Dear Einstein Toolkit Team I am a new Einstein Toolkit user and have a simulation error. I can run DNSdata_test.par with GRHydro, but I cannot run it when I switch GRHydro to IllinoisGRMHD. In detail, I changed the activethorns from GRHydro to IllinoisGRMHD, and added some activethorns such as GRHayLib, GRHayL and GRHayLHD. In addition, I commented out parameters of GRHydro like ?GRHydro::sources_spatial_order?. And, I wrote HydroBase::evolution_method = "IllinoisGRMHD?. The error message is as follows: ?WARNING level 0 from host hubble process 22 in thorn Cactus, file /data/usr/Cactus/configs/sim/build/Cactus/main/SetParams.c:93: -> CCTKi_SetParameter: Error at line 36 in parameter file /data/usr/sim_Result/test_BNS_GW_Piecewise4_Cactus_Illinois8/output-0000/DNSdata_test.par while activating thorns? Also, one of participants of the Einstein Toolkit workshop advised that I had to activate DNSdata which I had commented out and to comment out parameters of thorns which I did not activate. After making these changes, a different error appeared. It is the following: WARNING level 0 from host hubble process 0 in thorn Cactus, file /data/usr/Cactus/configs/sim/build/Cactus/main/SetParams.c:93: -> CCTKi_SetParameter: Error at line 37 in parameter file /data/makino/test_BNS_GW_Piecewise4_Cactus_Illinois9/output-0000/DNSdata_test_copy.par while activating thorns. The list of activated thorns is provided below for reference: ActiveThorns = "Boundary CartGrid3D CoordBase Fortran InitBase IOUtil LocalReduce SymBase Time" ActiveThorns = "AEILocalInterp" ActiveThorns = "MoL Slab SpaceMask SphericalSurface" ActiveThorns = "Carpet CarpetInterp CarpetInterp2 CarpetIOASCII CarpetIOHDF5 CarpetIOScalar CarpetLib CarpetIOBasic CarpetReduce CarpetRegrid2 CarpetSlab CarpetTracker CarpetMask LoopControl" ActiveThorns = "Formaline" ActiveThorns = "HTTPD Socket" ActiveThorns = "NaNChecker TerminationTrigger TimerReport" ActiveThorns = "ADMbase ADMcoupling ADMmacros CoordGauge StaticConformal" ActiveThorns = "RotatingSymmetry180 ReflectionSymmetry" ActiveThorns = "Constants TmunuBase HydroBase " ActiveThorns = "QuasiLocalMeasures" ActiveThorns = "EOS_Omni" ActiveThorns = "GRHayLib" ActiveThorns = "GRHayL" ActiveThorns = "IllinoisGRMHD" ActiveThorns = "SummationByParts" ActiveThorns = "GenericFD NewRad" ActiveThorns = "ML_BSSN ML_BSSN_Helper ML_ADMConstraints" ActiveThorns = "Hydro_Analysis" ActiveThorns = "Dissipation" ActiveThorns = "DNSdata" ActiveThorns = "GRHayLHD? The line reported in the second error (line 37) corresponds to: ActiveThorns = "GRHayLHD" Am I missing any required thorns, parameter settings, or something else for using IllinoisGRMHD with DNSdata_test.par? Thank you very much for your time and assistance. I have attached the parameter file for reference. If any additional information would be helpful, I would be happy to provide it. Best regards, Taiki Makino Graduate School of Science, Nagoya University makino.taiki.g6 at s.mail.nagoya-u.ac.jp ?? Outlook for Mac -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DNSdata_test_copy.par Type: application/octet-stream Size: 16540 bytes Desc: DNSdata_test_copy.par URL: From beyhannkarakas at gmail.com Tue Jun 16 09:47:35 2026 From: beyhannkarakas at gmail.com (=?UTF-8?Q?Beyhan_Karaka=C5=9F?=) Date: Tue, 16 Jun 2026 15:47:35 +0100 Subject: [Users] ET Simulation Error In-Reply-To: References: Message-ID: Date: Tue, 16 Jun 2026 00:00:00 +0000 > From: MAKINO Taiki > To: "users at einsteintoolkit.org" > Subject: [Users] ET Simulation Error > > > Dear Einstein Toolkit Team > > I am a new Einstein Toolkit user and have a simulation error. > > I can run DNSdata_test.par with GRHydro, but I cannot run it when I switch > GRHydro to IllinoisGRMHD. In detail, I changed the activethorns from > GRHydro to IllinoisGRMHD, and added some activethorns such as GRHayLib, > GRHayL and GRHayLHD. > > In addition, I commented out parameters of GRHydro like > ?GRHydro::sources_spatial_order?. And, I wrote HydroBase::evolution_method > = "IllinoisGRMHD?. The error message is as follows: > > ?WARNING level 0 from host hubble process 22 > in thorn Cactus, file > /data/usr/Cactus/configs/sim/build/Cactus/main/SetParams.c:93: > -> CCTKi_SetParameter: Error at line 36 in parameter file > /data/usr/sim_Result/test_BNS_GW_Piecewise4_Cactus_Illinois8/output-0000/DNSdata_test.par > while activating thorns? > > Also, one of participants of the Einstein Toolkit workshop advised that I > had to activate DNSdata which I had commented out and to comment out > parameters of thorns which I did not activate. After making these changes, > a different error appeared. It is the following: > > WARNING level 0 from host hubble process 0 > in thorn Cactus, file > /data/usr/Cactus/configs/sim/build/Cactus/main/SetParams.c:93: > -> CCTKi_SetParameter: Error at line 37 in parameter file > /data/makino/test_BNS_GW_Piecewise4_Cactus_Illinois9/output-0000/DNSdata_test_copy.par > while activating thorns. > > The list of activated thorns is provided below for reference: > > ActiveThorns = "Boundary CartGrid3D CoordBase Fortran InitBase IOUtil > LocalReduce SymBase Time" > ActiveThorns = "AEILocalInterp" > ActiveThorns = "MoL Slab SpaceMask SphericalSurface" > ActiveThorns = "Carpet CarpetInterp CarpetInterp2 CarpetIOASCII > CarpetIOHDF5 CarpetIOScalar CarpetLib CarpetIOBasic CarpetReduce > CarpetRegrid2 CarpetSlab CarpetTracker CarpetMask LoopControl" > ActiveThorns = "Formaline" > ActiveThorns = "HTTPD Socket" > ActiveThorns = "NaNChecker TerminationTrigger TimerReport" > ActiveThorns = "ADMbase ADMcoupling ADMmacros CoordGauge StaticConformal" > ActiveThorns = "RotatingSymmetry180 ReflectionSymmetry" > ActiveThorns = "Constants TmunuBase HydroBase " > ActiveThorns = "QuasiLocalMeasures" > ActiveThorns = "EOS_Omni" > ActiveThorns = "GRHayLib" > ActiveThorns = "GRHayL" > ActiveThorns = "IllinoisGRMHD" > ActiveThorns = "SummationByParts" > ActiveThorns = "GenericFD NewRad" > ActiveThorns = "ML_BSSN ML_BSSN_Helper ML_ADMConstraints" > ActiveThorns = "Hydro_Analysis" > ActiveThorns = "Dissipation" > ActiveThorns = "DNSdata" > ActiveThorns = "GRHayLHD? > > > The line reported in the second error (line 37) corresponds to: > > ActiveThorns = "GRHayLHD" > > Am I missing any required thorns, parameter settings, or something else > for using IllinoisGRMHD with DNSdata_test.par? > > Thank you very much for your time and assistance. > > I have attached the parameter file for reference. If any additional > information would be helpful, I would be happy to provide it. > > Best regards, > > Taiki Makino > Graduate School of Science, Nagoya University > makino.taiki.g6 at s.mail.nagoya-u.ac.jp > > Dear Taiki, You should remove the GRHayL from the active thorns as the thorn name is GRHayLib for that. And you don't need HydroBase::evolution_method = "IllinoisGRMHD" for IGM. You activate both IGM and GrHaylHD you should choose one. Please have a look at the example parfiles: Cactus/arrangements/GRHayLET/IllinoisGRMHD and also in Cactus/arrangements/GRHayLET/GRHayLHD. Best regards, Beyhan. -------------- next part -------------- An HTML attachment was scrubbed... URL: