-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Post processing for stranded homogenization model loss in harmonic 3D models #422
Comments
What do you think @jvencels, should we separate the homogenization into |
Orthogonality between skin effect and proximity effects are assumed (without going into details, many articles mention that). With this, superposition can be applied and losses summed. Separately estimated skin and proximity losses will give an engineer more insight to focus on one or another loss type. |
FYI @jvencels It has an issue with showing the corrent fields. Shows only "Skin Loss" nodal field, other fields are empty. Also, that is really the "Proximity Loss" field. I need to check it. The way it works, you say "Calculate Homogenization Loss = Logical True" in CalcFields section. |
@jvencels I modified the existing homogenization test However, see the commit message What do you think? Should we just put the losses in "harmonic loss" and "joule heating" fields? |
@ettaka Regarding Joule losses, in 3D, they are not considering the fill factor. In other words, as a joule loss, we get For homogenized cases, we should use modified coilMaterialConductivity, likely Sigma 33? |
Ok I will put the proximity loss in |
Homogenization for harmonic 3D stranded coils exists, but the loss distribution processing is not yet implemented.
In principle, we could already replace the homogenized "sigma" in material parameters and get the correct "skin effect" loss. Thus, we would only need to implement the "proximity effect" loss based on the homogenized parameters.
However, the "homogenized" sigma is given in component. So we could also use that so that it is less confusing. In that case, we could implement a single
homogenization loss
field. Or then we could also separate the two in toproximity loss
andskin loss
components.The text was updated successfully, but these errors were encountered: