update info 2014 3

8/10/2019 Update Info 2014 3

1/23

Update InfoThis Update Info for the NAPA Release 2014.3 is a summary of the new features and improvements that have been implemented in the NAPAsystem since the previous Release 2014.2.

1. General1.1. Operating system versions

1.1.1. Prerequisites1.2. Support of 32bit NAPA will end soon

1.3. Exceed version1.4. Hardware configurations1.5. Napa Manuals1.6. License file1.7. Location of the files in the NAPA installation1.8. Demo projects1.9. Deprecation of features

1.9.1. Removed features1.9.2. Removal of PLOT task

1.10. Finding data from the databases1.11. Installation instructions

2. Grain Stability (GS)2.1. Error Corrections in Untrimmed Condition

2.1.1. Loading2.1.2. Feeding Holes

3. Arguments in task DAM

4. Napa Steel4.1. Expand and Unshare4.2. Divide4.3. Properties4.4. Box Selection

5. FEM5.1. Fine mesh model details

6. List of Corrected Errors6.1. Error Corrections6.2. Improvements

N A P A M a n u a l s 2 0 1 4 . 3

C o p y r i g h t 1 9 9 2 - 2 0 1 4 N A P A . A l l r i g h t s r e s e r v e d . 1 / 2 3

8/10/2019 Update Info 2014 3

2/23

1. General

1.1. Operating system versions

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

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

The following Windows Server operating system versions are currently supported:

Windows Server 2003 minimum of Service Pack 2Windows 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 4Windows Installer 3.1 or laterInternet Explorer 5.01 or later

1.2. Support of 32bit NAPA will end soon

2014 NAPA releases are the last 32bit versionsAfter 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 version

The officially supported and recommended Exceed version for Release 2014.3 is . NAPA is basically compatible with the olderExceed 14.0versions of Exceed, for example, Exceed 8.0 but there are following known 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, allmemory will eventually be reserved. This is not a serious problem if NAPA + Exceed is shut down a couple of times per week as thereserved memory is then freed.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 ispushed down. This means that, for example, the @-sign will not be appear. The solution is to press the Ctrl button once and the keyboardreturns to the normal state.

Note: sometimes Exceed gives the error message "All xserver displays are in use. Exceed cannot run without a display. Please tryagain at a later time" when run on Windows Vista or Windows 7 and NAPA cannot be started. The easy workaround is to right-click onthe NAPA shortcut, and select "run as administrator".

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

3/23

1.4. Hardware configurations

A high performance workstation is recommended for NAPA use - meaning fast processor, graphics adapter and hard drive (SSD), Gigabitethernet as well as enough memory.

The recommended minimum hardware configuration is:

Processor: Any 64-bitOperating System: 64-bit Windows from the above listMemory: 4 GB

Free Disk Space: 60 GBGraphics Adapter: 256 Mb memory, OpenGL 1.2 compatibleNetwork Adapter is requiredScreen resolution 1600 x 1200 pixels.

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

Processor: Up from Pentium III 1000 MHzMemory: 1 GB for XP/VistaFree Disk Space: 10 GBGraphics Adapter: 64 Mb memory, OpenGL 1.2 compatibleNetwork Adapter is requiredScreen resolution 1024 x 768 pixels. It is recommended to start NAPA with Tinylayout if this resolution is used (the word isTinylayout

entered into the field User Profile in the Login window).

1.5. Napa Manuals

1.6. License file

The NAPA Release 2014.3 requires a new updated license file. New license files will be delivered to the NAPA Contact Persons in good timebefore the old licenses expire.

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

renewed manualsUpdated NAPA user manuals are delivered with this NAPA Release. The manuals for the release 2014.3 are only delivered in pdfformat and the html version of the manuals is not included. The functional key F1 can still be used to launch the manuals and theautomatic navigation to the relevant chapter is implemented in the pdf manuals. The function key F1 works properly with the manualsonly if the Adobe Acrobat reader is used. It is possible to open the manuals with any pdf reader but the support for the navigation to therelevant chapter with the F1 key is only available in the Adobe Acrobat reader.

The solution in the release 2014.3 where only a pdf version of the manuals is delivered is a step in a renewal process of the manualstechnology. In future releases the manuals will be delivered with more advanced technologies. Also the layout of the manuals isaffected by the renewal.

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

4/23

1.7. Location of the files in the NAPA installation

The same way as the previous releases starting from 2012.1, NAPA Release 2014.3 will automatically be installed in a subfolder named 20143under the selected NAPA folder, e.g. C:\Napa\20143\. This subfolder contains all needed files, including NAPA executables, NAPA database andthe manuals.

The file names and corresponding locations are the following:

Name Explanation Location

napa_20143_x86.exe 32bit NAPA executable ...\Napa\20143\bin\

napa_20143_x64.exe 64bit NAPA executable ...\Napa\20143\bin64\

napadb.db NAPA database for 2014.3 Release ...\Napa\20143\database\

index.html NAPA Manuals for 2014.3 Release ...\Napa\20143\manuals\

demo projects Demo projects delivered with the release ...\Napa\pr\demoprojects\

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

1.8. Demo projects

The demo projects are installed into a folder under the Napa\pr -folder. The current selection of demo projects includedemoprojects

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 only if they don't exist in the target directoryto avoid overwriting the old files. If the new projects are needed to be installed, the old ones must be removed manually before the new

installation. With the client-server installation, the demo projects are installed only to the client computer and should be opened with the option'Open Project From File...' in NAPA.

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

5/23

1.9. Deprecation of features

During the long history of NAPA development, a vast amount of features have been implemented into the system. During this time also newfeatures have been developed that are superseding the functionality of old ones. In other cases old features have become obsolete and should beremoved in order to allow more efficient maintenance and development of the system. When this needs arises, old functionality will be set to thestatus of deprecation with the purpose to communicate that usage of the old functionality is to be avoided. It also means that the feature orfunction may be removed in the future.

Please note that deprecation a synonym to removal as such. Removal of a given feature is done based on a separate decision afteris notreceiving feedback from the NAPA User Community.Thus, it is highly recommended that the list below is followed up for each Release and the

discussion is kept open between end users and NAPA also in this matters. Please contact Customer Service ( to)[email protected] your opinion!

Feature Motivation Details on SupersedingFunctionality

Announcedin UpdateInfo

IssueNumber

Status

HLE subtask from theDEF task

HLE contains a collection of testcommands for the Hull Surface Editorwithout the presence of GUI. Theseare not needed anymore.

