This an issue with Paraview.
When I calculate the potential integral in the coil volume, the results are equal to those from FEMM.
FEMM:
Integral of A over selection:
2.42274e-006 Henry Amp meter^2
Elmer:
2.424273847989E-006
Paraview:
1.28535e-05
Axis Symmetric post processing
-
- Site Admin
- Posts: 4832
- Joined: 22 Aug 2009, 11:57
- Antispam: Yes
- Location: Espoo, Finland
- Contact:
Re: Axis Symmetric post processing
Good that things got sorted out. Probably I never understood the issue. So was there a missing weight in the integration?
\int f dA
is different than
\int 2pi r f dA
?
-Peter
\int f dA
is different than
\int 2pi r f dA
?
-Peter
Re: Axis Symmetric post processing
We are still trying to figure it out what to do with Paraview. If it is needed, as Elmer is great.
Re: Axis Symmetric post processing
How about creating a new field in the calculator
coordsX*A
where instead of coordsX put the proper variable that represents the distance from axis?
coordsX*A
where instead of coordsX put the proper variable that represents the distance from axis?
-
- Posts: 9
- Joined: 01 Feb 2024, 05:11
- Antispam: Yes
Re: Axis Symmetric post processing
Sorry, but I'm not completely clear of what result I will achieve doing
There shouldn't be x,y -> r,phi conversion?
From my understanding, Elmer is calculating everything as if (Z-axis) would be 2*pi*r. That is the reason why "SaveScalars" work.
However, when it comes to postprocessing, the results are wrong.
It seems to be considered as Cartesian. Elmer is not giving the full info to paraview.
It seems to lack of one post processing step or some kind of Elmer conversion.
I've asked the same quesiton in Paraview forum
https://discourse.paraview.org/t/axis-s ... ng/13889/3
and it seems that Paraview don't have the ability to understand that the result is axis symmetric.
Code: Select all
coordsX*A
From my understanding, Elmer is calculating everything as if (Z-axis) would be 2*pi*r. That is the reason why "SaveScalars" work.
However, when it comes to postprocessing, the results are wrong.
It seems to be considered as Cartesian. Elmer is not giving the full info to paraview.
It seems to lack of one post processing step or some kind of Elmer conversion.
I've asked the same quesiton in Paraview forum
https://discourse.paraview.org/t/axis-s ... ng/13889/3
and it seems that Paraview don't have the ability to understand that the result is axis symmetric.
-
- Site Admin
- Posts: 4832
- Joined: 22 Aug 2009, 11:57
- Antispam: Yes
- Location: Espoo, Finland
- Contact:
Re: Axis Symmetric post processing
Hi,
In Elmer we assume
1) Cartesian 2D
x = Coordinate 1
y = Coordinate 2
2) Axially symmetric
r = Coordinate 1
z = Coordinate 2
There is nothing that could go to paraview that would indicate how it should intepret them. This is the metadata for coordinates included in VTU file:
-Peter
In Elmer we assume
1) Cartesian 2D
x = Coordinate 1
y = Coordinate 2
2) Axially symmetric
r = Coordinate 1
z = Coordinate 2
There is nothing that could go to paraview that would indicate how it should intepret them. This is the metadata for coordinates included in VTU file:
Code: Select all
<Points>
<DataArray type="Float64" NumberOfComponents="3" format="appended" offset="1338012"/>
</Points>