OOFEM forum

Frictional contact fails with non-zero friction value

null@example.com (sandip) — Mon, 25 May 2026 07:35:27 +0000

We are exploring if we can use OOFEM to model a powder compaction problem. We understand that the Drucker-Prager model is readily supported, but the cap is not implemented. We are right now checking the DP model for powder compaction, where the setup has a frictionless punch and die bottom but has friction in the die walls and powder.

For the above context, to test the frictional contact boundary condition, we tried the tutorial problem shared on the OOFEM website. The shared example works as is when the friction value used is 0.0. But it fails when we use a non-zero friction value like 0.1. We need your input on whether this is supported. The modified solver input file is attached.

PETSc SEGV error with oofem -p

null@example.com (farrokh) — Mon, 23 Mar 2026 00:27:17 +0000

I am reporting a segmentation fault encountered when using the OOFEM -p.

OOFEM Build: Latest version with MPI and PETSc/MUMPS enabled.
Verification: ctest -R partest passed (14/14 tests).
Platform: WSL2 (Ubuntu) on Windows.

The Issue:
Running the attached TwoStepCasting_01.in with manual partitions TwoStepCasting_01.in.0 and TwoStepCasting_01.in.1 works correctly:
mpirun -np 2 ./oofem -f TwoStepCasting_01.in

However, using
mpirun -np 2 ./oofem -p -f TwoStepCasting_01.in

carshes into the following error:
------------------------------------------------------------------------------------------------
Job: TwoStepCasting_01.in.0
Job: TwoStepCasting_01.in.1
OctreeLocalizer: init
Solving [step number 1, time 7.200000e+03]
Applying initial conditions
Spatial localizer init done
Solving [step number 1, time 7.200000e+03]
Applying initial conditions
Assembling external forces
Assembling external forces
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind and https://petsc.org/release/faq/
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run
[0]PETSC ERROR: to get more information on the crash.
[0]PETSC ERROR: Run with -malloc_debug to check if memory corruption is causing the crash.
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 59.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------------------------------------------

I would appreciate any guidance on why the -p flag leads to this memory error in this specific parallel case.

OOFEM 2026 training course

null@example.com (bp) — Tue, 17 Mar 2026 23:28:51 +0000

We are happy to announce the next OOFEM training course. The course is targeting to Ph.D. students, engineers, and researchers to allow them to quickly acquire the knowledge and practical skills necessary to employ OOFEM.

Course date: 7.-9. September, 2026
Venue: Czech Technical University in Prague, Prague, Czech Republic
See http://www.oofem.org/en/courses for more information and registration

OOFEM 3.0 is officially out!

null@example.com (bp) — Mon, 29 Dec 2025 15:55:19 +0000

OOFEM 3.0 is officially out!

A major release packed with new capabilities: XML input reader, symbolic multi‑physics module, Pyodide/WASM support, additive manufacturing tools, vtkhdf5 export, new advection models, mechanical contacts, and more.

For detailed information see the ChangeLog

constantSurfaceLoad for PlaneStrain does not produce expected stresses

null@example.com (gereon.wildermann) — Wed, 10 Dec 2025 12:33:34 +0000

I am applying constantSurfaceLoad to a single quad1planestrain element, but the resulting stresses do not match the expected values. To illustrate the issue, I attached a minimal reproducible example (one element, 0.1 m edge length and 1 m thickness, 1 MPa surface load on each positive face):

import numpy as np
from oofem import util, oofempy

problem = oofempy.staticStructural(nSteps=2, outFile="test_square.out", stiffMode=1, manrmsteps=100000, maxiter=300, initialguess=0, rtolf=1e-3) # engngModel
domain = oofempy.domain(1, 1, problem, oofempy.domainType._PlaneStrainMode, tstep_all=True, dofman_all=True, element_all=True)
problem.setDomain(1, domain, True)

