Software training,tutorials,download,torrentOrcaFlex is the world’s leading package for the dynamic analysis of offshore marine systems, renowned for its breadth of technical capability and user friendliness. OrcaFlex also has the unique capability in its class to be used as a library, allowing a host of automation possibilities and ready integration into 3rd party software.
New in version 11.0f
Bug fixes
Vessel manoeuvring load has been changed to exclude a contribution that was previously double-counted. Part of the contribution to vessel inertia load from added mass was included in the simulation twice. The removal of this contribution from the manoeuvring load is done by the first term of the load component equations presented in the theory.
The WAMIT output file presenting multibody added mass and damping data for import was assumed to always refer to waves by period. This assumption could be false, and the imported data would then be associated with the wrong period or frequency. The import process will now attempt to determine whether the .1 file refers to waves by period or by angular frequency.
Opening the Morison element type data form could result in grid index out of range error messages for models containing a large number of Morison element types.
These bugs are fixed in version 11.0f.
New in version 11.0e
Bug fixes
Users could encounter an error with message “Attempt to read a variable that has not been logged” when requesting velocity or acceleration results for a shape object that was (directly or indirectly) held by a constraint. To trigger the bug, the constraint had to begin moving during simulation by use of the out-frame release stage data or release condition, and have only fixed degrees of freedom initially.
When solving in the frequency domain at low frequency, the wave drift load process relies on interpolating the QTF data on wave direction relative to vessel heading. Previously the vessel’s heading in reset state was used to perform this calculation. However, the vessel’s heading after the static equilibrium has been calculated is more appropriate. This will most significantly affect vessels for which the static equilibrium has a large yaw disparity relative to the reset heading.
Invalid floating point operation errors could be shown when performing calculations for models with lines using the slug flow contents method and that also specify the frequency domain dynamics solution method. The errors are thrown by the slug flow drawing code so a simple workaround is to disable slug flow drawing for each line that uses the slug flow contents method.
A multithreading bug could lead to program crashes when opening multiple data files simultaneously. This has been observed when starting a batch run, but the issue could also occur when using the API to open multiple data files simultaneously.
Slam force coefficients were not being saved to text data files for line types of the equivalent line category.
Python post calculation actions which use user defined results previously failed with an unexpected error.
These bugs are fixed in version 11.0e.
New in version 11.0d
Drawing
Support for Gmsh .msh files has been added for wire frame drawing import, and shaded graphics model import.
Bug fixes
When copying objects between models via the clipboard, OrcaFlex copies associated type objects. For instance, if a line is copied from one model to another, any line types that the line uses are also copied. If the target model already contains type objects with the same names, then a decision must be made: use the data from the clipboard, or use data already in the target model? OrcaFlex is meant to ask the user to make this decision, but since 10.3a the mechanism to ask the user has been broken and the program always opts to use the data already in the target model.
Panel mesh import for Sesam .fem files was failing (reporting an invalid node number error) for some valid files that contain triangular elements (ELPTYP=25).
Embedded Python execution (e.g. external function, post calculation actions, user defined results, etc.) would sometimes fail for virtual Python environments.
Stiffener attachments protecting the ends of lines could make an unwanted Rayleigh damping contribution to the line end connection load if torsion is not included and the protected line end also has finite end connection stiffness.
Loading a static state simulation file could result in an invalid floating point operation if a summary results window was active.
Binary data files did not store information on whether constraint and turbine objects were locked in the model browser.
YAML fatigue files that use BaseFile were not being processed correctly in batch mode. The base file was being overwritten with the output .ftg file, and the output spreadsheet was being saved with the wrong file name.
Shaded graphics model import from panel mesh files was failing with an unexpected program error for very large mesh files.
These bugs are fixed in version 11.0d.
New in version 11.0c
Drawing
Support for Aqwa .dat files has been added for wire frame drawing import, and shaded graphics model import.
Support for Sesam .fem files has been added for wire frame drawing import, and shaded graphics model import.
Multibody Hydrostar .hst files are now supported for wire frame drawing import, and shaded graphics model import.
The TRANS, ROTA keywords in Hydrostar .hst files are now supported.
Automation
A new function, C_AssignWireFrameFromPanelMesh has been added to the programming interface. This is used to to set an object’s wire frame drawing data based on an imported panel mesh. This function is equivalent to the GUI’s functionality to import wire frame vertices and edges. The Python, MATLAB and C# interfaces also make this functionality available.
For the Python API, the tags property now returns None for objects that do not support tags. Previosuly an exception was raised.
For the Matlab API, a new method named HasTags has been added.
Bug fixes
Disabled line contact relationships were being used to determine the extent of the coupling between lines when using either the solve coupled systems line statics step 2 policy or the include coupled objectsmodal analysis option. This meant that the degrees of freedom of a larger group of model objects than was strictly required may have been included as part of a single coupled analysis, even when the system could have been decomposed into two or more independent subsystems. This just affected the grouping of the degrees of freedom when performing the analysis; the results of any coupled analysis would still have been valid.
Line contact relationships in which the protected or splined lines had not been assigned were simply being ignored during the calculation. Such relationships are invalid and should have been brought to the attention of the user via an error message.
Attempting to use the analytic catenary solver to determine the shape of a line in reset state could sometimes lead to an unexpected error if the line was neutrally buoyant.
Attempting to view an instantaneous valuerange graph for the final time-step of a simulation may have resulted in an access violation for lines that use line feeding. This only affected some models and only for a small subset of the line results variables.
Morison element drag diameters were not being converted correctly when the model units system was changed. For instance, if drag diameters were entered in SI units, and the model units system was subsequently changed to US units, then the Morison element drag diameters were not being correctly converted from metres to feet.
The PD 8010 Young’s modulus was not being converted correctly when the model units system was changed. This data is used in the PD 8010 torsion, load combinations and bending strain checks.
The SHEAR7 bending stress curvature load factor was not handled correctly when using non-SI units systems. When OrcaFlex creates the SHEAR7 data file, it must convert to the units system used by SHEAR7. When using non-SI units, SHEAR7 requires stress values to be given in kpf/in2 (ksi), but previous versions of OrcaFlex were incorrectly converting to lbf/ft2.
An access violation error was raised if the OrcFxAPI function C_GetVarID was called for an OrcaFlex object that does not provide any results, e.g. type objects.
In versions 11.0a and 11.0b the controls on the cycle histogram options panel were, erroneously, disabled.
Previous versions could erroneously report that connection moments would not be transferred between two lines, neither with torsion included and connected with zero connection stiffness. This could only have happened if the slave line had at one time had torsion included and a non-zero end connections twisting stiffness had been set.
In versions 11.0a and 11.0b, it was possible in the 3D view window to drag attachment objects
Product: OrcaFlex 11.0f
Version:11.0f
Supported Architectures: x64/X32
Language: english
Supported Operating Systems: Windows 7even or newer
Size: 1CD