Modelling and Analysis

Framework: Why the reported Can Length is not equal to the modelled length in GeniE

Refer to Page 84 in Framework UM, it emphasized that the can/stub segment must be defined with one FEM element. If assign a mesh property to these beams to divide the can segments into two or more FEM elements, this will lead to the incorrect can length is recognized by Framework.

Use PRINT CHORD-AND-BRACE can check the can length in Framework, the information will be listed as below.

Back to top

3D-Beam (All): Problems with the model / database

If you are experiencing problems with your model/database, in some cases it is possible to do a clean-up by exporting it to an xml-format and then importing the xml-file again.

  1. Use File Export
  2. Answer No to the question about GeniE
  3. Close 3D-Beam and open a new job
  4. Use File - Import to open the model again

Sometimes the local axes are changed by this clean-up, so the model should be checked after this operation.

Back to top

API LRFD Different utilisations in Framework and GeniE

There are two differences that can cause utilisation to be different in GeniE and Framework when performing punching check for joints:

  • Both programs check the chord and aligned chord. However, when checking the aligned chord, Framework uses the A, Wmin and gamma of the chord. In GeniE the values of the aligned chord are used.
  • When the contribution from the axial load in the brace is higher than 1, differences might occur due to a simplification in Framework calculation (see attached file). Please see the attached document.

Back to top

Chords and Braces in GeniE

When GeniE identifies chords and braces it assesses the following criteria in prioritized order:

  1. Diameter of section
  2. Beams with internal joints
  3. Length of the beams
  4. Names

Cross section thickness is not taken into account. There was a change order for this in our development database so hopefully it will be corrected soon. In your case it is the length of the beams that becomes governing.

The option you have to overrule it is the "Beams with internal joints".

If you join the two beams that you want as cord to one beam the joint becomes an internal joint for that beam. The other two beams will have end joints. This way you can control which one to use as cord.

There is one issue with this. An X joint should actually be modelled with two continuous beams. Then GeniE will know that these beams should be kept straight when you introduce gaps at the ends.

It seems like you have accounted for this manually in your model by moving the X joint to make the beams straight. When using one joined and one split beam to control cord/brace you still have to align the beams manually.

Back to top

FEA (All Versions): Bulb profiles from Nauticus Hull to Sesam GeniE

Bulb profiles are not implemented in Sesam GeniE, and will be substituted by Angle profiles.

When extruding a 2-dimensional Section Scantlings model from Nauticus Hull to a 3-dimensional GeniE concept model, all Bulb profiles are automatically converted to Angle bars with approximately the same section properties, e.g. the section modulus should be as close as possible.

If the automated procedure doesn't work properly, e.g. the section properties are missing for some of the beams in the concept xml file, the following warning message is issued in GeniE:

Warning: XML-import problems While importing/exporting: No prSection named Bulb.... exists -> DNV_structure_concept_protocol : model...

Workaround: Users must find a substitute profile to use instead of the Bulb profiles. Then there are two options:

  1. Replace the Bulbs with the substitute in Nauticus Hull Section Scantlings. OR
  2. Keep the Bulbs in Section Scantlings. Attach the substitute profile to the beams that have no profile in GeniE.

See also FAQ: "How to convert small bulb profiles to angle profiles with similar properties".

Back to top

FEA (All Versions): Nauticus is closing down when extruding a cross section

We have found that Nauticus Hull sometimes crashes (closes) when attempting to extrude a cross section with stiffeners on curved segments, e.g. in the bilge area.

A workaround in such cases is to do some testing by removing stiffeners from curved segments. If the extrude command then works ok with no errors or warnings, then keep this cross section and add the stiffeners back onto the model in GeniE later on.

Back to top

FEA (v18.15 and older): Why am I not able to change the application path in FEA_GeniE project setup?

Question: The initial setup in Nauticus Hull FEA tool uses a GeniE path (GeniER.exe) that does not exist. When trying to change it to the correct path using the change-link on the right side in the window, it does not work.

Answer: This setup is no longer in use and should be removed to avoid the confusion. The correct path and GeniE version are to be set by using the "Application Version Manager" (AVM). Do as follows:

Close Nauticus Hull

Open AVM, and set correct path and executable version of GeniE *

Open Nauticus Hull. The project setup in the Nauticus FEA-tool should now have been updated correspondingly

  • AVM should be installed if not already present on your computer

Back to top

GeniE: Partially split plates warning

What does the Partially split plates warning mean?

Partially split plates warning intended to warn user that some elements are having improper geometry or mesh so user can check it. Partially split plates are not always a source of problem but GeniE warns about this because it is not uncommon that users wanted to have a beam go all the way through the plate but due to some modelling mistake the beam stops a few mm from the plate edge, thus the warning will help identify that issue.