# load time function
ltf1 = oofempy.constantFunction(1, domain, f_t=1.)
ltfs = (ltf1, )
# boundary conditions
bc1   = oofempy.boundaryCondition(    1, domain, loadTimeFunction=1, dofs=(1,), prescribedValue=0.0, set=4)
bc2   = oofempy.boundaryCondition(    2, domain, loadTimeFunction=1, dofs=(2,), prescribedValue=0.0, set=5)
surf_load1 = oofempy.constantSurfaceLoad(3, domain, loadTimeFunction=1, components=(1e6,0.), set=2, loadtype=3) # 1 MPa in x Direction
surf_load2 = oofempy.constantSurfaceLoad(4, domain, loadTimeFunction=1, components=(0.,1e6), set=3, loadtype=3) # 1 MPa in y Direction
bcs = (bc1, bc2, surf_load1, surf_load2)

# nodes, elements and sets
n1= oofempy.node(1, domain, coords=(0.0, 0.0, 0.0))
n2= oofempy.node(2, domain, coords=(0.1, 0.0, 0.0))
n3= oofempy.node(3, domain, coords=(0.1, 0.1, 0.0))
n4= oofempy.node(4, domain, coords=(0.0, 0.1, 0.0))
nodes = (n1, n2, n3, n4)
elem1 = oofempy.quad1planestrain(1, domain, nodes=(n1, n2, n3, n4))
elems= (elem1,)
set1 = oofempy.createSet(1, domain, elements=(1,))
set2 = oofempy.createSet(2, domain, elementboundaries=(1,2)) #x_pos
set3 = oofempy.createSet(3, domain, elementboundaries=(1,3)) #y_pos
set4 = oofempy.createSet(4, domain, elementboundaries=(1,4)) #x_neg
set5 = oofempy.createSet(5, domain, elementboundaries=(1,1)) #y_neg
sets = (set1, set2, set3, set4, set5)

# material and cross section
mat1=oofempy.isoLE(1, domain, d=0.0, talpha=0, E=30e9, n=0.2)

cs1 = oofempy.simpleCS(1, domain, thick=1, material=1, set=1)

mats = (mat1,)
cs = (cs1,)

# add eveything to domain
util.setupDomain (domain, nodes, elems, cs, mats, bcs, (), ltfs, sets)
vtkxml = oofempy.vtkxml(1,problem, domain_all=True, tstep_all=True, dofman_all=True, element_all=True, vars=(1,2,4,12), stype=1)
vtkPy =  oofempy.vtkmemory(1,problem, domain_all=True, tstep_all=True, dofman_all=True, element_all=True, vars=(1,2,4,), stype=1, pythonExport=1)

print("\nSolving problem")
problem.init()
problem.postInitialize()
problem.checkProblemConsistency()

problem.giveTimer().startTimer(oofempy.EngngModelTimerType.EMTT_AnalysisTimer)
activeMStep = problem.giveMetaStep(1)
problem.initMetaStepAttributes(activeMStep)
problem.setRenumberFlag()

t_global = 0.
t_final = 1.
dt= 1.
while t_global < t_final:
    t_global+=dt

    #run oofem
    problem.preInitializeNextStep()
    problem.giveNextStep()
    currentStep = problem.giveCurrentStep()
    print("Current step:", currentStep.giveNumber())
    currentStep.setTargetTime(float(t_global))
    problem.initializeYourself(currentStep)
    problem.solveYourselfAt(currentStep)
    problem.updateYourself( currentStep )
    problem.terminate( currentStep ) 
    #evaluating fields
    for p in vtkPy.getExportRegions():
        stress = p.getInternalVertexValues(oofempy.InternalStateType.IST_StressTensor)
        vertices = p.getVertices()
        print("Average stress in x direction:", np.mean(stress, axis=0)[0]/1e6, "MPa; Expected:", 1 , "MPa")
        print("Average stress in y direction:", np.mean(stress, axis=0)[4]/1e6, "MPa; Expected:", 1 ,"MPa")
        print("Average stress in z direction:", np.mean(stress, axis=0)[8]/1e6, "MPa; Expected:", 0.2*(1. + 1.),"MPa")

problem.terminateAnalysis()
print("done")

The computed stresses differ from my expected values

Average stress in x direction: 0.05 MPa; Expected: 1 MPa
Average stress in y direction: 0.05 MPa; Expected: 1 MPa
Average stress in z direction: 0.020000000000000004 MPa; Expected: 0.4 MPa

