BUGFIX: Operations on "time aware" vectors were being performed even if they were empty.#88
Open
VitorSouzaLNLS wants to merge 2 commits intomasterfrom
Open
BUGFIX: Operations on "time aware" vectors were being performed even if they were empty.#88VitorSouzaLNLS wants to merge 2 commits intomasterfrom
VitorSouzaLNLS wants to merge 2 commits intomasterfrom
Conversation
VitorSouzaLNLS
requested review from
HenriqueWS11,
fernandohds564,
otavio-silveira,
vellosok75 and
xresende
fernandohds564
approved these changes
Mar 31, 2026
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.
In the new accelerator's function
update_time_aware_infothe operationtime_aware_displacements.back() += line_length - cum_lengthwas being performed (or trying to be performed) even if the vector was empty, as in cases like transport lines with no time-aware element.Thanks to @otavio-silveira and @HenriqueWS11 for our discussion about "twiss matching" that led us to find out this bug.