Also, having a Partially split plate can create some improper mesh elements if the plate is not properly split at the end of the beam/feature edge. Increase the quality of mesh or modelling will solve this warning. If the analysis can run and plate is not your interest, Partially split plate warning can be ignored to a certain extent (with users consent).

Back to top

GeniE (6.6-08): Which shortcuts exist in GeniE?

In GeniE it is possible to use keyboard shortcuts. The following is an overview of the shortcuts available in GeniE.

File

Ctrl+N - New workspace

Ctrl+O - Open workspace

Ctrl+S - Save workspace

Edit

Ctrl+Z - Undo

Ctrl+Y - Redo

Ctrl+U - Set Undo mark

Ctrl+T - Copy (with transform)

Del - Delete

View

Alt+O - Options

Alt + B - Changes background color from default to white

Tools

Alt+M - Turn activity monitor on with only meshing activity set to active

Alt+D - Turn activity monitor on with current analysis set to active

Alt+P - Presentation (of results in Results views)

Alt+G - Beam result diagrams

Alt+C - Customize

Help

F1 - Help

Model viewing

F2 - Rotate (with right mouse button)

F3 - Zoom (with right mouse button)

F4 - Pan (with right mouse button)

Ctrl+Shift + RMB - Zoom rubber band (with right mouse button)

Shift + RMB - Zoom to the cursor

Ctrl+ RMB - Pan

model

Alt + RMB - Rotate model

Alt+Z - Fit to selection (new in GeniE V6.6-08)

X + RMB - Rotate model around axis that is currently in vertical position

C + RMB - Rotate camera

Z + RMB - Rotate camera

S + RMB - Set camera to see model in horizontal position

F5 - ISO view

F6 - View from X axis

F7 - View from Y axis

F8 - View from Z axis

F9 - Fit (zoom in/out to fit model in screen)

F10 - Spin model

Alt+S - Show selection only

Alt+Plus - Add selection (display together with other currently shown concepts)

Alt+Minus - Remove selection (hide concepts)

Alt+A - Show all

Alt+Q - Show complement (of currently shown concepts)

Modelling

F11 - Snap perpendicular/tangential/plane/eccentric (select option via Toolbar button)

ESC - cancel operations/go to selection mode

Back to top

GeniE (7.2-02 from All): ERROR in input on T-file, data is missing for element

If Sestra 8.8-02 aborts with the following error message:

ERROR in input on T-file for superelement type 1 on level 1

Check of T-file (.FEM) revealed the following errors:
* Material data is missing for element 221137 (the reference number in GELREF1 is zero)                                                                                    
* Geometry data is missing for element 221137 (the reference number in GELREF1 is zero)                                                                                    
* Local coordinate system is not defined for element 221137 (the reference number in GELREF1 is zero)

or Sestra 10 with the error message: Execution failed!

Error when fetching beam orientation vector for internal element number 50657. Unable to find the unit vector with transformation id 0.

This is likely caused by some orhpaned and duplicate elements without properties. The orphaned elements come from a bug during import in older GeniE versions, but the issue was fixed in version 7.4-18 (and later). The error may occur in models created in older versions. If you encounter the error use the following script (paste to command line) to simply remove the elements. The script command is available since version 7.3-15.

Me_Analysis1 = MeshEditor(Analysis1);
Analysis1.step(1).DeleteLoads();
Me_Analysis1.RemoveOrphanElements();

Back to top

GeniE (All version from 8.0): Plate Code Check for corrugated bulkhead

This knowledge article is to provide tutorial of plate code check (yield and buckling) for corrugated bulkhead. Please find attached tutorial document, and example model. GeniE journal file is also attached.

Please be noted that GeniE 8.4 version with dual assembly option has been used. If using old version, like GeniE 7.x version, there could be problem.

Back to top

GeniE (All Versions from 5.1-11): How to define your own correction shear forces and bending moments using the slicer in GeniE

The procedure to create your own slicer including correction shear forces and end moments is described in the attachment. In brief the procedure consists of exporting a ruleloads xml from Nauticus Hull as for a regular cargo hold analysis with rule loading, and then modifying the target values for correction shear forces and end moments in GeniE. Please see the attached document.

Back to top

GeniE (All Versions from 7.0): How to resolve missing nodes for segmented piles

Symptoms: The number of nodes/displacements reported by Splice is less than the number of soil layers reported by Splice when a pile with a segment change is used.

Cause: At segment changes, the default mesher in GeniE creates longer pile elements, to make sure that the same number of elements is generated. However, in case of a segment change, an additional node is required at the segment change. As a result, Splice receives less nodes than soil layers from GeniE, and hence reports less displacements than soil layers.