none 2013.4 NAPA-18719 nocommentsreceived,removalunderconsideration

STAB: LISTargqnt(qnt1,qnt2)

syntax

Obsolete syntax format. Thedocumented standard syntax handles

all needed use cases.

LIST

argqnt

arg1=a1

arg2=a2

2013.4 NAPA-29204 nocomments

received,removalunderconsideration

CL: CNT (CNTT,CNTA and CNTL)commands forentering TAB taskwith a predefinedtable or workarea

These commands were implementedon a pilot level and are a non standardway of entering the TAB task. Thesame functionality is available usingnormal NAPA table commands (TAB,WA etc.).

opening the given tablein the table editor

2013.4 NAPA-29116 nocommentsreceived,removalunderconsideration

DA: LIST REPORT LIST REPORT is a non-documentedand very limited fixed list format fordamage stability. It only displays someselected parameters and is sufficientfor a complete damage stability report.

Similar results as in LISTREPORT can beproduced by utilisingdifferent lists in DA. Thealternative solutions willalso give more flexibilityin presenting andorganizing the values.


DA: CHANGE GM(CGM) command

Originally intended for visualconfirmation of results for a given GM.This functionality however would affecta larger set of calculation results andimpose a great risk in producingincorrect results even for reports.

The functionality isreplaced with PLDDMGM and LISTDMGM. These are LQ /PQ operated and muchsafer to use.


CR: PLOT command This concerns the fixed format PLOTfunctionality in the CR task only. The

PLOT .macros and PLOT commandsin other tasks are not affected by this.The function is already largely coveredby PLD command in CR.

The command isreplaced with the PLD

LIM / DLIM commands inCR_I / CR_D.

2013.4 NAPA-28632 commentsfrom users

underconsideration

SP: Secpro task Current Secpro users are using SPservice functions not the commands inSP task. The SP task is not neededand it is removed to reduce themaintenance load. The SP servicefunctions will work as before.

SecPro servicefunctions. See!COM SP.F


N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

6/23

LAU (launching) task The launching (LAU) task has beenreplaced by the Launching managerwhich doesn't use the LAU task.

Launching Manager 2013.1 NAPA-23420 commentsreceived,revision ofplans underconsideration

LD: PLOT command(except "dot macros")

PLD and DRW commands can do thesame (PLOT .id remains).

2013.1 NAPA-18624 commentsfrom usersunderconsideration

TON (tonnage) task The tonnage (TON) task has beenreplaced by the Tonnage managerwhich doesn't use the TON task.

Tonnage Manager 2013.1 NAPA-18613 nocommentsreceived,removalunderconsideration

LD: IDMODE CCODE IDMODE CCODE is not used and thesetting is not saved.

none 2013.1 NAPA-18623 nocommentsreceived,removalunderconsideration

Body plan window There is a better tool available in the

CONTRACT_DESIGN managerapplication.

Contract Design

Manager

2013.1 NAPA-23762 comments

received,deprecationplanswithdrawn

Pattern editor in theSteel main window

The current quality of the tool is notgood. Instead of updating this tool wewill provide other, more user friendly,tools to create stiffeners, seams andopenings.


LOADand comDUMP

mands in the TOC

Don't support all the new informationincluded in the descriptions, e.g.possible to loose information includedin the drawings. Service functionsDM.DUMP and DM.LOAD should beused instead of the commands. Therecommended way of creating a"cleaned" database is to use theManager applicationMGR*EXPORTDB.

Service Functionsdm.load() anddm.dump()


Implicit summation oflists in calculatorexpressions

Causes confusing result when commais mistakenly used as decimalseparator and interpreted as listsummation. No known intentional usecases. e.g. !CAL 2,3,5

!CAL 2+3+5 2012.1 NAPA-18618 nocommentsreceived,removalunderconsideration

HMODE in the LD This mode has caused large confusionamong users and unexpected changesin results (floating position mainly) due

to the different approach to balance theship. All other alternatives than GZ cancause incorrect results and we intendto make the GZ alternative nowpermanent for all calculations.

2012.1 NAPA-18620 nocommentsreceived,

removalunderconsideration

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

7/23

DM.WHAT(refnr)service function

Asking what a reference number pointsto is consider bad programming style.As the programmer obtained thereference number from somewhere, heshould know what the referencenumber points to. For this reason thefunction is deprecated. It does notmean that we would be removing thisfunction anytime soon, but more asguidance that this function should be

avoided.


DM.RENAME() withoption 'E'

Option 'E' in DM.RENAME has allowedthe creation of multiple descriptionswith the same name which will lead toincorrect functioning of the system.


CaPSL printersupport

These printers are not manufacturedanymore and they could still be usedas a windows printer.


SQL.* servicefunctions These functions have never beenofficially supported. 2012.1 NAPA-18643 nocommentsreceived,removalunderconsideration

INQUIREcommand

in TAB

The recommended way of modifyingtables is opening the table in the tableeditor and changing it there.


Graphical input with":" syntax

Cannot be supported in WindowsPresentation Foundation (WPF). Someof the most common use cases of thecolon-syntax (placement of texts &markers in graphics) can be handledwith interactive annotations.


GR.INPUT,GR.LIVEINPUT,GR.BOXDRAGservice functions

Cannot be supported in WindowsPresentation Foundation (WPF).Zooming and mouse input should behandled with mouse events handlers,instead of calling these functions.


Text terminal support Unix text terminal support will beremoved, including any commands forthese devices, e.g. !block

2012.1 NAPA-20361 nocommentsreceived,removalunder

consideration

!VAR TILDE,C !VAR TILDE,Callows changing the

tilde (~) character that is used forcontinuation character used by TYPEcommand to some other character.


N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

8/23

PLOT task / usingIOF for drawings

The IOF supports only storing integerdata. Drawings contain other types ofdata as well. Storing drawings to IOFand fetching them back from there mayloose some data from the drawings.Saving of drawings to database workswell and preserves all data.As hard disk drives and memory areless of a scarce resource than before,the concept of the IOF as a file that

contains a fixed amount of the last youwrote to it makes less sense.

For these reasons Napa developmentis going towards the direction thatdrawings are stores in the database.Most macros using IOF for storingdrawings can be modified to use !SEN

D TO DB, and those using IOF

only to save and then send to

printer can use the !SEND

command to a printer.

The macroDATA*FIND_DEPRECATED_PLOT inNAPADB can be used to search a

