Search found 2390 matches
- Today, 16:41
- Forum: General
- Topic: B field from wire current
- Replies: 4
- Views: 35
Re: B field from wire current
I ran it and received the same error, not seen that error before floodfill is a programming function to fill an array typically by area. It must have something to do with the BCs These BCs do not throw the error Boundary Condition 1 Target Boundaries(3) = 4 5 6 Name = "cube_4_faces" AV {e}...
- Today, 13:55
- Forum: ElmerSolver
- Topic: Non-conformal mesh contacts
- Replies: 10
- Views: 77
Re: Non-conformal mesh contacts
The whole case is here
https://github.com/mrkearden/case
https://github.com/mrkearden/case
- Today, 13:44
- Forum: ElmerSolver
- Topic: Non-conformal mesh contacts
- Replies: 10
- Views: 77
Re: Non-conformal mesh contacts
- Today, 13:15
- Forum: ElmerSolver
- Topic: Non-conformal mesh contacts
- Replies: 10
- Views: 77
Re: Non-conformal mesh contacts
You can use Salome to import the stp file which comes in as one solid, but use the explode command to show that it is really 13 different solids (or bodies) in Elmer. The goal would be to merge these 13 into one sold to obtain a conforming mesh, Or use the 13 to define mortar conditions. bodies.png
- Today, 12:00
- Forum: ElmerSolver
- Topic: wrong displacement values using "ElasticSolver"?
- Replies: 16
- Views: 96
Re: wrong displacement values using "ElasticSolver"?
Mika is correct that the Large Deflection = False works in Elastic Solver when the UMAT subroutine is defined for the material.
Converges quickly to the desired answer regardless of number on non=linear iterations.
Converges quickly to the desired answer regardless of number on non=linear iterations.
- Yesterday, 22:33
- Forum: ElmerSolver
- Topic: wrong displacement values using "ElasticSolver"?
- Replies: 16
- Views: 96
Re: wrong displacement values using "ElasticSolver"?
scanning in the case of elasticsolver is just a step solution where each step depends on the previous solution.
- Yesterday, 18:01
- Forum: ElmerSolver
- Topic: wrong displacement values using "ElasticSolver"?
- Replies: 16
- Views: 96
Re: wrong displacement values using "ElasticSolver"?
I did not do transient, I did scanning, which does not incorporate the acceleration or velocity terms.
- Yesterday, 12:54
- Forum: ElmerSolver
- Topic: wrong displacement values using "ElasticSolver"?
- Replies: 16
- Views: 96
Re: wrong displacement values using "ElasticSolver"?
If I run it in steps instead of steady state, the result path is not a linear line, there is a curve, a non-linear response
Large Deflection = False
which elastic solver ignores
This is with theLarge Deflection = False
which elastic solver ignores
- Yesterday, 12:17
- Forum: ElmerSolver
- Topic: wrong displacement values using "ElasticSolver"?
- Replies: 16
- Views: 96
Re: wrong displacement values using "ElasticSolver"?
By "nothing non-linear" I meant I thought the displacements were to small too reach the large displacement theory,
Yes ElasticSolver is using the large deflection formulation
According to the manual
Large Deflection = False
only shows up in the shell solver, not ElasticSolver
Yes ElasticSolver is using the large deflection formulation
According to the manual
Large Deflection = False
only shows up in the shell solver, not ElasticSolver
- Yesterday, 12:12
- Forum: ElmerSolver
- Topic: Non-conformal mesh contacts
- Replies: 10
- Views: 77
Re: Non-conformal mesh contacts
On the mortar condition there needs to be BC surfaces at the interface. Loading the mesh into ElmerGUI there are only 10 boundary surfaces all on the top faces of the surface.
I can't change this without the stp file.
I can't change this without the stp file.