Solution: This issue was addressed in GeniE V7.0, but is only solved when using GeniEs partial mesher. To solve the issue, use the following steps:

  1. In the folder tree on the left-hand side of the GeniE window, right-click on your analysis and select Choose mesher > Use partial mesher to enable GeniE's partial mesher.
  2. Next, edit the mesh activity settings by right-clicking on the meshing step in the folder tree or in the activity monitor. Make sure to set the mesher to always regenerate mesh.
  3. Remesh and re-analyse the model. Additional nodes are now created along the pile. In particular, additional nodes are generated at the segment ends. This makes sure that each soil layer receives one node (or two in case of a segment change). As a result Splice will compute the displacements corresponding to these nodes.

Back to top

GeniE (All Versions): Changing default version of GeniE in Brix Explorer for Sesam

Go to folder Files\DNVS\Sesam\BRIXExplorer\config

Open Sesam.config file in some editor. Check for the location of GeniE in the file. Change it to your desired GeniE version location and save the file. NOw Start Brix and default GeniE version will be picked from your desired location.

Back to top

GeniE (All Versions): Conical sections for non-tubulars

Description: After applying a non-tubular cone section, GeniE shows the section in the graphical user interface, but will not mesh the segment. Sestra will give an error when trying to analyse.

Explanation: Cone sections for beams are only working for tubular sections. As such, non-tubular variable sections will not get meshed and will subsequently give an error in Sestra.

Workaround: As a workaround, one can apply an average cross-section to the beam segment for which one wanted to have the cone. When GeniE meshes a tubular cone section it will transfer the cone into an equivalent diameter section as well, so in principle one could do the same straightaway in the modeller.

Another method is to model the model the conical segment using plates and connect these to the beams using support rigid links.

Back to top

GeniE (All Versions): How do I merge results and load cases from multiple analyses to perform a single code check

This requires some work with both GeniE and Prepost. It basically involves that you merge your analysis results into a single analysis results file, after which a capacity manager is created for doing a code check of this new analysis. The procedure for this is outlined in the attached FAQ document. Please see the attached document.

Back to top

GeniE (All Versions): Why and how to scale down basic load cases in a pile-soil analysis?

Description: In GeniE you may need to scale down the basic load cases when performing a pile-soil analysis.

Explanation: In a non-linear pile-soil analysis only results for the load combinations are normally of interest. In real life, there will always be multiple loads simultaneously acting on a piled structure, e.g. a jacket. For example, a wave load will never occur alone, but will always be accompanied by a gravity load and most likely even more loads. These different loads exist in the different load cases in GeniE, while the combined simultaneous loading is applied using load combinations. With this in mind, imagine only a wave load acting on the structure, so without any other loads acting on the jacket. This will most likely give a large stress in the piles, and the loading may even be such that a tensile stress results in some piles. These loads will give trouble in the convergence of the pile-soil analysis and in certain cases the basic load cases may cause the whole analysis to stop. Even more, these kinds of loads do not exist as such in reality, as also e.g. gravity will act on the structure together with the wave. The load combinations will usually give no convergence issues in the pile-soil analysis, while the separate load cases may do so. Hence, to circumvent this problem, the basic load cases can be scaled down, e.g. by a factor 100, to make sure the pile-soil analysis converges and the analysis does not stop with a convergence error.

How to control it? You are able to change the behaviour of scaling the load cases in GeniE by setting the scaling factor. This is done using the command: GeniERules.Meshing.basicLCfactor = 0.01;

0.01 will scale down the basic load cases by a factor 100. A value of 1 will give no scaling of the basic load cases. Note that this may cause the issues mentioned above. If you want to check which value is active at the moment, you can use: print(GeniERules.Meshing.basicLCfactor);

Back to top

GeniE (All Versions): Exception caught: Database not supported

This error occurs when a workspace created in a newer version of GeniE is opened in an older version of GeniE.

To fix this problem, you can either install the older version of GeniE and open it or import the analysis by creating a new Workspace, then selecting File -> Read Command File.

Browse and select the *.js file of the old analysis and click Open. Alternatively, importing xml file is a better option.

Back to top

GeniE (All Versions): How to change or delete a prescribed displacement

Problem: A load case contains a prescribed displacement (for a support point with prescribed type of boundary condition). How to change or delete this part of the load case and not the whole load case? Solution: Go to Load Cases folder (or analysis activity if the load is stored there) and double-click the load case. Then double-click Explicit Loads and right-click the relevant prescribed displacement to open Properties to change or click Delete to delete.

Back to top

GeniE (All Versions): Stresses in General Beam cross-section

