simple SHIPFLOW configuration setup

[simple SHIPFLOW configuration setup]

If you want to run a simple Shipflow setup for testing purposes a configuration as this should be sufficient.

 

xflow

title( title = "Shipflow_example" )

program( xpan )

vship( fn = [0.26], rn = [1e9] ) [iNFO: this is a full scale example]

hull( mono, xmauto, h1gr = "hull", fsflow, xmdens="coarse" ) [iNFO: the ships SectionGroup is called "hull" here ]

offset( file = Offsets|completeHull.exportSHF("hull_example"), lpp = 157, xaxdir = -1, ysign = 1, xori = 157, zori = 6.2 )

[iNFO: the ships OffsetGroupAssembly is called "completeHull" here, 157 represents LPP, 6.2 the draft ]

 

xpan

control( free, nonlin )

iterati( maxit = 10 )

parall( nthread = 4) [iNFO: adjust your number of coarse available]

If you want to test the viscous flow solver as well, add xchap in xflow->program and run the case with following xchap settings.

 

xchap

parall( nthread = 4 )

control( start, maxit = 10 )

 

To run a more exact case, the number of iterations in xpan should be set to 20 and for viscous calculations to about 5000. The mesh density xmdens sould be set to "fine" for accurate potential flow analysis.

[Connect SHIPFLOW Application]

If you don't link the Shipflow Computation with the application of Shipflow, the external program can not be started.

 

Remeber to choose "local setup" to link the computation with a local Shipflow setup. In the "Local Execution Settings" choose one of the available "Local Applications". If no application is available, generate a new one by clicking on the little notepad. Then give this application a recognisable name and fill in the local path of your shipflow.bat

(for example: C:/opt/SHIPFLOW4.7.02-x86_64/bin/shipflow.bat).

 

Now Shipflow is successfully linked.

[How do I handle Error messages when starting the CAESES]

The startup log shows single system entries during the startup process. It can be found for Windows users under following path:
 

C:\Users\YOURNAME\AppData\Roaming\friendship\etc\log\startuplog.html

If problems occure errors entries will be written in the startup log.

For example: licence file problems can be determined by entries in this startup log

IMPORTANT: When contacting the FRIENDSHIP Support, this startuplog has to be attached. If you are using a node-locked license, you have to send the fslicense.dat, too.