My question is whether this behavior arises from incorrect input or misuse of constantSurfaceLoad on my side, or whether it points to an underlying issue in the current implementation.

I am using the current version of my fork [url=https://github.com/gereonwildermann/oofem-gw/tree/devel]oofem-gw
(devel)[/url], recently merged with the latest oofem/devel.

Any insights or suggestions would be very helpful.

Thank you!

DSS solver fails to build on Windows/MSVC

null@example.com (ChristosM) — Wed, 03 Dec 2025 18:42:41 +0000

Hi,

I’m trying to enable the DSS linear solver in OOFEM on Windows using Visual Studio 2022.
I have Cloned upstream OOFEM (https://github.com/oofem/oofem.git) and Configured with CMake:
cmake -S . -B build-vs -G "Visual Studio 17 2022" -DUSE_DSS=ON
After I tried to built target liboofem in Release or Debug.

The build always fails with the same 10 linker errors, for example:
dssmatrix.obj : error LNK2001: unresolved external symbol "public: virtual bool __cdecl oofem::DSSMatrix::canBeFactorized(v
oid)const " (?canBeFactorized@DSSMatrix@oofem@@UEBA_NXZ)
dssmatrix.obj : error LNK2001: unresolved external symbol "public: virtual enum oofem::SparseMtrxType __cdecl oofem::DSSMat
rix::giveType(void)const " (?giveType@DSSMatrix@oofem@@UEBA?AW4SparseMtrxType@2@XZ)
dssmatrix.obj : error LNK2001: unresolved external symbol "public: virtual bool __cdecl oofem::DSSMatrix::isAsymmetric(void
)const " (?isAsymmetric@DSSMatrix@oofem@@UEBA_NXZ)

and similar errors for DSSSolver.
Is DSS expected to work on Windows/MSVC in the current version?
Is there a known patch or branch where DSS is maintained?

Thank you

Bond-slip models in Python

null@example.com (gereon.wildermann) — Mon, 11 Aug 2025 11:29:03 +0000

Hi everyone,

I am trying to implement the bond–slip behaviour for reinforced concrete (BondCEB) in Python by replicating the bondceb02.in OOFEM test.

To do so, the Python script below was used.
Of course, oofempy.bondceb, oofempy.InterfaceCS, and oofempy.IntELPoint had already been added to the binding files.

import oofempy
import util 

# Create problem - BondCEB interface material - rebar pull-out in 3D
problem = oofempy.staticStructural(
    nSteps=20, 
    deltat=1.0,
    outFile="bondceb02.out", 
    rtolf=1.0e-3, 
    maxiter=50, 
    initialguess=1,
    nmodules=1,
    errorcheck=True,
)

# Create domain
domain = oofempy.domain(1, 1, problem, oofempy.domainType._3dMode, tstep_all=True, dofman_all=True, element_all=True)
problem.setDomain(1, domain, True)

# Load time function
ltf1 = oofempy.piecewiseLinFunction(1, domain, t=(0.0, 20.0), f_t=(0.0, 1.0))
ltfs = (ltf1,)

# Nodes
n1 = oofempy.node(1, domain, coords=(-0.1, -0.1, 0.1))
n2 = oofempy.node(2, domain, coords=(-0.1, 0.0, 0.1))
n3 = oofempy.node(3, domain, coords=(0.1, 0.0, 0.1))
n4 = oofempy.node(4, domain, coords=(0.1, -0.1, 0.1))
n5 = oofempy.node(5, domain, coords=(-0.1, -0.1, -0.1))
n6 = oofempy.node(6, domain, coords=(-0.1, 0.0, -0.1))
n7 = oofempy.node(7, domain, coords=(0.1, 0.0, -0.1))
n8 = oofempy.node(8, domain, coords=(0.1, -0.1, -0.1))
n9 = oofempy.node(9, domain, coords=(-0.1, 0.1, 0.1))
n10 = oofempy.node(10, domain, coords=(0.1, 0.1, 0.1))
n11 = oofempy.node(11, domain, coords=(-0.1, 0.1, -0.1))
n12 = oofempy.node(12, domain, coords=(0.1, 0.1, -0.1))