given database and locate macros thatuse this feature.


!VAR & In NAPA macros, the '@' character isnormally used to identify calculatorexpressions and variables, but with'!VAR &' the ampersand charactertakes that role. to be!VAR &

deprecated, as the '@' charactershould be always used.


VARDEF* table as aSource in theManager

The VARDEF* table should always belocated in the VARDEF column in theMGR* table, not in the SOURCEcolumn.

2011.2 NAPA-18580 nocommentsreceived,removalunder

consideration

!SCIcommand Related to the VMS operating systemwhich has not been supported in lastfew years.


Report GUI in theOutput tabs

The reporting functionality is based onan old VARDEF* table format which isnot compatible with the WindowsPresentation Foundation (WPF). Thesame reporting functionality is availablewith report macros (dot macros),Manager applications etc.


DEF: subtask DFN Not supported when TrueType fontsare taken into use in the graphics as apart of the graphics technologyrenewal.


N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

9/23

DR: subtask LDR The same functionality is available, forexample, with the PLOT .LINESDRcommand and in the Contract DesignManager application. A new applicationfor lines drawing creation will bedeveloped and released beforeremoval of the LDR task. -> Beforeremoving this subtask we will providenew and better tools to create linesdrawings. There are already similar

functionality in .LINESDR macro and inthe Contract Design Manager. Wewould like to remove duplicatedfunctionality and replace them with onetools having better user experiencethan the predecessors


Digitizer tablets The need to support this functionality isquestionable due to limited use.


UI.MAKELONGNAMEservice function

DB.MAKELONGNAME has the samefunctionality.

2011.1 NAPA-18509 nocommentsreceived,removal

underconsideration

UI.GETNAMECOMPSservice function

DB.GETNAMECOMPS has the samefunctionality.


OUTcommand in LD

task

This concerns all OUT lists in LDexcept for OUT LOAD. Outputprovided by the OUT command canalready be produced using normal listsin LD.

Functionality in thecommand OUT isavailable using the LISTcommand in a moreflexible way. Replacingfunctionalities can be

seen from the list below:

OUT STR => LISTSTROUT FRS => LISTFRSOUT FLO => LISTFLO / LIST FLPOUT OPE => LISTOPEOUT STAB => LISTST H (table outputoption H makes ahorizontal list likeOUT STAB)OUT HEAD =>TYPE [email protected]()_:@ld.note()


GUI commandsstarting with !! (e.g. !

)!MERGE

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


N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

10/23

OGL service functions Will not work in the WindowsPresentation Foundation (WPF).Macros containing calls to thesefunctions will have to be modified in thefuture.


GCR task GCR task is a very limited subsystemcompared to CR. The functionalitypreviously only available in GCR is

now available in CR as well.

Checking the grainstability criteria shouldbe done in intact criteria

task (CR_I?>) with thecriteria group IGC. TheCHECK command inGCR is also replacedwith LIST GSCH in CR.

2010.2 NAPA-18473

Widget Editor The support for the Motif User Interfaceis ending when Motif is replaced withWPF.


Command iPERFORM

n tables

The command PERFORM is notsupported in Docbook output. Thefunction can be replaced by running a

macro.

2009.1 NAPA-18429 commentsfrom usersunder

consideration

1.9.1. Removed features

The following list shows the features which have been removed:

Feature Motivation RemovedinRelease

GCR sub task under GS Checking the grain stability criteria (group IGC) should be done in intact criteria task (CR_I?>). AllGCR functionality expect the CHECK command has been available in the CR_I task already forseveral years. In the Release 2014.2, the command LIST GSCH under CR_I task was introduced

for replacing the CHECK command from the previous GCR task. It produces an identical resultlist, but uses CR-arguments instead of command specific parameters.

2014.2

Docbook Javaimplementation

In the previous release Docbook printing was ported to .NET which gave significant performanceimprovements. The old implementation in Java was still optionally available through a servicefunction. Now the old java implementation has been removed.

2014.1

Napa database connectivity The code would have had to be ported to .NET, and as far as we know nobody was using thisfunctionality so investing into keeping it available did not make sense.

2014.1

HDC (Hydrostatic checktask)

The task is a relic intended for internal testing purposes and is now obsolete. Service functionshave been developed instead to fill the functionality offered by the HDC task.

2014.1

HYD & STAB task: STOREand FETCH commands

These old, non standard commands in HYD and STAB only contribute to making the programharder to master. Saving and reading back hydrostatic data is no longer needed from performancepoint of view and could even result in incorrect data without up-to-date check functionality.

2014.1

LD: LIST DAM The same functionality with better output is available in DAM task, when the init case refers to theloading condition. This old functionality is believed to be outdated.

2014.1

LD: DHC (damage check)command

The command is related to LIST DAM which was also deprecated. 2014.1

DAM: Instant DAfunctionality

This functionality was never officially released and will now be removed. 2014.1

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

2014.1

DAM: subtask CROSS Replaced by new and better functionality in and in DAM task.LIST EQT LIST DEQP 2014.1

N A P A M a n u a l s 2 0 1 4 . 3

C o p y r i g h t 1 9 9 2 - 2 0 1 4 N A P A . A l l r i g h t s r e s e r v e d . 1 0 / 2 3

8/10/2019 Update Info 2014 3

11/23

DAM: subtask IMO IMO A.265 can be calculated also directly in the DAM task. 2014.1

IF (condition) [LINE] andGOTO [LINE]

Editing macro by adding or removing lines destroys the jumps. 2013.3

Set of GS output macrosand vardefs with the samename (GS-OUTPUT2,GS-OUTPUT3,GS.ALLOWABLEGM and

GS.MINGM)

Macros were using GCR-task which will be deprecated also. Code contained hard coded valueswhich meant that the results were suitable for example only.

2013.2

LIST GCRin LD task Checking the grain stability criteria should be done in intact criteria task (CR_I?>). Use the criteriagroup IGC.

2013.2

CP: old type soundingdevices

Old format means before 1987. Command CNV converses the old format and this will be doneautomatically before the old type is removed from the code.

2013.2

OLISTcommand in the

DAM task (old style list)and related old criteria andold moment definitions inDAM task

Replaced by new lists a long time ago. 2013.2

NPN.TVMESH() servicefunction

TVMESH command in SH task gives better support for volume mesh generation. Can be run withSHA.COMMAND service function also.

2013.1

SDI task (subdivisionindices / USSR)

Unused code 2012.2

