Trac

trac@lists.einsteintoolkit.org

8708 discussions

#1066: Implement IMEX integrators in MoL
by Roland Haas 12 Dec '22

12 Dec '22

#1066: Implement IMEX integrators in MoL Reporter: Erik Schnetter Status: open Milestone: Version: Type: enhancement Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): Though @{557058:56049c54-f8c2-4b6c-9b88-ab697c967495} just pointed out a flaw in my thinking. So I no longer have a direct application for this. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1066/implement-imex-in…

1 0

#1066: Implement IMEX integrators in MoL
by Roland Haas 12 Dec '22

12 Dec '22

#1066: Implement IMEX integrators in MoL Reporter: Erik Schnetter Status: open Milestone: Version: Type: enhancement Priority: minor Component: EinsteinToolkit thorn Changes (by Roland Haas): responsible: [] (was ) assignee: Roland Haas (was ) Dana Alic contributed an implementation of IMEX integrators for MoL. I attach the implementation as a patch (based on r133 of MoL). The implementation is well tested. The patch does not apply cleanly, and seems to make some modifications to the schedule etc. as well that have since been superseded by other changes to MoL. **Keyword:** Comment (by Roland Haas): have some renewed interest in this -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1066/implement-imex-in…

1 0

#2626: Multipole is not OpenMP parallelized
by Gabriele Bozzola 05 Dec '22

05 Dec '22

#2626: Multipole is not OpenMP parallelized Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: enhancement Priority: trivial Component: Comment (by Gabriele Bozzola): If I did reach a final conclusion, I forgot about it. I see I have a commit about it: [https://bitbucket.org/Sbozzolo/einsteinanalysis/commits/69b64606b6a1ac35405… I think I claim that this is \(marginally\) faster in production runs. ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2626/multipole-is-not-…

1 0

#2674: Einstein Toolkit != Cactus
by Zach Etienne 05 Dec '22

05 Dec '22

#2674: Einstein Toolkit != Cactus Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: minor Component: Comment (by Zach Etienne): There are a number of modules that don’t depend on Cactus in the Cactus directory, including NRPyPN, and ExternalLibraries. Maybe a directory structure should be created under `EinsteinToolkit/` , including Cactus, SelfForce, NRPyPN etc? Also wouldn’t it be best if the download directions for the Einstein Toolkit downloaded the entire Toolkit, instead of separate instructions for other modules under the ET umbrella? Yeah sorry I was confused of the definition of “blocker”, thanks for clarifying. Still I believe this should be fixed. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2674/einstein-toolkit-…

1 0

#2674: Einstein Toolkit != Cactus
by Roland Haas 05 Dec '22

05 Dec '22

#2674: Einstein Toolkit != Cactus Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: minor Component: Comment (by Roland Haas): Note that what is in the “Cactus” directory _is_ actually Cactus. For the non-cactus based codes \(SelfForce1D and kuibit\) we \(have to, since they do not work well with GetComponents\) provide separate download instructions. So certainly what GetComponents downloads is not all of the Einstein Toolkit. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2674/einstein-toolkit-…

1 0

#2674: Einstein Toolkit != Cactus
by Roland Haas 05 Dec '22

05 Dec '22

#2674: Einstein Toolkit != Cactus Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: minor Component: Changes (by Roland Haas): responsible: [] (was ) assignee: Zach Etienne (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2674/einstein-toolkit-…

1 0

#2674: Einstein Toolkit != Cactus
by Roland Haas 05 Dec '22

05 Dec '22

#2674: Einstein Toolkit != Cactus Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: minor Component: Changes (by Roland Haas): priority: minor (was blocker) Comment (by Roland Haas): ## Priority | Value | Meaning | | --- | --- | | blocker | The ET does not build, or another problem which means development cannot continue. | | critical | At least one important thorn cannot be used, or something else is severely broken. | | major | Needs to be fixed before release, or documented as broken in release notes | | minor | Not important enough to necessarily look at before a release | | trivial | Very low priority, though maybe not trivial to implement | Since this does not got imply that the ET does not build, or another problem or otherwise means development cannot continue. Not a blocker. Please don’t abuse priorities. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2674/einstein-toolkit-…

1 0

#2503: Various small problems with FishboneMoncriefID
by Roland Haas 05 Dec '22

05 Dec '22

#2503: Various small problems with FishboneMoncriefID Reporter: Gabriele Bozzola Status: open Milestone: ET_2023_05 Version: development version Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Roland Haas): Thanks, I added a milestone. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2503/various-small-pro…

1 0

#2503: Various small problems with FishboneMoncriefID
by Roland Haas 05 Dec '22

05 Dec '22

#2503: Various small problems with FishboneMoncriefID Reporter: Gabriele Bozzola Status: open Milestone: ET_2023_05 Version: development version Type: bug Priority: minor Component: EinsteinToolkit thorn Changes (by Roland Haas): milestone: ET_2023_05 (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2503/various-small-pro…

1 0

#2503: Various small problems with FishboneMoncriefID
by Zach Etienne 05 Dec '22

05 Dec '22

#2503: Various small problems with FishboneMoncriefID Reporter: Gabriele Bozzola Status: open Milestone: Version: development version Type: bug Priority: minor Component: EinsteinToolkit thorn Comment (by Zach Etienne): Yes, I did make some progress but was pulled off to another project. My conclusion: the thorn is generally in need of modernization, and I hope to have some time before the May 2023 release to get the above issues fixed, as well as others to bring it more in line with the standards set within `Baikal` . Please consider May 2023 the target for F-M thorn modernization. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2503/various-small-pro…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac