Update Info 2013.3-1

© NAPA 1992-2013 All rights reserved.

NAPA Manuals 2013.3Update Info



Table of Contents1 General................................................................................... 1

1.1 Operating system versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 Support of 32bit NAPA will end soon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 Exceed version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4 Hardware configuration for computers running Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.5 Napa Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.5.1 Browser setting for Online Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.6 License file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.7 Important changes in the installer since NAPA Release 2012.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.7.1 Demo projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.8 Deprecation of features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.8.1 Removed features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.8.2 @GOTO label in macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.8.3 Removal of PLOT task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.8.4 Removal of the CROSS task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.9 Finding data from the databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.10 Installation instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 GM....................................................................................... 112.1 Export to IGES format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2 Accuracy Check Between Surfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 Free Form Deformations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4 Transformation Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 GS....................................................................................... 14

4 Reporting and generating PDF files.................................................... 154.1 Speed and memory consumption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5 SH....................................................................................... 165.1 Potential flow solver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5.1.1 External Result Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165.2 Viscous flow solver RANS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.2.1 External Result Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175.2.2 Triangular wetted surface integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6 SHS...................................................................................... 176.1 Long term extreme value calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

7 ST....................................................................................... 197.1 Structure Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197.2 Aveva Marine/Tribon interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197.3 Aveva Marine/Tribon Manager (MGR*TRIBON). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197.4 Bracket location by 3 points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217.5 Opening requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217.6 Object selection method in Structure Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217.7 Folded flange for plain brackets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217.8 FEM Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227.9 Edit Parametric Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

8 FEM...................................................................................... 23



8.1 FEM Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238.1.1 Ugrade existing FEM Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238.1.2 Plot Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

8.2 Smoothing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238.3 Bracket toe cut. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238.4 ClassNK PS-HULL DSA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248.5 Idealization of Openings (Omit Element Option). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248.6 STL-Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248.7 Mesh parameter changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

9 Weight calculation...................................................................... 259.1 Column dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259.2 Formula references to automatically calculated columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

10 Manager Applications.................................................................. 2610.1 Drawing Manager (MGR*DRAWING). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

10.1.1 Offset Polygon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2610.1.2 Trim Polygon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2610.1.3 Extend Polygon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2610.1.4 ST Group Annotation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2610.1.5 ST Group Annotation Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2710.1.6 Fillet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2710.1.7 Mirror. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

10.2 InterfaceToRules Manager (MGR*INTERFACE_TO_RULES). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2810.2.1 Manager tree heirarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2810.2.2 Hull Girder Bending. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2810.2.3 Frame system Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2910.2.4 Transverse Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2910.2.5 Compartment Info(GL-LINK). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3010.2.6 Class NK Ship3D Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3110.2.7 Class NK Performance Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

10.3 MARPOL Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3110.4 Free Form Deformation Manager (MGR*FFD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

11 Napa Basic............................................................................. 3311.1 Accuracy improvements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

11.1.1 For loop end conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3311.1.2 Conditional statement evaluation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3311.1.3 Comparison of floating point numbers in macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

12 Performance improvements........................................................... 3512.1 Performance improvement: macro search order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3512.2 Resource files search order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

13 Known Issues........................................................................... 3613.1 Balancing loading conditions in the NK Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3613.2 Damage definition window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3613.3 Optimisation with multiple parallel processes and the Seakeeping subsystem. . . . . . . . . . . . . . . . . 3613.4 %-sign in a list header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

14 Corrected Errors in Release 2013.3................................................... 37


1 (46)


1 GeneralThis Update Info for the NAPA Release 2013.2 is a summary of the new features and improvements that havebeen made to the NAPA system since the previous Release 2013.1.

The list of corrected errors is presented in the last chapter of this Update Info.

1.1 Operating system versionsThe following operating system versions (both 32-bit and 64-bit) are currently supported:

■ Windows Vista + minimum of Service Pack 1■ Windows 7

The following Windows Server operating system versions are currently supported:

■ Windows Server 2003 minimum of Service Pack 2■ Windows Server 2008 (not supported on Server Core Role)■ Windows Server 2008 R2 (not supported on Server Core Role)

1.1.1 Prerequisites

■ Microsoft .NET Framework 4■ Windows Installer 3.1 or later■ Internet Explorer 5.01 or later

1.2 Support of 32bit NAPA will end soon■ 2014 NAPA releases are the last 32bit versions. After 2014 the release package will contain only the

64bit version of NAPA■ NAPA 64bit version requires that both the hardware and the operating system have to be 64bit

1.3 Exceed versionThe officially supported and recommended Exceed version for Release 2013.2 is Exceed 14.0. NAPA isbasically compatible with the older versions of Exceed, for example, Exceed 8.0 but there are followingknown issues in the older Exceed versions:

■ Older Exceed versions are not Windows 7 compatible.■ Older Exceed versions are not 64-bit compatible.■ Memory leak. Exceed 9.0/10.0/11.0 reserves memory cumulatively and if NAPA is kept running

constantly for a long period of time, all memory will eventually be reserved. This is not a seriousproblem if NAPA + Exceed is shut down a couple of times per week as the reserved memory is thenfreed.

■ Scandinavian characters. The Scandinavian characters are not available with Exceed 11.0.■ Problem with keyboard input. After interactions in the graphic window with the mouse, the keyboard

may behave as if the Ctrl button is pushed down. This means that, for example, the @-sign will not beappear. The solution is to press the Ctrl button once and the keyboard returns to the normal state.

Note: sometimes Exceed gives the error message "All xserver displays are in use. Exceed cannot runwithout a display. Please try again at a later time" when run on Windows Vista or Windows 7 and


2 (46)


NAPA cannot be started. The easy workaround is to right-click on the NAPA shortcut, and select "run asadministrator".

1.4 Hardware configuration for computers running WindowsA high performance workstation is recommended for NAPA use - meaning fast processor, graphics adapterand hard drive as well as enough memory. The recommended minimum hardware configuration is:

■ Processor: Any 64-bit■ Operating System: 64-bit Windows from the above list■ Memory: 2 GB■ Free Disk Space: 60 GB■ Graphics Adapter: 256 Mb memory, OpenGL 1.2 compatible■ Network Adapter is required■ Screen resolution 1600 x 1200 pixels.

It is, however, possible to run NAPA on a computer with a lower performance. The absolute minimumhardware requirements would be:

■ Processor: Up from Pentium III 1000 MHz■ Memory: 1 GB for XP/Vista■ Free Disk Space: 10 GB■ Graphics Adapter: 64 Mb memory, OpenGL 1.2 compatible■ Network Adapter is required■ Screen resolution 1024 x 768 pixels. It is recommended to start NAPA with Tinylayout if this resolution

is used (the word Tinylayout is entered into the field User Profile in the Login window).

1.5 Napa ManualsUpdated NAPA user manuals are delivered with this NAPA Release.

The recommended browser for the manuals is Internet Explorer 8 or later. Mozilla can be used but it doesnot show the search results' highlights correctly.

1.5.1 Browser setting for Online Manuals

Please check the following settings in order to ensure that the Manuals are displayed properly:

1. Internet Explorer settings:

■ Tools -> Internet Options -> Advanced tab■ Scroll down to the Security section.■ Make sure that "Allow active content to run in files on My Computer" is ticked.

2. JAVA support on your computer:

■ Please make sure that the JAVA Runtime Environment is installed on your computer. You candownload the software from www.java.com -> Download

3. Make sure that you have installed the latest browser updates.

Note: it is strictly not recommended to run NAPA system with any operating system version lower thanindicated or without the indicated service packs or patches.

http://www.java.com


3 (46)


1.6 License fileNAPA Release 2013.2 can be run with the license file delivered for the NAPA Release 2012.1 until September2013. Updated license files will be delivered to the NAPA Contact Persons in good time before the old licensesexpire.

If there are less than 7 days to the license's expiry date, a warning message is given when NAPA is started.

1.7 Important changes in the installer since NAPA Release 2012.1

There are several changes in the NAPA installer affecting, for example, possible batch files used in startingNAPA.

The same way as the previous releases starting from 2012.1, NAPA Release 2013.3 will automatically beinstalled in a subfolder named 20133 under the selected NAPA folder, e.g. C:\Napa\20133\. This subfoldercontains all needed files, including NAPA executables, NAPA database and the manuals. The official release2013.3 is though named 2013.3-1 and the corresponding folder is hence C:\Napa\20133-1\

The changed locations and names are the following:

Name Explanation Location

napa_20133-1_x86.exe 32bit NAPA executable ...\Napa\20133-1\bin\

napa_20133-1_x64.exe 64bit NAPA executable ...\Napa\20133-1\bin64\

napadb.db NAPA database for 2013.3 Release ...\Napa\20133-1\database\

index.html NAPA Manuals for 2013.3 Release ...\Napa\20133-1\manuals\

demo projects Demo projects delivered with therelease

...\Napa\pr\demoprojects\

Server and Client installations have also been changed to improve the efficiency of NAPA usage over anetwork. Only NAPA license file (napalic.txt), NAPA system database (sysdb.db) and NAPA IOF (iof.dat andiof_x64) are still located on the server computer (in the napa\pr folder).

1.7.1 Demo projects

The demo projects are installed into a folder demoprojects under the Napa\pr -folder. The current selectionof demo projects include

D-BULKER Bulk carrier, Lref = 216m, Bref = 36m, Tdwl = 15m

D-CONTAINER Container ship, Lref = 185m, Bref = 32m, Tdwl = 9m

D-FRIGATE Frigate, Lref = 138m, Bref = 16m, Tdwl = 4.9m

D-ROPAX RoPax vessel, Lref = 207.5m, Bref = 30m, Tdwl = 7.2m

The names of the demo project databases don't include the release suffix anymore. They are installed onlyif they don't exist in the target directory to avoid overwriting the old files. If the new projects are neededto be installed, the old ones must be removed manually before the new installation. With the client-serverinstallation, the demo projects are installed only to the client computer and should be opened with theoption 'Open Project From File...' in NAPA.


4 (46)


1.8 Deprecation of featuresThis chapter has been included in all Update Infos since NAPA release 2009.1 and it informs which featuresare proposed to be removed from NAPA in the future. It is highly recommended that the features in thelist are not used anymore. It will be informed separately when the feature has been removed.

The main motivation of deprecated features is in maintaining the system and improving the overall qualityof the system.

Please contact NAPA Customer Service ([email protected]) if you have any questions orcomments!

The following table lists the features which may be removed in the future:

Feature Motivation Announced inUpdate Info

Issue Number

LAU (launching) task The launching (LAU) task hasbeen replaced by the Launchingmanager which doesn't use theLAU task.

2013.1 NAPA-23420

IMO subtask in the DAM IMO A.265 can be calculated alsodirectly in the DAM task.

2013.1 NAPA-23369

LD: PLOT command (except "dotmacros")

PLD and DRW commands can dothe same (PLOT .id remains)

2013.1 NAPA-18624

TON (tonnage) task The tonnage (TON) task hasbeen replaced by the Tonnagemanager which doesn't use theTON task

2013.1 NAPA-18613

LD: IDMODE CCODE IDMODE CCODE is not used andthe setting is not saved

2013.1 NAPA-18623

Body plan window There is a better tool available inthe CONTRACT_DESIGN managerapplication

2013.1 NAPA-23762

DAM: MODE VDIR The calculation mode VDIR(variable direction) in the DAMshould not be used. Mode TWDIR(twisting direction) is the correctmode for this purpose.

2013.1 NAPA-24489

LD: LIST DAM The same functionality withbetter output is available in DAMtask, when the init case refersto the loading condition. This oldfunctionality is believed to beuseless.

2013.1 NAPA-18614

Pattern editor in the Steel mainwindow

The current quality of the toolis not good. Instead of updatingthis tool we will provide other,more userfriendly, tools to createstiffeners, seams and openings

2013.1 NAPA-24915

GB service functions Not used and nevercommunicated to the customers

2013.1 NAPA-20548


5 (46)


32bit NAPA The 64bit version of NAPA isfully compatible also with 32bitdatabases, and it is possible torun 32bit databases with boththe 32bit and the 64bit versionsof NAPA.

2012.1 NAPA-23381

LOAD and DUMP commands in theTOC

Don't support all the newinformation included in thedescriptions, e.g. possible toloose information included inthe drawings. Service functionsDM.DUMP and DM.LOAD should beused instead of the commands.The recommended way ofcreating a "cleaned" database isto use the Manager applicationMGR*EXPORTDB.

2012.1 NAPA-18674

Implicit summation of lists incalculator expressions

Causes confusing result whencomma is mistakenly usedas decimal separator andinterpreted as list summation.No known intentional use cases.e.g. !CAL 2,3,5

2012.1 NAPA-18618

HMODE in the LD The modes other than GZ cancause incorrect results and themode is confusing.

2012.1 NAPA-18620

DM.WHAT(refnr) service function The caller is supposed to knowto what one is referring to andwhether the reference number isvalid.

2012.1 NAPA-18595

DM.RENAME() with option 'E' Option 'E' in DM.RENAME hasallowed the creation of multipledescriptions with the same namewhich will lead to incorrectfunctioning of the system.

2012.1 NAPA-18597

CaPSL printer support These printers are notmanufactured anymore and theycould still be used as a windowsprinter.

2012.1 NAPA-18632

!VIEW SHARE Was never fully supported,complicates the programunnecessarily.

2012.1 NAPA-18631

Explorer window Very limited functionality. 2012.1 NAPA-18641

SQL.* service functions These functions have never beensupported.

2012.1 NAPA-18643

INQUIRE command in TAB Obsolete since GUI Table Editor. 2012.1 NAPA-18625

Graphical input with ":" syntax Cannot be supported in WindowsPresentation Foundation (WPF).Some of the most commonuse cases of the colon-syntax

2012.1 NAPA-18640


6 (46)


(placement of texts & markersin graphics) can be handled withinteractive annotations.

GR.INPUT, GR.LIVEINPUT,GR.BOXDRAG service functions

Cannot be supported in WindowsPresentation Foundation (WPF).

2012.1 NAPA-18639

Text terminal support Unix text terminal supportwill be removed, including anycommands for these devices,e.g. !block

2012.1 NAPA-20361

!VAR TILDE,C !VAR TILDE,C allows changingthe tilde (~) character that isused for continuation characterused by TYPE command to someother character.

2012.1 NAPA-18666

PLOT task / using IOF fordrawings

No support for any of thenew drawing features, andthe same operations can bedone using !SEND TO WPRor !SEND TO DB. The macroDATA*FIND_DEPRECATED_PLOTin NAPADB can be used to searcha given database and locatemacros that use this feature.

2011.3 NAPA-18588

!VAR & In NAPA macros, the '@' characteris normally used to identifycalculator expressions andvariables, but with '!VAR &' theampersand character takes thatrole. !VAR & to be deprecated,as the '@' character should bealways used.

2011.3 NAPA-18584


7 (46)


VARDEF* table as a Source in theManager

The VARDEF* table should alwaysbe located in the VARDEF columnin the MGR* table, not in theSOURCE column.

2011.2 NAPA-18580

DAM: subtask CROSS Replaced by new and betterfunctionality in LIST EQT andLIST DEQP in DAM task.

2011.2 NAPA-18576

!SCI command Related to the VMS operatingsystem which has not beensupported in last few years.

2011.2 NAPA-18572

Tribon Surface Interface (TBSI) TBSI is obsolete for both TRIBONSurface Server and IGES export -unused code.

2011.2 NAPA-18568

Report GUI in the Output tabs Reporting functionality wasbased on old VARDEF* tableformat which is not compatiblewith the Windows PresentationFoundation (WPF). The samereporting functionality isavailable with report macros(“dot” macros), Managerapplications etc.

2011.1 NAPA-18525

DEF: subtask DFN Useless when TrueType fonts aretaken into use in the graphics asa part of the graphics technologyrenewal.

2011.1 NAPA-18521

DR: subtask LDR The same functionality isavailable, for example, with thePLOT .LINESDR command andin the Contract Design Managerapplication. A new applicationfor lines drawing creation will bedeveloped and released beforeremoval of the LDR task.

2011.1 NAPA-18517

Digitizer tablets Based on old technology which isdifficult to maintain.

2011.1 NAPA-18513

UI.MAKELONGNAME servicefunction

DB.MAKELONGNAME has the samefunctionality.

2011.1 NAPA-18509

UI.GETNAMECOMPS servicefunction

DB.GETNAMECOMPS has the samefunctionality.

2011.1 NAPA-18505

OUT command in LD task LIST command has the samefunctionality.

2011.1 NAPA-18485

GUI commands starting with !!(e.g. !!MERGE)

Will not work in the WindowsPresentation Foundation (WPF),and has been replaced with MTF.*and UI.* service functions.

2011.1 NAPA-18481

OGL service functions Will not work in the WindowsPresentation Foundation (WPF).Macros containing calls to

2012.1 NAPA-18647


8 (46)


these functions will have to bemodified in the future.

!VAR SHOW command Will not work in the WindowsPresentation Foundation (WPF).

2011.1 NAPA-18477

GCR task Checking the grain stabilitycriteria should be done in intactcriteria task (CR_I?>). Use thecriteria group IGC.

2010.2 NAPA-18473

Widget Editor Support ending for Motif UI 2009.1 NAPA-18449

GOTO statement in line # Incompatible with GUI TextEditor, maintenance of the macrocode is difficult

2009.1 NAPA-18445

IF (condition) line # Incompatible with GUI TextEditor, maintenance of the macrocode is difficult

2009.1 NAPA-18437

Command PERFORM in tables Unused feature. 2009.1 NAPA-18429

1.8.1 Removed features

The following list shows the features which have been removed:

Feature Motivation Removed inRelease

Set of GS output macros and vardefswith the same name (GS-OUTPUT2,GS-OUTPUT3, GS.ALLOWABLEGM andGS.MINGM)

Macros were using GCR-task which willbe deprecated also. Code contained hardcoded values which meant that the resultswere suitable for example only.

2013.2

LIST GCR in LD task Checking the grain stability criteria shouldbe done in intact criteria task (CR_I?>).Use the criteria group IGC.

2013.2

CP: old type sounding devices Old format means before 1987. CommandCNV converses the old format and this willbe done automatically before the old typeis removed from the code.

2013.2

OLIST command in the DAM task (oldstyle list) and related old criteria and oldmoment definitions in DAM task

Replaced by new lists a long time ago. 2013.2

NPN.TVMESH() service function TVMESH command in SH task gives bettersupport for volume mesh generation.Can be run with SHA.COMMAND servicefunction also.

2013.1

SDI task (subdivision indices / USSR) Unused code 2012.2

Foreign language explanation texts anderror messages.

There have been some error messageexplanations stored in languages otherthan English. These have not beenrecently maintained, and the coverageof the translations has been poor. Errormessages and explanation texts only inEnglish will be supported.

2012.2


9 (46)


Explanation texts of commands in projector system database

In some SH subsystems the user has beenable to write his own explanation textsfor commands. The format for explanationtexts in Napa has changed and the supportfor the old explanation text format will beremoved.

2012.2

STEP, MEDUSA, SCHIFFKO and AUTOKONlinks

Old links not in use anymore 2012.2

OLOFT task Unused code 2012.1

MGR*SHIPSYSTEMS Limited functionality 2012.1

MGR*FUEL_SYSTEM Limited functionality 2012.1

Information Systems (IS) task in the SH. Unused code 2012.1

Macros, Tables and Vardef tables with theprefix INT* and TSB*

The INT and TSB Manager applicationshave been removed in Release 2010.1

2012.1

Outfit Window 2012.1

Drawing Window The Drawing window functionalitieshave been replaced by renewed Drawingmanager

2012.1

Immediate view update, command !VIEW ISU and service function GR.ISU.

2012.1

Service functions GR.SIZEU, GR.SIZEV,GR.PAGEU, GR.PAGEV, GR.PAGELIMITS.

2012.1

Commands !WINDOW, !VIEW andservice function GR.CREATEWINDOW

2012.1

Command !WINDOW R. 2012.1

1.8.2 @GOTO label in macros

Macros having GOTO with direct line jumps (line #) or even older macros having just line jumps should beupdated by using @LABEL statement.

@GOTO label; label: jump address expressed by a label with the @LABEL command

@GOTO FINISH...@LABEL FINISH

1.8.3 Removal of PLOT task

Due to the deprecation of the PLOT task it is possible that the customers need to update their own macroswhich have been using the PLOT task and/or commands related to it. In addition to the command PLOT (toenter the PLOT task, usually done from the main task or from the SRV task), the deprecated commands are:

!GR FGR.SIZE('P')GR.SCALE('A')!GR F!GR +F!GR F-TEMP!GR F-RESTORE

../managers/Drawing/index.html#drawing_manager

../managers/Drawing/index.html#drawing_manager


10 (46)


!VI ... F!SEND ... TO F!SEND ... TO IOF

There is a macro DATA*FIND_DEPRECATED_PLOT in the NAPADB with which the macros in the given databasecan be scanned to find the deprecated commands. For example, the SYSDB can be scanned with the followingcommand:

TASK?>!ADD FIND_DEPRECATED_PLOT('pr/sysdb.db')Searching 'pr/sysdb.db'Scanning 189 macros...Possible use of IOF for drawings in DATA*CREATE_NAPAINTRO line 461: !GR +FPossible use of PLOT task in DATA*CREATE_NAPAINTRO line 502: PLO; @PRI; 5; 1; SCA 1/1000; TU; OK ; !ENDPossible use of IOF for drawings in DATA*DSN20533 line 3: !gr +fPossible use of PLOT task in DATA*DSN20533 line 8: ploPossible use of IOF for drawings in DATA*DSN_13309 line 188: !GR +FPossible use of PLOT task in DATA*DSN_13309 line 1176: SRV;PLO;(WPR);1;1 @@ ENTER PRINT OUT WORK

The most common workaround is to replace !SEND TO IOF by !SEND TO WPR or !SEND TO DB and tonot enter the PLOT task at all.

Should you need any assistance in updating the macros, please contact NAPA Customer Service([email protected]).

1.8.4 Removal of the CROSS task

The task CROSS for Cross flooding calculations has been removed. Almost all functionality related to crossflooding calculations is available in task DA with the help of LIST DEQT. The possibility to calculate therequired diameter of a cross flooding pipe is not yet implemented in LIST DEQT. The plan is to add thisfunctionality in future releases. Until then the release 2013.1 can be used for this calculation as the CROSStask is still available in that release.

1.9 Finding data from the databasesThe general selection command !SEL (!EXP !SEL) offers a lot of useful possibilities for finding data fromthe databases (e.g. from the project or the system databases). The following example searches HMODE textfrom all the DATA* macros in the system database (unit 2). Macros having HMODE text are stored in the arraycalled LIST which content can be seen with the command !VAR LIST LIST.

TASK?>!SEL 2 NAME>DATA* LOC<HMODE

11 items selected, names stored in array LIST

TASK?>!VAR LIST LIST

1.10 Installation instructionsThe installation instructions for NAPA and Exceed are gathered into one PDF document. Please find thedocument Installation_instructions.pdf on the NAPA Release 2013.1 installation media.

Installation Instructions can also be found from the NAPA Manuals.

../inst/installation/index.html#inst


11 (46)


2 GM

2.1 Export to IGES formatThe older installer handles the export of Surfaces & Curves together. Now, the export to IGES option forSurfaces & Curves can be done in a better way.

Export to IGES dialog

As seen in the above snapshot, the export of Surfaces & Curves are controlled separately under Surfacesand Include Curves region.

The inclusion of the curves for exporting can be controlled with the available options under Include Curvesarea.

2.2 Accuracy Check Between SurfacesNow, a tool to check accuracy between two different NURBS surfaces is available under Tools menu.


12 (46)


Accuracy Check Tool Between Surfaces

As seen in the above snapshot, the target or different surface is selected to generate the compareddifference values in the table. And it follows the same behaviour as in Surface Offset Table while plottingin graphics.Addition to that, the points which has the distance more than the minimum tolerance is plottedin highlighted color.

The Minimum tolerance between Surfaces is set in Options--> View and Behaviour -->File tab as shownin figure below:

../gm/hulleditor/index.html#HSE-surfoffset


13 (46)


Accuracy Check Tool Tolerance

2.3 Free Form DeformationsThe transformations of the FFD-manager or the related service functions GM.BOXTRANSFORMSURFACE etc.created before always a surface of the NURBS format regardless of the type of the original surface. Now, thetype of compressed facet surfaces (=332) is maintained, others are still converted into the NURBS format. Ifthe structure of the 332-surface is needed in the result, but the original facet surface is not of that type, aconversion can be made by SUR sur2; FACET sur1 TYPE=332 ; before the transformation.

2.4 Transformation TaskThe transformation task makes now use of the molded volume with end-corrections. This is the sameas the volume returned by the function INQNT(‘HULL’,’VOLM’,REF(‘TDWL’)). It differs from the volumeINQNT(‘HULL’,’VOLT’,REF(TDWL)) or VOL(‘HULL’) where the plate thickness is taken into account. Beforethe transformation task used a volume where the end-corrections were not used to improve the accuracy.


14 (46)


3 GSGeneral improvements related to void area calculations in grain stability

■ A new function called gs.getintervalvvoid for getting the volume of a void over a certain x-sectionrange has been introduced. Earlier it was common to integrate the listed void area values over thelength in the report macros, which caused that the void volume, load volume and room volume werenot exactly matching.

■ The handling of unsymmetric grain cargo holds has been improved. Especially the cases where thecargo room is located completely on either side of the ship might have caused incorrect results earlier.

■ Handling of shifted voids in case of hg=0 has been improved. Earlier it was possible that dummy valuesoccurred in the listing and plotting.

■ A Program crash occured sometimes in the case where two hatches intersected in the same x-coordinate.

Some of these improvements have been available already in earlier releases but because the improvementsare related to each others they are all published at the same time.


15 (46)


4 Reporting and generating PDF filesIn release 2013.1 there was a performance degradation of the reporting compared to previous releases whichhad been introduced as a side-effect of a correction to out-of-memory problems with very large reports.The user had to chose between good performance, and possibility to generate very large reports, but youcould not have both at the same time.

Now the reporting code has been rewritten which improves the performance and the resolves the memoryproblems.

4.1 Speed and memory consumptionOn a system with very much RAM available, the 2012.2 version consumes lots of the memory and is reasonablyfast (45 seconds). Release 2013.1 consumes less than a third of the memory, but takes too long time tofinish. The latest release has approximately the same performance as the 2012.2 release and consumes theleast memory. The performance will of course vary depending on the contents of the report, but there is asignificant improvement from the 2013.1 release.


16 (46)


5 SH

5.1 Potential flow solver

5.1.1 External Result Processing

The calculation generates four result files and stores them in the directory defined by the quantity FOPTH(available in ther command line and under 'Calculation' in the CFD Manager). Those four files consist ofinformation about hull pressures and flow velocities (hull_out) and the wave elevation (wave_out), bothsaved for the use in Tecplot (.dat) and ParaView (.vtk). Each of those pairs can be opened together. Examplesof this output is shown below:

External files ‘hull_out.vtk’ and ‘wave_out.vtk’ in ParaView

External files ‘hull_out.dat’ and ‘wave_out.dat’ in Tecplot

More information about the potential flow solvers can be found under Introduction to TAHARA and PATCH.

../sh/taha/index.html#potential_flow_introduction


17 (46)


5.2 Viscous flow solver RANS

5.2.1 External Result Processing

The format of the RANS output files were updated. In addition to Tecplot, they can now be viewed with theopen source post-processor ParaView.

5.2.2 Triangular wetted surface integration

In order to get more accurate pressure integrals, the integration method for the dynamic and hydrostaticpressure components was updated. While the pressure integration was previously built up on virtual panels -one per each hull node point – for which the normal vectors were calculated based on the coordinates of therespective node’s neighbours (see figure ‘Integration based on virtual panels’), the quadrilateral panels fromthe hull facet surface are now split into two triangles each (one exemplary one is depicted in figure ‘Trianglebased integration’), for which the normal vectors can be calculated exactly. This change leads to higherprediction accuracy with respect to both resistance and floating position compared to previous Releases.

Integration based on virtual panels

Triangle based integration

More information about the viscous flow solver RANS can be found under RANS Solver, General.

../sh/rans/index.html#viscous_flow_introduction


18 (46)


6 SHS

6.1 Long term extreme value calculationsA new task for long term extreme value calculations is available as MAXE under SHS seakeeping.

The manuals for MAXE task can be found here.

../shs/maxe/index.html#maxe


19 (46)


7 ST

7.1 Structure LibraryA tool to see the preview of objects from structure library is available under Libraries menu.

7.2 Aveva Marine/Tribon interface■ Added possibility to select surfaces/panels to be exported to AM/Tribon. It has been implemented as

a table which is given as a parameter to the export command or in the Tribon Manager export options.Additionally a group of option can be given in the table.

■ Shell profiles traces can now be exported as whole length meaning that if a trace goes outside blocklimits, the trace is defined in full length while the profile is limited inside block.

7.3 Aveva Marine/Tribon Manager (MGR*TRIBON)Table input of panels has been implemented to the Tribon Manager. It can be used by going into specificblock item and selecting there "Give exported surfaces as a table".


20 (46)


MGR*TRIBON panel input table

Surfaces can be imput one by one to the empty default table or by pressing the button "Fill tableautomatically". Latter one populates the table automatically with current block surfaces. It is recommendedto use the automatic filling. The default table includes the following columns:

■ Surface name: name of the surface/panel which is to be exported■ Block: current block■ Owner surface: Owner surface or plane. For curved SHELL parts it is important to check that the owner

surface is HULL■ Panel type: Type of panel. -1 for curved panels, 1 for planar X panels, 2 for planar Y panels, 3 for

planar Z panels, 4 for planar inclined panels and 5 for knuckled panels. It is imporant to check thatany panel does not show 999 for this value. In this case, the definition of the panel or block definitionshould be double checked.

■ Geometry type: Patch or combined patch for curved panels, SO of FACET for planar panels.■ Part count: number of individual parts (number of closed boundary curves) for each surface. Should

always be 1, in case of something else, the surface should be devided into several separate surfaces.Block limit can also split a surface into several parts.

■ Target format: XML or SCH depending on the type of the surface. For planar panels the format can bemanually changed to be XML by activating the drop down menu of the cell.

■ Panel name: Free of choice panel name which overrides the default panelname of interface. If this isempty, default automatically generated ones are used.

■ Curved surface suffix: suffix for other curved surfaces than HULL. This one is used together with shipletters in object names.

■ Export geometry: Export the surface geometry in selected format. Currently supported only IGES.

User may also use any predefined table by typing the table name into the "Surface table name" field or byselecting it from the database using the selection tool next to table name field. User must then make surethat all required columns are defined in the table. More information can be found from the Aveva Marine/Tribon interface manual.

If the block is plotted using the "Plot block in OpenGL" button, table highlight can be used to visualizesurfaces on the graphics. Table hightlight is activated by first plotting the block and then selecting a rowfrom the table.

It is always recommended at least to check the surfaces for previously mentioned problems by using thetable. Output can then be done without the table by deselecting the option "Give exported surfaces as atable". If the table is not visible in the manager, any changes made to table are not taken into accountwhen exporting.


21 (46)


Changes to block specific tables are saved automatically.

7.4 Bracket location by 3 pointsThe location of a bracket can be defined with 3 points describing the corner and sides of the bracket. Thissyntax can be used with plain brackets and with general brackets type 2.

->name (x0, y0, z0) (x1, y1, z1) (x2, y2, z2)

7.5 Opening requestsThe file format of opening request files has been changed to 3D Dump (3DD) format. At the same timesupport for arbitrary shaped openings has been added.

Reading opening requests in 3DD format is supported only in 32bit Napa.

7.6 Object selection method in Structure LibraryIn Structure library, the old method of selecting the library objects from a list of names has been changedinto new method of selecting it from the list of bitmaps as shown below.

Structure Library Object Selection

The desired object can be selected from the palette shown and start adding the object.

7.7 Folded flange for plain bracketsA folded flange can be defined for plain brackets by FOLD=width option of FLALOC column in BRACKETStable. For example "FOLD=100" creates a folded flange which width is 100mm. Side of the flange can bedefined in FLASIDE column of STDEF table. The value of the column can be either F (front) or B (back). Bydefault the value is F.

The trace of the folded flange is fixed on built-in brackets and equals to the straight part of the free edge.Folded flange is not supported for built-in brackets without straight edge. On user defined brackets the UVFFstatement can be used to define the trace of the folded flange.

The folded flange is visualized in 2D drawings with a standard shape that can be seen in the example below.Line type is controlled via pen control table and different line type can be used based on the side of theflange (front/back). The minimum distance in drawing (mm) between flange line and free edge of bracketcan be controlled with MDD1=d option in PLO BRA command. The text for annotation can be given in columnTEXT in BRACKETS table.

Example:

BRACKET BRID PLTH MAT FLALOC TEXT


22 (46)


-------------------------------------------------------------BTT200F TT*200*200*20*20 12.0 A FOLD=30 30FL.

Bracket with folded flange in 3D view and in 2D view (both front and back viewing directions).

7.8 FEM ToolbarThis toolbar will be removed in future from NAPA Steel. Use FEM manager for further use

Open FEM manager in NAPA Steel from here. ( Managers -> FEM ).

7.9 Edit Parametric ObjectAny parametric object can be edited by selecting it from the graphics and by right-click -> Edit ParametricObject.

Edit the active parametric object

Editing of parameters: edit parameter and limit values to get the desired result. It behaves similar tothe interactive mode of structure library replacing the old method of Edit Parameters in which only theparameter values can be modified using keyboard input..


23 (46)


8 FEM

8.1 FEM Manager

8.1.1 Ugrade existing FEM Models

The user can upgrade the existing FEM models to be compatible with the latest development in FEM Manager.The system asks the user if the FEM models are wanted to be upgraded and also when the system has finnishedthe update process.

8.1.2 Plot Options

Element Thickness Plot: The user can plot the elements with a respective color and a legend with allthicknesses in the current FEM model.

The color indicates the element thickness.

Free Edge Plot:The user can plot the free edge of the FEM model ontop of the mesh or plot only the freeboundary to the graphics area.

8.2 SmoothingSmoothing algorithm doesn't move the nodes which are located on FEM Traces. This way the user can createstructured mesh manually and still apply smoothing to that particular object or objects.

8.3 Bracket toe cutThe mesh for such objects that have very narrow end shape, e.g. transverse web bracket can be controlledwith parameter "Tol. for Bracket Toe Cut.". See the example below where the bracket toe is idealized forglobal analysis purpose.


24 (46)


8.4 ClassNK PS-HULL DSAThere has been several improvements made for the ClassNK PS-HULL DSA interface:

■ Both, stiffened panels and unstiffened panels, are generated for SideTrans, HoldBHD, SwashBHD,LStool_Aft and Fore, L.UStool, L.LStool, LBHD members in cases where not all panels fulfill thestiffened panel requirements, according to Common Structural Rules for Double Hull Oil Tankers.

■ Improved member mapping function■ Knuckle line included as panel boundary■ Improved corner node search for irregular panels■ User input for panel limits

8.5 Idealization of Openings (Omit Element Option)In the FEM-manager, the idealization option OMIT_ELEMENT of openings, does not any more change the platethickness of the FEM-elements in the neighborhood of the omitted elements. However, in the use of old FEM-toolbar of ST, the corresponding options G11, L11 or F11 of openings in the FEMINCL column of the STDEF-tables still omit elements and change plate thicknesses as before (but with increased accuracy in the caseof the FEMDEF-option ‘Omit elements’)

8.6 STL-FormatThe OUT command of the FEM-task has the new option STL, that can be used to write a triangle mesh intothe ASCII STL format. With option SYM, the elements reflected with respect to the Y=0 plane are added tothe file also. The STL-output of FEM-models is internally used by the new service function GM.TOSTL thatconverts surfaces to STL-format.

8.7 Mesh parameter changesDue to the changes in the surface meshing procedure, the default value for Weight on shape quality ischanged from 0.7 to 1.0. This ensures optimal amount of quadrangles in the mesh.


25 (46)


9 Weight calculation

9.1 Column dependenciesIn releases from 2012.1 until 2013.2 there has been issues when WG uses the value of a column calculatedby a formula. In this case value of the formula would not get evaluated before the table value was used byWG, resulting in WG using the value empty string or zero.

9.2 Formula references to automatically calculated columnsWG automatically adds some columns to the weight tables, for example the column REFVAL. If you reallyneed to refer to this value from a formula you should explicitly declare the column and it should be declaredbefore (=to the left of) the column with the formula referring to REFVAL.


26 (46)


10 Manager Applications

10.1 Drawing Manager (MGR*DRAWING)Drawing toolbar in Drawing manager contains new tools for drafting and annotations.

10.1.1 Offset Polygon

New tool for creating an offset polyline from existing polyline has been added. Offset polyline can becreated either from non-interactive line or interactive two point line and polyline.

10.1.2 Trim Polygon

New tool for trimming line with another line has been added. Trim functionality can be used for twopoint line or polyline. Either non-interactive line or interactive two point line and polyline can be used asa reference for trimming.

10.1.3 Extend Polygon

New tool for extending line to another line has been added. Extend functionality can be used for twopoint line or polyline. Either non-interactive line or interactive two point line and polyline can be used asa reference for extending.

10.1.4 ST Group Annotation

New ST annotation tool to annotate group of steel objects inside a selection rectangle has been added. The object type and quantity selection is similar to the ST Text Annotation. By default each marking is locatedin the center of the object but user can manually move markings to the better locations if needed. During theupdate of drawing the manual modifications are kept if there is an object of same type in the same locationthan before. The selection of objects to be annotated can be restricted with a separate selection criteria.


27 (46)


Example of ST group annotation. All the plates inside selection rectangle are marked with selectedquantities (plate thickness and material).

10.1.5 ST Group Annotation Table

New ST annotation tool to annotate group of steel objects inside a selection rectangle and create an

annotation table based on the selected objects has been added. The tool is similar to the ST GroupAnnotation tool explained above but the way of representing the markings is different. In the annotationtable there is a collection of different values of selected objects. The most common value is on the firstline and the rarest on the last line. Each line in the table has a different marking symbol and the samesymbol exists on the drawing right next to the object. The objects having the most common value are notmarked on the drawing.

Example of ST group annotation table. All the different longitudinal deck stiffeners inside selectionrectangle are listed in the table and corresponding markings are shown along the traces.

10.1.6 Fillet

New tool for filleting two lines has been added. Fillet can be created between two intersecting lines andnon-intersecting lines. Currently the fillet functionality is supported only for the interactive two point lineand polyline. Non-interactive lines are not supported.


28 (46)


10.1.7 Mirror

New tool for mirroring primitives has been added. Mirrored primitives can be created for the selectedprimitives along the reference line.

Note: The current mirror functionality is supported for basic primitives: Line, Polyline, Rectangle, Circle,Arc, Line with end Symbols & Revision Cloud.

10.2 InterfaceToRules Manager (MGR*INTERFACE_TO_RULES)

10.2.1 Manager tree heirarchy

The manager tree heirachy of Interface to Rules Manager, GL Rules, has been modified as shown below -

manager tree

10.2.2 Hull Girder Bending

"Hull girder bending" is the amount of bending caused to the ship's hull by external forces. For example,the bending moment is the highest in the midship section when the ship's ends are supported by crests of awave known as `sagging' or `positive bending'. When the ship is riding the crest of a wave at it's midships,the bending moment is known as `hogging' or `negative bending'. Bending moments are measured in tonne-metres.

This item will list the bending moment informations. Tree structure view of this item is shown below

Still water item is always visible in this folder. But harbour and flooded condition is visible only if the followingoptions are selected -


29 (46)


In all these three items, select the loading groups from the listbox. On update, BEND (min, max), SHEAR(min, max) and TORSION (min, max) information will be listed in main window and added into the tables.Envelope curve diagram is plotted for the corresponding loading groups. Example diagram is shown below.

10.2.3 Frame system Info

This folder contains three sub items, namely Frame Table, Longitudinal Grid and Vertical Grid. This folderis common for all the rules in this manager.

FRAME TABLE

This item will show the framing system defined in the project database. The first tab "Frame Definition" willshow how the framing system is defined and the second tab "Detailed Frame List" will list all the frames intothe table in detail. These tables cannot be edited.

LONGITUDINAL GRID

This item will show the Longitudinal framing system defined in the project database. The first tab"Longitudinal Grid" will show how the longitudinal framing system is defined and the second tab "Detailedlongitudinal Grid" will list all the frames into the table in detail. These tables cannot be edited.

VERTICAL GRID

This item will show the Vertical framing system defined in the project database. The first tab "Vertical Grid"will show how the longitudinal framing system is defined and the second tab "Detailed vertical Grid" will listall the frames into the table in detail. These tables cannot be edited.

10.2.4 Transverse Members

Transverse members exported at this item of the manager based on the structure type selected.

trans.members

Transverse Plate Properties of the transverse objects listed in the item.


30 (46)


trans.plates

Transverse Stiffener Properties of the transverse objects listed in the item.

trans.stiffener

10.2.5 Compartment Info(GL-LINK)

Now compartment geometry information can be exported to GL and compartment information can be seenin Longitudinal Members folder.

Note: There are some known issues in Compartment export to Poseidon. These will be fixed in the nextrelease.


31 (46)


10.2.6 Class NK Ship3D Interface

It is now possible to limit the exported model by setting the limits in export item. All the main objectscompletely outside the given limits are omitted.

Limits field

10.2.7 Class NK Performance Interface

It's possible to select/assign the loading condition type as SEAGOING or HARBOR and also possible to add and

delete the selected loading conditions by using and buttons respectively.

Loading Conditions

10.3 MARPOL ManagerThe marpol manager has been improved to include the following changes:

1) The regulation 13A has been updated to Regulation 12A as per the new amendment made for Oil FuelTank Protection.

2) Light draught is given as input instead of Partial draught for accidental oil outflow performancecalculations. The partial draught is calculated as dpartial = (dscantling-dlight)*0.6+dlight

3) The option offered to automatically attempt to identify a possible skeg is offered as an experimentalfeature for the clearance calculation. The regulation states that a skeg should not be considered as the


32 (46)


baseline to measure 1.5h from bottom shell. The default value is that the skeg is not identified (the lowestpart of the section is used as baseline), but if desired you can turn the option on and based on the sectiongeometry the macro will attempt to identify a skeg in each section under the hull. A skeg is searched for belowthe design waterline (TDWL) and inside 1/4 of the breadth of the section measured from the centreline. Asection is considered to exist if the section curve has an angle of >=50 degrees. Do note that this feature isstill with experimental status and will likely be improved later on. It is not for sure this method will workfor all skeg shapes.

10.4 Free Form Deformation Manager (MGR*FFD)Following improvements have been included into the Free Form Deformation Manager application:

1) Patch surfaces and combined surfaces are now supported. Previously only NURBS surfaces were supported.

2) Blending factor, which defines the magnitude of the transformation, can now be given within the rangeof -10...+10.

3) Improvements to the plotting options of the surface/grid.


33 (46)


11 Napa Basic

11.1 Accuracy improvementsSome changes has been made to improve the accuracy of Napa Basic macro execution. Both changes arerelated to tolerances and will change macro execution flow in some corner cases where there are comparisonof numbers that are almost equal.

11.1.1 For loop end conditions

In previous releases the check whether to end a for loop has been compared using a tolerance. This createdproblems when the step was a small floating point number in which case the loops was not carried out thecorrect number of times.

@FOR KK=21.349,21.352,0.001 !TYPE ##################### @KK @NEXT

In the example above, the loop should be carried out four times and the output should be:

##################### 21.349##################### 21.35##################### 21.351##################### 21.352

In older releases due to the use of tolerances in the for loop end condition comparison, this loop wasincorrectly executed 14 times.

11.1.2 Conditional statement evaluation

Napa basic conditional operators less than (<), greater than (>), equals (=), not equal(<>), less than orequal and greater than or equal has previously been using tolerances in the comparisons. This has led toinaccuracy in cases where small numbers are compared. In this release the error has been corrected, so thatno tolerances are used for these comparisons.

Below is an example:

@r1=0.004945742@r2=0.004945744

@if r1<r2 then !type smaller than@elseif r1>r2 then !type greater than@else !type the same@endif


34 (46)


The above example would before the correction output that r1 and r2 were equal, although they clearlyare different. Starting from this release comparisons are done without tolerances so the above will output"smaller than" as it should.

11.1.3 Comparison of floating point numbers in macros

As the tolerances previously used for comparisons like a=b has been removed, care must be taken whenprogramming comparisons between floating point numbers. So instead of writing:

@if a=b then...@else...@endif

it is better to do the comparison using a tolerance:

@if abs(a-b)<0.00001 then...@else...@endif


35 (46)


12 Performance improvements

12.1 Performance improvement: macro search orderNapa macros have traditionally been looked up using the search order DB1, DB2 and DB7. On Napa installationswhere the sysdb and project database are located on a remote server that is not in the same local areanetwork this had a negative impact on performance.

Now there is a new service function called ai.rundb7() that searches for macros with remote search order,so that napadb is searched first, then sysdb and finally the project database. The places where theGraphical User Interface runs macros have been changed to use this new function. This results in improvedresponsiveness of the GUI, especially in the beginning of the run.

12.2 Resource files search orderTo improve the responsiveness of the Graphical User Interface in installations where the access to projectand system database is slow, the search order for resource files has been changed. This may change thebehavior of the program in the unlikely event that the user has overridden some resource files provided byNapa by storing modified copies in the system database. Typically the file concerned would be RES*SYSTEM.If a copy of RES*SYSTEM has been stored in the system database it will no longer be executed. Only the fileRES*SYSTEM in the Napadb will be used.

In case a customer wants to have some company specific resource settings it is now possible to store them ina file called RES*COMPANY in the sysdb. In case RES*COMPANY exists in the sysdb it will be used automaticallywhen starting NAPA. The user specific resource files are also available and they are executed quite as inearlier releases.


36 (46)


13 Known Issues

13.1 Balancing loading conditions in the NK ManagerThe balancing of the arrival loading conditions in the NK Loading Condition generation manager(NK_LCOND_GEN) is not always successful. It is advised to check that the targets were met after balancing.

13.2 Damage definition windowThe damage definition window should not be used to edit complex damage definitions. Complex damagesare for example damages generated by the PROB Manager or damages containing A-class stages and crossflooding. Modifying these using the damage definition window can result in an incorrect definition and wrongend results.

13.3 Optimisation with multiple parallel processes and the Seakeeping subsystemThe combination of running optimisation on multiple processes and involving calcualtions in the Seakeepingsubsystem does not function yet and might cause the system to stop responding.

13.4 %-sign in a list headerWhen the %-sign is included in a list header (e.g TOO HD=(('50%COND','DESCRIPTION'),U) it is interpreted asa variable flag. If the variable is not defined, there will be an error message when producing the list.


37 (46)


14 Corrected Errors in Release 2013.3The following error corrections and improvement suggestions have been included in the new release. The IDnumber refers to the action number maintained by the Customer Service at Napa Ltd.

List of corrected errorsID Description

NAPA-315 Default value of parameter PBTY in reference value set to empty string insteadof "undefined".

NAPA-9802 @GOTO <linenumber> syntax is not any more supported in NapaBasic macros.Please instead use @GOTO <label-name> combined with @LABAL <label-name>

NAPA-13189 The command !WHERE shows now more accurately which Napadb is used in caseof running a patch release

NAPA-14663 Support for changing variable-marking character @ in NapaBasic to & with !VAR & has been removed. @ is now the only character identifying variable-expressions in Napa Commands and starting NapaBasic statements.

NAPA-17893 "!exp send/grl" explanation command updated with ID information and itmentions that it works from version 3 onwards

NAPA-19874 LR_SCM IS2008 features are now available with the normal LR_SCM license

NAPA-20258 Explanation text of GME.NODE has been corrected regarding the record number2.

NAPA-21603 Diagram plotting (DIAG): creating diagrams with infinite values (or NaN) was notdetected. Now an error message is raised if it happens.

NAPA-23987 NAPA Start up fails in 32bit Windows XP

NAPA-24133 The documentation for converting databases from 32bit to 64bit has beenimproved in the manuals

NAPA-24522 Execution of command '!PRF sel PERM' is disbaled for adminstrators. Attemptto use this command as an adminstrator will raise error "Command in wrongcontext (E 3)'.

NAPA-24638 The TGRES calculation method was not working on a statistical hull due to aninstallation problem. This has been fixed in this release.

NAPA-24755 CP: Compartment Hydrostatics Output -tab for listing, PLD, list.macros,plot.macros and reports related problems fixed. Earlier it was possible thatnothing was listed of plotted because compartment selection was not handledproperly.

NAPA-24872 In a structured if - then - else statements, error in evaluation of the test-expression (eg. undefined variable) has been resulting in execution of both true-branch and false-branch. Now error in evaluation leads to evaluation of thefalse-branch only.

NAPA-24928 CL: LIST CT for a given container arrangement produced wrong results for longcontainers

NAPA-25014 Option STYPE of command GEN DAM accepts alternative *LASTn, where n isany positive integer. This formulation means that the given type of s-factor isassigned to n last stages. Multiple *LASTn's or combining *LASTn with a *LASTis not supported. Also note that the stages affected are the ones generated


38 (46)


according to the STAGE option in GEN DAM including optional stages and notnecessarily the last n ones after calculation.

NAPA-25036 CP: Old type (older than Rel. 87) sounding devices in CP are now automaticallyconverted into the new format

NAPA-25063 A warning (W31099) is triggered if the wave reaches up to the upper limit of thebackground mesh during a RANS calculation.

NAPA-25161 LD: calculation with deck load and changed added loading condition could resultin program crash

NAPA-25180 Endcode Symbols: Support for rotation of text for endcode symbols of stiffenersis only available when the symbol is created as a drawing primitive.

NAPA-25182 Default profile I*100*10 is not used anymore. If Invalid profid is used thestiffener is not created and an error message is shown in main window.

NAPA-25217 Memory leak in arrays returned using $RESULT variable corrected.

NAPA-25230 DA flood.sim: possibility to define initial air pressure for a room with the newcommand AIRP in the init case definition

NAPA-25249 Option 'PERM' in transparent command '!PRF' obsoleted.

NAPA-25292 NAPA ER: In some cases adding a new condition to the scenario tree couldresult in changes being added to the current condition. The new condition washowever restored if it was pressed in the tree again. This is now fixed.

NAPA-25476 Criteria groups named MODU.COL and MODU.SURF updated. Criterion V.MINGZ0is substituted by criterion MODU.MINGZ0. These two consider differently therange. For the range MODU.MINGZ0 consider the second intercept or the end ofthe range whichever is less.

NAPA-25493 MGR*PROB: Item "Minimum GM report": Regulation 9 results are skipped if theyare not valid.

NAPA-25498 DAM: The probabilistic damage stability freezed in a very rare case when 32bitproject database was used in a 64bit NAPA. This issue is now fixed.

NAPA-25515 The default text export format in DXF export is text instad of graphicsregardless of the layer in which the text exists.

NAPA-25540 The total W2 in COATING* tables is now the direct sum of each row

NAPA-25591 INC: possibility to define tank specific slack limits for tanks in the TMASS table.New quantities SLACK and LSALCK are also available in LQ TNK.

NAPA-25609 MGR*SHS-SEAKEEPING: Saving the result list failed under Regular Waves andIrregular Waves output.

NAPA-25631 INC: listing of arbitrary quantities from the TMASS table with *qnt syntax in LQTNK did not work properly if also incling tanks were listed

NAPA-25642 Accessing Napa API from a unmanaged C/C++ program failed to load managedassemblies.

NAPA-25656 CP -> PAR task: The description of a device was not displayed with command DEScomp without the option DEV (e.g. DES DEV comp).

NAPA-25659 MGR*SH-POWERING: LCB values shown in the Geometry item was wrong in casethe AP was not located at X=0. This is now fixed in the new release.

NAPA-25669 Now we can export the Gl file to Poseidon


39 (46)


NAPA-25682 AM-interface: Wrong ordering of stiffener tags is fixed. There was a possibilitythat a stiffener referred to not created stiffener which was situated later incurrent panel.

NAPA-25685 LD: warning is now shown when adding a mass load with undefined type of load.

NAPA-25698 LD: NH option included in explanation text for LIST SD and LIST ST

NAPA-25701 RANS/MGR*CFD: Improved restart function based on a more accurate wettedsurface area. The resistance coefficients CF, CPRS, CPH and CT are calculatedfrom the forces determined within the _IT directory and averaged for the _MAINdirectory, while the wetted surface S in the _MAIN directory is taken from theGEOM task.

NAPA-25729 NK Manager; The keel thickness was not considered properly for MouldedDraughts in the balancing tool for loading conditions in the stability booklet

NAPA-25745 NAPA Steel-Aveva Marine link: Added check for missing MAT (material)definitions.

NAPA-25748 "Undefined alternative" error messages corrected to be more informative

NAPA-25762 os.movefile function replaced with os.copyfile + os.deletefile to be able toinherit the security rights from the final destination path.

NAPA-25787 LD: new option GLOBAL for SFC CSR. with this option the shear force iscorrected at all bulkheads unless all bulkheads are homogenous.

NAPA-25817 Tolerances removed from napabasic logical operators <, >, = and <>. This maychange the behavior of some macros.

NAPA-25823 MGR*PROB: Manually set vertical extent limit (in advanced mode) was taken intoaccount in the damage generation only when the subdivision table containedsome vertical penetration limits (decks). Now it is taken into account alwayswhen it is defined.

NAPA-25832 LD: an error is raised if the lightweight version contains maxval definitionsfor shear force or bending moment limit values. This is valid only for very oldprojects (over 20 years). The maxval definitions are not supoorted anymore andinstead the STLIM argument should be used.

NAPA-25869 NK Manager; The default trim range for initial conditions under SOLAS 2009 isnow set to aft trims. This concerns the default trims that are set as 1% and 2% ofLs

NAPA-25899 NK Manager; The trim sign in REF is taken into account properly in the combinedTrim&Heel corrections tables under Sounding tables

NAPA-25906 NK Manager, Sounding tables. The sign of heel (- / +) is now inline with theletter P and S indicating to which side the ship is heeling also in lefthandedcoordinate systems

NAPA-25976 DA: Instantaneous compartment connections are taken into account also in theACLASS stages during the calculation.

NAPA-25985 MGR*PROB: When the calculation stage CROSS60s was added by using theADVANCED mode of PROB Manager, the s index of the stage 1 should have beenignored in the index calculation. Instead of that, the s indices of the stages 1and CROSS60s were both incorrectly taken into account. This happened only inthe ADVANCED mode, not in the NORMAL mode.

NAPA-26009 Ruby and .NET framework are available in all NAPA API's (C/C++, .NET)

NAPA-26088 Manuals search engine updated to work with latest java update.


40 (46)


NAPA-26147 CR: moments usn.wind1 and usn.turnmom1: unused parameter TP2 removed. Noeffects on results

NAPA-26159 new service function IN.FLOPOSINWAVE for balancing draft and trim in the givenwave. For use of the second generationintact stability calculations

NAPA-26179 !L command for listing preceding commands has been fixed to work as expectedwith multi-line commands (some problems were found in regard to multiline-commands with !L in release 2013.mar)

NAPA-26183 JVM does not crash NAPA at startup when the given upper memory boundary isset too low.

NAPA-26230 MGR*GENERAL_OPT: Total time used for the optimization was incorrectly shownin the Optimization Progress Window in case the optimization took more than 24hours.

NAPA-26232 MGR*SH-POWERING: Applying the correction to the resistance or propulsioncoefficients did not work in the previous release. This is now fixed and the fixwas also included in the final 2013.1 release.

NAPA-26235 DA: Flood.sim: using several stages in the damage case with different time stepsdid not work properly

NAPA-26247 DA: location of an opening that was defined as GEOMOBJ=point was incorrect.

NAPA-26251 @parameters() statement with trailing tab character generated error in CRmacros.

NAPA-26253 MGR*PROB: The damage definition list using LIST DDAM in the report now alsoshows the STAGE value. This is to avoid confusion for the user when the sameroom can appear multiple times for the same damage.

NAPA-26330 MGR*FFD; The user interface has been modified with new buttons for creatingnew cases and deleting existing cases.

NAPA-26341 Four new quantities are implemented in LIST DRES: - ESC_IMMA, angle ofimmersion of the escape routes - IMM_ROUTE, name of the escape routeimmersing first - ESC_IMRES, immersion reserve of the escape routes -RES_ROUTE, name of the escape route having the minimum reserve. If anyof these quantities is set to the quantity selection of LQ DRES, the set of therelevant openings is divided into two parts, escape routes and openings withoutthe escape routes. In that case the quantities FA, FLOPEN, FAUN, FLUNOP, FAWE,FLWEOP, RESFLD and OPEN are calculated with the opening set excluding theescape routes.

NAPA-26352 MGR*NK Stability booklet: The displacement correction for trims used thestability hull (STAB) from REF instead of the hydrostatic hull (HYDR)

NAPA-26353 Dam: re-definition of initial condition in a macro could sometimes causeincorrect results due to a bug in up-to-date handling. This could only occur ifcalculation was very rapid.

NAPA-26360 MGR*NK: "Displacement Correction Table Due to Deflection" -item has beenmodified. A new calculation method based on the DFL command (Deflection) inHYD is used instead of the old method which was based on the Wave commandin HYD. Small changes in the results of the magnitude 0.4% will be seen.

NAPA-26431 SH: CALC command has an option of giving the sub-task in which the calculationshould be performed. In the previous release there was an error that this alsochanged the sub-task to the given one. This has now been fixed so that thecurrent sub-task remains active.


41 (46)


NAPA-26466 DA; improved up-to-date control for the initial conditions

NAPA-26491 GS: An error which caused incorrect results in case the grain cargo space andthe girder definitions were asymmetric has been corrected

NAPA-26492 USN.A.MXH criteria defintion is updated to user USN.A.MAXH macro forevaluating the max. heel. CRIT, USN.A.MXH, 'Max. Heel After Damage, ShipsWithout SP Systems' TYPE, MACRO MET, IF, ATT<REQ REQ, USN.A.MAXHEEL

NAPA-26505 CR: moment arm, quantity MOMARM, is now available in LQ GZC and LQ DGZC

NAPA-26536 Updated US Navy criteria DDS 079-1 to Version 2.01 from 30 Jan 2008 1.Range 'RANG, -, MIN(70, FA)' added to following criteria: USN.WIND.GZMIN,USN.TURN.GZMIN, USN.CROWD.RDY. 2. In the moment USN.TOW the k-parameter in the formula is changed, from imperial to SI-units

NAPA-26712 MGR*LR_SCM, MARPOL 12A: Clearance distance for compartments not needed tobe checked is no longer reported

NAPA-26715 Masses tab in ER includes add, edit and del mass load option.

NAPA-26730 MGR*CFD - TAHARA: The complete result output document can now begenerated by a folder level update of the 'Output' Manager tree item withoutmissing data and main window errors. After this folder level update thedocument can be printed with the print button saying 'Print selected item'.

NAPA-26750 MGR*SHM-Manoeuvring: Wheelhouse Poster included unnecessary characters "A"and "B" with large font. This error has now been fixed and those characters arenot displayed anymore.

NAPA-26753 Damage criteria USN.A.MINAREA and USN.A.AREA calculation macros improved.The effect of the GZ reduction is now taken better into account. The methodfor finding the equilibrium angle (considering the reduced GZ curve) and themethod for calculating the area should still be improved.

NAPA-26784 Problem in using general bracket with stiffeners on boundary is fixed.

NAPA-26799 MGR*SH-POWERING and MGR*SHM-MANOEUVRING: Selected transom curve wasnot higlighted in the graphics of the Resistance Prediction Method item. Thiserror has been fixed.

NAPA-26802 Provided the program can calculate the complete fluid equalization timebetween the successive stages, the type of s-factor is assigned NONE in theintermediate flooding phases if the equalization time is less than 60 s.

NAPA-26812 NAPA ER: Removing a breach occasionally could cause instability in the probgramleading it to close. This has now been addressed.

NAPA-26813 Breached compartments in NAPA ER sometimes was drawn with a completelydifferent cargo filling level that the actual one.

NAPA-26820 MGR*MARPOL and MGR*NK: Default CDB values for the accidental outflowcalculation have now been improved. Most cases are now handled correctly, butin some rare cases the topology might not return all neighboring tanks and a 0.6value might show up as 1 instead (user editable in the Manager application).

NAPA-26823 MGR*MARPOL and MGR*NK: The y distance from the HULL to the tank is nowdrawn horisontally in the critical section plot and not diagonally.

NAPA-26920 The file reader of the RANS grid quality task RGQU has been updated for thehandling of the ParaView formatted RANS output file FLOWEX.DAT


42 (46)


NAPA-26940 MGR*FFD: Pressing Update on items Create Bounding Box and ApplyTransformation were resetting the current zoom and projection. This has beenimproved now so that zoom and projection are retained.

NAPA-26942 DA flood. sim.: dumping a simulated phase into a separate damage case withda.dumpphase function could cause NAPA to freeze

NAPA-26953 Changes in quantity standard causing unit conversion errors were corrected inOormers (Task OORT) resistance prediction method

NAPA-26954 SH-Powering Manager : Oortmers method's wrong traffic light indication problemhas fixed

NAPA-26992 The command !SPAWN caused the 64bit version to crash in some cases

NAPA-27010 NK Manager; Forward draft limitation is not effective for no heavy ballastconditions for bulk carriers.

NAPA-27013 PDF creation performance issue. See "Reporting" chapter in Update Informationfor details.

NAPA-27037 LD: only the wave name is now stored in arguments since the definition datacould cause problems in generating wave surface for 3D plots.

NAPA-27054 Wave calculation with LD, CR, HYD, STAB and in.waveqnt(): Calculation of GM/KM in a wave is now based on moment of inertia of projected waterline area.This slightly affects the results especially in steep waves. This has no effects oncalculation in calm water.

NAPA-27093 HYD: possibility to delete wave definitions with command UNS WAVE

NAPA-27147 calculator function INQNT: quantity TK is replaced by more descriptive TMAX.For backward compatibility TK is still supported as a synonym.

NAPA-27221 Freeboard Manager: The effective length for superimposed superstructureswas given although the effective length should apply only for first tiersuperstructures. Now the effective length for a superimposed forecastle or poopis set as 0.

NAPA-27228 Criterion range changed to FAUN instead of FA in A.AREA.70 and A.AREA.100.

NAPA-27240 The possibility to use ;** and ;!* as a NapaBasic comment (in addition to @@)had been broken but is now working again. Please still prefer to use @@ to markcomments.

NAPA-27280 DATA*DA.PLOT_FLOAT: A macro for plotting the floating position in OpenGL for adamaged case is now available in NAPADB.

NAPA-27300 DATA*GM.PROJECTION_CURVE: lower case name is now automatically convertedto uppercase

NAPA-27310 Generated damages cannot be saved when the damage definition GUI is openedfor damages in the PROB Manager.

NAPA-27368 MGR*NK: MARPOL 12A outflow calculation for bottom damages now reports '-'values for Yp, Ys, Y-port and Y-stbd when the tanks are located completelyabove the dB waterline and calculation acc. to the rule isn't possible.

NAPA-27394 LD: PLOT .LOADS corrected to work also with active (not saved) setup definition

NAPA-27396 The Frame Table tree item in INTERFACE_TO_RULES manager has been changedso that the Frame Tables, Transverse Grid and Vertical Grid are in separate treeitems. The details of Transverse and Vertical Grids are also visible. Also, all thedetails are visible only for information purpose and is not editable.


43 (46)


NAPA-27397 LD: LIST STR now shows dummy value (-) for relative values if both limit curvesare on the same side and the option MID is not used.

NAPA-27421 The search engine of the Napa Manuals stopped working after Java 7 Update 25was installed. The manuals of this release have been updated so that they work,and from NapaNet there is a utility called ManualsUpdater.exe that can be usedto update the manuals of any old versions so that the search engine works inthose.

NAPA-27427 When a png image was used as page header figure (e.g. company logo), the sizeof the logo was wrong when printed with docbook (using Ibex). The logo wasprinted in too large size.

NAPA-27431 The required value for the intact CCS.MINGM criterion for crane ships in transithas been corrected

NAPA-27437 Reading stored arguments in HYD without a deflection (DFL) defined did notreset the DFL value

NAPA-27455 CR_I, 2nd generation intact stability: change of wave definition did not triggerrecalculation of results

NAPA-27460 TP.copyline() function to copy also the exception information of the copied cells

NAPA-27466 PROB Manager: The limitation of the name of the subdivision table is 12characters. A check for the length of the name has been added on the topleveland in the Subdivision item. A warning is given if the name exceeds 12characters

NAPA-27480 GS: A problem related to unsymmetrical grain cargo spaces has been corrected.In rare cases when a hold was located completely on either side of the ship,wrong calculation results were obtained.

NAPA-27482 ER: A tool for selecting the strength limit curves has been added in strength tab.

NAPA-27558 MGR*CFD: The volume mesh generation task TVME is entered before RANScalculations are restarted from existing cases in order to make the draftquantity TASIM available. Previously an error (E31003) was shown in the mainwindow after the last iteration and the list in the Text Viewer of the 'Calculation'item was not updated, while the calculation was still carried out properly evenbefore.

NAPA-27567 DA: To ensure damage descriptions are stored intact regardless of possible errorsduring the damage creation, internal error flags are now cleared prior to writingthe description to the database. An unlike but possible scenario of an errorarising in the middle of a damage creation was found and now eliminated. Thiscould have lead to differences in results if the calculation would have beenforced again after exiting the damage task and the damage descriptions werenot saved correctly.

NAPA-27577 Quantity TMREL can now be used for the strength tab with strength mode 2 inNAPA ER. Previously this resulted in errors.

NAPA-27580 MGR*CFD - TAHARA: A popup asking for a valid file path is shown if a non-existing file output path is used in the 'Calculation' Manager tree item.Previously, the non-existing output path for the result files was raising the'Unspecified file error' (E11075) in the main window.

NAPA-27604 CL: explanation texts on using WREL option in ADD and CHG commands havebeen fixed


44 (46)


NAPA-27605 LD: Problem with side wave handling fixed. Calculation in exact side wave (DIR90 or -90 deg) resulted in incorrect heeling direction. Also drawing the wave inx-section with left handed coordinate system was reflected.

NAPA-27640 MGR*GENERAL_OPT: The displacement DISV can now be used as an objective(e.g. 'to be maximizaed'), when an automatic hull form variation (e.g. withMGR*FFD) is used together with the Optimization Manager MGR*GENERAL_OPT.

NAPA-27644 Napa did not function properly in an operating system with Turkish languagesettings.

NAPA-27658 For Regulation 12A, If Capacity of fuel oil tank exceeds 2500m3, Popup appearswith warning message and cannot continue with calculation.

NAPA-27677 MGR*FREEBOARD: Freeboard length calculation improved by giving curve namesto the sections done in the macro. Unnamed sections are replaced by the nextsect() call and could cause calculations to be done with the incorrect sectioncurve.

NAPA-27692 SHS, MGR*SHS-Seakeeping: When running seakeeping calculations, the resultdirectories are created and searched for ship velocities in knots up to aprecision of one decimal.

NAPA-27706 CAT command in TOC task fixed

NAPA-27713 MGR*CFD / Panelization for RANS: Generated fore and aftbody blocks arecombined in one single block also, if stern template 2 is chosen.

NAPA-27756 The device specific options for !SEND TO DXF, !SEND TO INT and !SEND TO SVGdid not work properly

NAPA-27760 REF System. The calculation of the parameter BMAX with the command CALCBMAX was incorrect in the release 2013.2-1

NAPA-27798 MGR*LR_SCM; Folder "Arrangement particulars" under SOLAS II-1. The openingstable is now correctly populated and the correct opening data is presented.

NAPA-27885 MGR*LR_SCM: Activation of CROSS600 is added when crossflooding time is morethan 600s on calculating the stability of Solas II-1 results.

NAPA-27904 MGR*MARPOL and MGR*NK: For Regulation 12A outflow calculations Yb and Hwvalues are now included in the result table even if OBMIN will be =0 due to notbound by shell.

NAPA-27921 The latest changes in INTERFACE_TO_RULES manager for Poseidon link will workwith Poseidon version 13.0.5 or later.

NAPA-27945 CR_I: criterion type SURF2 changed so that required value is zero if there is noreal solution for Melnikov's function (very high and steep waves)

NAPA-27950 GS: Void calculation improved in case when coaming height was matching withdeck height and hatch side girder height was below 15 cm. Also plotting of voidsimproved in case when coaming height was matching with deck height.

NAPA-27984 HYD; An error in the calculation of the quantities WSA and AREA for objectsdefined with the command COMB has been corrected. The error occured only in2013.2-1.

NAPA-27990 LD: new option D in DRW BRE for using dashed line with any color in drawingbreaches.

NAPA-28000 MGR*LAUNCHING: Center of point force (XQ) was wrongly calculated. Reasonwas that trim correction and CG of ship were not used correctly. This fix has alsosmall effect on the QA and QF in the results.


45 (46)


NAPA-28081 LD. quantity XRELBMMX was not supported by service function LD.SQNT althoughit was mentioned in the explanation text.

NAPA-28097 MN.versions() service function return value when opening database that lacksproject description corrected.

NAPA-28123 MGR*NK: Unnecessary error removed that came from a missing profile curvefrom CR_D arguments when running SFC definitions. This only happened in raresituations where the model still had a link to a deleted profile curve but theerror could be confusing for the user.

NAPA-28125 Changed the order of fonts used to: Tahoma,Swiss,Helvetica,sans-serif,Verdana

NAPA-28161 Geometry Editor: when opening the room, the crosshairs are to be moved to thecenter of gravity of the room. Due to an error, the decimals of the coordinatevalue were truncated and thus leading to an incorrect coordinate.

NAPA-28221 MGR*LR_SCM: IS2008 model test heeling moment now applied for LR.WINDHEEL1and LR.WINDHEEL2 criteria

NAPA-28241 MGR*NK: Heading part of the S-value tables centered and font size adjusted.

NAPA-28278 In preview release 2013.2 the tolerance for the end condition of a for loop hadbeen removed in order to increase the accuracy of for-loops. This caused issueswith the last iteration of the loop not being executed in some cases. Now thereis a very small tolerance that is relative to the size of the loop increment that isused for the comparison of the end condition.

NAPA-28309 LD GUI: "Print operations" -button in the Balancing tool of the loading conditionswindow fixed. The same tool is available in the ER-window and in the LoadingComputer.

NAPA-28315 DA: Function da.assign corrected to match with the explanation text. Earlier ithas been possible that the result has been an array instead of a variable.

NAPA-28317 The LIST .PROFILE macro in CR was broken and did not produce any results

NAPA-28328 MGR*SHM-Manoeuvring: Visibility diagram included unnecessary characters "A"and "B" with large font. This error has now been fixed and those characters arenot displayed anymore.

NAPA-28333 MGR*SHS-SEAKEEPING: If the user doesn't have license feature for the SOURtask, then for some of the Manager items there were undefined variable errors.These errors have been fixed now.

NAPA-28369 MGR*NK_STRENGTH_BOOKLET: Heading of the "Envelope Curve of BendingMoment" adjusted to the same page with the diagram when printing from thefolder level. Earlier it was possible that the heading was in the previous page.

NAPA-28372 LD: Calculation of shear force correction in damage case improved in case whenSFC is defined by using a macro and damaged hold is loaded with liquid.

NAPA-28403 MGR*NK: Page break logic in the stability booklet report improved.

NAPA-28420 MGR*NK: Page break logic in the loading manual report improved.

NAPA-28661 MGR*OSS: Listing of maximum VCG in the Calculate Results folder under DamageStability Calculations for several damage groups sometimes mixed the maxvcgvalues up in the lists for these cases.

NAPA-28665 LD/LGDEF: definition of moment of inertia in lightweight (command I) did notwork in releases 2013.2 and 2013.3.


46 (46)


NAPA-28695 Manuals search engine does not work with latest java updates. Usemanualsupdater.exe utility from NapaNet to update manuals for any old Napaversions.

NAPA-28710 LD/LGDEF: Lloyds distribution, in 64bit program Cb=0.85 caused unreasobalevalue error although this is the maximum allowed value. Worked properly with32bit program.

NAPA-28775 NK Manager, Grain stability. The summary table of grain heeling moments is nowalways sorted according to the LCG of the holds

NAPA-28791 NK Manager, Grain stability. The holds are now sorted according to LCG in theGrain Criteria (Form B) report

NAPA-28864 [NK Manager]: Incorrect judgment about weather criteria when Form3 isselected in Select the Form for Representing Loading Cases are corrected.

NAPA-28955 MGR*NK: Frame distance table modified in order to avoid overlapping texts incase of complicated frame space definition.

NAPA-28958 Startup time of Hull Surface Editor in installations with slow databases (e.g.over wide area network) improved.

NAPA-28968 FEM Manager: Corrosion Reduction Parameter added for stiffeners as shellelements.

NAPA-29070 DA: Possible noice in the waterline section generated in the probabilisticcalculation is now being filtered out. This could happen in extremely rare casesbut result in e.g. incorrectly measured b values.

NAPA-29124 CR: Damage stability criterion definitions with different requirements for phaseEQ in intermediate stages and the last (final) EQ was broken. Criteria definedwith Releases before 2013.1 were however not affected.

NAPA-29202 OSS: The damage calculation option for twisting freely was not always appliedcorrectly in all result macros and errors also ocurred when running result macrosfor this option.

NAPA-29207 DA: CAT OGR did not work in 2013.2

NAPA-29266 Printing figures and tables from stability booklet and loading manual use correctsize to fit the page without clipping.

NAPA-29278 DOCBOOK printing works with option 'fit to page' to all paper sizes

NAPA-29309 CR: LIS PHM improved so that it lists both sides in case when MODE BOTH isselected in CR arguments. This is relevant for asymmetric grain cargo holds.

Documents

Update Info 2013.3-1