Its not possible to display Beam stresses through Beam Results diagram and Report in GeniE. User can see stresses in General Cross-section using Xtract.

Back to top

GeniE (All Versions): Can't delete object from GeniE, script execution error.

If you get a script error about unnamed object when trying to delete an object from a GeniE workspace, try the following workaround:

Add all named objects to a named set and export a concept XML file using the option Export subset.

Then import the concept XML file into a new workspace.

Back to top

GeniE (All Versions): How to create a dynamic set

Besides the 'Create set' option, GeniE gives you tools to create a 'dynamic set'.

The difference between a 'set' and a 'dynamic set' is that dynamic sets are continuously updated when creating new objects.

Today, the only option to create a dynamic set is to use GeniE JScript language with the following commands.

The command used to create a dynamic set is:

DynamicSet(
AbstractLimit
);

Where
AbstractLimit
 is one of the following limit functions:

LimitAbovePlane(Plane3d)
- Add to the dynamic set All objects above specified Plane3d();

LimitAnd(AbstractLimit, AbstractLimit)
- Combine 2 limit functions;

LimitBelowPlane(Plane3d)
- Add to the set all objects below specified Plane3d

LimitBox(Point, Point)
- Add to the set all objects that are inside cube spread along main axis between specified points

LimitInOrAbovePlane(Plane3d())
- Add to the set all objects that are above or exactly on the Plane3d();

LimitInOrBelowPlane(Plane3d())
- Add to the set all objects that are below or exactly on the Plane3d();

LimitInPlane(Plane3d())
- Add to the set allAll objects that are exactly on the Plane3d();

LimitInSet(AbstractSet)
- Add to the dynamic set objects from another Set, doesnt work when you want to add to dynamic set objects from another dynamic set.

LimitLine(Point, Point)
- Add to the dynamic set all objects that are exactly on the specified line

LimitLower(string, Variant)
- Add to the dynamic set all objects with specified property (as string) and value that is lower than specified, e.g. LimitLower("Height",0.3)

LimitLowerInclusive(string, Variant)
- Add to the dynamic set all objects with specified property (as string) and value that is lower or equal to specified, e.g. LimitLower("Height",0.3)

LimitNot(AbstractLimit)
- Exclude selected limit from dynamic set

LimitNumber(string, Variant, tlLimitNumber)
- Check if value of property is within limit

LimitOr(AbstractLimit, AbstractLimit)
- Create a dynamic set that is union of two or more existing dynamic sets.

LimitPlane(plane3d, LimitPlane)
- Add to the set all objects that are laying exactly on the specified plane3d

LimitString(string, string, bool)
- Add to the dynamic set all objects that contains specified name

LimitUppedInclusive
- Add to the dynamic set all objects with specified property (as string) and value that is higher or equal to specified, e.g. LimitLower("Height",0.3)

LimitUpper 
- Add to the dynamic set all objects with specified property (as string) and value that is higher than specified, e.g. LimitLower("Height",0.3)

Examples of Dynamic sets:

//This example adds i.e. web frames to dynamic sets.

//Script will create frames from (FromFrame) to (ToFrame) in spacing of (FrameSpace).

//Script can be modified to be used along Y or Z axis as well.

    //***** Dynamic Sets *****//
    var FromFrame = -5;
    var ToFrame = 235;
    var Framespace = 0.8 m;
    var ActualIndex;
    var ActualFrameX;
    var FrameName;
    var FrameSetArray = Array();
    for (i = FromFrame; i < ToFrame + 1; i++)
    {
                    ActualIndex = i + Math.Abs(FromFrame);
                    ActualFrameX = i * Framespace;
                    FrameName = "FR" + i;
                    FrameSetArray[ActualIndex] = DynamicSet(LimitInPlane(XPlane3D(ActualFrameX)));
                    FrameSetArray[ActualIndex].name = FrameName;
    }

//This script converts all dynamic set in workspace into regular sets.

    for (var namedSetObject in ModelObjects)

    {
                    if( namedSetObject.supportsType(typeSet) )
                    {
                                    var arrayOfObjectsInSet = new Array();
                                    var name = namedSetObject.name;
                                    tempSet = Set();
                                  
                                    for (var objectInSet in namedSetObject)
                                    {
                                              arrayOfObjectsInSet.push(objectInSet);
                                              tempSet.add(objectToAdd);
                                    }

                                    Delete(namedSetObject); 
                                    tempSet.name = name;
                    }
    }

Back to top

Support rigid links should not be created by copy rotation operation, because then the dependent and independent nodes will get different coordinate system orientations. You can verify the local coordinate sytems by labelling them for the support rigid link (and any relevant support curves).

Unless the use is intended, this will give wrong results in analysis.

The differences between summed loads and reaction forces for the translational DOFs reported at the end of the Sestra.lis file should be small numbers typical in the range 1.e-5 or less. If the independent and dependent point's coordinate systems are misaligned, the values are typically 1.e-1 or larger.

Back to top

If spring stiffness is defined for any DOF in a rigid support link, it will not work properly. The spring will not take any reaction force.

Back to top

GeniE (Version 6.5-04): Boolean operation error in GeniE when executing JScript

When executing the following commands in GeniE:

val1 = 1;
val2 = 2;
val3 = 3;

print((val1 <= val2) && (val2 >= varl));
print((val1 <= val2) || (val2 >= val3));

GeniE will throw an exception: JS0001 Cannot convert (line: 1: type -> bool). The workaround is to use a later version of GeniE.

Back to top

GeniE (All Versions): Beam deflections are reported 0 at the beam ends

Deflections in GeniE are reported as the displacements relative to the beam or line ends, so the ends always have 0 deflection. Please see the attached document.

Back to top

GeniE Modelling issue: red exclamation mark on beam

Question: what does the red exclamation mark mean?

Answer: When the beam which has an offset depending on the intersection of two other beams. Then, for some reason, one of these two beams is deleted (e.g. it is joined with another or the user has delete it directly). The offset can not be defined anymore. For such issue, we will give an exclamation mark to remind the user.

So please check the questioned beam to check if there is abnormal offset. Below is an example.

This issue relates to Bug 16075.

Back to top

GeniE reports displacements of all FEM Nodes, even if a set has been selected

Question: GeniE reports displacements of all FEM Nodes, even if a set has been selected. Why? Answer: In GeniE, three types of results could be generated when printing FEM node displacements via save report.

  1. If in the concept model without any frame joints. Then the displacement of all the FEM nodes will be printed no matter which set is selected.
  2. If the concept model has frame joints, and then
  • if the selected set does not include any joints, then no fem node displacement will be printed
  • if some joints are included in the selected set, then only the fem nodes corresponding to these joints will be printed. For such case, the different selected set will generate different fem node displacement report.

Back to top

GeniE(All Versions from 6.5-04): How to eXtract and print detailed curve information

The following commands can be used to eXtract and print detailed information about guiding geometry curves:

Command:

print(<Curve>.GetCurveInformation());

Expected output:

  -> Curve Information:

  Definition Interval:  [0,22.4768]
  Is Closed:            0
  Is Self-Intersecting: 0
  Is Planar:            1
  Is Line:              0
  Is Polyline:          0
  Is Rational:          0
  Number of segments:   4
  Degree:               3
  Analytic Continuity:        C2
  Geometric Continuity:       G2
  Analytic Stable Continuity: C2

Command:

print(<Curve>.GeometryToString());

Expected output:

  -> BSplineCurve3D{Name[Curve1],Layer[],ControlPoints[Point(10.0000000000:0.0000000000:0.0000000000)

  Point(5.9968401846:0.4905205538:0.0000000000) Point(0.2034128748:1.2004085681:0.0000000000)
  Point(4.9830908462:4.9492725386:0.0000000000) Point(9.7726718238:9.0147146125:0.0000000000)
  Point(3.9542987567:8.1128962700:0.0000000000) Point(0.0000000000:7.5000000000:0.0000000000)],
  KnotVector[    0.0000000000    0.0000000000    0.0000000000    7.9056941504   11.4412280564   14.9767619623    22.4767619623   22.4767619623   22.4767619623]
  Degree[3] };

Command:

point1 = <Curve>.EvaluateAtParameter(...parameter...);

Expected output: This command will create a point specified by user name, at curve parameter specified by user.

Command:

Print(<Curve>.GetParameter(...point on the curve...));

How to solve Command will return curve parameter for the specified point on the curve.

Command:

point = <Curve>.EvaluateAtLocalParameter(... double in [0,1]...);

Expected output: Point on curve will be given when specifying position as parameter. Parameter value between 0 and 1.

Command:

print(<Curve>.GetLocalParameter(...point on the curve...));

Expected output: Command will return parameter from 0 to 1, from start of the curve to specified point on the curve.

Command:

point = <Curve>.EvaluateAtLengthFraction(... double in [0,1]...);

Expected output: Point on curve will be given when specifying position as parameter. Parameter value between 0 and 1.

Command:

vector = <Curve>.TangentVector(...point on the curve...);

Expected output: Command will return tangential vector at specified point on curve.

Command:

radius = <Curve>.CurvatureRadius(...point on the curve...);

Expected output: Command will return curvature radius at specified point on curve.

Command:

vector = <Curve>.CurvatureVector(...point on the curve...)

Expected output: Command will return curvature vector length at specified point on curve.

Command:

<Curve> = Curve.VectorCurvatureFunction(...no points...,...scale factor...);
scale factor - real numbers R
number of points - Natural positive numbers

Expected output: For given curve, the curvature function will be displayed.

Back to top

GeniE: Applying loads on a full circular beams in GeniE are doubled

The loads are doubled if the beams are either full circle or semi circle.

The proposed workaround is to have 4 beams around the circumference of the tube, and apply a load to each of them. This can be done by dividing the beams again, such that each covers a sector of 90 degrees. After division, the loads must again be applied to the newly created beams.

Back to top

GeniE: Error Mass matrix Max index and NDOF_rmFixedDofs do not match

If when running earthquake analysis in GeniE, the below error is issued.

This error is related to the file M1.SIF generated in eigenvalue analysis.

For earthquake analysis, we need run eigenvalue analysis twice with different options. The sequence is mandatory.

  • First run: check the option "Mass Matrix", run the analysis to generate M1.SIF.

If there are supernodes in the structure, then in this step, the user need modify the Sestra.inp file manually to remove the DRED card.

Second run: uncheck the option "Mass Matrix", but check the option "Modal Mass Factors", run the analysis to generate R1.SIN and save the modal mass participation factors.

If this error is issued, there are two possibilities:

  • There is no M1.SIF generated in the first run
  • There are supernodes in the structure, but DRED card is not removed manually in the first run

Back to top

GeniE-Improving Compatibility When Reading Old JS files into Higher Version

Some model errors were happened when reading old format JS files to build GeniE workspace. These JS file may be generated by the customer self-develop tool. To avoid model error, it needs to set the compatibility option when reading JS file into GeniE. It is recommended to select V3.3-38 or older.

Back to top

Midnodes incorrectly positioned, not in the middle of the edge or out of line

When using 2nd order elements in GeniE, the midnodes are placed at the parameter position 0.5 of the curve between the end nodes. For some models, the parametrization is non-uniform; this may lead to distorted mesh, missing mesh, or wrongly positioned midnodes. This can happen if the underlying geometry description is distorted.

Enabling "Uniformized face parametrization" from the Edit > Rules > Meshing menu will will better align the midnodes correctly , but it can have negative impact on performance. The alternative is to recreate the plate/shell to get a better parametrization, or manually use mesh edit functionality to move nodes a little (the mid nodes will follow and snap to correct position).

Back to top

Open large FEM files in Usfos Xact

Sometimes, when trying to use Usfos Xact to open a large FEM model file, it will report an out-of-memory problem and fail to open the model in the graphics user interface. When this happens, user could use Struman to convert the FEM model file into Usfos result RAF file format. The Usfos result file format could handle much larger file sizes up to a few GBs.

Back to top

Patran-Pre (All): How to define beam properties

See the attached document for how to define beam properties in Patran-Pre. Please see the attached document.

Back to top

Programe association on .gni files.

To the unset the GeniE programe version on the .gni file the following has to be done.

"Start---Run," type in "regedit" and try deleting .gni file associations from the "Registry Editor." Make sure you delete all the file associations.

Back to top

PULS (All): The four variants of PULS

PULS is available in four variants based on the same calculation engine. Three of the variants are licensed and installed differently:

  • PULS integrated in GeniE supporting the CSR Tank and offshore (DNV-RP C201, Pt 2) code checks. This requires the GeniE CCPL licenses and the installation of both GeniE and Nauticus Hull. Previously this also required the installation of RuleService.
  • PULS Excel spreadsheet This requires the PULSXL license and is part of the NH rule check license and installation.
  • PULS AV (Advanced viewer) standalone program. This requires the PULS AV license within the buckling assessment package (BAP) and the installation of Nauticus Hull. Note that the BAP package license also includes the above PULSXL license.

Note that PULS is also being used in Nauticus Hull Section Scantlings for hull girder capacity in the ULS check according to Offshore Standard DNVGL-OS-C102 (Ch.2 Sec.4.3). This requires the Nauticus Hull Rule Check license and installation of Nauticus Hull.

Back to top

Sesam Compartments with Dipole elements

How to create a compartment model including dipole elements in GeniE, and use them in HydroD?

Please see the document which is found in the , together with model files.

Notice that there is also a tutorial in HydroD 6.2 and later versions on how to use dipole elements in the panel model and compartments for Wadam analyses, available from the Help menu.

Back to top

Sesam: How to script the installation of Sesam

To script the installation of Sesam 2011 DVD and all its components, please follow the guidelines in the attachment. Please see the attached document.

Back to top

Sesam: What product is Waloco part of

