Search found 79 matches
- 22 May 2013, 21:34
- Forum: Software development
- Topic: Why p elements are applied to ALL solvers?
- Replies: 1
- Views: 4063
Why p elements are applied to ALL solvers?
Hello, If using p-element in one solver, by setting Element = "p:1 b:4" it appears that all the other solvers are also integrating using p-elements, i.e. for 706 elements we get CurrentElement % pdefs % gausspoints is equal to 343 CurrentElement % bdofs is equal to 4 whereas for 'normal' 7...
- 08 May 2013, 01:06
- Forum: External tools
- Topic: only the first component exported in vtu format
- Replies: 5
- Views: 6694
only the first component exported in vtu format
Hello, I have the strange behaviour that only the first component of an exported variable with dofs>1 is saved in the vtu output file. The export of the variable in the sif file writes: Solver i ... Exported Variable 1 = -dofs 2 "Integrated Velocity" End but only "Integrated velocity ...
- 06 May 2013, 20:38
- Forum: Software development
- Topic: Edges values
- Replies: 4
- Views: 5522
Re: Edges values
Hello, I post here the reply I had from Juha regarding my second post of this list. Olivier Hi, the edges should have faces as "boundaryinfo % left & right" pointers. In 3D the two are just some of the faces that the edge joins, no way to control that in advance i think. The parent ele...
- 02 May 2013, 02:21
- Forum: Software development
- Topic: Edges values
- Replies: 4
- Views: 5522
Re: Edges values
Hi Thomas, Thanks for your answer. For the second post (no material associated with edge elements) I really don't think that the problem comes from here as I'm working on a 2D test case (no extrusion). For the first post (about the different behaviour for 3D meshes), yes it might be the raison, the ...
- 28 Apr 2013, 02:04
- Forum: Software development
- Topic: Edges values
- Replies: 4
- Views: 5522
Re: Edges values
Hello again, One more issue I'm facing with using edge element. It seems that like for boundary element, no material is associated? In the solver, I have a loop over the edge elements and need "material" to read parameters in the material section of the sif file. DO t=1, Solver % Mesh % Nu...
- 27 Apr 2013, 03:25
- Forum: Software development
- Topic: Edges values
- Replies: 4
- Views: 5522
Edges values
Hello, I have developed a solver for which the variable is defined as a edge value (one value per element edge) of 303 or 404 elements of a 2D mesh. For that purpose, I set Element = "n:0 e:1" in the solver section This is working fine if my global mesh is 2D (i.e. if the global mesh is th...
- 12 Mar 2013, 04:30
- Forum: Software development
- Topic: dBasisdx over Edges
- Replies: 1
- Views: 3514
dBasisdx over Edges
Hello, I'm solving for a variable defined on the element edges (202 type element). For the assembly, I'm doing a loop over Solver % Mesh % NumberOfEdges. The call to ElementInfo return Basis(1:2) = [0.21132486540518713 0.78867513459481287] dBasisdx(1:2,1) = [0.0000000000000000 0.0000000000000000 ] d...
- 22 Nov 2012, 21:35
- Forum: Installation & compilation
- Topic: src to f90 introduce error in f90 files
- Replies: 3
- Views: 3145
Re: src to f90 introduce error in f90 files
Hi again,
I have changed my c compiler (was the GNU GCC 4.8.0 20120603, and I came back to the apple compiler) and it solves the problem.
Might come from the cpp which clean de src by deleting c comments (but why in f90 files ?).
Regards,
Olivier
I have changed my c compiler (was the GNU GCC 4.8.0 20120603, and I came back to the apple compiler) and it solves the problem.
Might come from the cpp which clean de src by deleting c comments (but why in f90 files ?).
Regards,
Olivier
- 22 Nov 2012, 18:28
- Forum: Installation & compilation
- Topic: src to f90 introduce error in f90 files
- Replies: 3
- Views: 3145
Re: src to f90 introduce error in f90 files
Hi Peter,
It is not only the isovarying_string.f90 function. It is ALL function which contain '//' somewhere that are changed when moving from .src to .f90...
Olivier
It is not only the isovarying_string.f90 function. It is ALL function which contain '//' somewhere that are changed when moving from .src to .f90...
Olivier
- 22 Nov 2012, 09:41
- Forum: Installation & compilation
- Topic: src to f90 introduce error in f90 files
- Replies: 3
- Views: 3145
src to f90 introduce error in f90 files
Hello, I have a strange behaviour I have never experienced so far! Some of the .f90 files build from the fem/src .src files contain errors: at least, each time there is '//', the end of the line is deleted in the f90 file. For example, the line interface operator(//) in iso_varying_string.src writes...