Search found 4843 matches
- 24 May 2024, 17:48
- Forum: ElmerSolver
- Topic: 3D simulation of a Motor without application of a load
- Replies: 10
- Views: 483
Re: 3D simulation of a Motor without application of a load
Hi Felix, The torque in 2D and 3D is a little different. In 2D it must be multiplied by the length of the machine even when using 2.5D approach. In 3D not. In both cases the result must be multiplied with the number of symmetric sections. Regarding BCs here are some that I've been using lately. Here...
- 24 May 2024, 17:24
- Forum: General
- Topic: B field from wire current
- Replies: 5
- Views: 148
Re: B field from wire current
Hi, Yes, the primary field for the solver is the vector potential. If we want to set magnetic flux density directly the code needs to do some non-trivial bookkeeping since the value of flux density is obtained by looping over element edges. In this case no value for AV was given so where should the ...
- 15 May 2024, 18:18
- Forum: Bug reports
- Topic: Wrong SaveScalars convective flux
- Replies: 1
- Views: 1923
Re: Wrong SaveScalars convective flux
Hi Cedric, Maybe you could check to remove the SaveScalars instances that give correct solution and check whether the problematic instances still give wrong answers. Or do the result depend on which order the instances are accessed. The module should not have any memory that it was called with diffe...
- 15 May 2024, 18:08
- Forum: Bug reports
- Topic: High order infinite loop during partition/ parallel run fails
- Replies: 3
- Views: 420
Re: High order infinite loop during partition/ parallel run fails
Hi
Replace "StatElecSolve" with "StatElecSolveVec" and you may have better success.
-Peter
Replace "StatElecSolve" with "StatElecSolveVec" and you may have better success.
-Peter
- 15 May 2024, 18:00
- Forum: Bug reports
- Topic: Bug in SaveScalars in parallel?
- Replies: 2
- Views: 335
Re: Bug in SaveScalars in parallel?
Just to note: this was fixed by Fabien.
The reason for the original bug was that the application of this routine was extended beyond nodal fields. If we have other type of fields we cannot use just the parallel info related to the geometric nodes.
-Peter
The reason for the original bug was that the application of this routine was extended beyond nodal fields. If we have other type of fields we cannot use just the parallel info related to the geometric nodes.
-Peter
- 08 May 2024, 13:34
- Forum: General
- Topic: Elmer's solution for coupling different solvers
- Replies: 3
- Views: 153
Re: Elmer's solution for coupling different solvers
Hi,
We are still working on some minor issues. I think our marketing department got a little ahead of us! But great to have the visibility even though it puts some pressure on us.
-Peter
We are still working on some minor issues. I think our marketing department got a little ahead of us! But great to have the visibility even though it puts some pressure on us.
-Peter
- 08 May 2024, 13:28
- Forum: ElmerGUI
- Topic: Model induction between two coils
- Replies: 31
- Views: 787
Re: Model induction between two coils
Hi CoilSolver is merely a static current conduction solver with some special hacks that make life easier for coils, e.g. 1) You can define currents for closed coils without having to create an extra cut on it 2) You can normalize the current density automatically to have desired total current 3) You...
- 06 May 2024, 16:53
- Forum: Installation & compilation
- Topic: Error: Insufficient space in Bsend buffer
- Replies: 9
- Views: 1309
Re: Error: Insufficient space in Bsend buffer
Hi Juris,
Great! I just committed the fix to devel.
-Peter
Great! I just committed the fix to devel.
-Peter
- 03 May 2024, 17:36
- Forum: Installation & compilation
- Topic: Error: Insufficient space in Bsend buffer
- Replies: 9
- Views: 1309
Re: Error: Insufficient space in Bsend buffer
Hi Juris,
What if you increase the size at line 4602. E.g. to
CALL CheckBuffer( 8*TotalL + ParEnv % NumOfNeighbours*(1+MPI_BSEND_OVERHEAD) )
-Peter
What if you increase the size at line 4602. E.g. to
CALL CheckBuffer( 8*TotalL + ParEnv % NumOfNeighbours*(1+MPI_BSEND_OVERHEAD) )
-Peter
- 03 May 2024, 16:59
- Forum: General
- Topic: Storing an variable from UDF at each iteration step
- Replies: 2
- Views: 291
Re: Storing an variable from UDF at each iteration step
Hi Eric,
What is the size of your variable?
Are you sure that your case is an UDF rather than a Solver. If you have transient history then the Solver provides some services to advance a variable forward when doing timestepping. So what would the UDF do? The answer depends on your goal.
-Peter
What is the size of your variable?
Are you sure that your case is an UDF rather than a Solver. If you have transient history then the Solver provides some services to advance a variable forward when doing timestepping. So what would the UDF do? The answer depends on your goal.
-Peter