Fix for child nodes order in AccNode class#109
Merged
azukov merged 1 commit intoPyORBIT-Collaboration:mainfrom Feb 27, 2026
Merged
Fix for child nodes order in AccNode class#109azukov merged 1 commit intoPyORBIT-Collaboration:mainfrom
azukov merged 1 commit intoPyORBIT-Collaboration:mainfrom
Conversation
…ist of the parent node. It means, at the entrance they did not account for presiding child nodes. It is fixed.
azukov
approved these changes
Feb 27, 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
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.
If you add a child node to the ENTRANCE or EXIT the child node was always added to the end of the child nodes list. Now, if you add a child node to the entrance it will be inserted as the first element of the list for entrance child nodes. That is default behavior, but you can control it with place_in_part parameter of the addChildNode(...) method in AccNode class.