Free Boundary Coil Optimization#456
Draft
lazersos wants to merge 12 commits into
Draft
Conversation
added 11 commits
May 5, 2026 15:58
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.
This adds an ability to STELLOPT to perform free boundary coil optimization. This is sometimes called single stage optimization. To run in this mode, not only must coil optimization be performed but the VMEC
INDATAnamelist will requireLFREEB=Tand the user to provide an initalMGRID_FILEwhich VMEC can use to run. This MGRID file will only be read once and STELLOPT will generate new MGRID files as it runs. This is attributed to the fact that when VMEC reads theINDATAnamelist it automatically checks theMGRID_FILEand loads it. If it does not load, the code will setLFREEB=Fand then STELLOPT will behave as if fixed boundary optimization is happening.Please check to make sure non-coil optimization runs are not affected.