You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The models of the CS and PF coils are a rather rickety structure, all standing on an input like this:
* Peak current per turn input for PF coil i [A]
cptdin = 4.0d4, 4.0d4, 4.0d4, 4.0d4, 4.0d4, 4.0d4, 4.0d4, 4.0d4
This component is the CS current: pfv.cptdin[pfv.nohc - 1]. This determines the number of turns and therefore the size of the conductor. This causes trouble whenever there is anything that sets an absolute scale for the coil conductor - specifically, the CS fatigue model (class CsFatigue). This is based on assumed initial crack sizes, whose initial default values are:
(although t_crack_radial is subsequently overwritten).
It is up to the user to make sure that the CS current is enough to ensure adequate fatigue life. It is easy to end up in with fatigue life which is very short or even zero.
It would be good to resolve this - either by making the CS current an iteration variable, or by allowing the code to calculate it in some other way.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The models of the CS and PF coils are a rather rickety structure, all standing on an input like this:
This component is the CS current:
pfv.cptdin[pfv.nohc - 1]
. This determines the number of turns and therefore the size of the conductor. This causes trouble whenever there is anything that sets an absolute scale for the coil conductor - specifically, the CS fatigue model (class CsFatigue
). This is based on assumed initial crack sizes, whose initial default values are:(although
t_crack_radial
is subsequently overwritten).It is up to the user to make sure that the CS current is enough to ensure adequate fatigue life. It is easy to end up in with fatigue life which is very short or even zero.
It would be good to resolve this - either by making the CS current an iteration variable, or by allowing the code to calculate it in some other way.
@ajpearcey @timothy-nunn @chris-ashe @clmould ?
Beta Was this translation helpful? Give feedback.
All reactions