b0136d835e
- the earlier implementation of externally controlled lumped point motion (see merge request !120 and OpenFOAM-v1706 release notes) was conceived for the motion of simple structures such as buildings or simple beams. The motion controller was simply defined in terms of an orientation axis and divisions along that axis. To include complex structures, multiple motion controllers are defined in terms of support points and connectivity. The points can have additional node Ids associated with them, which makes it easier to map to/from FEA models. OLD system/lumpedPointMovement specification -------------------------------------------- //- Reference axis for the locations axis (0 0 1); //- Locations of the lumped points locations (0 0.05 .. 0.5); NEW system/lumpedPointMovement specification -------------------------------------------- // Locations of the lumped points points ( (0 0 0.00) (0 0 0.05) ... (0 0 0.50) ); //- Connectivity for motion controllers controllers { vertical { pointLabels (0 1 2 3 4 5 6 7 8 9 10); } } And the controller(s) must be associated with the given pointDisplacement patch. Eg, somePatch { type lumpedPointDisplacement; value uniform (0 0 0); controllers ( vertical ); // <-- NEW } TUT: adjust building motion tutorial - use new controllor definitions - replace building response file with executable - add updateControl in dynamicMeshDict for slowly moving structure
35 lines
1.2 KiB
Bash
Executable File
35 lines
1.2 KiB
Bash
Executable File
#!/bin/sh
|
|
cd "${0%/*}" || exit # Run from this directory
|
|
. ${WM_PROJECT_DIR:?}/bin/tools/RunFunctions # Tutorial run functions
|
|
#------------------------------------------------------------------------------
|
|
|
|
# Cleanup old junk that may prevent things from starting
|
|
rm -f comms/OpenFOAM.lock
|
|
|
|
# If OpenFOAM stops prematurely, trigger the external solver to stop
|
|
trap '[ -e comms/OpenFOAM.lock ] && echo "status=done" > comms/OpenFOAM.lock' EXIT TERM INT
|
|
|
|
# Simulated external solver.
|
|
# Using -scale 0.01 since input movement table included visual scaling
|
|
|
|
if false
|
|
then
|
|
# Create response file
|
|
runApplication -overwrite \
|
|
../code/building-motion -deltaT 0.001 -nTimes 5001 -output response.txt
|
|
|
|
# Use response file for states
|
|
runApplication -overwrite \
|
|
lumpedPointMovement -scale 0.01 -removeLock -slave response.txt &
|
|
else
|
|
|
|
# Generate states on demand
|
|
runApplication -overwrite \
|
|
../code/building-motion -scale 0.01 -removeLock -slave &
|
|
fi
|
|
|
|
# Run moveMesh with deltaT corresponding to dynamicMeshDict updateInterval
|
|
runParallel moveMesh -deltaT 0.001
|
|
|
|
#------------------------------------------------------------------------------
|