Foreign languageexplanation texts and errormessages.

There have been some error message explanations stored in languages other than English.These have not been recently maintained, and the coverage of the translations has been poor.Error messages and explanation texts only in English will be supported.

2012.2

Explanation texts ofcommands in project orsystem database

In some SH subsystems the user has been able to write his own explanation texts for commands.The format for explanation texts in Napa has changed and the support for the old explanation textformat will be removed.

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 Vardeftables with the prefix INT*and TSB*

The INT and TSB Manager applications have been removed in Release 2010.1 2012.1

Outfit Window 2012.1

Drawing Window The Drawing window functionalities have been replaced by renewed Drawing manager 2012.1

Immediate view update,

command and!VIEW ISUservice function GR.ISU.

2012.1

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

2012.1

Commands ,!WINDOW !VI

and service functionEW

GR.CREATEWINDOW

2012.1

Command .!WINDOW R 2012.1

N A P A M a n u a l s 2 0 1 4 . 3

https://docs.napa.fi/pages/viewpage.action?pageId=13599990https://docs.napa.fi/pages/viewpage.action?pageId=13599990

8/10/2019 Update Info 2014 3

12/23

1.9.2. Removal of PLOT task

Due to the deprecation of the PLOT task it is possible that the customers need to update their own macros which have been using the PLOT taskand/or commands related to it. In addition to the command (to enter the PLOT task, usually done from the main task or from the SRV task),PLOT

the deprecated commands are:

!GR F

GR.SIZE('P')

GR.SCALE('A')!GR F

!GR +F

!GR F-TEMP

!GR F-RESTORE

!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 database can be scanned to find thedeprecated commands. For example, the SYSDB can be scanned with the following command:

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 +F

Possible use of PLOT task in DATA*CREATE_NAPAINTRO line 502: PLO;

@PRI; 5; 1; SCA 1/1000; TU; OK ; !END

Possible use of IOF for drawings in DATA*DSN20533 line 3: !gr +f

Possible use of PLOT task in DATA*DSN20533 line 8: plo

Possible use of IOF for drawings in DATA*DSN_13309 line 188: !GR +F

Possible 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 by or and to not enter the PLOT task at all.!SEND TO IOF !SEND TO WPR !SEND TO DB

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

1.10. Finding data from the databases

The general selection command offers a lot of useful possibilities for finding data from the databases (e.g. from the project!SEL (!EXP !SEL)

or the system databases). The following example searches HMODE text from all the DATA* macros in the system database (unit 2). Macroshaving HMODE text are stored in the array called LIST which content can be seen with the command .!VAR LIST LIST

TASK?>!SEL 2 NAME>DATA* LOC!VAR LIST LIST

1.11. Installation instructions

The installation instructions for NAPA and Exceed are gathered into one PDF document. Please find the document Installation_instructions.pdfon the NAPA Release installation media.

The installation Instructions can also be found in the last chapter of the .NAPA Manuals

N A P A M a n u a l s 2 0 1 4 . 3

https://docs.napa.fi/display/NFDM143/NAPA+Installation+Instructionshttps://docs.napa.fi/display/NFDM143/NAPA+Installation+Instructions

8/10/2019 Update Info 2014 3

13/23

2. Grain Stability (GS)

2.1. Error Corrections in Untrimmed Condition

These corrections might have been valid in cases when the cargo hold is located only at one side of the center line (SB or PS)

2.1.1. Loading

It has been possible that an error in the generation of the grain load shape occurred. Please see the figure below.

After the correction, the grain load shape looks as follows.

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

14/23

2.1.2. Feeding Holes

In case when the cargo hold locates in the negative side of the Y-axis, the error "Feeding hole outside hatch (E23012)" might have occurredwhen trying to use the feeding holes. This error caused incorrect heeling moment and volume results also.

3. Arguments in task DAM

There is a small change related to how the arguments are stored in task DAM. In case the argument AAS (Automatic Argument Storing) is OFF(not given) none of the arguments should be stored automatically. In earlier releases the arguments RCR, SWH and TRLIM were thoughautomatically stored when exiting from DAM and restored when entering DAM the next time. In the release 2014.3 none of the arguments arestored automatically unless AAS is set to ON.

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

15/23

4. Napa Steel

4.1. Expand and Unshare

Expand and Unshare are available with Right click menu option for selected Stiffeners, Openings and Seams.

Unshare: Unshares the STDEF/SEAMDEF definition table which is been shared by multiple objects.

Expand: Expands the stiffeners, opening and seams sharing same Id in STDEF/SEAMDEF definition table. Expanded Ids are referred with suffix

of ##(for original group definition) and #(for expanded set).

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

16/23

4.2. Divide

A new functionality for dividing the stiffeners is now available. The function divides the stiffeners at the given locations and adds a new definitionrows to STDEF table. After selecting the stiffener,Divide dialog can be opened from Right click menu named 'Divide'. Locations can be pickedinteractively from the graphics.

4.3. Properties

A new option is available in right click menu to change the properties of stiffeners, plates and openings. After selecting stiffeners,plates oropenings, the properties dialog can be opened from right click menu named "Properties".

For stiffeners, the available properties are Profile and Material.

For plates, the available properties are Thickness and Material.

For Openings, the available property is Opening.

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

17/23

4.4. Box Selection

Several objects of same type can be selected using box selection. Box selection can be activated by clicking button. Clicking the button,opens the object filter dialog(currently object filter supports only stiffeners, plates and openings). On selecting the desired object type from objectfilter, a box should be drawn to select and highlight all objects within the box.Click "Activate" button in the dialog to activate the box selectionagain.

Box selection is quite handy to select several objects and change available properties at one time using right click menu "Properties"

Note :For changing the 'Properties' using Right click after doing a 'Box selection' , it has to be made sure that either Stiffener/

Opening/Plate is selected in the Component field as shown in the figure(Image shows example of a stiffener(S) selected)

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

18/23

5. FEM

5.1. Fine mesh model details

All necessary structural details can be included into the fine mesh models. Previously, the stiffener holes; the corner notches; the folded flanges ofbrackets; and the bracket stiffeners has not been available for the fine mesh models.

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

19/23

N A P A M a n u a l s 2 0 1 4 . 3


8/10/2019 Update Info 2014 3

20/23

6. List of Corrected Errors

All the following error corrections and improvement suggestions have been included in the new release. The key number refers to the actionnumber maintained by the Customer Service at NAPA.

6.1. Error Corrections

