Hi, can you attach the files you mention?

Hi, is this related to Github issue https://github.com/oofem/oofem/issues/170 (which has been resolved) or not?

The problem is that you are trying to apply surface load. The 2D elements, like quad1planestrain, have boundary edges and only one surface, corresponding to element itself. In general surfaces are entities of dimension 2, while edges are entities of dimension 1. So what you actually want is to apply edge load (ConstantEdgeLoad) on element edges.
I thus suggest the following modification:

load1 = oofempy.constantEdgeLoad(3, domain, loadTimeFunction=1, components=(1e6,0.), set=2, loadtype=3) # 1 MPa in x Direction
load2 = oofempy.constantEdgeLoad(4, domain, loadTimeFunction=1, components=(0.,1e6), set=3, loadtype=3) # 1 MPa in y Direction

...

set1 = oofempy.createSet(1, domain, elements=(1,))
set2 = oofempy.createSet(2, domain, elementedges=(1,2)) #x_pos
set3 = oofempy.createSet(3, domain, elementedges=(1,3)) #y_pos
set4 = oofempy.createSet(4, domain, elementedges=(1,4)) #x_neg
set5 = oofempy.createSet(5, domain, elementedges=(1,1)) #y_neg

This should fix the problem.

Hi Gereon,
thank you for sharing your repository link. I was able to trace the problem, which was in initialization of Domain object.
I believe I have fixed the problem in the official devel branch.

Unfortunately, you have forked your repo from Vit oofem repository, so I think  you have to ask Vit to merge the official devel branch into his repository, and then you can do the merge as well.

Borek.

Hi Gereon,
the elementboundaries is a list containing a sequence of pairs specifying the element number and boundary number.
So you can append additional pairs to the list. For example, to apply load also on boundary with id = 5 of element 2, you can use

set3 = oofempy.createSet(3, domain,elementboundaries=(1,2,2,5) )

Hi Gereon,
I have just pushed the commit to devel branch that solves your problem.

The prototype python code for demonstration:

import oofempy
import util

problem = oofempy.staticStructural(nSteps=1, outFile="test_5.out")

# domain (if no engngModel specified to domain, it is asigned to the last one created)
domain = oofempy.domain(1, 1, problem, oofempy.domainType._2dPlaneStressMode, tstep_all=True, dofman_all=True, element_all=True)
problem.setDomain(1, domain, True)

ltf1 = oofempy.constantFunction(1, domain, f_t=1.)
ltfs = (ltf1,)

# boundary conditions
bc1 = oofempy.boundaryCondition(1, domain, loadTimeFunction=1, prescribedValue=0.0)
n2 = oofempy.nodalLoad(2, domain, loadTimeFunction=1, components=(1.,0.), dofs=(1,2))
bcs = (bc1, n2)

# nodes
n1 = oofempy.node(1, domain, coords=(0.,  0., 0. ), bc=(bc1,bc1))
n2 = oofempy.node(2, domain, coords=(2.4, 0., 0. ), bc=(0,bc1))
n3 = oofempy.node(3, domain, coords=(2.4, 0.8, 0.), load=(n2,) )
n4 = oofempy.hangingnode(4, domain, coords=(1.2,  0.0, 0.), doftype=(2,2), dofidmask=(1,2))
nodes = (n1,n2,n3, n4)

# material and cross section
mat = oofempy.isoLE(1, domain, d=1., E=30.e3, n=0.2, tAlpha=1.2e-5)
cs  = oofempy.simpleCS(1, domain, thick=0.5, material=1, set=1)

# elements - assign through sets
e1 = oofempy.trPlaneStress2d(1, domain, nodes=(1,2,3))
elems = (e1,)

set1 = oofempy.createSet(1, domain, elements=(1,)) #Ettringite

# setup domain
util.setupDomain(domain, nodes, elems, (cs,), (mat,), bcs, (), ltfs, (set1,))

problem.init()
problem.postInitialize()
problem.checkProblemConsistency()
problem.solveYourself()

step = problem.giveCurrentStep(False)
problem.updateYourself(step)

#check solution
print (domain.giveDofManager(1).giveDofWithID(oofempy.DofIDItem.D_u).giveUnknown(oofempy.ValueModeType.VM_Total, step))
print (domain.giveDofManager(2).giveDofWithID(oofempy.DofIDItem.D_u).giveUnknown(oofempy.ValueModeType.VM_Total, step))
print (domain.giveDofManager(4).giveDofWithID(oofempy.DofIDItem.D_u).giveUnknown(oofempy.ValueModeType.VM_Total, step))

Hard question for linux guy ;-)
I found useful this link: https://learn.microsoft.com/en-us/visua … ew=vs-2022

In solution explorer, right click on liboofem target, select Properties, then go to Linker->Debugging and set "Debuggable Assembly" to YES. Rebuild oofemlib target, rebuild oofem target, start debugging (make sure you have Debug mode active).

I tested on VS 2022 and it works.

Hi,
the problem was really with CRLF/LF encoding.
After converting
- linDyn.in worked for me with recent GitHub version
- running nldyn.in ended up with segmentation fault, this is fixed now in GitHub
- now, both input decks give same results (compared (visually) on time history of x-displacement of node 2) on Linux.
I am not able to run it on Win right now.

HI Vit,
nice add on. Recently I have set up oofem blog, where announcements of new functionalities would fit nicely (https://oofem.github.io). You can try to make a new post on this.
Borek

Dear Gordan,
first of all, welcome.

I think your problems can be resolved, if you build only relevant targets from the solution. In your case, building "oofem" and "oofempy" targets is sufficient.

You don't need to set USE_HDF5=ON and install HDF5 libraries.
Additionally, the pybind11 is included as git submodule, so there is no need to install it separately.

Let me know,
Borek

Hi Fernando,

there are at least two options:
1) You can define local coordinate system in node (lcs keyword). When defined, all boundary conditions are applied in this local coordinate system. Also all unknowns (displacements, rotations, reaction forces) are computed in this local coordinate system. Illustrated in many tests, see, for example, tests/sm/beam2d_4.in
2) You can model inclined supports using stiff truss elements aligned with the direction of restrained displacement. In this case the outputs are in global coordinate system, but be careful here, introducing stiff elements can have impact on your solution, so the option 1 should be preferred.
Borek