# rebar nodes
n13 = oofempy.node(13, domain, coords=(-0.1, 0.0, 0.1), dofidmask=(1,2,3,4,5,6))  # beam node
n14 = oofempy.node(14, domain, coords=(0.1, 0.0, 0.1), dofidmask=(1,2,3,4,5,6))   # beam node

nodes = (n1, n2, n3, n4, n5, n6, n7, n8, n9, n10, n11, n12, n13, n14)

# Elements
e1 = oofempy.lspace(1, domain, nodes=(1, 2, 3, 4, 5, 6, 7, 8))  # concrete element 1
e2 = oofempy.lspace(2, domain, nodes=(2, 9, 10, 3, 6, 11, 12, 7))  # concrete element 2
e3 = oofempy.beam3d(3, domain, nodes=(13, 14), refnode=9)  # rebar beam element
e4 = oofempy.IntELPoint(4, domain, nodes=(2, 13), normal=(0, 0, 1), length=0.1)  # bond element 1
e5 = oofempy.IntELPoint(5, domain, nodes=(3, 14), normal=(0, 0, 1), length=0.1)  # bond element 2

elems = (e1, e2, e3, e4, e5)

# Materials
mat1 = oofempy.isoLE(1, domain, d=1.0, E=3.36e10, n=0.2, tAlpha=1.0)  # concrete material
mat2 = oofempy.isoLE(2, domain, d=1.0, E=2e11, n=0.3, tAlpha=1.0)     # rebar material
mat3 = oofempy.bondceb(3, domain, 
                       kn=6e12, ks=6.135e10, 
                       s1=0.001, s2=0.002, s3=0.0065, 
                       taumax=1.541e7, tauf=6.164e6)  # bond material

materials = (mat1, mat2, mat3)

# Cross sections
cs1 = oofempy.simpleCS(1, domain, material=1, set=1)  # concrete cross section
cs2 = oofempy.simpleCS(2, domain, area=3.1416e-4, material=2, set=2)  # rebar cross section  
cs3 = oofempy.InterfaceCS(3, domain, thickness=6.28319e-2, material=3, set=3)  # interface cross section

cross_sections = (cs1, cs2, cs3)

# Sets
set1 = oofempy.createSet(1, domain, elements=(1, 2))  # concrete elements
set2 = oofempy.createSet(2, domain, elements=(3,))    # rebar element
set3 = oofempy.createSet(3, domain, elements=(4, 5))  # bond elements
set4 = oofempy.createSet(4, domain, nodes=(1,))       # fixed node (all DOFs)
set5 = oofempy.createSet(5, domain, nodes=(1, 4))     # nodes with constrained y,z
set6 = oofempy.createSet(6, domain, nodes=(14,))      # loaded node

sets = (set1, set2, set3, set4, set5, set6)

# Boundary conditions
bc1 = oofempy.boundaryCondition(1, domain, loadTimeFunction=1, 
                               prescribedValue=0.0, dofs=(1, 2, 3), set=4)  # fixed support
bc2 = oofempy.boundaryCondition(2, domain, loadTimeFunction=1, 
                               prescribedValue=0.0, dofs=(2, 3), set=5)     # y,z constraint
bc3 = oofempy.boundaryCondition(3, domain, loadTimeFunction=1, 
                               prescribedValue=0.0, dofs=(4, 5, 6), set=2)  # rotation constraint rebar beam element
bc4 = oofempy.boundaryCondition(4, domain, loadTimeFunction=1, 
                               prescribedValue=8e-3, dofs=(1,), set=6)      # prescribed displacement

boundary_conditions = (bc1, bc2, bc3, bc4)

# Setup domain
util.setupDomain(domain, nodes, elems, cross_sections, materials, boundary_conditions, (), ltfs, sets)

print("\nSolving BondCEB rebar pull-out problem")

# Initialize problem
problem.init()
problem.postInitialize()
problem.checkProblemConsistency()

# Start analysis timer
problem.giveTimer().startTimer(oofempy.EngngModelTimerType.EMTT_AnalysisTimer)
activeMStep = problem.giveMetaStep(1)
problem.initMetaStepAttributes(activeMStep)
problem.setRenumberFlag()

