DEFEATURE: remove ccm26ToFoam (issue #536)
- not maintained and less functionality than ccmToFoam.
This commit is contained in:
parent
63812aa110
commit
6e8586df5d
@ -1,36 +0,0 @@
|
||||
#!/bin/sh
|
||||
#------------------------------------------------------------------------------
|
||||
cd ${0%/*} || exit 1 # Run from this directory
|
||||
|
||||
# Optional component: continue-on-error
|
||||
# - may not have third-party installed
|
||||
export WM_CONTINUE_ON_ERROR=true
|
||||
|
||||
# Parse arguments for compilation (at least for error catching)
|
||||
. $WM_PROJECT_DIR/wmake/scripts/AllwmakeParseArguments
|
||||
|
||||
warning="==> skip ccmio"
|
||||
|
||||
if settings=$($WM_PROJECT_DIR/bin/foamEtcFile config.sh/ccmio)
|
||||
then
|
||||
. $settings
|
||||
else
|
||||
echo "$warning (no config.sh/ccmio settings)"
|
||||
exit
|
||||
fi
|
||||
|
||||
# Build libccmio (.a|.so) - use static linkage for fewer issues
|
||||
$WM_THIRD_PARTY_DIR/makeCCMIO lib
|
||||
|
||||
: ${FOAM_EXT_LIBBIN:=/usr/lib$WM_COMPILER_LIB_ARCH} # Extra safety
|
||||
export FOAM_EXT_LIBBIN
|
||||
|
||||
if [ -e $CCMIO_ARCH_PATH/include/libccmio/ccmio.h \
|
||||
-a \( -e $CCMIO_ARCH_PATH/lib/libccmio.a -o -e $FOAM_EXT_LIBBIN/libccmio.so \) ]
|
||||
then
|
||||
wmake $targetType ccm26ToFoam
|
||||
else
|
||||
echo $warning
|
||||
fi
|
||||
|
||||
#------------------------------------------------------------------------------
|
@ -1,3 +0,0 @@
|
||||
ccm26ToFoam.C
|
||||
|
||||
EXE = $(FOAM_APPBIN)/ccm26ToFoam
|
@ -1,9 +0,0 @@
|
||||
EXE_INC = \
|
||||
-I$(LIB_SRC)/finiteVolume/lnInclude \
|
||||
-I$(LIB_SRC)/meshTools/lnInclude \
|
||||
-I$(CCMIO_ARCH_PATH)/include
|
||||
|
||||
EXE_LIBS = \
|
||||
-lfiniteVolume \
|
||||
-lmeshTools \
|
||||
-L$(CCMIO_ARCH_PATH)/lib -L$(FOAM_EXT_LIBBIN) -lccmio
|
@ -1,36 +0,0 @@
|
||||
1. how to write mesh from prostar
|
||||
|
||||
Type ngeom,[name].ngeom,star in the command line. This will create a
|
||||
.ngeom file of your Prostar model.
|
||||
|
||||
If you have boundaries defined, these will be kept in the .ngeom file so
|
||||
you won't have to rename and redefine the boundaries in ccm+. However,
|
||||
the values (properties) are not exported.
|
||||
|
||||
If you don't have boundaries you'll get a single wall patch in ccm+ that
|
||||
you'll have to split accordingly.
|
||||
|
||||
2. how to load it into star-ccm+
|
||||
|
||||
In ccm+ create a new simulation and do File>Import...
|
||||
|
||||
Browse to the location where you have your .ngeom file, select it, press
|
||||
OK and that's it.
|
||||
|
||||
3. how to do merging (or is automatic?)
|
||||
|
||||
If you had couples in your Prostar model, your meshes will all be
|
||||
"fused" together automatically in ccm+ when you import the .ngeom file.
|
||||
Keep a look on the output window in Prostar when you run the ngeom
|
||||
command to make sure the couples are exported OK.
|
||||
|
||||
Alternatively, you can "fuse" the different fluid regions in ccm+. To do
|
||||
this select all the fluid regions you want to merge together from the
|
||||
command tree on the left of your screen, under Regions. Press control
|
||||
and click on top of each one, once you've selected all, click the
|
||||
right-hand buttom of your mouse and select Fuse...
|
||||
|
||||
4. how to save it from star-ccm+
|
||||
|
||||
Once your model is ready in ccm+ (i.e. all regions and boundary patches
|
||||
defined), go to File>Export... and select .ccm format.
|
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue
Block a user