Waloco is not its own product, but is part of HydroD ext. STRU with Prod code HYDSTR1 and Wajac with Prod code WAJBA1.

For these products the license file should include Waloco.

Back to top

Sima: How to visualize models generated by Sesam-GeniE

Follow the below steps to visualise models generated by Sesam-GeniE:

Open a model in GeniE.

Choose "File | Save Graphics As" and save file as a ply-file or obj-file.

Open Sima, read in a test case.

Expand "Model | Bodies" folder. Right click on a body, then choose the "Assign Body Geometry" option and locate the file generated in step 2. Open the file.

Back to top

Static accelerations/inertia loads are not applied on mass of matrix element, while total mass matrix is correct

When using external matrix (element), applying static acceleration/inertia loads are not applied on mass of matrix element, while total mass matrix is correct/accounted. As total mass is correct, the dynamic response will include effect of the mass of the matrix element, while static response does not.

This is intended behavior from Sestra 8.

There could be some possible workarounds for this, until Sestra implement new option for this.

One workaround is to apply loads through AMDLOAD (load of matrix element) cards, but calculating that for each load case / load step will be quite complex.

Another feasible workaround is to add equivalent point masses on connection locations for external matrix.

For example of below TP model, total mass and z-coordinate of COG is as below.

Mass : 152 tonne COG Z: 18.7681m

Then user can calculate point masses as below, to have equivalent mass & z COG.

Then replace mass information of global model

Define zero mass on external matrix And add point masses to have equivalent mass & COG

Back to top

Usfos (8.6 to All) - Error in Pro_Illegal

Starting from Usfos 8.6, more strict checks on the finite element model are performed. If elements do not pass this check then the analysis will stop and the error message "Error in Pro_Illegal" will be printed.

Version 8.6 performs the following checks:

  • Element length to diameter ratio cannot be less than 0.5 in standard beam element.
  • Beam eccentricity (e1+e2) to length ratio cannot be higher than 0.5.
  • Soil layer thickness to pile diameter ration cannot be lower than 1.

Version 8.7 and following perform the previous checks and also:

  • Shell element angle cannot be smaller than 10°.

The elements that fail these criteria will be printed in the "out" file. Also, label files will be written to highlight the illegal elements in Xact.

To allow some or all elements to comply with less strict cirteria, the user can add the Illegal command in the control file to that effect. More information can be found on the release notes of Usfos 8.6 and 8.7. Please see the attached document.

Back to top

Usfos (All Versions): Axial Stress-Results attribute

All Usfos Versions: The Axial stress is a linear combination of contribution from Bending moments and Axial forces.

Note that these stresses are valid for elastic responses, (uses linear stress distribution).

Back to top

Usfos (All Versions): Checking soft connections or disconnected members

All Usfos Versions: Sometimes due to modelling mistakes, members may not be connected properly or the connection is too soft. Its recomended that user run an eigenvalue analysis for such model which will help in detecting the problematic locations in the model.

Back to top

Usfos (All Versions): Running Usfos in batch mode

Attached folder contains a model file and two different runs are done for waves in different directions. Wave-loads are computed by Wajac. You many need to make some chages in the wave1.inp and wave2.inp by changing the drive locations. Please see the attached document.

Back to top

Usfos (All Versions): Struman prints warning "Your Licence Expired X days ago"

Struman will print a warning stating that the user license has expired.

This is a fake warning! and Struman will work regardless of the printed warning.

Struman needs a separate license file from Usfos to work, but will not fail if the date of this license file has expired. Please see the attached document.

Back to top

Usfos: Error message prompt to contact support@Usfos.com

When the error message prompt you to contact "support@Usfos.com" , this indicated that you're not installed Usfos from DNV installation file. Hence please uninstall Usfos and download Usfos from DNV. After completely downloading the file > Unzip > Open the folder and double click setup.exe to install

Back to top

WindExtension (2.0-662 from 2.0-660): Limitation due to pile/soil analysis in Framework

Applies from version 2.0-660 to version 2.0-662 Use Framework Version 3.6.6 or higher when including pile/soil in the Sesam Wind analysis.

Back to top

Xtract (4.1-02 ): Combine/Scan dialogs don't open for Element average results

From version: 4.1-02 To version: All

After selecting any component of any attribute in position Element average the Scan and Combine dialogs don't open.

In case of Combine workaround is: Select any component of any attribute other than Element average. Open combine dialog. Select desired Element average component.

In case of scan workaround is: (Workaround described for combine does not work since the component currently selected when opening the scan dialog is the one to be scanned and this cannot be changed.) Workaround is to paste in a command or read a command input file.

Note: The link below from status list also include the same information.