# Solve all time steps
for step in range(1, 21):  # 20 steps
    problem.preInitializeNextStep()
    problem.giveNextStep()
    currentStep = problem.giveCurrentStep()
    
    print(f"Solving step {step}, time = {step * 1.0}")
    currentStep.setTargetTime(float(step * 1.0))
    
    problem.initializeYourself(currentStep)
    problem.solveYourselfAt(currentStep)
    problem.updateYourself(currentStep)
    problem.terminate(currentStep)
    


# Terminate analysis
problem.terminateAnalysis()
print("\nBondCEB analysis completed successfully!")

When the Python script is excecuted, the function problem.postInitialize() throws following error:

RuntimeError: Unsupported mode
In giveDofManDofIDMask (oofem/src/sm/Elements/Interfaces/intelpoint.C:299)

What is causing this “Unsupported mode” error in IntELPoint, and how can I resolve it?
Is it related to the dofidmask that is assigned to the interface element’s nodes (n13 and n14), or is there another initialization step I’m missing?

Thanks in advance for your help!

Set of Element Boundaries for constantSurfaceLoad in Python

null@example.com (gereon.wildermann) — Fri, 02 May 2025 16:34:41 +0000

Is it possible to create a set of multiple element boundaries in order to apply the same constantSurfaceLoad to multiple elements?

I added a short example of a python code. In set3 I define the surface where I want to apply the surface load(e.g. element 1 surface 2). What is the best way to add the surface of element 2 to this set?

import oofempy
import util # some utility functions
import numpy as np
problem = oofempy.staticStructural(nSteps=2, outFile="test_boundaryload.out", rtolf=1e-3, lstype=4, stiffMode=1, smtype=8, manrmsteps=100000, maxiter=200, initialguess=0) # engngModel
domain = oofempy.domain(1, 1, problem, oofempy.domainType._3dMode, tstep_all=True, dofman_all=True, element_all=True)
problem.setDomain(1, domain, True)
# load time function
ltf1 = oofempy.constantFunction(1, domain, f_t=1.)
ltfs = (ltf1, )
# boundary conditions
# loadTimeFunction parameter can be specified as int value or as LoadTimeFunction itself (valid for all objects with giveNumber() method)
bc1   = oofempy.boundaryCondition(    1, domain, loadTimeFunction=1,    prescribedValue=0.0)
surf_load = oofempy.constantSurfaceLoad(2, domain, loadTimeFunction=1, components=(0.,0.,-10e6), set=3, dofs=(1,2,3), loadtype=3)
bcs = (bc1,surf_load)
# nodes
# if one value is passed as parameter where oofem expects array of values, it must be passed as tuple or list (see load in n4)
n1 = oofempy.node(1, domain, coords=(0.,  0., 0. ), bc=(1,1,1))
n2 = oofempy.node(2, domain, coords=(0.1, 0., 0. ), bc=(0,0,1))
n3 = oofempy.node(3, domain, coords=(0.1, 0.1, 0. ), bc=(0,0,1))
n4 = oofempy.node(4, domain, coords=(0., 0.1, 0. ), bc=(0,0,1))
n5 = oofempy.node(5, domain, coords=(0., 0., 0.1), bc=(0,0,0))
n6 = oofempy.node(6, domain, coords=(0.1, 0., 0.1), bc=(0,0,0))
n7 = oofempy.node(7, domain, coords=(0.1, 0.1, 0.1), bc=(0,0,0))
n8 = oofempy.node(8, domain, coords=(0., 0.1, 0.1), bc=(0,0,0))
n9 = oofempy.node(9, domain, coords=(0.,  0.2, 0. ), bc=(0,0,1))
n10 = oofempy.node(10, domain, coords=(0.1, 0.2, 0. ), bc=(0,0,1))
n11 = oofempy.node(11, domain, coords=(0., 0.2, 0.1), bc=(0,0,0))
n12 = oofempy.node(12, domain, coords=(0.1, 0.2, 0.1), bc=(0,0,0))

nodes = (n1, n2, n3, n4, n5, n6, n7, n8, n9, n10, n11, n12)
# material and cross section
mat_1 = oofempy.isoLE(1, domain, d=1., E=30e9, n=0.2, tAlpha=1.2e-5)
mat = (mat_1,)
cs1 = oofempy.simpleCS(1, domain, material=1, set=1)
cs = (cs1,)

