Elmer Discussion Forum

But surely, no one can expect me to be able to debug the Elmer code itself as I never was involved in its design !

Hello Well, fine I went back to the first test I uploaded to this forum and I printed ngp as well. the minimum (maximum) of both ngp and nd is 3 (4) I then commented out the DEALLOCATE code and altered the allocate code following it to IF (.NOT. ALLOCATED(Basis)) THEN ALLOCATE(Basis(4,4), dBasisdx(4...

I have replaced TimeCoeff => ListGetElementRealVec( TimeCoeff_h, 4, Basis, Element, Found ) by IF (t >Active/2) THEN TimeCoeff => ListGetElementRealVec( TimeCoeff_h, 5, Basis, Element, Found ) ELSE TimeCoeff => ListGetElementRealVec( TimeCoeff_h, 4, Basis, Element, Found ) ENDIF Now TimeCoeff points...

I managed to simplify the SIF and code tremendously and still get the erroneous output. I ran on: OS - RedHat or CentOS Compiler - intel/2020.1.217 with the following commands (everything is attached in weirdbug.zip) elmerf90 -o SoSimpleTest.so SoSimpleTest.F90 ElmerSolver timecoef.sif > printout.tx...

This function is to be found in file Lists.F90. Its 2nd parameter, ngp, is the number of Gaussian integration points. ngp is a function of the element type. It will thus vary as I loop over all active elements in the mesh. Now when I call this function, setting this 2nd parameter to a constant equal...

I am sure this will happen to somebody else so I will answer my own question: When you add your routines in the CONTAINS clause of your modified Elmer solver, then the following code will avoid memory corruption after you call your routines (denoted by MyTest1 and MyTest2 ) ..... MyVar1 = 1 !$OMP PA...

Good day everybody

I would assume GetNOFColours(Solver) has nothing to do with colors in a photo. I see it being used in conjunction with OpenMP directives
( anything that starts with !$OMP ) but comments associated with colours are very scanty in the Elmer code.

Hi

If I see that a solver contains !$OMP directives and I add my own subroutine to it, how I can ensure segmentation fault errors will not occur in that subroutine when I call it ?

Regards

I think it was compiled around March 2021.

There seems to be a limit to the number of exported variables within a solver section because I get : MAIN: Reading Model: 2023.sif LoadInputFile: Scanning input file: 2023.sif LoadInputFile: Scanning only size info LoadInputFile: First time visiting LoadInputFile: Reading base load of sif file ERRO...