Back to top

Xtract (4.1-02): Why is the Models, Results and or Sets tab not shown?

Symptoms:

One, more or all of the tabs on the left hand side may be hidden after opening a model in Xtract.

Cause:

The tabs can be hidden/closed by pressing on the red 'x' (close) button in the top right of the tab. This will take away the tab from the view.

Solution:

To get back all tabs, go to the Window-menu and click Database. This will hide all tabs. After this, go to the Window-menu again and click Database again. This will show all tabs again, including the ones that were hidden earlier.

Back to top

Xtract (All Versions): Abrupt changes in deformation plots

The issue may be 'complex evaluation' in Xtract. When Xtract presents a wave represented as a complex load case you have to specify the phase of the wave. Here Xtract has several options;

True minimum

True maximum

Absolute minimum

Absolute maximum

Phase

Default when you make a combination with a complex load case is absolute max. This means that Xtract will find the phase that gives absolute max length of the displacement vector at all nodal points (for result selection DISPLACEMENTS all) The phase giving absolute max may vary from node to node and hence there is no continuity in the displacement plot for such a combination. To get a plot that is easier to grasp you may make a combination where all the nodal results are for the same phase of the wave. This means making a combination with the Phase e.g. 0 deg. The phase is the third parameter in the combine command or you select it in the combine dialogue. In your case:

combine "amec-combination-input" max "Nodes" "Displacement" "all" "1" "29" "1" 1.3 "1" "31" "1" 1.3 "1" "32" "1" 1.3 "1" "33" "1" 1.3 "1" "2" "1" 0.7
combine "amec-combination-input" 0 "Nodes" "Displacement" "all" "1" "29" "1" 1.3 "1" "31" "1" 1.3 "1" "32" "1" 1.3 "1" "33" "1" 1.3 "1" "2" "1" 0.7

The fact that Xtract evaluates the results node by node may be confusing because the results may not be comparable from one node to the next. On the other hand the absolute max value for each node is often what you are after..

Back to top

Xtract: Combination of Individual Result Cases and Plots

It is possible in Xtract to combine the results for different stress results for a single loadcase.

Say you want to determine the principle stress range of P1 and P2 for a single loadcase.

Plot P1

Results-Scan - Maximum, give it a name

Plot P2

Results - Scan - Minimum, give it a name

then you can combine results through Results - Combine - P1scan and P2scan with a factor if you like.

Also useful for calculating different variations of the VM stress, some codes specify the VM stress calculation, and doing any other general combination or math on an individual result.

Back to top

Xtract: Error opening Xtract.MLG when starting Xtract

When Xtract opens through Start > All Programs > DNV Software > Applications > Xtract V4.1-02 then Xtract will open a log file (Xtract.jnl) plus some other working files in the location specified in the "Start in" field of the Xtract shortcut. By default, the "Start in" is C:\Users\<user account>\Xtract\.

If you do not have write access to this "Start in" folder, then Xtract will not start, but instead report two error messages:

"Error opening Xtract.MLG" followed by "OPERATING SYSTEM MESSAGE NO.: 9"

Please check whether you can access the folder defined in "Start in" (use Right click, Properties to view "Start in) and that you have write privileges to it.

If you get these two error messages when you start Xtract, please change to a different folder you have write access to, i.e. %temp% (your default temporary folder).

Note: when you open Xtract from GeniE, Sesam Manager or any other program, then the log file will be opened from the folder where the results file, opened by Xtract, is found and Xtract will not report this error.

Back to top

Xtract: How to select and save to file result case or component using line-mode commands

Here are some proper variants of the command after having selected an attribute by the result select ... command:

result save "C:\Temp\Table1.txt" coords components resultcases saves all components for all resultcases and including coordinates for the current attribute

result save "C:\Temp\Table2.txt" components resultcases saves all components for all resultcases for the current attribute

result save "C:\Temp\Table3.txt" coords components saves all components including coordinates for the current attribute

result save "C:\Temp\Table4.txt" coords saves current component of the current attribute including coordinates

cords, components and resultcases are keywords and not parameters. The manual says page 5-2:

Commands (keywords and parameter words) are in the command description written in normal font while parameters that can take different values are written in italic font.

Brackets are used for optional input: text

Back to top

Xtract: 'Unable to start Xtract'

This message may appear when, for example, GeniE or DeepC is trying to start Xtract.

Please check if Xtract is installed on your computer. The default installation path is Files (x86)\DNVS\Xtract\Bin and C:\Program Files\DNVS\Xtract\Bin depending on your Operating System version. If it's not there, then please download it.

Also, please make sure that you install Application version manager (AVM) on your computer which helps programs to locate the .exe files.

Back to top