# elements
e1 = oofempy.lspace(1, domain, nodes=(1,2,3,4,5,6,7,8))
e2 = oofempy.lspace(2, domain, nodes=(4,3,10,9,8,7,12,11))
elems = (e1,e2)

volume_elem_center_1 = np.array([0.05, 0.05, 0.05])
volume_elem_center_2 = np.array([0.15, 0.15, 0.15])

#sets
set1 = oofempy.createSet(1, domain, elements=(1,2)) #volume with material 1 and cross section 1
set2 = oofempy.createSet(2, domain, nodes=(5,6,7,8)) #nodes with prescribed load
set3 = oofempy.createSet(3, domain,elementboundaries=(1,2) ) #set of element boundaries with surface load
sets = (set1, set2, set3)

# add eveything to domain
util.setupDomain (domain, nodes, elems, cs, mat, bcs, (), ltfs, sets)

print("\nSolving problem")
problem.init()
problem.postInitialize()
problem.checkProblemConsistency()
problem.setRenumberFlag()
problem.solveYourself()
problem.terminateAnalysis()
print("done")

#evaluating fields

internalFieldStress = oofempy.InternalVariableField( oofempy.InternalStateType.IST_StressTensor, oofempy.FieldType.FT_Unknown, oofempy.MaterialMappingAlgorithmType.MMA_ShapeFunctionProjection, domain)
currentStep = problem.giveCurrentStep()
answer=oofempy.FloatArray()
coord = oofempy.FloatArray(volume_elem_center_1)
internalFieldStress.evaluateAt(answer, coord, oofempy.ValueModeType.VM_Total, currentStep)
print("Stress at center of element 1: ", answer)

answer=oofempy.FloatArray()
coord = oofempy.FloatArray(volume_elem_center_2)
internalFieldStress.evaluateAt(answer, coord, oofempy.ValueModeType.VM_Total, currentStep)
print("Stress at center of element 2: ", answer)

Using HangingNode in Python

null@example.com (gereon.wildermann) — Fri, 14 Mar 2025 08:49:09 +0000

Hello,
in order to model reinforced concrete, I would like to model the rebar using hanging nodes within oofempy.
How are the hanging nodes getting initialized correctly, since there is no class called oofempy.hangingnode ?

Regards Gereon

Additive Manufacturing test output

null@example.com (rskacelik) — Tue, 19 Nov 2024 17:29:05 +0000

I tried a test job for AM and I couldn't get the SM to print to vtk.
I added a line to the structural mechanics test job with the vtk output "vtkxml tstep_step 60 domain_all element_all primvars 1 1"
The program prints only the header of the vtk file.
I also increased the number of steps to 1000 to actually activate the elements in the storage. I get the temperature results after adjusting the number of steps but not the structural mechanics.
In the structural mechanics test this output is not present, can the oofem display these results or does it only calculate the temperature fields
Thank you for your help.
R.S.

Fibered cross section

null@example.com (johnnyontheweb) — Sun, 04 Aug 2024 19:07:22 +0000

Hi all,
I write about FiberedCrossSection, for which I made a trial improvement that can be seen here:
https://github.com/johnnyontheweb/oofem … 2885a10377

by adding the possibility to specify areas and positions for fibers, hence the class is not limited to rectangular fibers (for instance, think about a round cross section subdivided in triangular portions). Please find attached a test input deck.

I haven't already asked a Pull Request, simply because I was looking for material models to use with; it seems only IsoLE is actually supported (the so called _Fiber material mode). Can you confirm? Has it been used before in some of your scientific works? I cannot find any sample other than fiberedcs01.in in tests/sm.

As far I understand, each fiber material gives {sigmaX, tauXY, tauXZ}, hence also shear and torsion for beams can be integrated over the fibers. If so, every 3d material in OOFEM can be interfaced with fiber section by providing:
- stresses: just {sigmaX, tauXY, tauXZ}
- tangent material matrix 3x3: just set the diagonal as {d.at(1,1), d.at(4,4), d.at(5,5)}, where d is the Jacobian matrix. The material stiffness d.at(1,1) does not have mixed terms since other Eps and Gamma are 0. In addition, in isotropic elastic conditions d.at(4,4)=d.at(5,5)=G. As a consequence, it could make sense also having orthotropic material in fibers, just to have different Gs, but in this case fiberedcs will return the wrong stiffness matrix, because tangent is provided for torsion by using d(2,2) only.

