Use VMEC events for loss accounting - #54
Draft
rogeriojorge wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uses the VMEC boundary mask and termination time for loss accounting. Axis hits, custom terminations, and solver failures are reported separately.
Collisional traces use the termination state for lost position and energy. Loss calculations no longer scan sampled trajectories or depend on post-event
infvalues.The 200-particle QP trace kept 90 losses and 8 axis terminations. Tracing took 5.53 s with a 758 MB peak resident set in the profiling run.
Depends on #53. No test files changed.