Fixing the build of Princeton-D TF Coils#372
Merged
shimwell merged 3 commits intofusion-energy:mainfrom Aug 4, 2025
Merged
Conversation
Member
|
@RemDelaporteMathurin just wondering if you have any objection to merging this. I think this shape was one that you made originally. |
Member
|
Sure! Thanks for the improvement Ross! |
Contributor
Author
|
No worries. Great work on putting the original piece together, neat feature! |
Member
|
many thanks, sorry this took a while to reveiw |
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.
I was trying to build a simple parametric ST with Princeton-D TF coils. When using certain paramaterisations the build would hang and never finish.
Here is the code I was using:
I swept r2: 100<=r2<=800.
I have a scan through the source and printed it out. It appeared to be getting stuck on the minimize() function for the error. Digging into this the error is calculating the distance between the guess and the actual value of z_0. To calculate z_0 we want the error to =0. I therefore decided to switch out the minmize function for a bracketed root-finder, where the problem can collapse quickly without being sensitive to the z_0 guess. It should be more robust and take fewer evaluations. This has solved the problem, and with a wide range of TF configurations I can get a build.
There is now a warning showing for the solver:
I was going to set another PR focused on fixing this warning, but wanted to get eyes on this first now that the build completes consistently.