Key Component/s Update Info

NAPA-34375 AI Fixed bug in AD.VARDEF(macro,vardefs) that has causes AD.VARDEF invalid behavior for some macros.

NAPA-33598 CL CL: LQ CLC improved so that formulas can be used although the referring quantities are in brackets (not visible).

NAPA-33608 CL CL: improved error handling for definition of owner numbering: bay, row and tier numbers are limited to two digits,and invalid definition is no more accepted.

NAPA-31609 CP CP: LIST .DESCOMP improved so that the compartment mentioned in the header matches with the content of thecurrent page when printing with WPR.

NAPA-33812 CP CP: The command TYPE could cause syntax errors due to incorrect command interpretation

NAPA-32731 CR Plot macro 'PLOTCR.GMLIM.I.TR' improved to take the trim sign into account.

NAPA-32598 CR CR_I: Criterion type SURF2 for second generation intact stability has been updated to use argument VS (servicespeed) instead of the full speed (VF)

NAPA-33181 CR CR_D: criterion A.RS.SE range limit changed to vanishing stability according to ABS MOBILE OFFSHOREDRILLING UNITS 2014 Part 3 Chapter 3 Section 2, 3.3.3

NAPA-33599 CR CR_D; the criteria RANGE.M, MAXGZ.M and MINAREA.M have been changed to use flooding angle ofunprotected openings (FAUN) instead of general flooding angle FA, for the calculation of range.

NAPA-32986 CR, DA CR_D; LIST DLIM. If several trims were used in the arguments the MINGM and MAXKG values were incorrect inthe output. The results from the last trim were shown for all trims. The error is affecting the versions 2013.4 and2014.1

NAPA-31942 DA DA: PLOT .DAMDEF macro updated to include more options. Please check the options with PLO .DAMDEF ? inDA task.

NAPA-33033 DA DRW DAM command's option ASTA did not take into account the A class stages properly. Now, with the optionASTA only the newly damaged compartment(s) in the given stage are drawn, without the previously floodedcompartments.

NAPA-33457 DA DA & LD: improvements in balancing algorithms for offshore structure stability (option TWDIR), some results maychange due to increased accuracy in balancing.

NAPA-33436 DA DA: various improvements in the algorithms for OSS calculation options TWDIR and HDIR to ensure that theequilibrium floating position is found. These changes may cause small difference in the results when compared toolder releases.

NAPA-33539 DA DA: Plot macro PLOTDAM.DAMCHECK improved in order to avoid an error caused by obsolete MENU option fromthe DRW ALL command. Also a check for existence of the damage table added in order to avoid unnecessaryerror when damage group is used.

NAPA-31221 GM The name of the curve that is created with !GM GET curve/version/project has now the proper suffix *version.

NAPA-33667 GM Offset surfaces generated from a preparable NURBS surface of NAPA failed if there were more than 1530 patchesin the surface.

NAPA-31780 GM The Geometry Editor can now treat rooms that are defined with the ROOM command and has got a name with

more than 60 characters.

NAPA-33603 GM Explanation text of service function GM.TABTOCUR fixed.

NAPA-33224 GS, MGR*NK NK Manager: LC editing tool -> Compartments having GRAIN purpose that are shown in Compartments tab andcompartments other than GRAIN are shown in Grain tab when user try to add loading condition from ADDCONDITION tab. This problem is resolved by adding the tab change event to the tab.

NAPA-33357 GS, MGR*NK NK: Grain Criteria (Form B) -> The permissible heeling moment is not calculated when feeding distances inX-direction ill defined on main deck. A Popup with the relevant error message is now displayed in this case.

NAPA-33403 LD Calculation of transversal moments has been fixed when the loading condition includes mass loads that areattached to crane base defined by CRA command in LD task. Now the calculation of transversal moments followthe same logic as the calculation of longitudinal moments, that is, the moments are modeled by four point masseslocated inside the crane base.

N A P A M a n u a l s 2 0 1 4 . 3

https://jira.napa.fi/browse/NAPA-34375https://jira.napa.fi/browse/NAPA-33598https://jira.napa.fi/browse/NAPA-33608https://jira.napa.fi/browse/NAPA-31609https://jira.napa.fi/browse/NAPA-33812https://jira.napa.fi/browse/NAPA-32731https://jira.napa.fi/browse/NAPA-32598https://jira.napa.fi/browse/NAPA-33181https://jira.napa.fi/browse/NAPA-33599https://jira.napa.fi/browse/NAPA-32986https://jira.napa.fi/browse/NAPA-31942https://jira.napa.fi/browse/NAPA-33033https://jira.napa.fi/browse/NAPA-33457https://jira.napa.fi/browse/NAPA-33436https://jira.napa.fi/browse/NAPA-33539https://jira.napa.fi/browse/NAPA-31221https://jira.napa.fi/browse/NAPA-33667https://jira.napa.fi/browse/NAPA-31780https://jira.napa.fi/browse/NAPA-33603https://jira.napa.fi/browse/NAPA-33224https://jira.napa.fi/browse/NAPA-33357https://jira.napa.fi/browse/NAPA-33403https://jira.napa.fi/browse/NAPA-33403https://jira.napa.fi/browse/NAPA-33357https://jira.napa.fi/browse/NAPA-33224https://jira.napa.fi/browse/NAPA-33603https://jira.napa.fi/browse/NAPA-31780https://jira.napa.fi/browse/NAPA-33667https://jira.napa.fi/browse/NAPA-31221https://jira.napa.fi/browse/NAPA-33539https://jira.napa.fi/browse/NAPA-33436https://jira.napa.fi/browse/NAPA-33457https://jira.napa.fi/browse/NAPA-33033https://jira.napa.fi/browse/NAPA-31942https://jira.napa.fi/browse/NAPA-32986https://jira.napa.fi/browse/NAPA-33599https://jira.napa.fi/browse/NAPA-33181https://jira.napa.fi/browse/NAPA-32598https://jira.napa.fi/browse/NAPA-32731https://jira.napa.fi/browse/NAPA-33812https://jira.napa.fi/browse/NAPA-31609https://jira.napa.fi/browse/NAPA-33608https://jira.napa.fi/browse/NAPA-33598https://jira.napa.fi/browse/NAPA-34375

8/10/2019 Update Info 2014 3

21/23

NAPA-33393 LD LD: handling of given freesurface moment (FSM) for mass loads has been corrected so that the GZ curve isproperly calculated also with free t rim calculation mode.

NAPA-31535 LD LD: LIST .LCREP improved so that the loading condition mentioned in the header matches with the content of thecurrent page when printing with WPR

NAPA-31148 Manuals, technology Some automatically generated command explanations in the manuals were duplicated. The problem has beenfixed and the output should now be proper.

NAPA-32741 MGR*CFD MGR*CFD/Panelisation: Due to an existing system limit of handl ing panel block definit ions, the maximum numberof accepted characters of an NPN Panel Directory created inside the CFD-Manager was reduced to 11 (and thus15 characters incl the automatic prefix 'NPN.').

NAPA-32749 MGR*FFD MGR*FFD: An unnecessary result surface preparation was removed from the "Apply Transformation" tree i tem inthe FFD-Manager.

NAPA-33168 MGR*FREEBOARD MGR*FREEBOARD: Calculation of the Winter Timber Freeboard modified to match with the MSC.143(77) ChapterIV.

NAPA-28486 MGR*GENERAL_OPT General Optimisation: Algorithm 'Systematic' did not work properly due to an error in internal table control. InMGR*GENERAL_OPT there was no problem.

NAPA-30469 MGR*HMD General Optimisation: Some of the output functional ity does not work in case of using variable names includingmathematical symbols (like + - * /). Therefore using such variable names is now blocked. Same applies forobjectives and constraints.

NAPA-32905 MGR*LIGHTWEIGHT LD.TABLETOLIG function did not work when the currently open lightweight was updated. This bug caused errormessage on LGDEF task not being open. This worked in releases older than 2013.2.

NAPA-32902 MGR*LR_SCM MGR*LR_SCM: Purposes offered in the MARPOL oil outflow folder were taken from the PAR*PRO table which insome cases can result in too few or incorrect purposes offered. Now the purposes are populated from thearrangement table

NAPA-32682 MGR*MARPOL Adjusted tolerance for CDB calculation in Marpol Manager to avoid incorrect CDB values in some cases.

