Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add maxWeight reduction to the MultiEigenStepperLoop #1628

Merged

Conversation

benjaminhuth
Copy link
Member

@benjaminhuth benjaminhuth commented Oct 26, 2022

This allows to choose between mean and maxWeight as reduction methods. A third method for the mode should be also added, but it does not yet work really well, and the maxWeight is also a bit of a "poor mans mode".

This PR makes this also configurable for the GSF in the examples.

Should be merged after #1627

@benjaminhuth benjaminhuth removed the 🚧 WIP Work-in-progress label Nov 7, 2022
@benjaminhuth benjaminhuth added this to the next milestone Nov 7, 2022
@benjaminhuth benjaminhuth removed the 🛑 blocked This item is blocked by another item label Nov 8, 2022
@kodiakhq kodiakhq bot merged commit 1b3c69a into acts-project:main Nov 8, 2022
@github-actions github-actions bot removed the automerge label Nov 8, 2022
@benjaminhuth benjaminhuth deleted the feature/multi-stepper-max-weight branch November 9, 2022 08:38
@paulgessinger paulgessinger modified the milestones: next, v21.1.0 Nov 11, 2022
kodiakhq bot pushed a commit that referenced this pull request Nov 11, 2022
This is a major refactoring of the GSF. It changes the propagation structure, and the way the GSF records states to the `MultiTrajectory`. It also removes the smoothing code, since it is not really useful at the moment, as the component states are not exported anyways.

should be merged after #1609 and #1627 and #1628 

We should add performance monitoring in this or a later PR

Fixes #1666
CarloVarni pushed a commit to CarloVarni/acts that referenced this pull request Dec 22, 2022
This is a major refactoring of the GSF. It changes the propagation structure, and the way the GSF records states to the `MultiTrajectory`. It also removes the smoothing code, since it is not really useful at the moment, as the component states are not exported anyways.

should be merged after acts-project#1609 and acts-project#1627 and acts-project#1628 

We should add performance monitoring in this or a later PR

Fixes acts-project#1666
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component - Core Affects the Core module Component - Examples Affects the Examples module Impact - Minor Nuissance bug and/or affects only a single module Improvement Changes to an existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants