Search found 46 matches
Re: emacs
Thanks for the tip Carlos. As I'm a vi fan I did a quick syntax file for vi. to put under ~/.vim/syntax/sif.vim if version < 600 syn clear elseif exists("b:current_syntax") finish endif syn case ignore syn keyword SifType Real Integer Logical String File Procedure MATC syn match SifNumber ...
- 30 Jun 2011, 11:20
- Forum: ElmerSolver
- Topic: Sliding and non penetration
- Replies: 5
- Views: 3857
Re: Sliding and non penetration
Hi Juha, Yes I tried the "Normal-Tangential Velocity Rotate = Logical False" flag. It has no effect if I use a Slip coeff in direction 1, but I get very high vertical velocities if I use the Dirichlet Condition with this flag. If I reduce the "large number" I see an increase of t...
- 29 Jun 2011, 15:49
- Forum: ElmerSolver
- Topic: Sliding and non penetration
- Replies: 5
- Views: 3857
Re: Sliding and non penetration
Hi Juha, If I put a large number for Slip Coefficient 1 I get zero velocities (in every direction), so that the no flux condition is respected, but I loose my sliding velocities. What about 2nd order elements? Would it be possible to add the definition of 715 elements in the function GetElementSide ...
- 23 Jun 2011, 17:32
- Forum: ElmerSolver
- Topic: Sliding and non penetration
- Replies: 5
- Views: 3857
Sliding and non penetration
Dear all, I'm loosing mass through my bottom boundary where I have a sliding law and a non-penetration condition in Normal tangential for the Stokes Solver: Boundary Condition 2 Target Boundaries = 1 Flow Force BC = Logical True Normal-Tangential Velocity = Logical True Velocity 1 = Real 0.0 Slip Co...
- 07 Jan 2011, 20:43
- Forum: Bug reports
- Topic: Save Scalars and Parallel Reduce
- Replies: 1
- Views: 3729
Save Scalars and Parallel Reduce
Hi in the SaveScalars, for Boundary integrals there is lines like this DO j=1,Model % NumberOfBCs IF( BoundaryHits(j) > 0 ) THEN IF( TRIM(Oper) == 'boundary int mean' ) THEN BoundaryFluxes(j) = BoundaryFluxes(j) / BoundaryAreas(j) END IF WRITE (Name,'(A,A,A,A,I2)') TRIM(Oper),': ',TRIM(VariableName)...
- 30 Sep 2010, 17:14
- Forum: Bug reports
- Topic: MUMPS workspace too small
- Replies: 5
- Views: 7159
MUMPS workspace too small
Dear Elmer Developpers; I've had troubles recently with mumps for big parallel simulations; The error message from mumps is WORKSPACE TOO SMALL FOR DMUMPS_ ERROR RETURN ** FROM DMUMPS INFO(1)= -9 etc... It's possible to solve this problem by defining mumps control parameter icntl(14) (i.e by adding ...