NAPA-33029 MGR*MARPOL MGR*MARPOL: Regulation 12A - Oil fuel tank protection -> Clearance of Fuel oi l tanks item; The HREQ andWREQ values are set to 0 for small tanks (capacity General weather cri teria -> Flooding angle corrected when there is a change in openningarrangement table.

NAPA-32662 MGR*NK MGR*NK: The deterministic damage stability NK Rule 13 is now available also for tanker ship types.

NAPA-32759 MGR*OSS MGR*OSS: The total wind heel ing moment for azimuth angles in the Wind Moment Listing item has been

corrected. Previously it had a small difference compared to the moment reported in the GZ list.

NAPA-32818 MGR*OSS MGR*OSS: Item "Wind Moment Listing" in the part Damage Stabi li ty. The total wind heeling moment in the outputwas calculated incorrectly becausethe sum of the wind force impacting on the wind model parts were not considered correctly.

NAPA-32623 MGR*OSS MGR*OSS; The heel and trim is now considered correctly in the calculation of the thruster force and its arm whencalculating the Total Wind Heeling Moment in the item "Wind Moment Listing"

NAPA-32624 MGR*OSS MGR*OSS, Item; Wind Moment List ing: Calculation formula and quantity name of ZCP unif ied wi th the quantityZW.

NAPA-33520 MGR*PROB MGR*PROB: If GM values are not given in definition table of the initial condition, it will be calculated based on theKG values for MIN GM Report. Now formulas are added to the KG and GM values columns in Initial conditiondefinition table to calculate the values accordingly.

NAPA-33725 MGR*PROB PROB Manager, water on deck damages: The number of zone damages generated is increased by one to al low

for a damage extending over both end bulkheads for the shortest zone. Previously it only broke one of them.

NAPA-33198 MGR*PROB MGR*PROB: Error message is thrown when Progressive option together with ACLASS=STA is given for damagegeneration. This is applied for all the regulations(Regulation 8.1, Regulation 2.-3, Regulation 9) under PROBmanager.

NAPA-33482 MGR*PROB PROB Manager: Damages generated for Regulation 9 that include a-class combinations populated in differentdamages now have the ACLASS stage renamed to ACLASS#. This is to avoid opening up compartmentconnections for the rooms in the ACLASS stage during the damage definition, and this way avoid the differenta-class combination damages to be treated as duplicates when they damage (indirectly) the same set of rooms.

NAPA-33483 MGR*PROB MGR*PROB: The A class connections were not generated properly as STAGES in Regulation 9. The damageswere corrupted.

NAPA-26105 MGR*PROB MGR*PROB: Several escape routes can be given from same compartment.

N A P A M a n u a l s 2 0 1 4 . 3

https://jira.napa.fi/browse/NAPA-33393https://jira.napa.fi/browse/NAPA-31535https://jira.napa.fi/browse/NAPA-31148https://jira.napa.fi/browse/NAPA-32741https://jira.napa.fi/browse/NAPA-32749https://jira.napa.fi/browse/NAPA-33168https://jira.napa.fi/browse/NAPA-28486https://jira.napa.fi/browse/NAPA-30469https://jira.napa.fi/browse/NAPA-32905https://jira.napa.fi/browse/NAPA-32902https://jira.napa.fi/browse/NAPA-32682https://jira.napa.fi/browse/NAPA-33029https://jira.napa.fi/browse/NAPA-33366https://jira.napa.fi/browse/NAPA-33356https://jira.napa.fi/browse/NAPA-32662https://jira.napa.fi/browse/NAPA-32759https://jira.napa.fi/browse/NAPA-32818https://jira.napa.fi/browse/NAPA-32623https://jira.napa.fi/browse/NAPA-32624https://jira.napa.fi/browse/NAPA-33520https://jira.napa.fi/browse/NAPA-33725https://jira.napa.fi/browse/NAPA-33198https://jira.napa.fi/browse/NAPA-33482https://jira.napa.fi/browse/NAPA-33483https://jira.napa.fi/browse/NAPA-26105https://jira.napa.fi/browse/NAPA-26105https://jira.napa.fi/browse/NAPA-33483https://jira.napa.fi/browse/NAPA-33482https://jira.napa.fi/browse/NAPA-33198https://jira.napa.fi/browse/NAPA-33725https://jira.napa.fi/browse/NAPA-33520https://jira.napa.fi/browse/NAPA-32624https://jira.napa.fi/browse/NAPA-32623https://jira.napa.fi/browse/NAPA-32818https://jira.napa.fi/browse/NAPA-32759https://jira.napa.fi/browse/NAPA-32662https://jira.napa.fi/browse/NAPA-33356https://jira.napa.fi/browse/NAPA-33366https://jira.napa.fi/browse/NAPA-33029https://jira.napa.fi/browse/NAPA-32682https://jira.napa.fi/browse/NAPA-32902https://jira.napa.fi/browse/NAPA-32905https://jira.napa.fi/browse/NAPA-30469https://jira.napa.fi/browse/NAPA-28486https://jira.napa.fi/browse/NAPA-33168https://jira.napa.fi/browse/NAPA-32749https://jira.napa.fi/browse/NAPA-32741https://jira.napa.fi/browse/NAPA-31148https://jira.napa.fi/browse/NAPA-31535https://jira.napa.fi/browse/NAPA-33393

8/10/2019 Update Info 2014 3

22/23

NAPA-33464 MGR*PROB MGR*PROB: Drawing memory usage reduced in the i tem "Draw & Edi t" in the Manager in order to improve theperformance

NAPA-33006 MGR*PROB MGR*PROB: Regulation 8.2 damages now also disregards the stage 1 s calculation i f cross occur and the 60second stage is selected to be included in the calculation.

NAPA-33076 MGR*STABILITY_BOOKLET MGR*STABILITY_BOOKLET: Item "Longitudinal Strength" under the "Loading Conditions" -folder improved.Earlier it was possible that the layout components might have been overlapping, for example the diagram on top ofthe table in the middle etc. The sizes of the components are now fixed. Also the formatting of the quantities used inthe item are now following the quantity standard. The inputfield "Size of the Diagram frame (W * H [m]" from the"Str. Diagram Control" -tab of "Loading Conditions" -folder is removed, because that input was not used in anyitem.

NAPA-32979 MGR*STABILITY_BOOKLET MGR*STABILITY_BOOKLET: Criteria group 2008IS-A2.2 taken into use instead of the group A749-3.1 as thedefault selection of the "Relevant intact stability criteria group" in the top level and in the item "Stability Criteria"under the "Loading Condition" -folder. Item renamed to "Stability Criteria (2008 IS Code) for indicating that thecriteria group is fixed in that item. The top level selection for the relevant intact stability criteria group is valid in theitem "Stability Criteria List".

NAPA-33188 MGR*STABILITY_BOOKLET MGR*STABILITY_BOOKLET: Item "Loads List" under the "Loading Conditions" -folder improved so that theloading condition listed will match with the manager tree also when the loading condition is not active beforehand.

NAPA-33337 MGR*V-LINES MGR*V-LINES: Error "no result obtained error" avoided and dashed l ine shown in case when no results obtained.

NAPA-33375 MGR*V-LINES MGR*V-LINES: Dashed l ines shown in case when no calculation results obtained in the "Final Trim Lines" -tableitems. This fix makes it is possible to complete the drawing in the plot items under the same folder.

NAPA-33236 SHS In SHx tasks the series syntax like (VSinit, VSfinal, VSstep) works now correct ly also when the values are given indecreasing order.

For example the command VS KNOTS (20 14 -2) will result in ship speeds equal to 20, 18, 16, and 14 knots.If the step in this case were given as positive, the error message 30022 would be shown indicating that the syntaxis wrong.

NAPA-32389 ST ST: problem with end-cut trimming fixed.

NAPA-33612 TP Napa table to excel link correctly handles FR, WEB, LONG, VERT quantities.

57 issues

6.2. Improvements

Key Component/s Update Info

NAPA-32684 CR CR_I: Plot macros PLOTCR.IMO and PLOTCR.IMO_2008IS improved. The macros are for plotting a single calculeither loading condition from LD (LOADS argument) or floating position based on the T, TR or DISP -arguments. Tchecking whether there is a single calculation case active or not, was not working properly.

NAPA-33132 DA DA: New function for checking permeability definition. See !exp da.permcheck

NAPA-32641 DA DA: Calculation accuracy has been improved when calculating init/dam case in DA task and option TWDIR is in u

NAPA-32419 LD LD GUI: Side information added to the criteria list under criteria tab.

NAPA-33151 MGR*CFD noudi

NAPA-32758 MGR*DREDGER CR: Dredger Calculation manuals are updated to support the regulation DR68.

NAPA-32687 MGR*INTERFACE_TO_RULES More information can be found here :https://docs.napa.fi/pages/viewpage.action?pageId=6005921#InterfacetoRules(INTERFACE_TO_RULES)-BVRU

NAPA-33136 MGR*INTERFACE_TO_RULES Transverse bulkhead item has been removed from mgr*interface_to_rules manager. Selection of Transverse bulkselection can be done in Transverse members folder.

NAPA-33182 MGR*LAUNCHING MGR*LAUNCHING: Units added for distance traveled from starting point in Launching Output.

NAPA-33391 MGR*NK NK Manager: Solas 2009 -> Setup selection supported in subdivision item.

NAPA-33128 MGR*PROB MGR*PROB: The logic behind the "Check the abnormalit ies" button of the item "Def init ions - Permeabilit ies" improcommon syntax validation is executed before executing the PROB-manager specific syntax validation, which is al

NAPA-33294 MGR*PROB PROB Manager, v-l ines item: Internal structure of the macro handl ing the experimental HEEL and HEEL+RANGEcalculation revised for better performance.

NAPA-24591 MGR*PROB MGR*NK: Stage texts can be given more than 3 in damage generation item.

N A P A M a n u a l s 2 0 1 4 . 3

https://jira.napa.fi/browse/NAPA-33464https://jira.napa.fi/browse/NAPA-33006https://jira.napa.fi/browse/NAPA-33076https://jira.napa.fi/browse/NAPA-32979https://jira.napa.fi/browse/NAPA-33188https://jira.napa.fi/browse/NAPA-33337https://jira.napa.fi/browse/NAPA-33375https://jira.napa.fi/browse/NAPA-33236https://jira.napa.fi/browse/NAPA-32389https://jira.napa.fi/browse/NAPA-33612https://jira.napa.fi/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+%22NAPA%22+and+%28+fixVersion+%3D+%222014.Sep%22+OR+fixVersion+%3D+%222014.3-1%22+%29+and+issuetype+%3Dbug+and+issuetype+not+in+subTaskIssueTypes%28%29+and+resolution+%3D+%27fixed%27+and+%28status+%3D+closed+or+status+in+%28Verified%2C+Integrated%29+and+%28%27Verified+In%27+in+%28%222014.Sep%22%29+OR+%27Verified+In%27+in+%28%222014.3-1%22%29%29%29+and+%27Update+info%27+%21%7E+%27no+udi%27+and+component+not+in+%28componentMatches%28%27LC.*%27%29%2C+%27MGR*NAPA_LC%27%2C+%27Voyage+Optimization%27%29+ORDER+BY+component%2Csummary+++https://jira.napa.fi/browse/NAPA-32684https://jira.napa.fi/browse/NAPA-33132https://jira.napa.fi/browse/NAPA-32641https://jira.napa.fi/browse/NAPA-32419https://jira.napa.fi/browse/NAPA-33151https://jira.napa.fi/browse/NAPA-32758https://jira.napa.fi/browse/NAPA-32687https://docs.napa.fi/pages/viewpage.action?pageId=6005921#InterfacetoRules(INTERFACE_TO_RULES)-BVRULESBV_RULEShttps://jira.napa.fi/browse/NAPA-33136https://jira.napa.fi/browse/NAPA-33182https://jira.napa.fi/browse/NAPA-33391https://jira.napa.fi/browse/NAPA-33128https://jira.napa.fi/browse/NAPA-33294https://jira.napa.fi/browse/NAPA-24591https://jira.napa.fi/browse/NAPA-24591https://jira.napa.fi/browse/NAPA-33294https://jira.napa.fi/browse/NAPA-33128https://jira.napa.fi/browse/NAPA-33391https://jira.napa.fi/browse/NAPA-33182https://jira.napa.fi/browse/NAPA-33136https://docs.napa.fi/pages/viewpage.action?pageId=6005921#InterfacetoRules(INTERFACE_TO_RULES)-BVRULESBV_RULEShttps://jira.napa.fi/browse/NAPA-32687https://jira.napa.fi/browse/NAPA-32758https://jira.napa.fi/browse/NAPA-33151https://jira.napa.fi/browse/NAPA-32419https://jira.napa.fi/browse/NAPA-32641https://jira.napa.fi/browse/NAPA-33132https://jira.napa.fi/browse/NAPA-32684https://jira.napa.fi/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+%22NAPA%22+and+%28+fixVersion+%3D+%222014.Sep%22+OR+fixVersion+%3D+%222014.3-1%22+%29+and+issuetype+%3Dbug+and+issuetype+not+in+subTaskIssueTypes%28%29+and+resolution+%3D+%27fixed%27+and+%28status+%3D+closed+or+status+in+%28Verified%2C+Integrated%29+and+%28%27Verified+In%27+in+%28%222014.Sep%22%29+OR+%27Verified+In%27+in+%28%222014.3-1%22%29%29%29+and+%27Update+info%27+%21%7E+%27no+udi%27+and+component+not+in+%28componentMatches%28%27LC.*%27%29%2C+%27MGR*NAPA_LC%27%2C+%27Voyage+Optimization%27%29+ORDER+BY+component%2Csummary+++https://jira.napa.fi/browse/NAPA-33612https://jira.napa.fi/browse/NAPA-32389https://jira.napa.fi/browse/NAPA-33236https://jira.napa.fi/browse/NAPA-33375https://jira.napa.fi/browse/NAPA-33337https://jira.napa.fi/browse/NAPA-33188https://jira.napa.fi/browse/NAPA-32979https://jira.napa.fi/browse/NAPA-33076https://jira.napa.fi/browse/NAPA-33006https://jira.napa.fi/browse/NAPA-33464

8/10/2019 Update Info 2014 3

23/23

NAPA-33359 SH noudi

NAPA-32970 Steel Main Window Expand and Unshare are available wi th Right c lick menu option.Unshare: Unshares the STDEF definition table for selected Stiffeners, Openings and Seams.Expand: Expands the Stiffeners, Openings and Seams sharing same ID in STDEF definition table

NAPA-33456 Steel Main Window In NAPA Steel Main Window, the "Apply Limits" button has been removed. In order to switch off the limits, either th- - - -" from the droplist can be made, or the limit field can be made blank.

NAPA-33969 Steel Main Window Line tool is added under drafting tools. Using Line tool user can mention the 2D point co-ordinates and plot a strai

17 issues

N A P A M a n u a l s 2 0 1 4 . 3
https://jira.napa.fi/browse/NAPA-33359https://jira.napa.fi/browse/NAPA-32970https://jira.napa.fi/browse/NAPA-33456https://jira.napa.fi/browse/NAPA-33969https://jira.napa.fi/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+%22NAPA%22+and+%28+fixVersion+%3D+%222014.Sep%22+OR+fixVersion+%3D+%222014.3-1%22+%29+and+issuetype+%3D+improvement+and+issuetype+not+in+subTaskIssueTypes%28%29+and+resolution+%3D+%27fixed%27+and+%28status+%3D+closed+or+status+in+%28Verified%2C+Integrated%29+and+%28%27Verified+In%27+in+%28%222014.Sep%22%29+OR+%27Verified+In%27+in+%28%222014.3-1%22%29%29%29+and+%27Update+info%27+%21%7E+%27no+udi%27+and+component+not+in+%28componentMatches%28%27LC.*%27%29%2C+%27MGR*NAPA_LC%27%2C+%27Voyage+Optimization%27%29+ORDER+BY+component%2Csummary++++++++++++++https://jira.napa.fi/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+%22NAPA%22+and+%28+fixVersion+%3D+%222014.Sep%22+OR+fixVersion+%3D+%222014.3-1%22+%29+and+issuetype+%3D+improvement+and+issuetype+not+in+subTaskIssueTypes%28%29+and+resolution+%3D+%27fixed%27+and+%28status+%3D+closed+or+status+in+%28Verified%2C+Integrated%29+and+%28%27Verified+In%27+in+%28%222014.Sep%22%29+OR+%27Verified+In%27+in+%28%222014.3-1%22%29%29%29+and+%27Update+info%27+%21%7E+%27no+udi%27+and+component+not+in+%28componentMatches%28%27LC.*%27%29%2C+%27MGR*NAPA_LC%27%2C+%27Voyage+Optimization%27%29+ORDER+BY+component%2Csummary++++++++++++++https://jira.napa.fi/browse/NAPA-33969https://jira.napa.fi/browse/NAPA-33456https://jira.napa.fi/browse/NAPA-32970https://jira.napa.fi/browse/NAPA-33359

update info 2014 3

Documents