Is it as simple as that or am I missing something? I kindly ask your advice in order to plan to add the needed code for _Fiber interface in other materials (e.g. Concrete02, etc.).
thanks in advance

EDIT:
just to clarify: the question for implementation is relative the material that redefines material mode and don't have support for _Fiber (StructuralMaterial has it, hence if not overloaded, all good).

Does VTK output work on Windows?

null@example.com (mpalaversa) — Tue, 16 Jul 2024 17:55:33 +0000

Is it possible to use VTK output on Windows? I haven't managed to make it work.

I have done the following: downloaded VTK, generated the solution in Cmake (included only BUILD_SHARED_LIBS), built sucessfully in VS, generated OOFEM solution in Cmake with USE_VTK included and path set to VTK's bin directory in VTK_DIR. When I go to VS after that, it doesn't find the VTK related .h files. I have tried this with the last code from OOFEM's main master and from master in my fork (this is OOFEM code from a few years ago) and I get the same errors on both.

Compilation problems on Mac

null@example.com (gustel) — Fri, 07 Jun 2024 12:51:09 +0000

I have not updated my OOFEM fork for a while with the development version. When I now try to do this, I cannot compile the current development version on my Mac. Does anybody know how to resolve it?

The compilation errors seems to start with the SolutionStatusExportModule commit: https://github.com/oofem/oofem/commit/a … c960abf33b

The error line is like this:
============================
/oofemOriginal/src/oofemlib/solutionstatusexportmodule.C:151:76: error: cannot pass object of non-trivial type 'std::string' (aka 'basic_string') through variadic method; call will abort at runtime [-Wnon-pod-varargs]
============================

If I comment this line out, I get linking errors like
============================
"_HOST_TYPE", referenced from:
oofem::SolutionStatusExportModule::initialize() in solutionstatusexportmodule.C.o
"_MODULE_LIST", referenced from:
oofem::SolutionStatusExportModule::initialize() in solutionstatusexportmodule.C.o
"_OOFEM_GIT_HASH", referenced from:
oofem::SolutionStatusExportModule::initialize() in solutionstatusexportmodule.C.o
"_PRG_HEADER", referenced from:
oofem::OutputExportModule::initializeFrom(oofem::InputRecord&) in outputexportmodule.C.o
oofem::EngngModel::initializeFrom(oofem::InputRecord&) in engngm.C.o
oofem::StaggeredProblem::initializeFrom(oofem::InputRecord&) in staggeredproblem.C.o
oofem::EigenValueDynamic::initializeFrom(oofem::InputRecord&) in eigenvaluedynamic.C.o
oofem::LinearStability::initializeFrom(oofem::InputRecord&) in linearstability.C.o
oofem::IncrementalLinearStatic::initializeFrom(oofem::InputRecord&) in incrementallinearstatic.C.o
"_PRG_VERSION", referenced from:
oofem::SolutionStatusExportModule::initialize() in solutionstatusexportmodule.C.o
=====================================

IsotropicAsymmetric1DMaterial producing error

null@example.com (Chris) — Tue, 21 May 2024 23:53:00 +0000

Hi,

I am trying to use isoasymm1d material with Beam3D, to simulate tension / compression only members. My input deck is simple, but once I attempt to assign the material to an element, I get the output:

Error:property #71 on element 9 and GP 1 not defined
In IsotropicAsymmetric1DMaterial::oofem::Material::give, number: 2 (material.C:60)

Am I doing something wrong? How can I apply this material to Beam3D elements?

Thank you in advance.

Cannot compile in VS / Windows after last changes

null@example.com (johnnyontheweb) — Tue, 21 May 2024 10:44:03 +0000

Hello,
I cannot compile oofem with Visual Studio under windows after the changes occurred in 14/15 May 2024, please see:
https://github.com/oofem/oofem/issues/1 … 2119024032