Last Update: March 24, 2005 This file contains only those errors corrected in MSC.Nastran 2005r1 (Version 2005.0.0) and those errors that are currently corrected for the upcoming MSC.Nastran 2005r2 release. The errors corrected in 2005r2 are designated with Version 2005.0.2 and 2005.1. Those designated with 2005.0.2 are also corrected in the initial 2005 release for Opteron/EM64T(x8664). Note that there will be additional error corrections integrated in the 2005r2 system before it is released. 5448 2005.0.2 Buckling Analysis - Superelements - Mislabeled Output Upstream eigenvector data recovery in buckling analysis incorrectly identifies the output as the first subcase. The eigenvalue label is correct. 6982 2005.0.2 Heat Transfer Analysis - PARAM,LGDISP - Solution Does Not Converge PARAM,LGDISP is intended only for the nonlinear structural analysis. However, if it is used in heat transfer analysis (SOL 153 or 159) the solution will not converge. Avoidance: Delete the PARAM,LGDISP from any heat transfer analysis. 27833 2005 Documentation - Getting Started with MSC/NASTRAN The "Getting Started with MSC/NASTRAN User's Guide" states that "In any coordinate system, all angular input is in degrees, but output ... is in radians". This statement needs clarification. The "input" refers only to geometric locations. If an angular enforced displacement is specified the input is in radians. 30010 2005 Superelements - BEGIN BULK SUPER, RESTART - SFM 3001 A restart of a superelement problem will result in the fatal message shown below, if the cold start contains superelements defined in the main bulk data section as well as other superelements defined in the partitioned bulk data sections. *** SYSTEM FATAL MESSAGE 3001 (SEP1X ) THE EXECUTIVE FILE 0 DOES NOT EXIST. PROGRAMMER INFORMATION: SUBROUTINE SEPMAB Avoidance: Define all superelements in either the main bulk data section or the partitioned bulk data section, but not both. 32296 2005.1 Differential Stiffness - STATSUB, Superelements - UFM 5423 (MPYAD) In SOL 105, or if differential stiffness is requested (STATSUB Command) in SOLs 103 and 107 through 112, when superelements are present and no SUPER command, or SUPER=ALL, is specified, then static loads will be generated for the second or dynamic subcase and the job will fail with the following error messages. *** USER FATAL MESSAGE 5423 (MPYAD) ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES COLS ROWS FORM TYPE NZWD DENS TRAILER FOR GOAT IS 106 12 50 2 2 60 4333 TRAILER FOR UAS IS 103 1 12 2 2 8 3333 TRAILER FOR UOOX IS 104 2 50 2 2 40 2000 34940 2005 Nonlinear Heat Transfer - RADBC, NLITER - SFM 4276, Traceback In the radiation dominate problem, the stiffness term is approximately equal to 4*T**3. Therefore, if the guess at the initial temperature value is too low for the problem, the temperature may rapidly exceed an infinite value and the traceback that follows will occur: Trap encountered: SIGTRAP - Trace trap FP overflow Traceback: Offset 0x00000014 in procedure zerod_ Offset 0x00000564 in procedure nrdbcd_ Offset 0x00001124 in procedure nlemg_ Offset 0x00000780 in procedure nliter_ Offset 0x00000088 in procedure xsem15_ Offset 0x00000990 in procedure mainal --- End of call chain --- Avoidance: Make a better estimate of the initial temperature on the TEMPD bulk data entry. In general it is safer to have a very high initial temperature than too low The deck with default temperature=0.0 ran to the end without errors on v2005t1 of AIX and LINUX platforms. 37969 2005 Superelements - Poor Message, UFM 6790 (SEPO21) UFM 6790 shown below is output when a list superelement has no points that can be identified as boundary points. The fatal message is followed by table print which may be ignored. *** USER FATAL MESSAGE 6790 (SEPO21) THE FOLLOWING SUPERELEMENTS ARE DETACHED: 1 3 62000000007 52000000008 212000000002 222000000003 232000000004 242000000005 252000000006 61101529088 71102053376 81102577664 91103101952 101103626240 11 22000000001 42000000007 52000000008 212000000002 22 2000000003 232000000004 242000000005 252000000006 -1 0 0 0 0 0 38073 2005.0.2 Cyclic Symmetry - RESTART, STATSUB - Inefficient Restart If a restart from SOL 114 (Cyclic static) into SOL 115 (Cyclic modes) is performed to calculate pre-stressed modes of the model, the static solution will be re-calculated in SOL 115. There is no avoidance. 38308 2005 Heat Transfer Analysis - CHBDYE, QUAD4 - UFM 6285 If a heat transfer analysis attempts to calculate view factor from the edge of plate elements using CHBDYE with sides from 2 to 5, then you will get UFM 6285 Avoidance: Define the line segment with CHBDYP, LINE boundary elements. 38396 2005.0.2 Superelements - NASTRAN LOCBULK=2 - SFM 4192, SFM 3062 in SEMA If the multi-master method is used on a Cray and LOCBULK is set to 2 and there are GRID id's greater than 1000000 (one million) then the run may fail with SFM 4192, indicating undefined grid points. *** SYSTEM FATAL MESSAGE 4192 (SEMA) GRID POINT .... IN SUPERELEMENT 0 IS NOT DEFINED IN BGPDT FOR DOWNSTREAM SUPERELEMENT and 0*** SYSTEM FATAL MESSAGE 3062 MODULE = SEMA FAILURE OCCURRED IN UTILITY MAPBTI CALLED IN SUBROUTINE SEMA . REQUESTED EXTERNAL ID(S) NOT FOUND. Avioidance: There are several avoidances: 1. Insert the following DMAP alter in the residual structure run: compile phase0 alter ',np,' paraml bgpdt//'trai'/6/s,n,maxgid//s,n,nobgpdt $ if ( nobgpdt>-1 ) putsys(maxgid,186) $ endalter 2. Reduce all GRID id's to less than one million. 3. Run using a different computer type, or run using LOCBULK=1 38815 2005 Distributed Memory Parallel - DMP - Sigbus Error on SGI SGI distributed memory parallel jobs that request 8 or more processors may fail with a "SIGBUS: Bus error" as follows: Core from signal SIGBUS: Bus error (dbx) where > 0 _realloc(0x100193e8, 0x190, 0x19450152, 0x0, 0x110, 0x9436c5a, 0x94369bd, 0x94369d2) ["/xlv43/6.5.7m/work/irix/lib/libc/libc_n32_M4/gen/malloc.c":367,0xfb2a1fc] 1 parse_file(0x111, 0x1, 0x19450152, 0xfb51ef8, 0x110, 0x9436c5a, 0x45,0x94369d2) ["/home/poppy08/kak1/mpt/1.3/mpi/lib/libxmpi/libxmpi_n32_M3/all/all_parse.c":264 ,0x9406214] 2 parse_global_opts(0x9425388, 0x1, 0x19450152, 0xfb51ef8, 0x110, 0x9436c5a, Avoidance: The following changes need to be made to the nast707.dmp file: From: %MSC_ARCH=irix64:% print -nu3 -- "${hosts[$i]} -np 1 ${rcmds[$i]} -c$i -d%r.debug% jid=$jid $args" To: %M 1-4063523 2005.0.2 Superelements - PARAM,SESDAMP - SFM 3001 (GKAM), Wrong Answers If modal damping is requested for PART superelements using PARAM,SESDAMP,YES the run may fail with SYSTEM FATAL MESSAGE 3001 (GKAM) or get incorrect damping. This is due to the program trying to get the TABDMP1 data from the main bulk data. Avoidance: Copy the TABDMP1 entries into the main bulk data section. 1-4966763 2005 Complex Eigenvalue - SGI - Signal 10: Bus Error John, I think most of the old bus errors have been fixed in v2004 or v2005, if it's ok please close this error. On the SGI, it has been reported that on a large modal complex eigenvalue problem, the job terminates without any messages in the f06 file. The log file, however, contains the following messages: Receiving signal number 10: Bus error Job aborting... Unable to call dbx for trace: Resource temporarily unavailable Error unable to remove temp file: /tmp/tt1376064 This type of error is generally due to a misalignment problem and can only occur with the exact combination of memory usage, buffsize, other jobs running the background, and what the operating system is doing. It may occur on the SGI, SUN, and HP. MSC.Software has not duplicated this error on this particular model. Avoidance: Rerunning the job as it. Otherwise, changing the buffsize or memory may also work. 1-6054801 2005 Optimization/Aeroelastic Analysis - monitor points, restart - SFM 3001 A restart run in SOL 200 can fail due to a missing MPSRV datablock when attempting a static aeroelastic trim analysis. It appears that the failure only occurs when the design variables change the analysis model from the cold start to the restart. Avoidance: The following dmap alter can be used in the restart run to avoid the missing datablock: compile phase0 alter 'if ( aero )','nlheat'(3,-1) alter 'not(exter or image'(1,-1) if ( aero ) then $ $ $ Create the aerodynamic model geometry and other data dependent $ only on the model $ GP1 GEOM1,GEOM2,,GDNTAB,MEDGE,,dynamics/ xGPL,EQEXIN,xGPDT,xCSTM,xBGPDT,xSIL,,,/ S,N,LUSET/0/s,n,nopoints $ $ if ( desopt0 ) then $ equivx casexxu/aecase/always $ else $ equivx casecc/aecase/always $ endif $ $ call aero0 aecase ,edt ,xcstm ,dmi ,dmindx , xbgpdt ,pcdb ,geom3 / aebgpdts,aeusets ,aeboxs ,aecomp ,aero , acpt ,cstma ,trx ,control ,spline , mklist ,gpksk ,gdksk ,gpgk0 ,gdgk0 , mpjn2o ,mpjsfn2o,aempcomp,aemonpt ,saemprk , strucomp,monitor ,saerg0 ,aedbstdx,uxvst , pgvst0 / false /aertyp /s,nk /s,nj /s,nx / s,bov $ if ( ifpindx ) call xifpindx spline,,,,,,,,,//s,np $ endif $ aero 1-6155301 2005 Transient Analysis - TRLG - Enforced Acceleration gives poor answers An enforced acceleration problem may exhibit strange behavior due to the mixed precision computations in the TRLG module (specifically in the TRLGCD subroutine). 1-6519201 2005 Nonlinear Analysis - RESTART, TEMP(LOAD) - UFM 9086 Nonlinear analysis restarts (SOL 106) that change the thermal loads may fail with the following fatal message: USER FATAL MESSAGE 9086 (GETLOOP) PARAM, LOOPID, 1 DOES NOT CORRESPOND TO A VALID LOOP IDENTIFICATION NUMBER. Avoidance: In the restart deck replace: ASSIGN master='_____.MASTER' RESTART,version=1,keep with: ASSIGN x='______.MASTER' dblocate logi=x and insert the DMAP alter: compile nlstatic alter 'rstrt=','' rstrt=true $ endalter 1-7472309 2005.0.2 Frequency Response - SPCD - Insufficient time leads to incorrect message If an enforced displacment dynamic analysis has insufficient time to complete all frequency solutions the following warning message will correctly be output; however, it is incorrectly followed by system fatal message 5423 indicating an incompatible matrix multiply. USER WARNING MESSAGE 3045 (FRRD1) INSUFFICIENT TIME TO COMPLETE THE REMAINING 100 SOLUTION(S) IN MODULE FRRD1 USER INFORMATION: TIME ESTIMATE TO COMPLETE: 857 SECONDS TIME REMAINING 42 SECONDS SYSTEM FATAL MESSAGE 5423 (DMPYAD) ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES 1-8349125 2005.0.2 Superelements - SEELT lets you assign the same element to two different superelements No warning is issued if the SEELT entry is used to assign an element to more that one superelement. The SEMAP will indicate the superelement that the element was assigned to. This can result in unexpected answers for boundary matrices. . 1-8439702 2005.1 Frequency Response - PBUSHT, PELAST, PDAMPT, SPCD - Wrong Answers In a frequency response (SOL 108 or SOL 111) analysis using SPCD enforced motion, if frequency dependent properties are defined on a PDAMPT, PELAST, or PBUSHT entry, the frequency dependence is incorrectly interpolated. Avoidance: Insert the DMAP alter avoidance in the attachment. 1-8817411 2005 Matrix Methods - Complex Sparse Unsymmetric Decomp - Wrong Answers for rank of update greater than 1 Complex sparse unsymmetric decomp may exhibit wrong answers for large models when the rank of update specified by system(220) is set to a value larger than 1. In Version 2004 HPUX and Linux systems set this system(220)=32. Avoidance: For Linux and HP it is recommended that system(220) be changed to 1 in the system rc file. The client problem that discovered this problem encountered the error during inertia relief calculations. The problem was also avoided by specifying param,inrel,-2. 1-8821267 2005.0.2 Materials - MAT8 - Floating Point Exception from IFPS Specifying very large values, greater than e+40, for Yt on the MAT8 entry may cause a floating point exception in the IFPS module. 1-8957303 2005.0.2 Aeroelastic Analysis - AMP module unnecessarily re-executed for each flutter subcase In SOL 145 and SOL 200, the AMP module, which generates the QHH family of generalized aerodynamic matrices, is re-executed for each flutter subcase, even if there are no changes in modes or boundary conditions. This results in increased solution times. Avoidance: Insert the following DMAP alter: compile flutter alter 'dbstatus qhhl'(,-1) type parm,,i,n,qf,qc $ type parm,nddl,i,n,cmeth,fmeth $ qf=fmeth $ qc=cmeth $ fmeth=0 $ cmeth=0 $ alter 'ENDIF \$ NOQHHL\>0' fmeth=qf $ cmeth=qc $ alter 'FA1 KHH,BHH,MHH,QHHL','' dbview qhhl0=qhhl where (fmeth=0 and cmeth=0) $ FA1 KHH,BHH,MHH,QHHL0,CASES,EDT/ FSAVE,KXHH,BXHH,MXHH/ S,N,FLOOP/S,N,TSTART/S,N,NOCEAD/LPRINT $ alter 'ADR FPHH,CASEYY,QKHL','' dbview qkhl0=qkhl where (fmeth=0 and cmeth=0) $ ADR FPHH,CASEYY,QKHL0,FLAMA,AEBGPDT,AEUSET/ PKF/ BOV/MACH/'FLUTTER'/aeconfig/symxy/symxz $ compile flutsens alter 'DSFLTE KHHx,BHHx,MHHx,QHHL,','' dbview qhhl0=qhhl where (fmeth=0 and cmeth=0) $ DSFLTE KHHx,BHHx,MHHx,QHHL0,FLUTAB,r1tabr,casem,,/ CPHL,CPHR,VTQU0/1 $ endalter 1-9246401 2005.0.2 Static Analysis - PARAM,INREL, QSETi - SFM 6144, SFE 4276 PARAM,INREL in the presence of a q-set leads to the following fatal message: SYSTEM FATAL MESSAGE 6144 (MERGE1) THE SIZE OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE Avoidance: Apply the following alter: compile statrs alter 'na6=',''(,1) Na6=notset+6 $ Matgen ,/va6/6/na6/notset/6 $ alter 'Umerge1 uset,qra','' Umerge1 uset,qra,,,/qrg/'g'/'t'//1 $ for spcforces compile sedisp alter 'umerge uset,uls,'(3),'' if ( noqset>-1 and nolset>-1 ) umerge uset,uls,/uas/'l+q'/'l' $ endalter 1-10469313 2005.0.2 Heat transfer - view factor - If CHBDYG ID exceeds 1.0e8 then the view factor output is not printed If a CHBDYG ID exeeds 1.E8 then the view factor output will contain ***** for the id as shown below and the view factor output is not printed. ******* ******* 9.7893E-02 2.10642E-06 2.15175E-05 3.2974E-05 NO NO ******* ******* 9.7893E-02 2.44702E-05 2.49968E-04 3.8119E-04 NO NO ******* ******* 9.7893E-02 7.92138E-05 8.09187E-04 1.1879E-03 NO NO ******* ******* 9.7893E-02 1.52525E-04 1.55808E-03 2.1771E-03 NO NO ******* ******* 9.7893E-02 2.26236E-04 2.31105E-03 3.0770E-03 NO NO 1-10687517 2005 Heat Transfer - Format Error in a Large Field View Factor Punch File Large field view factor punch files may contain an incorrect extra line. 1-11399523 2005.0.2 Documentation/QRG - CQUAD4, GEOMCHECK The QRG description of the taper ratio calculation is in error. The quad4 taper ratio calculations are designed to produce taper ratio factors between 0.0 (indicating square/rectangular) and 1.0 (indicating pure triangular). The calculations are performed correctly. However, the discussion in the QRG fails to mention the fact that the taper ratio includes the subtraction of 1.0 to bring the ratio into the 0.0 to 1.0 range. The QRG discussion of the GEOMCHECK Executive Control Statement Remark 2 taper ratio calculation description (4th bullet) should be modified to state: ... is defined to be the absolute value of (the ratio of the area of the triangle formed at each corner grid point to one half of the area of the quadrilateral - 1.0). 1-11725405 2005 Documentation/QRG - CBUSH - Remark 10 references Remark 2 instead of Remark 3. Remark 10 of the CBUSH entry in the Quick Reference Guide says "When CID >= 0, the element x-axis is set as in Remark 2..." This should be changed to specify Remark 3 instead of remark 2. I.E. Change the statement to "When CID >= 0, the element x-axis is set as in Remark 3..." Also, the definitions on the TKIDi, TBIDi and TKNIDi fields on the PBUSHT can use some extra clarification. A statement should be added indicating that the data input corresponds to directions 1 through 6. For example, the TKIDi field is defined as follows: "Identification number of a TABLEDi entry that defines the stiffness vs. frequency relationship." This should be clarified to say: "Identification number of a TABLEDi entry that defines the stiffness vs. frequency relationship in directions 1 through 6." 1-12168411 2005.0.2 Case Control - SDAMP, K2PP, M2PP, B2PP - Unexpected Answers, Missing UFM 9041 for SOLs 118, 146, 200 Beginning in Version 2004 changes to TF, K2PP, M2PP, B2PP and SDAMPING between subcases in SOL 107 through 112 are supported and UFM 9041 is no longer issued. However, these changes are still not supported in SOLs 118, 146 and 200 and beginning in Version 2004 they are ignored and unexpected answers result. The following fatal message should still be issued: ^^^ USER FATAL MESSAGE 9041 (PHASE0) ^^^ THERE ARE CHANGES IN K2PP, M2PP, B2PP, SDAMP, OR TFL. ^^^ USER ACTION: SPECIFY K2PP, M2PP, B2PP, SDAMP, AND TFL ABOVE ALL SUBCASES. Avoidance: Other than not making these changes between subcases, there is no avoidance. 1-12388901 2005.0.2 Superelements - enforced motion, external superelements - Wrong answers If a boundary point of an external SE created using the EXTSEOUT feature has enforced motion specified for it in a subsequent assembly run, then its results come out OK as part of the residual output in the assembly run, but come out as null values as part of the external SE output. Avoidance: Specify PARAM,SPARSEDR,NO or insert the following DMAP alter: compile spdr1 alter 'call xAdd5 vscg0,vmcg,vadr,z01dr0,vyg' add5 v01z,vupse,,,/zzz $ equivx zzz/v01z/-1 $ compile super3 alter 'MPYAD ULS,UH2,\/ULS1','' MPYAD ULS,UH2,yls0/ULS1 $ endalter 1-12862226 2005 Documentation/QRG - param,mmfil The QRG description of the new parameter MMFI is incomplete. The information in the V2004 Release Guide on this parameters use needs to be transferred to the QRG. Avoidance: Please see the V2004 Release Guide. 1-13083904 2005.0.2 SSSALTER/Interactive Nastran - PLOAD4, CQUAD4 - UFM 4577 (GP3C) The interactive menu in Patran 2003r2 allows the user to generate a PLOAD4 on a 2D QUAD4 structure. If no stress request is made on the loaded elements the restart job will fail with the message: ^^^FAST RESTART MESSAGE *** USER FATAL MESSAGE 4577 (GP3C) PLOAD4 LOAD SET = 3 REFERENCES ELEMENT ID = 42 WHICH WAS NOT FOUND AMONG TRIA3, TRIA6, QUAD4, QUAD8, HEXA, PENTA OR HYPERELASTIC SOLID ELEMENTS IN THE PROBLEM. 0FATAL ERROR Avoidance: Add a stress output request for one of the elements loaded by PLOAD4. 1-13218909 2005.0.2 Postprocessing - Interactive Dynamics in Patran fails with SFM 6357 druing full g-set data recovery. When interactive dynamics is used in Patran and all output is selected, then nastran will stop and issue the message: *** SYSTEM WARNING MESSAGE 3001 (SEP1X) THE INPUT DATA BLOCK NAMED GEOM1QS AT POSITION 2 DOES NOT EXIST. *** SYSTEM WARNING MESSAGE 3001 (SEP1X) THE INPUT DATA BLOCK NAMED GEOM2S AT POSITION 3 DOES NOT EXIST. and *** SYSTEM FATAL MESSAGE 6357 (SEP1A) NO GRID POINTS FOUND The sssalter has been corrected in Version 2005; however, enforced motion is not supported and the alter terminates. 1-13229301 2005 Distributed Memory Parallel - DOMAINSOLVER, EIGRL - Poor Message, Extra Eigenvalues If a job is run with dmp=a and the EIGRL entry has ND=b and F1 and F2 are not specified, then (a X b) modes are found. That is b modes at each segment. If no DOMAINSOLVER entry is specified with F1 and F2 blank and dmp= is specified, the job may fail with the message: *** SYSTEM FATAL MESSAGE 3001 (READ) THE INPUT DATA BLOCK IN POSITION 11 DOES NOT EXIST. USER INFORMATION: THIS ERROR IS CAUSED BY ONE OF THE FOLLOWING: 1. THE DATA BLOCK IS UNSPECIFIED ON THE DMAP MODULE. 2. THE DATA BLOCK IS SPECIFIED ON THE DMAP MODULE AND ON THE SUBDMAP STATEMENT BUT NOT ON THE CORRESPONDING CALL STATEMENT. USER ACTION: 1. IF YOU ARE EXECUTING AN MSC.SOFTWARE SUPPLIED SOLUTION SEQUENCE AND NOT USING THE ALTER EXECUTIVE CONTROL STATEMENT, THEN CHECK FOR BULK DATA AND/OR CASE CONTROL INPUT ERRORS. IF NO ERRORS CAN BE FOUND, THEN CONTACT MSC.SOFTWARE CLIENT SUPPORT. 2. IF YOU ARE EXECUTING A DMAP PROGRAM NOT SUPPLIED BY MSC.SOFTWARE, THEN FOR DEBUGGING PURPOSES INSERT STATEMENT DIAGON(20) BEFORE THE MODULE SHOWN ABOVE. PROGRAMMER INFORMATION: THE FIST NUMBER IS 111 AND SUBROUTINE IS GOPEN DMP requires that F1 and F2 be specified. In Version 2005 this input will lead to the message: ^^^ ^^^ USER FATAL MESSAGE 9139 (PHASE0) ^^^ V2 (OR F2) ON THE SELECTED EIGRL (OR EIGR) ENTRY IS BLANK OR ZERO. ^^^ USER INFORMATION: A NON-ZERO VALUE FOR V2 (OR F2) IS REQUIRED INPUT FOR THIS DOMAINSOLVER OPTION. ^^^ 1-13251205 2005 Optimization/Design Sensitivity - PCOMP - Incorrect punched pcomp entries Solution 200 may produce incorrect PCOMPs entries in the punched output when the PCOMP LAM field is set to "MEM" in the original deck. The generated punched PCOMP entries may have a blank MEM field. Another problem with punched PCOMP entries that may be encountered is Ctrl-X in the SOUT field. Avoidance: Edit the punched outut to correct the problem pcomp entries. 1-13776201 2005 Documentation/QRG - RESVEC Keyword DMPLOD, NODMP Lead to UFM 601, Should be DAMPLOD and NODAMP The documented keywords for the RESVEC Case Control Command DMPLOD and NODMP do not work. The correct spelling is DAMPLOD and NODAMP. The incorrect spelling leads to UFM 601 (IFP1D) THE KEYWORD ON THE ABOVE CARD TYPE IS ILLEGAL OR MISSPELLED. 1-13860635 2005.0.2 Superelements - MPCF - Wrong Answers with Sparse Data Recovery In V2004, in a superelement, if MPCF output is requested for only some of the GRID points of the model, the MPCF output may be in error if sparse data recovery is active, i.e. PARAM,SPARSEDR,YES (default). In addition, an SPCF output request will be ignored. This error occurs only in the direct solution sequences; i.e., 101, 103, 108, 109, and 200 with ANALYSIS=DFREQ. Avodaince: Use PARAM,SPARSEDR,NO 1-13998601 2005 Documentation/QRG - FMETHOD Case Control Command Description Missing The FMETHOD Case Control command was inadvertently deleted from the V2004 Quick Reference Guide. Also remark 1 under the FLUTTER bulkdata entry description should point to the FMETHOD command not the METHOD command 1-13998622 2005 Documentation/QRG - ROTORG, TSTEPNL, Rotordynamics - Traceback in TRD1 The new rotordynamics capability in MSC.Nastran 2004 includes nonlinear effects which make the transient response algorithm not unconditionally stable. As such rotordynamics analysis may fail with a traceback in trd1. If this happens the user should specify a smaller timestep. 1-14120001 2005.0.2 Frequency Response - freq-dep elements, MPCForces - SFM 6143 SFM 6143 has been observed when performing a frequency response analysis in SOLs 108, 111, 146, and 200 with frequency dependent elements and MPCForces are being requested User Avoidance: Specify PARAM SPARSEDR NO or insert the following DMAP alter: compile fdrmgen alter 'equivx rxmgx\/rxmg','' alter 'paraml rmgg' if ( spdrm ) then $ equivx rxmgx/rxmg/-1 $ delete /rgm,,,, $ trnsp rxmg/rgm $ endif $ endalter 1-14125525 2005.0.2 Inertia Relief - PARAM,INREL, SUPORT - Multiple load case and DIMG,UACCEL, SFM 6144 Multiple boundary conditions with DMIG,UACCEL in SOL 101 will terminate with SYSTEM FATAL MESSAGE 6144. Avoidance: Insert the following DMAP alter: compile statrs alter 'urax' type db pg $ PARAML pg//'TRAILER'/1/S,N,NCUL $ total no. of loads if ( (ncul-6)<>nloads ) then $ ncul=ncul-6 $ nskip=nskip-1 $ MATGEN ,/COL/6/NCUL/NSKIP/NLOADS $ PARTN urax,COL,/,,urax1,/1 $ loads equivx urax1/urax/-1 $ endif $ endalter 1-14233604 2005 Elements - CQUADR, PARAM,CHECKOUT,YES - Incorrect grid point weight generator output Mass for the CQUADR element is not included in the grid point weight generator results when param,checkout,yes is specified. 1-14249707 2005 Documentation/QRG - SOL 600, PARAM,MARCPTH - Incorrect Default The MSC.Nastran V2004 indicates that the default for param,marcpth is 1. It is not, it is 0. The value of 0 indicates that marc is run within nastran and will look for the marc executable in the default installation directory. 1-14261401 2005 External Superelements - EXTSEOUT - Missing Output due to sparse data recovery A SOL 103 assembly run employing an external superelement created using the EXTSEOUT feature does not produce the requested output for the external SE. Avoidance: Insert PARAM,SPARSEDR,NO. 1-14380804 2005.0.2 Acoustic Analysis - SDAMPING(FLUID) - Unexpected Answers In SOL 111, coupled fluid-structure analysis, with multiple subcases, multiple specifications of SDAMPING(FLUID) are ignored and only the first is processed. Avoidance: Insert the following DMAP alter: compile semfreq alter 'caseg'(2),'' case casem,pvtc/caseg/'comm'/s,n,nskip/////// 'k2pp'/'m2pp'/'b2pp'/'tfl'/'sdamp'/'rgyro'/'sdampf'////// 'g'/'alpha1'/'alpha2' $ endalter 1-14487301 2005 Documentation/QRG - ECHO The 2004 release has new options for the PUNCH portion of the ECHO command. The QRG description of this command has errors in describing the new options. The PUNCH and NEWBULK describers should be changed as follows: PUNCH: The entire Bulk Data will be written to the punch file. (i.e,. omit the "in sorted form") NEWBULK: In SOL 200, a complete unsorted bulk data deck is written to the punch file with updated design model entries. (i.e., change "complete and sorted" to "a complete unsorted" 1-14595809 2005 Rotor Dynamics - UNBALNC, transient response, WTMASS, NLLOAD, imbalance PARAM,WTMASS does not change the load vector (NLLOAD output) leading to wrong answers. 1-14600924 2005.0.2 Static Analysis - APP HEAT, PARAM,HEATSTAT,YES, READ, MAT4 - SFM 4276 SOL 101 with APP HEAT or PARAM,HEATSTAT,YES may fail in the READ module with SFM 4276 This is possible if the bulk data entry MAT4 has specific heat or density. Avoidance: Insert the following DMAP alter: compile phase1a alter 'if ( rvrvd )'(,-1) rvdam=false $ rvrvd=false $ endalter 1-14646106 2005 Installation - Uninstall of Nastran 2004 also uninstalls Nastran 2001. Uninstall of Nastran 2004 also uninstalls Nastran 2001. This has been corrected with version 2005.0 installation/uninstall. (cdp 12/09/04) . 1-14720908 2005.0.2 Optimization/Design Sensitivity - OUTPUT4 - Extra records in the output4 dscm2 datablock The rayleigh quotient approximation used for eigen/freq responses in SOL 200 results in three columns in the DSCM2 matrix for each response. When these results are printed to the .f06 file, these additional columns are stripped off but when they are written to a file using OUTPUT4, they are still there. Avoidance: This alter moves the partitioning of the DSCM2 matrix so that is applies to the OUTPUT4 requests as well. COMPILE EXITOPT $ alter 'sdsc' IF (RQANO) THEN $ $ REMOVE SPAWNED GENERALIZED STIFFNESS AND MASS DSA FROM DSCM2 $ PARTN DSCM2,MRQA,/DSCM2NGS, DSCM2GS,,/1 $ EQUIVX DSCM2NGS/DSCM2/ALWAYS $ endif $ alter 'rqano'(3),'rqano'(3,3) $ endalter 1-14762903 2005.0.2 Optimization/Design Sensitivity - Superelements - Slow Convergence If an eigenvalue optimization task contains superlements and SCR=NO is used, convergence to the optimum design will be slowed due to incorrect sensitivity calculations in the DOM9 module. This only occurs if the Rayleigh quotient approximation is used in the approximate optimization task for the eigenvalue response. Avoidance: Apply the direct (ATTB=1) or inverse (ATTB=2) approximation technique for the eigenvalue response or insert the following alter: compile desopt alter 'cdelk,cdelm,cdelb'(3),'' delete /cdelk,cdelm,cdelb,delgs,delgm $ 1-14779931 2005 Nonlinear Analysis - plasticity - Failure to converge or wrong answers In nonlinear analysis, sol 106, Nastran does not handle a hardening slope change after the 1st hardening slope in plasticity analysis. This may lead to a failure to converge or wrong answers. 1-14949104 2005 Distributed Memory Parallel/Optimization - MODTRK - UFM 6458 A DMP optimization job that requests mode tracking will fail in module MODTRK with UFM 6458 (MTD0RD) complaining the requested mode does not exist. Avoidance: Apply the following dmap alter compile fea list alter 'IF ( MODETRAK>0 ) then','' IF ( MODETRAK>0 and PROCID <= 1 ) then alter 'IF ( MODETRAK>0 ) then'(2),'' IF ( MODETRAK>0 and PROCID <= 1 ) then $ COMPILE moders list alter 'disutil lama'(2,-1) putsys(1,109) alter 'disutil lama'(2) putsys(0,109) $ $ 1-15103324 2005 ACMS - WELD - Job terminates without messages This is now fixed - F2 missing on EIGRL now flagged in phase0 properly. PJS 8/24/04. If ACMS is used in a model with WELD element, the job may terminate in PHASE0. The following messages may appear in the f04 or f06 file: ACMS PHASE 0 BEGN Avoidance: For some problems, the following system cells modifications corrected the problem NASTRAN SYSTEM(360)=2000 NASTRAN BUFFPOOL=500 For SOL 103, GDMODES also avoided this error 1-15168101 2005 Optimization/Design Sensitivity - DSAPRT - Write operation tried to write a record that was too long A SOL 200 job on sgi irix that was writing a long DSAPRT record failed with the message "Write operation tried to write a record that was too long". Avoidance: There is no avoidance. 1-15214414 2005 DMP - MDMODES, EIGRL - Hang in SEMR2, Signal 15 Error If distributed memory parallel (dmp) mdmodes job is executed but f2 on the eigrl entry is not specified, the job may hang in SEMR2 or fail in various ways including a signal 15 error on HPUX Itanium. Avoidance: Specify f2 on the eigrl entry. In Version 2005 and beyond this condition is trapped with a user fatal message. 1-15217604 2005 SOL 600 - Excessive Memory is Required for large models Excessive memory is required for large SOL 600 model. Avoidance: There is no avoidance. 1-15238701 2005 Optimization/Design Sensitivity - DLINK, DESVAR - UFM 7008 If a DLINK entry references DESVAR entries that are not selected by a DESVAR command, the program issues USER FATAL MESSAGE 7008 (THE NUMBER OF DLINK ENTRIES EXCEEDS THE NUMBER OF DESVAR ENTRIES. USER INFORMATION: THE NUMBER OF DEPENDENT DESIGN VARIABLES MUST BE LESS THAN THE TOTAL NUMBER OF DESIGN VARIABLES). Avoidance: Remove the offending DLINK entry from the input file. 1-15242901 2005.0.2 Acoustic (Fluid Structure) Analsysis - MEFFMASS - UFM 5423 A fluid-structure model job with an MEFFMASS Case Control request fails with UFM 5423 (Attempt to multiply incompatible matrices) in the EFFMAS module when it is performing modal effective mass calculations for the structure. Avoidance: Insert the following DMAP alter: compile modefsrs alter 'EFFMAS CASEs,MsAA,PHsA,','' merge msaa,,,,vafs,/msaa1 $ merge phsa,,,,,vafs/phsa1/1 $ EFFMAS CASEs,MsAA1,PHsA1,LAMAs,USET,BGPDTS,, CSTMS,vsgq/ EFMFSMs,EFMASSs,RBMASSs,EFMFACs0,MPFACs, MEFMASs,MEFWTs/ 0/WTMASS $ endalter 1-15269705 2005 Superelements - PARAM,CONFAC - UFM 4277 and 4278 PARAM,CONFAC specifies the tolerance factor used in checking the congruence of the location of the boundary points between image superlements. In some models USER FATAL MESSAGE 4277 (SEP1ED)an d USER FATAL MESSAGE 4278 may be issued indicating that the tolerance has been exceeded when in fact it hasn't. Avoidance: An unrealistically large value of PARAM,CONFAC for example 1.0, may need to be specified to avoid the fatal message. 1-15279201 2005 Elements - CWELD - Floating Point Exception on Windows V2004 Client model with CWELD elements that runs successfully on other platforms fails with a floating point exception on Windows Verison 2004. The problem is resolved in Version 2005. Avoidance: Other than using Version 2005 or running on a different operating system, there is no known avoidance. 1-15297201 2005.0.2 Transient Response - MAXMIN - PARAM,POST,-1 or 2, PARAM,OUGCORD,BASIC - SFM 5423 If a modal transient response requests MAXMIN output, the solution may fail with the following error: *** SYSTEM FATAL MESSAGE 5423 (DMPYAD) ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES The error will occur for the following conditions: 1. Either PARAM,POST,-2 or both PARAM,POST,-1 and PARAM,OUGCORD,BASIC are defined 2. Modal transient (SOL 112) 3. Coordinate systems are present in the model 4. PARAM,MODACC<0 (default) Avoidance: Insert the following DMAP alter. ECHOOFF $ COMPILE SEDRCVR NOLIST $ ALTER 'MPYAD TRANSG'(,-1) $ IF ( SORT2MM ) THEN $ TRNSP UG/UGTX$ EQUIVX UGTX/UG/-1 $ ENDIF $ ENDALTER $ $ COMPILE SUPER3 NOLIST $ ALTER 'MPYAD TRANSG'(,-1) $ IF ( SORT2MM ) THEN $ TRNSP UG2/UGTX$ EQUIVX UGTX/UG2/-1 $ ENDIF $ ENDALTER $ ECHOON $ Example files attached. Details available in activity...Mark R 1-15323213 2005.0.2 SOL 600 - Not writing displacements to IDEAS universal file SOL 600 does not support writing output output to the IDEAS universal file. Beginning in v2005r2 this output may be obtained by using MARCIN to specify Marc's SDRC option. For example: MARCIN,0,0,SDRC,40,3 1-15388155 2005 Rotordynamics - RGYRO, STATSUB - SFM 4276, EC 30, TRD Rotodynamics models, RGYRO, with static subcases in transient analysis may fail in the TRD1 module with SYSTEM FATAL MESSAGE 4276 ERROR CODE 30. 1-15399501 2005.0.2 Dynamics - MCFRACTION in the presence of EPOINT - SFM 6144 (PARTN1) In a modal transient or frequency response analysis, if the model contains one of more EPOINTs (lagrange multiplier, for example) and the case control has an MCFRACTION request, the solution will fail with the following message: *** SYSTEM FATAL MESSAGE 6144 (PARTN1) THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE. SPECIFICALLY: where matrix RPHMC0 has more rows that VMCFG Avoidance: Insert the following DMAP alter ECHOOFF $ COMPILE FDRMGEN NOLIST $ ALTER 'DELETE .*VAD,VGP','' $ MERGE VMCFG,,,,,VGP/VMCFGX/1 $ EQUIVX VMCFGX/VMCFG/-1 $ DELETE /VAD,VGP,IEE,, $ ENDALTER $ ECHOON $ 1-15426513 2005.0.2 Restarts - RESTART, MODTRL - Attaching a read only database may lead to fatal error in MODTRL. Dynamic restarts may be inefficient and SubDMAPs PHASE1A. PHASE1DR, GMA and FREQRS may be executed unnecessarily. Furthermore, if the cold start database is attached read-only a fatal error may be issued in the MODTRL module. Avoidance: Insert the following DMAP alter in your cold start run: compile gma alter 'ENDIF \$ fastfr='(,-1) else $ xfastfr=false $ for restart efficiency endalter Or insert the following alter in your restart run: compile gma alter 'modtrl.*bdd'(,-2) dbstatus bdd//s,n,nobdd $ alter 'modtrl.*bdd','' if ( nobdd<1 ) modtrl bdd////6 $ alter 'modtrl.*k4hh'(,-9) if ( false ) delete /k4hh,,,, $ dbstatus k4hh//s,n,nok4hh $ alter 'modtrl.*k4hh','' if ( nok4hh<1 ) modtrl k4hh////6 $ endalter 1-15463011 2005 SOL 600 - TEMPD is not recognized by the translator In SOL 600 TEMPD is not recognized by the translator. This will lead to missing temperature loads and wrong answers. Avoidance: The only avoidance is to specify the initial temperature on TEMP entries. 1-15477101 2005 Nonlinear Analysis - TEMP(INIT), PCOMP - Wrong Answers For nonlinear analysis of temperature dependent composite materials, the initial stiffness matrix should be computed based on the initial temperature referenced by Case Control command TEMP(INIT)=N. However, for Version 2004, the initial stiffness matrix is computed based on the TREF on the bulk data entry PCOMP. This is wrong. 1-15525703 2005 Data Recovery - MAXMIN(DEF) results are order dependent If a MAXMIN(DEF) definition for a MAGnitude (either Translation or Rotation) follows a MAXMIN(DEF) for a specific component (i.e. T3), then the reported MAGnitude results will all be zero. If the order of the MAXMIN(DEF)s are reversed (MAG first, then component) the results are correct. This order gives zeros for the MAGT results: MAXMIN(DEF) ACCE T3 MAXALG=2 MAXMIN(DEF) ACCE MAGT MAXALG=3 whereas this order does not: MAXMIN(DEF) ACCE T3 MAXALG=2 MAXMIN(DEF) ACCE MAGT MAXALG=3 1-15550901 2005.1 Optimization/Design Sensitivity - SPCD - Incorrect Responses for Enforced Motion TPL deck d200rd15 demonstrates this error and correction in verison 2005. If a SOL 200 design task includes enforced motion using SPCD's, the final response and element data recovery results are incorrect. The optimization results are correct as are the sensitivities. Avoidance: If PARAM NASPRT 1 is used, all data recovery results will be correct. Alternatively, one can simply ignore the final response results and create an input deck from the final design. TPL deck d200rd15 demonstrates this error and correction in verison 2005. 1-15561701 2005 Optimization/Design Sensitivity - Superelements - SFM 3001 (SEP2DR) SOL 200 jobs with the design model in tip superelements and collectors between the designed tip superelements and the residual may fail during pseudo-load data recovery. Data recovery for collectors are skipped which causes the data recovery for tip superelements to fail. *** USER INFORMATION MESSAGE 7321 (SEDRDR) DATA RECOVERY FOR SUPERELEMENT 14 IS NOW INITIATED. *** SYSTEM FATAL MESSAGE 3001 (SEP2DR) THE INPUT DATA BLOCK NAMED SLIST AT POSITION 1 DOES NOT EXIST. Avoidance: For ACMS, use 'TREE=SINGLE' in DOMANSOLVER. For regular superelements, remove the collector definition. 1-15664507 2005 Nonlinear Heat Transfer - Excessive Output Heat transfer, sol 159, may place the: N O N - L I N E A R I T E R A T I O N M O D U L E O U T P U T for each timestep on a different page. If printed this wastes paper and it also has the potential of doubling the output because page header information is repeated for each page. 1-15738901 2005 Documentation/QRG - EQUILIBRIUM - Ignored in SE models Remark 3 of the EQUILIBRIUM Case control command in the QRG should indicate that the EQUILIBRIUM commnad produces no output in the presense of superelements. 1-15831209 2005.0.2 Nonlinear Analysis - ESE - Wrong Answers with INTOUT SOL 106, nonlinear analysis, may create incorrect nonlinear ESE when the 9th field of NLPARM bulk data card, INTOUT, is not set to ALL in Version 2004 and earlier releases. Avoidance: Specify INTOUT=ALL. It has been fixed in V2005.0.0 1-15831507 2005 Frequency Response - SUPORT - SFM 6424 and 6144 Direct Frequency response with SUPORT entries may fail with the messages: SYSTEM FATAL MESSAGE 6424 (DFNSB) THE NUMBER OF ROWS IN THE LOAD VECTOR AND THE FACTOR MATRIX ARE INCOMPATIBLE LOAD VECTOR ROWS = 2536 FACTOR MATRIX ROWS = 2537 SYSTEM FATAL MESSAGE 6144 (MERGE1) THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORS ARE INCOMPATIBLE. SPECIFICALLY: The number of rows in DAY is not equal to the number of zeros in partitioning vector VAY User Information: Size of input matrices and partitioning vectors: DAY : Rows= 2537 by Cols= 1 VAY : Rows= 2537 no. of non-zeros= 1 no. of zeros= 2536 0 Avoidance: compile sedfreq alter 'call mmfind1','' type parm,nddl,char8,n,ltset,llset $ UPARTN USET,Kaa/KLL,,,/ltset/llset $ UPARTN USET,maa/mLL,,,/ltset/llset $ CALL MMFIND1, Kll,Mll,USET,SILS,EQEXINS,,bgpdts/ MECHA,phir,vspc,lll/ s,mmech/'l '/false $ endalter 1-15854501 2005 Submittal - node= - V2004 Windows missing nastran.rmt file The PC version of v2004 (both r1 and r2) does not include the nastran.rmt file (.../msc/msc2004/i386). This means that the "node=" option does not function. Workaround is to copy the one from v2001 (however there are issues with that file as well as you need to include a line that reads: jidtype=%jidtype% as a minimum - this is addressed in a separate CSR - see 1-15854504) 1-15854504 2005 Submittal - UFM, Input file does not exist While using "node=" command to submit from Windows to unix, the job will fail if the extension of the input file ( .bdf for example) does not match the "jidtype" setting on the remote machine. This error persists even if the "jidtype=bdf" keyword is used on the launching PC side. Avoidance: If the following line is added to the PC's nastran.rmt file, then the jidtype keyword is passed thru correctly and the job recognizes the keywords and will run correctly: jidtype=%jidtype% Note that the "nastran.rmt" file itself is missing completely from the 2004 (r1 or r2) installations. The jidtype command above is in the standard nastran.rmt file for Windows. When it is included in the delivery, this error will be eliminated. 1-15895505 2005 Complex Eigenvalue Analysis - CLAN - Wrong Answers In Version 2004, complex Lanczos may produce bad answers if the block size is automatically augmented. The block size is only augmented when the number of repeated roots is greater than the block size or the solver is unable to converge and this rarely occurs in real world models. Avoidance: The problem can be avoided by setting system(108)=8. 1-15950532 2005 Elements - CTRIAX6 - Incorrect Stress Label When using axisymmetric elements, vonmises stresses are labelled as octahedral stresses. Only the labels are incorrect, the values are correct. 1-16028303 2005 Transient Analysis - SPCD - Wrong Answers with sparse data recovery. Sparse data recovery usage in transient analysis (both SOL 109 and SOL 112) employing SPCD enforced motion will give wrong answers if the base displacement or velocity is non-zero. This should not affect enforced acceleration scenarios, but may seriously affect enforced displacement or enforced velocity scenarios. Avoidance: Specify sparsedr=no. 1-16038804 2005 Documentation - DMAP Programmer's Guide Aerodynamic Module examples are obsolete In the DMAP Programmers Guide, the description of the aerodynamic modules is up to date. However, most of the examples still show the old argument lists, e.g. ADG, AMG, ... 1-16074001 2005 Dynamics/Enforced Motion/DMP/Acoustics - SFM 6144 (PARTN1) Acoustic models with enforced motion in DMP may fail with the message: SFM 6144 (PARTN1) Size of input matrices & partitioning vector incompatible Columns of PHSA0 not equal to rows of VR Avoidance: compile modefsrs alter 'if ( relmtn )'(2),'' if ( relmtn and not(procid>1 and (fdmodes or mdmodes)) ) then $ endalter 1-16096104 2005 Enforced Motion, SOL 109 - Unexpected Spikes in Acceleration Direct enforced motion with prescribed displacements (SOL 109) may result in unexpected acceleration spikes at the beginning and end of the enforced displacement. Enhancements to enforced motion have corrected this problem in version 2005. 1-16149704 2005 Distributed Memory Parallel (DMP - ASET - SFM 7467, SFM 6144 This is now fixed. (Remember don't test MDMODES on tiny job for now.) DMP does not support the use of ASET/ASET1 entries. If ASET/ASET1 is used, SYSTEM FATAL MESSAGE 7467 is issued correctly in version 2001. In version 2004, SFM 6144--the sizes of the input matrices and partitioning vectors are incompatible--is issued. Since ASET is not supported in DMP, this also implies that DMP does not support ADAMSMNF. Avoidance: For models using DMP, remove the ASET/ASET1 entries. ASET/ASET1 entires are supported in MDACMS and MDMODES and Freq Domain Modes in V2005. GDACMS and GDMODES are not supported. 1-16163101 2005 Elements - QUAD4, TEMP, MAT2, MAT8 - Poor Answers In MSC.Nastran a single precision transformation is performed for non-isotropic 2D materials (MAT2 and MAT8). This may lead to poor answers and is especially noticable when zero stresses are expected for a free expansion under thermal loads. Avoidance: Use the QUADR element. 1-16323804 2005 SOL 600 - CORDi - Loads applied in cylinderical coords are sometimes incorrect SOL 600 loads applied in cylinderical coordinates are sometimes incorrect. This can happen even if the loads are in the basic coordinate system but the grids have specified a cylindrical output coordinate system in field 7 of the GRID entry. In most cases, the loads are correct. Only in unusual circumstances are the loads incorrect. 1-16326601 2005 Optimization/Design Sensitivity - DESVAR - UFM 7105 When an optimization job specifies DESVAR IDs > 1 million and the DESVAR command is used to select part of DESVAR entries, the job may fail with the message: USER FATAL MESSAGE 7105 (DOPR3F) The Fiedl DVID aaaa on DVPREL1 Entry ID = yyyy is not selected by the DESVAR Case Control command. Avoidance: Specify DESVAR IDs < 1 million. 1-16443309 2005 External Superelements - EXTSEOUT, OUTPUT(PLOT), UFM 2025 (SDR2) If an external superelment, EXTSEOUT, superelement contains a displacement output request. and OUTPUT(PLOT) commands are used, the following FATAL message will occur: *** USER FATAL MESSAGE 2025 (SDR2) UNDEFINED COORDINATE SYSTEM ID = 268435455 Avoidance: Removing the OUTPUT(PLOT) section will eliminate the error. 1-16455901 2005 Optimization/Design Sensitivity - Eigenvector sensitivity with multiple boundary condtions broken Eigenvector sensitivity analysis based on DRESP1 entries was introduced in the 2004 release of MSC.Nastran. The original release supported multiple boundary conditions, but this capability was broken in the 2004.0.3 release (a.k.a 2004r2) when support for multiple boundary conditions in frequency response optimization was integrated. Avoidance: Use 2004.0.0 or version 2005. 1-16470701 2005 Optimization/Design Sensitivity - Multiple Boudary Conditions not robust with multipl analysis types Mutiple boundary conditions with frequency response analysis was introduced into SOL 200 in Version 2004.0.3 (a.k.a. 2004R2). Testing has shown problems when there are multiple disciplines as well as multiple boundary conditions. In particular, runs with ANALYSIS = MODES and ANALYSIS= MFREQ with different boundary condition can produce fatal messages. Quality report 1-1655901 is related. Avoidance: The dmap changes required to support analysis =MFREQ and analysis=MODES and multiple boundary conditions are extensive so this capability is not considered to be operational. It will be operational in Version 2005. 1-16470704 2005 Optimization/Design Sensitivity - Extra responses in formatted sensitivity prints Generalized mass and stiffness responses are "spawned" when the Rayleigh Quotient approach is applied to eigenvalue sensitivity analysis. These response are typically suppressed when formatted design senstivities are printed, but they appear if two different subcases share a DRES[1 id with type = eign or freq and the sensitivity is computed for both. In this case, the senstivities of the generalized matrices can appear following the eigenvalue sensitivities. Avoidance: An avoidance is to not share a DRESP1 ID for multiple subcases. 1-16503108 2005 Acoustics - FLSPOUT, STRUCTMP - Mislabeled Ouput Modal participation factors are calculated for each subcase but are mislabled as the first subcase. 1-16603701 2005.0.2 DMAP - NOT, AND, OR - SFM 223 poor diagnostic If the name of an expression like NOT or AND is used as a variable name, it is accepted in some statements but causes a message that is difficult to understand when it appears. An error report is attached to the back of the test problem, along with some suggested fixes. mag 1-16606402 2005 SSSALTER - spc101a alter missing In Nastran 2004 the spc101a alter was not included. Avoidance: SSSALTERs are posted to the web at: http://www.mscsoftware.com/support/prod_support/nastran/sssalters/v2004/toc.cfm 1-16630701 2005 Optimization - DRESP1 - Transient response types on the DRESP1 do not support multiple components. Rermark 7 for the DRESP1 entry in the QRG indicates that TDISP, TVELO, TACCL and TSPCF support multiple components. A code bug blocks this to a single component less than or equal to 6. Also for GPFORCP. the ATTA input is a grid id. therefore there are documentation errors in table 8-9 on the DRESP1 entry in the QRG and in Remark 7, GPFORCP should be omitted. Avoidance: Single components can be used for the transient responses with no loss of functionality. Mutiple components only simplify the input. 1-16658001 2005 Postprocessing - MCFRACTION - No output written to op2 file No MCFRACTION results are written to the op2 file. 1-16663924 2005 Differential Stiffness - CBAR - Missing UWM 6174 leads to wrong answers Solutions that use differential stiffness (105, 106 and any SOL with STATSUB) that have CBEAM elements with offsets will correctly issue the message below. However; this message may not be issued for similar models with CBAR elements. *** USER WARNING MESSAGE 6174 (EBEMD) BEAM ELEMENT (EID=110) WITH OFFSETS ARE NOT SUPPORTED IN DIFFERENTIAL STIFFNESS OR NONLINEAR ANALYSIS. REMODEL WITHOUT USING BEAMS WITH OFFSET. 0FATAL ERROR 1-16700702 2005 Postprocessing - POST - Missing Output in op2 file If POST NODISP is specified in one subcase then results may be missing from the op2 files in subsequent subcases. 1-16723804 2005 Frequency Response - MEFFMASS - signal 8 MEFFMASS command may lead to the following error on Nastran 2004 HPUX systems: ---------- SIGNAL CAUGHT: Signal number = 8 Signal code = 14 Signal tid = 1 Fault addr = 4000000001352823 FP inexact = 0x0 FP divide0 = 0x8000 FP underflow = 0x0 FP overflow = 0x10000 FP invalid = 0x0 Avoidance: Either remove the MEFFMASS command or run on another machine. 1-16761101 2005 Superelments - EXTSEOUT - Double Field Grids result in SFM 3002 in the BDRYINFO module. External superelements, EXTSEOUT, may fail with SYSTEM FATAL MESSAGE 3200 (LOGIC ERROR 28) in the BDRYINFO module if double field GRID entries are used. Avoidance: Use single field GRID entries or double field GRID entries with the grid IDs in columns 9-16 1-16769901 2005 Documentation - V2004 DMAP Programmers Guide - UMERGE1 The Version 2004 DMAP programmers guide shows the following for the format of the UMERGE1 module: UMERGE1 USET,A11,A21,A12,A22/MAJOR/SET1/SET2/IOPT $ It should be: UMERGE1 USET,A11,A21,A12,A22/A/MAJOR/SET1/SET2/IOPT $ 1-16771901 2005 Composites - PCOMPG - Strength Ratio may cause composite stress & failure index output error When PCOMPG bulk data entries are used (with a blank FT field) and Strength Ratio output request is turned on (PARAM,SRCOMPS,YES), the composites stress, failure index and strength ratio output may be either missing or incorrect. 1-16815502 2005 Composites - PCOMP - Nastran fails with signal 11 if duplicate IDs for MAT entries exist If a PCOMP entry references a MAT8 entry that has the same ID as another MAT entry, i.e. MAT1, Nastran fails with signal 11 in the log file. No other error messages are given. 1-16855001 2005 Nonlinear Analysis - STRESS(PUNCH) - Bad Output in PUNCH File In SOL 106, nonlinear analysis, a request for nolinear stresses to be output to the punch file, STRESS(PUNCH), will lead to NanQ or ????? in the punch file. 1-16858013 2005 Documentation - V2004 DMAP Programmers Guide - MTRXIN description for NOMATi The Version 2004 DMAP Programmer's Guide MTRXIN description for the NOMATi flags indicates that the flags are set to a value of +1 whether the matrix is present or not. The description indicates: NOMATi Output-integer-default=1. Generation flag. Set to +1 if MAT* is generated; 1 otherwise. this should read: NOMATi Output-integer-default=1. Generation flag. Set to +1 if MAT* is generated; -1 otherwise. 1-16877703 2005 Miscellaneous - Disk full on Windows 2000 leads Access Violation A "DISK FULL" condition may lead to an access violation on Windows 2000. Avoidance: This error can be avoided by specifying "sysfield=mapio=no" in a .rcf file or on the command line when the MSC.Nastran job is submitted. 1-16888416 2005 Installation - Installation Errors on AIX 5.2 - mscinfo[281]: ram+= : syntax error A "full" installation of MSC.Nastran 2004r2 on for AIX 5.2. fails with the following message while the installation is unloading the install script: mscinfo[281]: ram+= : syntax error 1-16903901 2005 External Superelements - EXTSEOUT - Missing Output An assembly run employing an external superelement created using the EXTSEOUT feature does not give any output for the external SE if the creation run has no DISP request. Avoidance: Apply the following dmap alter to the assembly run: compile extotmin alter 'dbstatus x_tug,x_rga',''(,1) $ dbstatus x_tug,x_tef,x_tes,x_tqg,x_rga// s,n,notug/s,n,notef/s,n,notes/s,n,notqg/s,n,norga $ if ( notug>0 or notef>0 or notes>0 or notqg>0 or norga>0 ) then $ endalter $ 1-16917801 2005 Optimization/Design Sensitivity - Multiple Boundary Conditions, Output labelled incorrectly. For SOL 200 with ANALYSIS=MFREQ and multiple boundary conditions, BC=, the output for 2nd subcase onwards are labelled incorrectly. Avoidance: Request DMAP alter from client support. 1-16917806 2005 Optimization/Design Sensitivity - DRESP2, DRESP1 - UFM 3007 (dopr3) SOL 200 jobs may fail if DRESP2 entries that reference DRESP2 entires coexist with DRESP2 entries that reference DRESP1 entries. 1-16924801 2005 Miscellaneous - Include may not working on Windows 2000 if file attributes are chaned from default On Windows 2000, if a nastran include data file has the attributes (properties, Advanced, uncheck the "file is ready for archiving" and uncheck the "For fast searching") Then the job aborts. 1-16936701 2005 SOL 700 - SOL 700 in Natran 2004r3 (2004.5) does not work on Windows systems SOL 700 for Natran 2004r3 (2004.5) does not work on Windows systems because the latest Intel compilers provide full path names for the dytran-lsdyna input file and dytran-lsdyna is not able to accept full path names. 1-16937701 2005 Case Control - ESE THRESH does not work when there is no SUBCASE command The THRESH option of the ESE Case Control command does not work if a SUBCASE command is not present. Avoidance: Add a SUBCASE command. 1-16938101 2005 SOL 600 - PCOMP - Wrong Answers when Z0 is specified When translating the Nastran PCOMP enty into a Marc deck, if the Z0 field is specified, then the resulting Marc COMPOSITE entry will be wrong. The current action is to take whatever value is in the PCOMP Z0 field and map it directly into the Marc's COMPOSITE 3rd datablock 4th field. The 'meaning' of the Z0 on the PCOMP entry and this field in Marc are incompatible. In NASTRAN, Z0 on a PCOMP entry defines the distance from the reference plane to the bottom surface of the laminate. In Marc, the field it is mapped to represents the position of the user-defined reference plane. This is the value of the local z-coordinate of the user-defined plane with respect to the geometric midplane. 1-16959902 2005 Superelements - SEEEXCLD - UFM 6788 (SEPMFS) A model that has duplicate boundary grids in the residual structure may fail to exclude the duplicate grid and may fail with the message: *** USER FATAL MESSAGE 6788 (SEPMSF) SUPERELEMENT 1 GRID 3 AND SUPERELEMENT 0 GRID 13 HAVE CONFLICTING MANUAL DIRECTIVES. 1-16978601 2005.0.2 Frequency Response - Enforced Motion, SPCD - UWM 2108, UFM 3046, SFM 3003, SFM 5423 If multiple boundary conditions are specified with enforced motion in dynamic analysis then the following errors may occur: V2004r1 and V2004r2 : UWM2108,UFM3046 V2004r3 and V2005 : UWM2108,SFM3003 or SFM 5423 Avoidance: Insert the following DMAP alter: compile phase0 alter 'if ( appc='(2),'' IF ( APP='FREQRESP' ) THEN alter 'LCGEN CASE1X','' LCGEN CASE1X,SLT,ETT,DYNAMIC0,GEOM4S/CASE1//APP $ alter 'if ( seid=0 and (app='(2),'' if ( false ) then $ alter 'if ( appc='(3),'' IF ( APP='FREQRESP' ) THEN alter ' gp4 ' paraml casew//'dti'/nskip/1//s,n,subcid $ call dbstore yg1,,,,//subcid/0/' '/0 $ compile phase1dr alter 'call phase1b'(,-1) paraml casew//'dti'/nskip/1//s,n,subcid $ call dbfetch /yg1,,,,/subcid/0/0/0/0 $ equivx yg1/yg/-1 $ compile semfreq alter 'nzyg0',''(,1) alter ' dpd '(,-1) paraml casem//'dti'/1/1//s,n,subcid $ call dbfetch /yg1,,,,/subcid/0/0/0/0 $ equivx yg1/yg/-1 $ tabpt DYNAMICS,GPLS,SILS,USET,PG/ $ tabpt pkyg,pbyg,pmyg,yg/ $ matmod yg,,,,,/nzyg0,/6 $ diagonal nzyg0/nzyg/'whole'/0. $ ones at non-null YS rows compile sedfreq alter 'nzyg0',''(,1) alter ' dpd '(,-1) paraml casem//'dti'/1/1//s,n,subcid $ call dbfetch /yg1,,,,/subcid/0/0/0/0 $ equivx yg1/yg/-1 $ matmod yg,,,,,/nzyg0,/6 $ diagonal nzyg0/nzyg/'whole'/0. $ ones at non-null YS rows endalter 1-17011701 2005 Optimization/Design Sensitivity - DRESP2 - Illegal Input to dopr3j When a DRESP2 response in a SOL 200 job intends to reference an existing DRESP1 entry but precedes with a DRESP2 flag, the job fails in DOPR3 with the fatal message "illegal input to subroutine DOPR3J". Avoidance: Specify the correct DRESP1 flag for the referenced entries. 1-17013601 2005 ADAMS/Flex - MNF grid point stress null for quadratic shell mid-side nodes The ADAMS/Flex modal neutral file's modal grid point stress/strain results are null for mid-side nodes of quadratic shell elements due to the fact that nastran does not compute grid point stress results for mid-side nodes of quad8 and tria6 elements. The ADAMS/Flex element face information for elements of these types should contain only the corner grid data and not the mid-side nodes. 1-17055508 2005 Superelements - PARAM,METHCMRS - UFM 3032 In solution 103 if param,methcmrs references an EIGR set id, the job may fail with the message: *** USER FATAL MESSAGE 3032 (READ) UNABLE TO FIND SELECTED SET ( 2000) IN TABLE (EED ) IN SUBROUTINE (REIG). Avoidance: Insert the following DMAP alter: compile phase0 alter 'SEP2.*nGEOM1,GEOM2,GEOM3,GEOM4'(2) if ( seid=0 ) equivx dynamic/dynamics/-1 $ endalter 1-17064430 2005 Distributed Memory Parallal - User must specify F2 on EIGR entry If a dmp job only specifies ND on the EIGR entry using method LAN and the DOMAINSOLVER entry specifies the partopt=freq option the job may attempt to solve all frequencies on all processors. Avoidance: The user must select F2 on the eigr entry. 1-17071801 2005 Miscellaneous - INPUTT2 - OP2 files with matrices and tables may lead to UFM in INPUTT2 OP2 files with intermixed tables and matrices that were correctly read in MSC.Nastran V2004.0.6 fail in V2004.5. The problem is caused because code handling end of matrix condition did not properly accept all valid conditions. corrected inputt2 per jas. 1-17081504 2005 Submittal - node=machine does not work on NT The node=machine nastran submit line option cannot be used from NT to a dissimilar machine. 1-17101627 2005.0.2 Frequency Response - ESE, OFREQ - OFREQ ignored If there are multiple subcases with different OFREQ callouts, the OFREQ command is ignored for ESE output. Avoidance: Either don't use OFREQ or only use one subcase when ESE output is desired 1-17104601 2005 SOL 600, SOL 700 - Windows Version 2004.5 not useable The switch to Intel Version 8 compiler in MSC.Nastran Version 2004.5 for Windows caused many problems in SOL 600 and SOL 700. Thus, this release should not be used for SOL 600 and 700 on Windows. 1-17148302 2005 Optimization/Design Sensitivity - DOPR1, PCOMP - Poor Message, Illegal input to DOPR1I A composite optimization job fails in DOPR1 with "Illegal Input to Subroutine DOPR1I" if the following two conditions are met: 1. The integer input with FID option is used to sepcify a designed laminate thickness or ply angle on a DVPREL1/2 entry and 2. The laminate thickness or ply angle that the FID represents is Not defined on a PCOMP entry. For example, only two laminates are defined on a PCOMP entry but the FID field on a DVPREL1 entry references the thickness for the third laminate. Avoidance: Only design the laminate thickness or ply angle on a DVPRELi entry that is defined on a PCOMP entry. 1-17172902 2005 Installation - Nastran 2004r3 nast20045.rcf file not created. The rcf file for Version 2004.5 (2004r3) on for Windows is created as a file named "nast2004.rcf" which is ignored. Avoidance: The program will recognize the rc file if it is renamed to "nast20045.rcf". 1-17177340 2005.0.2 Aeroelastic Analysis - Direct Enforced Motion, wrong results Solution 146 produces wrong results showing when direct enforced motion is used. The call to subDMAP SUPER3 with AULF is missing data block RGY (penultimate input data block). This may cause some grids to deflect incorrectly. Avoidance: PARAM,DDRMM,-1 will also avoid the data recovery error. 1-17194201 2005 ESE - UWM 4506, UIM 4507, subcase, TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM = 0.0 If a job incorrectly specifies SUBCASE1 with no space instead of SUBCASE 1, the subcase number is read as zero. If ESE output is requested, UWM 4506 and UIM 4507 may be issued indicating the total strain energy is zero. No warning message is given that the SUBCASE entry is in error. The ESE output shows TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM = 0.000000E+00 and no list of strain energies by element is output Avoidance: Correct the SUBCASE entry to leave a space between the word SUBCASE and the 1 1-17202601 2005 Acoustics - DAREA entries not converted to static loads if they reference fluid points Currently, DAREA entries are not converted into equivalent static load entries if they reference fluid grid points. 1-17203001 2005 Distributed Memory Parallel - MDACMS with ESE fails if PARAM,POST specified Parallel MDACMS with ESE request and PARAM,POST will fail since slave processes are not prevented from attempting to write to the output2 file. Solution is to modify the DMAP to call OUTPUT2 only on the master. (Alter can be generated on request.) 1-17210346 2005 Post Processing - PARAM,POST,-2 - Lama table not output2 with post,-2 The llama table is not output2 to the op2 file with param,post,-2. Avoidance: Use param,postext,yes. 1-17242803 2005 Post Processing - Incomplete XDB File The DBC/XDB object in the dictionary does not contain the correct control information, it contains the original object template when the create function completes. This may lead to an incomplete xdb file which may cause post processers to fail. This error has only been observed for one test file that contained 55 subcases. Avoidance: A possible avoidance is to change the block size of the xdb in the FMS section. 1-17252901 2005 External Superelements - UFM 1126, Datablock GOA already exists In Version 2004.5 an external superelement reduction run with ACMS results in the following fatal message: *** USER FATAL MESSAGE 1126 (GNFIST) DMAP MODULE UMERGE1 IS ATTEMPTING TO OUTPUT DATABLOCK 201 NAME = GOA , WHICH ALREADY EXISTS. Avoidance: Insert following DMAP alter: compile phase1b alter 'call segoa'(9,-1) delete /goa,,,, $ endalter 1-17278455 2005.0.2 Aeroelastic Analysis - OLOAD - Request Fails in SOL 146 The OLOAD output request for SOL 146 is not being honored when only frequency response analysis is performed. Avoidance: Run a transient analysis. Or apply the alter in the attachment. The alter changes the fifth input datablock in the final super3 call from ppf1 to pgf1 1-17280829 2005 Documentation/QRG - Release Guide, ASSIGN - Output2 Example 4 under the ASSIGN FMS statement is incorrect. The current example is as follow: assign op2 bigendian' ... assign op2='test_op2.12' unit=12 assign op2='test_op2.35' unit=35 form=formatted The op2 logical name is assigned to unit 12 and this unit number should not be changed on the assign statement. This is usually used for param,post-1 and param,post,-2. The example should be modified as follow: assign op2 bigendian ... assign op2='test_op2.12' assign output2='test_op2.35' unit=35 form=formatted 1-17280840 2005.0.2 Superelement - SELR, method - SFM 9104 In a static supelement analysis run, if case commands METHOD=n and seqset1 entries are included in the model, the job may fail with the following unclear messages: ^^^ USER FATAL MESSAGE 9104 (SELR) ^^^ THERE IS NO COUPLING BETWEEN INTERIOR POINTS OF THIS SUPERELEMENT AND ITS BOUNDARY POINTS. ^^^ USER ACTION: ADD SOME ELEMENTS CONNECTING THE INTERIOR AND BOUNDARY POINTS. Avoidance: Removing either the method command or the seqset1 entries will avoid the error. Note that neither one of these entities are used in sol 101 so the error is very unlikely. 1-17282301 2005 File Management Section - DBLOCATE - SFM 1013 Three successive DBLOCATE commands, the first 2 with NOCOPY and the last one with the COPY option, results in the following fatal message: *** SYSTEM FATAL MESSAGE 1013 (GBKMGX) CANNOT FIND CORRECT CLUSTER POINTER RECORD BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GBKMGX , FILE INDEX = 0. STATUS = 0 Avoidance: Do not mix COPY and NOCOPY options. 1-17297801 2005 Distributed Memory Parallel - EXTSEOUT - SFM 3008 UTMCOR In MSC.Nastran 2004r3(2004.5) a dmp run with external superlements may fail with the message: *** SYSTEM FATAL MESSAGE 3008 (UTMCOR) MODULE = MDENZO INSUFFICIENT CORE AVAILABLE FOR SUBROUTINE ENZO2 PROGRAMMER INFORMATION: LOCATION KEY = READ IN P Avoidance: Run without dmp or apply the following alter: compile cmpmode alter 'call mdacms ' (,-1) $ if( nproc>0 ) putsys(nproc,231) $ alter 'if ( fdcmrrs', '' $ if ( fdcmrrs OR mdacms ) then $ alter 'paraml cmphixz', '' $ paraml cmphixz//'trai'/1/s,n,nozset $ 1-17297961 2005 Installation - FLEXlm installation not handled correctly on hpia64 The current 'mscsetup' script correctly accounts for the hpuxia64 being distinct from hpux, as far as Patran and Nastran installs are concerned, however, when installing a FLEXlm server, the scripts in the .../msc/bin directory (flexlm, lm*) are based off an older mscsetup that does NOT account for the distinction as such, running those scripts on an IA64 will still search for the default 'hpux' location, when the install actually created an 'hpuxia64' folder, and the script will fail 1-17303819 2005 DMAP/Matrix Methods - SMPYAD method ABA wrong results for complex matrices The SMPYAD module ABA method produces wrong results for complex matrices under the following conditions: 1. Spill (multiple passes) used. 2. Triple loop kernels used. Avoidance: Set sys129=1 to bypass the ABA method. 1-17303823 2005 Acoustics - METHOD(FLUID) - Missing output and wrong answers For acoustics, if a METHOD(fluid) entry is not present in the Case Control, the fluid eigensolution is not performed. This conflicts with design intent and Remark 3 under the METHOD command in the QRG. Avoidance: Specify a METHOD(FLUID) entry in Case Control. 1-17322311 2005 Buckling Analysis - multiple buckling subcases - UWM 73, Wrong answers In buckling analysis UWM 73 will be issued if there are more than two buckling subcases in the following solution sequence: 1. SOL 105 with scr=no 2. SOL 200 with ANALYSIS=BUCK regardless of scr keyword Avoidance: Insert the following DMAP alter: compile super3 alter 'DBVIEW qGFs=qG' DBVIEW UGFb=UG WHERE (( (seid>0 and peid>0 and spc=* and mpc=* and suport=* and bmeth=* and mtemp=* and p2g=* and k2gg=* and m2gg=*) or (seid=0 and peid=0 and spc=cspc and mpc=cmpc and suport=csuport and bmeth=cmeth1 and p2g=cp2g and k2gg=ck2gg and m2gg=cm2gg and mtemp=cmtemp) )) $ DBVIEW qGFb=qG WHERE (( (seid>0 and peid>0 and spc=* and mpc=* and suport=* and bmeth=* and mtemp=* and p2g=* and k2gg=* and m2gg=*) or (seid=0 and peid=0 and spc=cspc and mpc=cmpc and suport=csuport and bmeth=cmeth1 and p2g=cp2g and k2gg=ck2gg and m2gg=cm2gg and mtemp=cmtemp) )) $ alter 'SEP4 CASESEP4' else if ( app1='bkl1' ) then $ SEP4 CASESEP4,PCDB,EMAP,XYCDB,UGFb,PUGF,QGFb,mmcdb/ DRLIST/ APP4/'SEID'/S,N,NODRALL/S,N,SEID0/S,N,NOUPL/CNTL $ alter 'DBVIEW UGs=UG ' DBVIEW UGb=UG WHERE (( (seid>0 and peid>0 and spc=* and mpc=* and suport=* and bmeth=* and mtemp=* and p2g=* and k2gg=* and m2gg=*) or (seid=0 and peid=0 and spc=cspc and mpc=cmpc and suport=csuport and bmeth=cmeth1 and p2g=cp2g and k2gg=ck2gg and m2gg=cm2gg and mtemp=cmtemp) )) $ alter 'NUGDWN=(NOGO=-1' else if ( app1='bkl1' ) then $ SEDR EMAPX,CASEX,PCDB,DRLIST,XYCDB,SLT,ETT, MAPSF,UGb,BGPDTSD,GDNTAB,,/ ULS,CASEDR,PCDBDR,XYCDBDR,,/ APP4/SEID/S,N,NOUP/S,N,NOSRT1//S,N,NOOUT/ S,N,NOPLOT/S,N,NOXYPLOT/'SEID'/NCUL $ NUGDWN=(NOGO=-1 AND SEID<>0) $ must appear right after sedr endalter 1-17370601 2005 Optimization/Design Sensitivity - MFREQ, DFREQ, scr=no - Wrong Answers Direct or modal frequency response optimization may produce different optimization results if scr=no is used. Avoidance : Use scr=yes A related problem has surfaced with a external se deck from GM. The client deck itself is not available. However, the problem can be reproduced with d200pe3 with resvec=no. Adding adelufx to the dbdelete fxied the problem. Or, scr=yes also does the trick. 1-17373002 2005 Enforced Motion - SPCD - Enforced motion in a subset of subcases results in SFM 5423. If a frequency response job with more than one subcase has an SPCD enforced motion specified in only a subset of the subcases, the job terminates with SYSTEM FATAL MESSAGE (SFM) 5423 in the MPYAD module. Avoidance: If a frequency response job with more than one subcase is to have SPCD enforced motion specified in only a subset of the subcases, define VERY SMALL enforced motion in those subcases where such enforced motion is not really needed. 1-17373523 2005 Elements - PBEAML, MAT8 - Poor Message, Missing UFM 2113 If a pbeaml entry incorrectly references a MAT8 entry a "Fatal Error" without any further information will be output in V2004.0.6. In V2001.0.9 the same job produces a better message- *** USER FATAL MESSAGE 2113 (EMG) ELEMENT 1 REFERENCED MATID 1 WHICH CANNOT BE USED TO OBTAIN REQUIRED PROPERTIES. Avoidance: Other than correcting the input there is no avoidance. 1-17378501 2005 Nonlinear Analysis - PCOMP, TEMP(MAT) - Wrong Answers Unsymmetric composite layups with temperature-dependent materials may produce wrong answers in nonlinear analysis. Avoidance: There is no avoidance. 1-17386627 2005 Miscellaneous - SWM 6498 UFM (1) - Unclear message Corrected usrmsg.F to increase dimension of array from 9 to 10. (cdp 8/24/04) If degrees of freedom are defined illegally in a set (e.g., constraining an dependent dof), the job should fail with a message similar to the following messages: USER FATAL MESSAGE 2101 (GP4) +165 GRID POINT 530 COMPONENT 1 ILLEGALLY DEFINED IN SETS UM US However, in v2004.5, the job may fail with the following unclear messages Windows machine. *** SYSTEM WARNING MESSAGE 6498 (MsgGen) Message number was not found. PROGRAMMER INFORMATION: Check call to MSGPOP from GP4 with message number 538976288.0. Severity is 'USER FATAL MESSAGE' (1) %1: ' 530' %2: ' 1' %3: ' UM' %4: ' US' %5: ' ' %6: ' ' %7: ' ' %8: ' ' %9: ' ' %10: '' Avoidance: Correct the offending entry 1-17395103 2005 DMAP - MPYAD - incorrect data in UFM 5423 If the MPYAD module issues SFM 5423, the message may contain an incorrect data block name specified in a prior execution of MPYAD. For example, in the following DMAP: MATGEN ,/A/4/4/3 $ MATGEN ,/B/4/3/4 $ MATGEN ,/C/4/3/3 $ MPYAD A,B,C/D $ MPYAD A,B, /E/1 $ the 1st multiply runs OK but the 2nd mpyad fails and references the C matrix in the first mpyad. SYSTEM FATAL MESSAGE 5423 (DMPYAD) ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES Avoidance: There is no avoidance. 1-17417801 2005 Complex Eigenvalue - CEAD - Eigenvector spill logic in complex Lanczos causes hard crash. The multishift logic in the complex branch of the complex Lanczos method suffers a hard crash when the eigenvectors spill. Avoidance: The avoidance is to increase memory or to use the old single vector complex Lanczos. 1-17432001 2005 Optimization/Design Sensitivity - DRSPAN, DOPR3 - SFM 4276 When an optimization job includes both DRSPAN subcases mixed with non-DRSPAN subcases, the job may fail with SFM 4276 with error code = 3001 in the DOPR3 module. Avoidance: Rearrange the subcases so that the non-DRSPAN subcases are put at the top of the DRSPAN subcases. 1-17446201 2005.0.2 Aeroelastic Analysis - DMIK The DMIK bulk data input provides a convient way of entering correction data related to the aerodynamic model. At present, this is supported only in SOL 144 and SOL 200 and is not supported in SOL's 145 and 146. Avoidance: The DMI equivalents of these matrices can be input or the following dmap avoidance can be applied to add the MATPOOL datablock in the call to PFAERO. The alter below applies to SOL 145 with a similar alter required for 146: CALL PFAERO cases ,EDTS ,ects ,bgpdts ,DMI , DMINDX ,PCDBS ,acpt ,aero ,matpool , mklist ,aempcomp,aemonpt ,saemprk ,control , aecomp ,cstma ,aebgpdts,mpjsfn2o,mpjn2o , aeusets / lajjt ,uajjt ,ajj0 ,wskjf ,D1JK , D2JK ,d1je ,d2je ,skj , , , , , , , ,WKK , , , , , , / 'DYNAMICS'/IMACHNO/IKBAR /S,PFILE /SKPAMP $ 1-17446504 2005 Rotordynamics - TRD1 - Traceback in TRD1 Rotordynamcis may fail in trd1 with a traceback. Avoidance: There is no avoidance. 1-17446507 2005 Rotordynamics - ROTORG, NLTRD2, CDAMPi, CVISCi, UNBALNC - Wrong Answers, Damping Ignored The rotor damping (CDAMPi, CVISCi) should add instability to transient response but damping is effectively not included. 1-17464201 2005 Nonlinear (SOL 106) - SFM 1014 - Solution 106 may fail with the following message: *** SYSTEM FATAL MESSAGE 1014 (GBKMGX) ERROR IN LOOKING UP CLUSTER NUMBER BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GBKMGX , FILE INDEX = 0. STATUS = 0 1-17469004 2005 Rigid Elements - AUTOMSET, DECOMP, UFMPACK - HPUX IA64 under Nastran 2004r3 Large models with automset may fail with the message below on Itanium running HPUX. From the f04 file Your use or distribution of UMFPACK or any modified version of UMFPACK implies that you agree to this License. THIS MATERIAL IS PROVIDED AS IS, WITH ABSOLUTELY NO WARRANTY EXPRESSED OR IMPLIED. ANY USE IS AT YOUR OWN RISK. From the log file: FATAL ERROR: thread: 1 routine: sysrcv reason: signal recvd error: -4 Avoidance: The only avoidance is to use version 2005. 1-17482902 2005 Submittal - libpath set incorrectly when exe= specified with no directory Fixed in round 16. When using nastran script with exe= keyword to override the default executable, if the pathname of the executable does not have any directory compoment specified, then the libpath will not include the correct directory path. 1-17510409 2005 Miscellaneous - MEM - 'Unable to allocate /XNSTRN/ Open Core (memory) on Windows XP MSC.Nastran requires that contiguous memory be allocated. MSC.Nastran requires dlls be loaded and these dlls use open core. The various Windows o/s may allocate the required open core differently causing more or less memory to be available for nastran. Windows XP has been found to allocate the memory in such a way that only 1100mb of contiguous space is left for nastran. MSC.Nastran V2005 dummys out unneeded FLEXlm dlls and this allows more memory to be allocated. Thus, this problem is considered partially addressed in Version 2005. MSC will continue to investigate more efficient ways to allocate memory. Note that it is a limitation of all Windows based operating systems that other applications that are executing will impact the amount of open core that can be allocated. MSC.Nastran V2005 has been further enhanced to improve dll management to maximize the available open core. Currently, it appears that MSC.Nastran can now access approximately 1.8GB of open core on all versions of Windows XP. 1-17584301 2005 Performance - Poor performance for unsymmetric FBS for uncoupled matrices The performance for unsymmetric FBS is poor when the matrices have very little coupling (i.e. very sparse RHS matrix). In this case, the code should select the special "MCE1-only" sparse FBS. 1-17604301 2005 Data Recovery - GPFORCE, SUBCOM - Missing output If GPFORCE is requested in a SUBCOM then "F-OF-SPC" may not be printed in the SUBCOM's grid point force balance output. Avoidance: Insert the following alter: COMPILE sedrcvr alter 'GPFDR CASEDR,UG,KELMX'(,-1) paraml qmg//'null'////s,n,nullqmg $ if ( nullqmg=-1 ) delete /qmg,,,, $ endalter 1-17620501 2005 Superelements/Frequency Response - DELAY, SPCD - SFM 4276 in DPD (in SEDLG subdmap) A SOL 111 superelement job employing DELAY data and SPCD enforced motion fails with SYSTEM FATAL MESSAGE 4276 (ERROR CODE 3021) on a call to the DPD module in the SEDLG subdmap during data recovery. 1-17647514 2005 Postprocessing - PARAM,POST,0 - GRIDX is not present in XDB for Collector Superelements THE GRIDX datablock is not present in the XDB when the superelement is a collector containing no elements. 1-17663601 2005 External Superelements - EXTSEOU, PSDF - Missing PSDF output in assembly run. When using the EXTSEOUT feature, the assembly run does not output the PSDF responses for velocities and accelerations for the external superelement. Avoidance: Insert the following DMAP alter in the assembly run: compile sedrcvr alter 'Multiply OTM' splitdva=-1 $ endalter 1-17664010 2005 Inertia Relief - param,inrel,-2 - Model with no mass does not issue UFM A model with no mass defined may only issue a max ratio warning message and continue when using param,inrel,-2. The job should issue a meaningful fatal message. +++++++++++++++++++++++++ A correct warning message is found in V2005.0.0. -TIN- ^^^ USER FATAL MESSAGE 9088 (SELG) ^^^ PARAM,INREL,-2 IS PRESENT BUT NO MASS IS DEFINED. 1 1-17670502 2005 Size Limitation - DCMP - Floating point exception error in DCMP for large models Verified with Nastran 2005, build date August 27, 2004 on AIX 5. AZ 10/01/04 This should be fixed now. PJS 8/27/04 In MSC.Nastran Version 2004.5, large models may fail in decomp on 64 bit aix systems (AIX 5 and above). SIGTRAP - Trace trap Signal generated for floating-point exception: FP invalid operation. 1-17673201 2005.0.2 File Management Section - ASSIGN with DELETE option fails - UFM 1277 or UFM 773 In Version 2004.0.7 and 2004.5.0 only: If the DELETE option is used on an ASSIGN MASTER statement and the file already exists, then the file assigned to MASTER is NOT deleted and UFM 1277 is issued. ASSIGN MASTER='model.MASTER', DELETE ASSIGN DBALL='model.DBALL', DELETE $ *** USER FATAL MESSAGE 1277 (DBDEF) THE FILE ASSIGNED TO LOGICAL NAME = MASTER IS NOT A VALID MASTER DBSET FOR A PRIMARY DATABASE. USER ACTION : VERIFY THE FILE NAME SPECIFIED ON THE ASSIGN MASTER STATEMENT. 0FATAL ERROR In Version 2004.0.7 and 2004.5.0 only; If the DELETE option is used on an ASSIGN for a non-MASTER file (e.g. DBALL) and that file exists, then the DELETE is ignored and UFM 773 is issued: ASSIGN MASTER='model.MASTER' ASSIGN DBALL='model.DBALL', DELETE ENDJOB *** USER FATAL MESSAGE 773 (DBDEF) THE FOLLOWING PHYSICAL FILE ALREADY EXISTS. LOGICAL NAME = DBALL PHYSICAL FILE = model.dba USER INFORMATION: NO ASSOCIATED DEFAULT FILES OR ASSIGNED DBSETS CAN EXIST PRIOR TO THE DATA BASE INITIALIZATION RUN. USER ACTION: DELETE THIS FILE AND RESUBMIT THE JOB. Avoidance: Manually remove all files used on ASSIGN statements prior to run 1-17706203 2005.0.2 Materials - MCSID - UFM 2025 Large, eight digit, MCSID IDs may incorrectly lead to UFM 2025. *** USER FATAL MESSAGE 2025 (TA1) UNDEFINED COORDINATE SYSTEM ID = 50500099 Avoidance: Use smaller ids. 1-17724607 2005.0.2 Optimization/Design Sensitivity - MFLUID - SFM 1126 If an optimization model contains MFLUID entries, the job will fail with the following messages. *** USER FATAL MESSAGE 1126 (GNFIST) DMAP MODULE MGEN IS ATTEMPTING TO OUTPUT DATABLOCK 204 NAME = MAR , WHICH ALREADY EXISTS. USER ACTION: DELETE THE DATABLOCK, OR USE FILE MAR=OVRWRT Avoidance: Insert the following alter. compile phase1a alter 'delete.*\/belm' delete /mar,,,, $ endalter $ 1-17727701 2005 Dynamics - DELAY - SFM 3002 (DPD), Specifying DELAY for dof with no excitation Specifying DELAY data for DOFs without any excitation may lead to SYSTEM FATAL MESSAGE 3002 on a call to SKPREC in the DPD module. 1-17764701 2005.1 Optimization/Design Sensitivity - Multiple Static Aero Subcases - Incompatible Matrices, SFM 4276 If a SOL 200 run is made with multiple static aero boundary conditions and the subcases have different externally applied loads, the sensitivity analysis can produce either wrong answers and go down paths that cause the solution to fail with a message that indicates incompatible matrices or a divide by zero errors. Avoidance: One avoidance is to remove the external loads. A more complete avoidance is to make the following NDDL change: PATH ULNDEL SEID,PEID,MPC,SPC,SUPORT, DESITER,PVALID,APRCH,HIGHQUAL, AUXMID,ADJOINT,DESINC,DISCRETE $ METH and make the following dmap alters: compile fea alter 'bcdr'(5),'bcdr'(5) BCDR CASEM//SEID/' '/0//true/ S,N,SPC/S,N,MPC/S,N,SUPORT/s,n,load///S,N,BC $ compile pslgdv alter 'bcdr'(2),'bcdr'(2) BCDR CASEM//SEID/' '/0//true/ S,N,SPC/S,N,MPC/S,N,SUPORT/s,n,load///S,N,BC $ alter 'bcdr'(8),'bcdr'(8) BCDR CASEbc//SEID/' '/s,n,nskip//s,n,bcflag/ S,N,SPC/S,N,MPC/S,N,SUPORT/s,n,load///S,N,BC $ alter 'segoa'(2) dbstatus auads//s,n,noaua $ alter 'nopa'(8),'' if ( nopa<1 and noaua> 0) then $ alter 'pav' NSKIPL=NLOADS+NSKIPL $ LOADS ACCUMULATOR alter 'pmav' nskplm=nloada+nskplm $ unrestrained loads accumulator alter 'nskplm'(4,-1),'nskplm'(4) compile gendv2p alter 'nddl','nddl' TYPE PARM,NDDL,I,N,MPC,SPC,suport,templd,deform ,load $ alter 'bcdr','bcdr' BCDR CASE0//0/' '/ S,N,NSKIP/S,N,NLOADS/S,N,BCFLAG/ S,N,SPC/S,N,MPC/S,N,SUPORT/s,n,load////-1 $ compile xsedrdr alter 'bcdr','bcdr' BCDR CASEbc//SEID/' '/s,n,nskip//s,n,bcflag/ S,N,SPC/S,N,MPC/S,N,SUPORT/s,n,load///S,N,BC $ 1-17767304 2005.1 Documentation/QRG - ADAMSMNF - SWM 7804 - No stresses/strains written to ADAMS mnf file Attempt to output solid element strains (CHEXA, CPENTA, CTETRA) into the Adams mnf file using the ADAMSMNF command will not work and will result in the message: SYSTEM WARNING MESSAGE 7804 (AFERRM) THE ADAMS/FLEX MNF GENERATION MODULE INPUT GRID POINT STRAIN DATA BLOCK OFP TABLE CODE IS NOT RECOGNIZED. OFP TABLE CODE IS 28. REQUEST FOR GRID POINT STRAIN OUTPUT IS IGNORED. No stresses or strains are written. Avoidance: Do not use PRINCIPAL on the VOLUME command. Explicitly use DIRECT to output stresses/strains into the mnf file. It is a restriction in the ADAMS/Flex interafce that it accepts only direct stresses and not principal. The ADAMSMNF command in the QRG needs a comment to this effect. 1-17769313 2005 Submittal - Estimate fails with Access Violation on Window Estimate may fail with an Access Violation message on Windows. Avoidance: Specify mem= on the nastran submittal line so that estimate does not run. 1-17776102 2005 Performance - Krylov performance may suffer due to DOF-based ordering The Krylov solver uses CFACTR to do the decomp for frequency response. This path to decomp uses degree-of-freedom based ordering. It should call CFACTR2 instead which uses grid based ordering. 1-17777901 2005 Performance - FASTFR check in GMA not correct If any structural matrices are missing, for example there are no fluid elements, the check in GMA to determine if FASTFR can be used is not correct. This may lead to slower run times. dfbella>>> New checking implemeted. 1-17790001 2005 SOL 600 - Temperature Loading with offs gives wrong results For SOL 600 an option has been added to apply thermal loading at the original node, the offset node or both. This is activated by a new parameters in Nastran 2005 named marcofft and moffcore. The defaults for these new parameters cause the temperature loading to be applied at both nodes. Models now gets the same thermal strains using SOL 600 and 106. 1-17818401 2005.0.2 Elements - CBAR, CBEAM - UFM 2026 when BGG, BGE, or BEE is specified for OFFT UFM 2026 indicating illegal geometry is generated for CBAR/CBEAM elements when the orientation vector for the element is defined using the reference grid point (G0) option and the OFFT (field 9) value specifies BASIC (Bxx codes) for the orientation vector. Avoidance: Specify GLOBAL (Gxx) code for the orientation vector. 1-17835201 2005 Buckling - Multiple buckling subcase - SFM 3002 in GPSP Solution 105, buckling, may fail in MSC.Nastran 2004 with SYSTEM FATAL MESSAGE 3002 in the GPSP module if multiple buckling subcases exist. 1-17845802 2005 Rotordynamics - LOAD, RFORCE - Wrong Answers In a static analysis with rotors, the gyroscopic moments may be missing from the load vecotr if the LOAD Case Control Command references a LOAD Bulk Data Entry. Avoidance: The LOAD Case Control Command should reference the RFORCE Bulk Data Entry directly without using the LOAD Bulk Data Entry. 1-17865308 2005 Optimization/Design Sensitivity - PARAM,XYUNIT,PUNCH(NEWBULK) - No punch file written, csv incomplet The DOM12F subroutine does not place any limits on the length of a record created that is to be written to the csv file. Machine limits exist and the program needs to be redesigned to write within these limits. Error message on AIX: 1525-005 The formatted I/O statement on the internal file cannot be completed because the end of the record was reached. The program will recover by ignoring the remaining data items in the I/O statement. XL Fortran (initialization): Out of memory. time: command terminated abnormally. Error on 32bit Linux: Input/Output Error 154: Wrong length record In Procedure: dom12f At Line: 319 Statement: Formatted WRITE Unit: Internal File Record Number: 1 1-17867401 2005 Acoustics - param,panelmp - Panel grid Mode Participation Factor output incorrect Structure Mode Participation Factor output for panel grid points is incorrect if any fluid grid point id is less than the largest id of the structural grid points in the problem. All other MPF output is accurate. Avoidance: Make sure that all fluid points have IDs greater than the largest ID of the structure grid points. 1-17889001 2005 Rigid Elements - PARAM,AUTOMSET,YES fails with multiple boundary conditions or SOL105 Runs with PARAM,AUTOMSET,YES could fail in SOL 105 or with multiple BC with UFM 1126 (GNFIST) (matmod attempting to output GM which already exists). Avoidance: compile sekr0 alter 'xmce1',''(,1) TYPE PARM,NDDL,CHAR8,Y,automset $ IF ( NOGM=-1 or automset='yes' ) then $ if ( automset='yes' ) delete /gm,,,, $ call xmce1 USET1,RMG1,KGG/GM,nuset/rsonly $ dbstatus nuset//s,n,nonuset $ IF ( getsys(np,400)<>0 and nonuset>0 ) equivx nUSET/uset1/always $ endif $ 1-17889901 2005.0.2 Elements - CWSEAM - TABPRT, conflicts in GEOM2 NDDL descriptions The format of the CWSEAM entry is changed after MODGM2 module. This results in conflicts in NDDL descriptions for this element type and the TABPRT contents of GEOM2 data block won't match the labels. 1-17907360 2005.1 Rigid Elements - RIGID(LAGRAN) - Lagrange RBE2 with TEMPD and TEMP produces SFM 3003 Lagrange RBE2 with TEMPD and TEMP causes the following error. *** SYSTEM FATAL MESSAGE 3003 (SSG1) ATTEMPT TO READ PAST THE END OF A LOGICAL RECORD IN DATA BLOCK ETT (FILE 107) IN SUBROUTINE GETEMP 1-17976601 2005.0.2 Documentation/QRG - MCFRACTION Remark 7 of the Quick Reference Guide description of the MCFRACTION case control command states that the filter applies to the sorting KEY item. However, this is incorrect. The filter is always applied to the RESPONSE magnitude, regardless of which item has been used to produce the sorted listing. - 1-18048305 2005 Installation/Documentation - buildsss.bat missing in V2004 The Version 2004 delivery is missing \msc\msc2004\nast\del\buildsss.bat Avoidance: Copy the attachment buildsss.bat.del to \nast\del\buildsss.bat. The IOG Documentation indicates: "msc2004 buildsss src=." However, for Windows, the "src=" is an improper format. The correct format for Windows should be: msc2004 buildsss full_path_of_source 1-18089601 2005 Optimization/Design Sensitivity - PCOMP Zero sensitivity coffecients for composites A composite optimization job may produce zero sensitivity coefficients if the following conditions are met: 1) two or more material properties are being designed, 2) one of the designed material properties is referenced by the PCOMP entry. Avoidance: Design a material property either being referenced by a PCOMP entry or by other property types, not both. 1-18126001 2005 Data Recovery - SORT2 in static and transient analysis - Excessive disk space usage IIn static and transient analysis when SORT2 or XYPLOT output is requested an unnecessary SDR3 operation occurs. On large problems this can require large amounts of disk space. Avoidance: Insert the following DMAP alter: compile sedrcvr alter 'strsort' if ( not sort2mm ) sdr3 oes2s,,,,,/oes1x1,,,,, $ alter 'strsort'(,1) if ( not sort2mm ) equivx oes1x/oes1x1/-1 $ alter 'sdr3 oes2s,,,,,','' 1-18136004 2005.0.2 Data Recovery - MAXMIN(DEF) two item codes - Wrong Answers The following format of the maxmin(def) commands cause incorrect data recovery. The RMS for the second item code was zero. Also, the Z2 von mises stress was wrong for Z2. MAXMIN(DEF) STRESS QUAD4 9 MAXALG(1) RMS MAXMIN(DEF) STRESS QUAD4 17 MAXALG(1) RMS Avoidance: Combine the items requested on one command, as shown below. MAXMIN(DEF) STRESS QUAD4 9 17 MAXALG(1) RMS 1-18137202 2005.0.2 Aeroelastic Analysis - AECOMP, MONPNT1 - Missing Monitor Point Output No Error message is issued when the COMP field on the MONPNT1 entry points to a nonexistent AECOMP entry. Instead, the MONPNT1 entry is just ignored and no output is generated for it. 1-18154902 2005.0.2 Frequency Response - Multiple FREQ subcases and scr=no - UFM 1126 When using scr=no with multiple frequency subcases with one of the subcase having the same DLOAD and FREQ request as a prior subcase the run will fail with: *** USER FATAL MESSAGE 1126 (GNFIST) DMAP MODULE FRLG IS ATTEMPTING TO OUTPUT DATABLOCK 201 NAME = PPF , WHICH ALREADY EXISTS. USER ACTION: DELETE THE DATABLOCK, OR USE FILE PPF=OVRWRT *** USER FATAL MESSAGE 1126 (GNFIST) DMAP MODULE FRLG IS ATTEMPTING TO OUTPUT DATABLOCK 204 NAME> > = FOL , WHICH ALREADY EXISTS. USER ACTION: DELETE THE DATABLOCK, OR USE FILE FOL=OVRWRT Avoidance: Insert the following DMAP alter: compile semfreq alter 'IF ( NOT NOPH2 and extdr','' dbstatus uhf//s,n,nouhf $ IF ( nouhf<1 and NOT(NOPH2) and extdr='no' ) THEN $ endalter 1-18192403 2005 Matrix Methods - Complex Unsymmetric Decomp , SYSTEM(221) - Wrong Answers MSC.Nastran HPUX systems are the only ones that set the rank of update for complex unsymmetric sparse decomp to greater than 1. This can lead to wrong answers. Avoidance: On HP system set system(221)=1 in the nastran rc file. On all other systems do not set this system cell. 1-18217901 2005.0.2 Dynamic Response - RESTARTS, SPCD - UFM 5423 Dynamic response restart jobs (SOL 108, 109, 111, and 112) may not handle enforced motion correctly. This may result in wrong answers in V2001 and V2004, but causes termination of the job with UFM 5423 in the FRLG module in V2005. Avoidance: Two avoidances exist. 1. Use a dummy (unused) FORCE or DAREA Bulk Data entry in the restart job. 2. Employ the following DMAP alter in the restart job: compile semfreq $ for sol 111 (use sedfreq for sol 108, sedtran for sol109 and semtran for sol112) alter 'dpd '(,-1) $ paraml yg//'trailer'/1/s,n,ygcols $ paraml pg//'trailer'/1/s,n,pgcols $ type parm,,i,n,extracol $ extracol = ygcols - pgcols $ $ append extracol null columns to pg append pg,/pgnew/1//extracol $ delete /pg,,,, $ equivx pgnew/pg/-1 $ 1-18228729 2005.0.2 Miscellaneous - Unicode text causes UFM 300 If a file is saved as unicode text, the nastran job may fail with the following message *** USER FATAL MESSAGE 300 (RCARD) DATA ERROR IN FIELD UNDERLINED. EMBEDDED BLANK. If you look at the file in Nodepad, it appears to look ok. However, if you look at it in a vi editor, you will see blanks between each character Avoidance: Save the file in standard text format 1-18235402 2005.0.2 CWELD Elements - Wrong Bearing Stresses for CWELD elements The bearing stress should equal the resultant of the shear forces divided by the (cweld diameter x minimum thickness of the connected shell elements). However, the dependency on the minimum thickness TMIN is broken and the output for the bearing stress is equal to simply the Shear Force divided by the Weld Diameter. This error has been verified by the initiator. 1-18239502 2005.0.2 Size Limitation - Maximum of 120 DMI matrices and DTI tables are allowed A maximum of 120 unique DMI matrices and 120 tables are allowed in the input. In Version 2001 an attempt was made to increase the limit to 1000 but the change was incomplete. 1-18300741 2005.0.2 Modal Transient Analysis - TIC - UFM 2133 (DPD) In SOL 112, when a degree of freedom is specified on a TIC entry that is not in the a-set the job will fail appropriately with the message: USER FATAL MESSAGE 2133 (DPD) *** USER FATAL MESSAGE 2133 (DPD) INITIAL CONDITION IN SET 1 SPECIFIED FOR POINT NOT IN ANALYSIS SET. However, the message does NOT indicate the grid and component. When a large number of TIC are present in the input file it is difficult to identify the problem input. 1-18419669 2005.0.2 Postprocessing - MPC data in GEOM4 datablock created by module MAKEOLD is not in single precision If the model contains MPC entries, and the MAKEOLD module is used to convert the MPC entries in the GEOM4 datablock to single precision, the conversion does not take place. This happens for instance when PARAM,POST,-1 or -2 are requested and PARAM,OGEOM,YES (default) is used. The error was reported because IDEAS was terminating when reading an op2 file created using PARAM,POST,-2. In addition to being corrected in the 2005r2 release, this error was corrected in a special build of 2004.5.1 on AIX, IRIX, and Sunos only. This system was not written to cd and is only availalbe from MSC's internal ESD site. Avoidance: Insert the following DMAP alter for 2004.5. This alter wil create an op2 file compatible with V2001 when either PARAM,POST,-1 or -2 is specified and NASTRAN OP2NEW=0. The alter deletes the erroneous MPC data from the GEOM4 datablock so it does not get written to the op2 file. An alter is also available that converts the double precision MPC data to single precision using the table insert functions of the PARAML module to create a single precision MPC data record which is then added to the GEOM4 datablock after MAKEOLD processing. NASTRAN OP2NEW=0 ECHOOFF $ $ V2004.5 op2 in 2001 format, post -1 and post -2 $ COMPILE OUT2GEOM NOLIST $ ALTER 'MAKEOLD GEOM4','' $ TYPE PARM,,I,N,RECNUM=1 $ $ $ remove MPC entries from GEOM4 DO WHILE (RECNUM>0) $ PARAML GEOM4//'DTI'/S,N,RECNUM,/1//S,N,ID1 $ PARAML GEOM4//'DTI'/S,N,RECNUM,/2//S,N,ID2 $ EQUIVX GEOM4/GEOM4Z/RECNUM $ IF (ID1=4901 AND ID2=49) THEN $ PARAML GEOM4/GEOM4Z/'TABDEL'/RECNUM/0 $ RECNUM=-1 $ ELSE $( RECNUM=4901 AND ID2=49) RECNUM=RECNUM+1 $ ENDIF $ (RECNUM=4901 AND ID2=49) ENDDO $ (RECNUM>0) MAKEOLD GEOM4Z,GEOM3,,,/GEOM4X,GEOM3X,,,/ 'GEOM4'/'GEOM3'////'GEOM4'/'GEOM3' $ $ $ for post -2 $ ALTER 'OUTPUT2 CSTMX' $ TYPE PARM,,I,N,NP $ IF (GETSYS(NP,403)=0) THEN $ MATMOD GEOM2X,,,,,/IGEOM2X,/13 $ matprn geom4,geom4x // $ $ OUTPUT2 IGEOM2X,GEOM3X,GEOM4X,GEOM1X,BGPDTX//0/OUNIT1//OMAXR/ $ 'GEOM2'/'GEOM3'/ GEOM4 / GEOM1 / BGPDT / $ 'GEOM2'/'GEOM3'/'GEOM4'/'GEOM1'/'BGPDT' $ OUTPUT2 IGEOM2X,GEOM3X,GEOM1X,BGPDTX//0/OUNIT1//OMAXR/ 'GEOM2'/'GEOM3'/ GEOM1 / BGPDT / 'GEOM2'/'GEOM3'/'GEOM1'/'BGPDT' $ ELSE $ ALTER 'OUTPUT2 GEOM2X' $ ENDIF $ $ $ for post -1 $ ALTER 'ELSE IF ( POST=-1' $ IF (GETSYS(NP,403)=0) THEN $ MATMOD GEOM2X,,,,,/IGEOM2X,/13 $ OUTPUT2 GEOM1X,IGEOM2X,GEOM3X,GEOM4X,EPTX//OTAPE2/OUNIT1//OMAXR/ GEOM1 / GEOM2 / GEOM3 / GEOM4 / EPT / 'GEOM1S'/'GEOM2S'/'GEOM3S'/'GEOM4S'/'EPTS' $ OUTPUT2 MPT,DIT,DYNAMICS//0/OUNIT1//OMAXR $ IF ( POSTEXT='YES' ) OUTPUT2 BGPDTX//0/OUNIT1//OMAXR/BGPDT/////'BGPDTS' $ ELSE $ ALTER 'OUTPUT2 BGPDTX' $ ENDIF $ ENDALTER $ ECHOON $ 1-18435641 2005.0.2 SOL 600/installation - Long Installation Paths - ** Severe Marc Translator Warning ** For SOL 600, long path names for the location of the marc executable will cause a failure on Windows. The default installation paths for MSC.Nastran V2005 are longer and thus this problem is exacerbated. ** Severe Marc Translator Warning ** Script to run Marc not in expected directory \\benelux1\applic\windows\msc.software\msc.nastran\2005\msc2005\marc\tools\run_m 1-18482126 2005.0.2 Optimization/Design Sensitivity - DESVAR - SFM 3001 (DOPR4) indicating DTOS2J does not exist An optimization job that has a DESVAR Case Control command that only activates shape variables but both sizing and shape variables are present, may fail in DOPR4 with SYSTEM FATAL MESSAGE 3001 indicating that DTOS2J does not exist. Avoidance: Apply the following dmap alter: compile predom list alter 'dopr1' type parm,,i,n,protyp $ protyp = 0 1-18491202 2005.0.2 Documentation/QRG - MCFRACTION - Wrong Description of Item SCALED Under the QRG description of the MCFRACTION Case Control Command, SCALED should be described as the " PROJECTION DIVIDED BY THE LARGEST MAGNITUDE OF MODAL RESPONSE". 1-18491296 2005.0.2 MCFRACTION - Incorrect description of "SCALED RESPONSE MAGNITUDE" in the f06 Description of the "SCALED RESPONSE MAGNITUDE" under the MODAL CONTRIBUTION FACTORS output in the f06 is not correct. It should read: PROJECTION MAGNITUDE DIVIDED BY THE LARGEST MAGNITUDE OF THE MODAL RESPONSE. 1-18501346 2005.0.2 Dynamic Analysis - MEFFMASS fails if the a-set is comprised entirely of q-set The modal effective mass calculation (MEFFMASS Case Control command) will terminate with the following message if the a-set is comprised entirely of q-set. SYSTEM FATAL MESSAGE 3007 (3007) ILLEGAL INPUT TO SUBROUTINE MPYAD In GDACMS (domainsolver acms) and PARAM,AUTOQSET,YES, it is typically the case that the a-set of the residual structure is comprised entirely of q-set. This condition can also occur with component mode analysis. Avoidance: 1. For non-GDACMS problems, insert some physical degrees-of-freedom on the ASETi entries. 2. For GDACMS problems or PARAM,AUTOQSET,YES problems, either switch to MDACMS (domainsolver acms (partopt=dof)) or insert the following DMAP alter: compile augqset alter 'usetq'(2) type parm,,logi,n,npl $ moduset ,,usetq/usetz/'move'/'l'/'o' $ equivx usetz/usetq/-1 $ compile phase0 alter ' gp4 '(,-1) if ( seid=0 ) atqset=false $ endalter If you are running PARAM,AUTOQSET,NO with GDACMS then insert SENQSET,0,0 in the Bulk Data section. 1-18504349 2005.0.2 Online Documentation - V2005 Index is labelled as "MSC.Nastran 2004" The "start point" for the MSC.Nastran v2005 documentation on the Online Documentation cd is labled "MSC.Nastran 2004 Books". The links for the Installation & Operations Guide, QRG, and Release Guide DO bring up the v2005 documentation. The link to the DMAP Guide is missing. New graphic pages without the year are to be used for future releases. 1-18511311 2005.0.2 MDACMS - MCFRACTION - Wrong Answers for MFRACTION with MDACMS If MCFRAC is requested with MDACMS (DOMAINSOLVER ACMS(PARTOPT=DOF)) then wrong answers may result in the MCFRAC output. Avoidance: There are 2 possible avoidances: 1. Specify an additional output request, like DISP, for the same points specified on the MCFRAC command. 2. Insert the following DMAP alter: compile semfreq alter 'call fdrmgen','' if ( sparseph='yes' and mdacms ) CALL FDRMGEN, USET,VGFD,CASERS,USETD,GM,GOt,goq,, MSF,,,,BSF,,,,KSF,K4SF,,,,asf,adsf, MMG,,BMG,,KMG,K4MG,,KDMG,KDSF,, MSS,,BSS,,KSS,K4Ss,,kdss,yg, ects,bgpdts,sils,xycdb,matpool,pg,dynamics,casecc, slist,emap,maps,,,,,mmcdb,oint,pelsets, pmyg,pbyg,pkyg,ajp,,nzyg,/ ,,,,,,, MSF1,BSF1,KSF1,mss1,bss1,kss1,MMG1,BMG1,KMG1,,,, vspcg,vmpcg,v01p,v01dr,vpg,vgdr,vmcfg,,,/ APP/APP/SOLTYP/FALSE/false/NOOSET/NOA/NOMSET/ S,DOMPCF/S,DOSPCF/NOSSET/NOUE/S,DOMPCFFD/ S,DOSPCFFD/FALSE/FALSE/rsonly/' '/ s,spdrs/s,spdrm/pexist/false/s,spdr/adptindx/true $ type parm,nddl,logi,n,seindr $ seindr=true $ add5 vpg,vmcfg,v01p/vxx $ equivx vxx/v01p/-1 $ endalter 1-18516872 2005 Submittal - mem=2800mb on NEC SX-6(SUPER-UX 13.1), SFM7620 occurs. MSC.Nastran 2004.0.6 (2004r2) and 2005.0.0 (2005 R1) on Nec SX-6 computers may fail with the fatal message shown below when a large memory request (mem=2800mb) is made. This error has been corrected in 2005.0.1 delivered on the 2005R1a cd. *** SYSTEM FATAL MESSAGE 7620 (GP3D) Dynamic memory block has incorrect checksum 1-18527891 2005.0.2 MDACMS - DMP, NUMDOM - K-PARTITIONING FAILED, Possble Wrong Answers If the user specifies a relatively large value for the number of domains, numdom, for a small problem in mdacms, the partitioner may fail and in rare cases produce wrong answers. When failure does happen the only message is "K-PARTIONING FAILED". Nevertheless MDACMS continues. Avoidance: Do no specify high values of numdom for small problems. Do not deviate significantly from the defaults. 1-18569569 2005.0.2 Model Checkout/Superelements - RBE3, PARAM,CHECKOUT,YES - Bad diagnostics with SELOC PARAM,CHECKOUT,YES may give bad diagnostic information when SELOC is present. The bad diagnostics is for the EMH matrix which is an equilibrium check on MPCs and constraint elements. The bad diagnostics will indicate a modeling error when no error exists. . Avoidance: Use another checking procedure, such as applying SPCDs in static analysis that should move the structure as a rigid body. If the MPCs and constraint elements pass this test they meet the equilibrium requirement. 1-18570326 2005.0.2 Elements - CWELD - Missing UFM 7549 (SEPWLD) Impropely defined cweld elements where the projection onto the surface cannot be found may not be trapped and the job may fail unexpectedly. Avoidance: There is no avoidance. 1-18589051 2005.0.2 Optimization/Design Sensitivity - DRESP2 with BETAMATCH referenced by DESSUB - SFM 3001 When an optimization job with BETA/MATCH DRESP2 response, it may fail in DOPR1 with SFM 3001 when the response is referenced by a DESSUB command. Avoidance: Remove the offending DESSUB entry. 1-18622044 2005.0.2 Topology Optimization - TOPVAR, PWELD - Poor Message MSC.Nastran 2005 topology optimization does not have a good fatal error message if the PID entry referenced on a TOPVAE entry does not exist. 1-18625541 2005.0.2 Postprocessing - param,post - UIM 4114 when writing large data blocks written to op2 file When writing data blocks larger than 1GW to an op2 file in binary format, the UIM 4114 data fields will overflow, causing '*********' to be put in the messages. The correction is to accumulate the values in INTEGER*8 variables and to change the format statements to I12. This will allow data blocks up to 1TW to be written to the op2 files without any UIM 4114 data field overflow. For binary mode OP2 files, this was fixed as part of the code turned in to fix quality number 1-18605381. For the time being, other possible error locations have not been fixed because it has been determined that the possibility of the error occurring is very low. 1-18635621 2005.0.2 Mass - NSM1 and NSML1 have alternate forms which do not allow continuation - Missing Fatal Message Tthe alternate forms of the nsm1 and nsml1 entries were designed and documented not to allow for continuation entries. If the user does have a continuation entry, the entire entry is processed as the basic form with a single ID. 1-18636381 2005.0.2 Optimization/Design Sensitivity - Problems when a designed property is zero in SOL 200 The design optimization capability in SOL 200 of MSC.Nastran applies move limits to the properties when solving the approximate optmization problem. If the baseline property is 0.0, the move limits can be very small with the result that a small movement in the design variables will result in a violated constraint. Avoidance: Avoid starting designs that result in a zero property value. Examples are the design of an I12 term in a beam starting from a cross setcion that has a plane of symmetry or the warping coefficents in a PBEAML with a box section type that is square. 1-18640031 2005 Eigenvalue Analysis - EIGRL, MAXSET - Nan values in Eigenvalue Table on Nec SX6 For most real world problems the NEC SX6 system's architecture is such that it realizes a performance gain when MAXSET on the EIGRL entry is set to 15 rather than the default value of 7 used on most other machines. For small problems, nastran will automatically lower the MAXSET value. One small test problem has been found that contained two static subcases (STATSUB) followed by two eigenvalue analysis where the value was lowered to 8 and it should have been lowered to 7. This resulted in Nan's being printed in the Eigenvalue summary table. Avoidance: If this problem is encountered, manually set the MAXSET value to one lower than what is reported for "BLOCK SIZE USED". Solving the eigenvalues for the two sucases in separate runs also avoided the problem. This problem has been corrected in 2005.0.1 delivered on the 2005 R1a cd. 1-18642547 2005 Cyclic Frequency Response - SOL 118, RESTART - Output Labled as Real instead of Complex on Nec SX6 A restart of SOL 118, Cyclic Direct Frequency Response in Version 2005 on Nec SX6, may result in output being labled as Real instead of Complex. Avoidance: Run the job as a cold start. This error is fixed in Versin 2005.0.1 delivered on the 2005 R1a cd. 1-18642630 2005 Superelement Component Mode Synthesis - PARAM,METHDCRMS - UWM 8592 (REIG), V2005 Nec SX6 Only If param,methcrms is specified in a superelement eigenvalue analysis on V2005 Nec SX6, then the job may fail with the message: *** USER WARNING MESSAGE 8592 (REIG) THE METHOD RECORD IN CASE CONTROL IS MISSING OR INCORRECT. THIS WILL CAUSE THE FOLLOWING FATAL ERRORS. USER ACTION: PUT A METHOD ENTRY IN CASE CONTROL WHICH POINTS TO AN EIGR, EIGRL, OR EIGB RECORD IN BULK DATA. *** USER FATAL MESSAGE 3032 (READ) UNABLE TO FIND SELECTED SET ( 2000) IN TABLE (EED ) IN SUBROUTINE (REIG). Avoidance: Other than not specifying this parameter, there is no avoidance. 1-18642659 2005 Miscellaneous - mem= = - SFM 7620 (GP3D) on Nec SX6 If a mem= is specified to be greater than 2800mb on MSC.Nastran 2004r2 or 2005 on Nec SX 6 the job may fail with the message: *** SYSTEM FATAL MESSAGE 7620 (GP3D) Dynamic memory block has incorrect checksum Avoidance: Make a smaller memory request 1-18643741 2005.0.2 Superelements - Multi-MASTER method, Shell Normals (SNORM) - Wrong Answers Shell normals computed in the "SEMAP" run are not being saved for the subsequent restart run and this may lead to poor answers. Avoidance: Insert the following DMAP alter in all runs: compile phase0 alter 1 type db gpsnt $ endalter 1-18688331 2005.0.2 Elements - CQUAD4, TRIA3, K6ROT - Incorrect drilling stiffness for membrane only elements. In MSC.Nastran Version 2004, the default for K6ROT was changed from 0. to 100. The new default works well for most models, but membrane only elements should use a K6ROT of 0.0. Avoidance: For models created entirely of membrane only elements, set param,k6rot,0.0. 1-18691831 2005.0.2 ACMS - UFM 740 (RDASGN) when using PACMS with PARTOPT=GRID In MSC.Nastran Version 2004.5 (2004r3) and Version 2005 if PACMS is used with PARTOPT=GRID then the job may fail with USER FATA MESSAGE 740 (RDASGN). *** USER FATAL MESSAGE 740 (RDASGN) UNIT NUMBER 12 HAS ALREADY BEEN ASSIGNED TO THE LOGICAL NAME OP2 USER ACTION: CHANGE THE UNIT NUMBER ON THE ASSIGN STATEMENT AND IF THE UNIT IS USED FOR PARAM,POST,<0 THEN SPECIFY PARAM,OUNIT2 WITH THE NEW UNIT NUMBER. AVOID USING THE FOLLOWING UNIT NUMBERS THAT ARE ASSIGNED TO SPECIAL FILES IN MSC.NASTRAN: 1 THRU 12, 14 THRU 21, 40, 50, 51, 91, 92. See the MSC.NASTRAN INSTALLATIONS/OPERATIONS GUIDE section on MAKING FILE ASSIGNMENTS for reference. Avoidance: Apply the following dmap alter: : compile phase0 $ alter 'OUTPUT2 EQEXIN//0/OUNIT2//OMAXR', '' $ if (procid=1) OUTPUT2 EQEXIN//0/OUNIT2//OMAXR $ endalter 1-18693301 2005.0.2 Postprocessing/Optimization - NDDL description of DOPTPRM is incomplete The NDDL description of the DOPTPRM is incomplete and this may cause the entry to be mis-translated by the UGS/I-Deas translator. Avoidance: There is no practical avoidance. 1-18693701 2005.0.2 Elements - CQUADR - Stress output mis-labeled In MSC.Nastran2005, if STRESS (CENTER) is specified for a CQUADR entry, "von mises" stress output in the f06 file, will be outputted as "max shear." STRESS(CENTER,VONMISES) S T R E S S E S I N Q U A D R I L A T E R A L E L E M E N T S ( Q U A D R ) ELEMENT FIBER STRESSES IN ELEMENT COORD SYSTEM PRINCIPAL STRESSES (ZERO SHEAR) MAX ID. DISTANCE NORMAL-X NORMAL-Y SHEAR-XY ANGLE MAJOR MINOR SHEAR 0 3300 -5.000000E-02 2.400000E+04 2.400000E+04 0.0 90.0000 2.400000E+04 2.400000E+04 2.400000E+04 5.000000E-02 2.400000E+04 2.400000E+04 0.0 90.0000 2.400000E+04 2.400000E+04 2.400000E+04 STRESS(CENTER,MAXS) S T R E S S E S I N Q U A D R I L A T E R A L E L E M E N T S ( Q U A D R ) ELEMENT FIBER STRESSES IN ELEMENT COORD SYSTEM PRINCIPAL STRESSES (ZERO SHEAR) MAX ID. DISTANCE NORMAL-X NORMAL-Y SHEAR-XY ANGLE MAJOR MINOR SHEAR 0 3300 -5.000000E-02 2.400000E+04 2.400000E+04 0.0 90.0000 2.400000E+04 2.400000E+04 6.511982E-10 5.000000E-02 2.400000E+04 2.400000E+04 0.0 90.0000 2.400000E+04 2.400000E+04 6.511982E-10 1-18710151 2005.0.2 Data Recovery - MCFRACTION - Missing Output when insufficient memory. If insufficient memory is allocated, MCFRACTION output may be missing. Avoidance: Allocate more memory. 1-18712781 2005.0.2 Distributed Memory Parallel - Frequency Domain Lanczos may hang on 32 bit linux Jobs running SOL 103 Distributed Memory Parallel (DMP) in the frequency domain on 32-bit Linux systems may fail. The symptom of failure is that the parallel processes hang indefinitely until killed manually. Frequency domain parallel is invoked via the following DOMAINSOLVER command: DOMAINSOLVER MODES (PARTOPT=FREQ) No other MSC.Nastran platform exhibits this behavior. Avoidance: Change the number of DMP processes assigned to the task. For example, if the job fails (hangs) with "dmp=4" then resubmit the job with "dmp=3" or "dmp=2". 1-18756447 2005.1 Postprocessing - PLOT ignored for Failure Index and Strength Ratio MSC.Nastran ignores the PLOT command for the OEFIT and OESRT datablocks. For large models this results in a large amount of data being written to the f06 file 1-18781681 2005.0.2 Optimization/Design Sensitivity - Job failed with PNAME/PBxSECT combo not supported For PBMSECT/PBRSECT, thcikness(es) for the CP and OP forms can be selected as design variable in SOL 200 job. Except the default thickness, all other thickness must be given an ID number. SOL 200 jobs without ID'd thickness as design variable failed with PNAME and PBxSECT combination not supported message. Avoidance: There is no workaround for this problem. 1-18791521 2005.0.2 Optimization/Design Sensitivity - DRESP2 with FUNC=BETA - SFM 3002 (DSTAP2 if DSA print is turned on When an design sensitivity job (DSAPRT(END=SENS) or PARAM,OPTEXIT,4) has a DRESP2 response with FUNC=BETA/MATCH, it may fail in DSTAP2 with SFM 3002. Avoidance: Use the combination of DRESP2 and DEQATN to perform Min/Max or matching data tasks. 1-18805654 2005 Large Jobs - MEM greater than 2 gig leads to Terminating, Received signal 11 SIGSEGV MSC.Nastran 2005 may fail on Sunos and issue the message below if more than 2 gig of memory is requested. *** TERMINATING /usr/local/msc/msc2005/solaris/analysis *** Received signal 11 SIGSEGV time: command terminated abnormally. Avoidance: Either request less than 2 gig of mem or obtain a corrected system at: http://www.mscsoftware.com/support/software_updates/index.cfm#nastran 1-18809851 2005.0.2 Postprocessing - RBE1, MAKEOLD, PARAM,POST - BE1 is not being converted by MAKEOLD module The RBE1 element is not being converted by the MAKEOLD module under PARAM,POST,-1 or -2. This may result in the RBE1 element not being properly read in or ignored by post-processors. Avoidance: Use RBE2 or RBE3 element. 1-18811301 2005.0.2 Optimization/Design Sensitivity - PBARL, PBEAML dimensions are incorrectly defined for the BOX. Table 2-5 of the MSC.Nastran User's Guide for Design Sensitivity and Optimization lists the constraints that are generated interrnally for different beam section types in the beam library (PBARL and PBEAML). The constraints are incorrect for the BOX section type. These should be: 2.0 * DIM4 - DIM1 2.0 * DIM3 - DIM2 The code has implemented the constraint specified in the table and, hence, is incorrect as well. The results is that it is possible for the optimizer to think the cross section dimensions are okay when in fact, they are producing physically meaningless beam properties (e.g, negative cross sectional areas). Avoidance: If possible, put limits on the design variables that preclude it from achieveing designs where DIM1 < 2 * DIM4 or DIM2 < 2*DIM3. Alternatively, DRESP2 entries can be used to supply the correct constraint conditions. 1-18815731 2005.0.2 Documentation/QRG - CBUSH - grounded - missing documentation A remark should be added to the Quick Reference Guide description of the CBUSH element that that is similar to remark 1 of the CELASi element that states that that a grounded terminal will develop when GA or GB is missing. 1-18826341 2005.0.2 SOL 600 - PLOAD4 - Wrong Answers In MSC.Nastran 2005 SOL 600, "PLOAD4" entries are converted to "0" type loads as defined on the Marc "DIST LOADS" entry regardless of which face is being loaded. Using the CTETRA element (element type 127 of MSC.Marc) as an example, the MSC.Marc "DIST LOADS" entry has the definition for the 1st field of 3rd data block:. 0--> Uniform pressure on face 1-2-3 1--> Nonuniform pressure on face 1-2-3 2--> Uniform pressure on face 1-2-4 3--> Nonuniform pressure on face 1-2-4 4--> Uniform pressure on face 2-3-4 . 1-18826551 2005.0.2 Optimization/Design Sensitivity - Formatted Prints of Total Strain Energy Sensitivity - SFM 3007 If the DSAPRT case control request is used to ask for formatted design sensitivty output and one of the responses is TOTSE (total strain energy), system fatal message 3007 is encountered. Avoidance: Unformatted design sensitivity output can be requested using OPTEXIT = 4 or 7 1-18828854 2005.0.2 Transient Analysis - TLOAD1 - Wrong Answers, US0 and VS0 values ignored The new Version 2005 US0 and VS0 fields on the TLOADi entries for specifying initial displacement and velocity are not recognized on the TLOAD1 entry and thus give wrong answers. TLOAD2s do recognize these fields. 1-18829138 2005.0.2 Superelements - PARAM,AUTOQSET - SFM 3007 (EFFMAS) issued when AUTOQSET is used Superelement models using PARAM, AUTOQSET, YES will fail with *** SYSTEM FATAL MESSAGE 3007 (EFFMAS) / ILLEGAL INPUT TO SUBROUTINE MPYAD if the Case Control includes a MEFFMASS request and PARAM, AUTOQSET, YES is included in the model. Avodiance: Revert to explicitly specifiying SPOINT/SEQSETi . 1-18831941 2005.0.2 Optimization/Design Sensitivity - DRSPAN - Response ID not found In SOL 200, DRSPAN can be utilized to select DRESP1s from multiple SUBCASEs for referencing on DRESP2 or DRESP3. This is an advanced capability to generate synthetic responses. However, SOL 200 job may fail with a message that indicates response ID not found if the DRSPAN did not appear in the first few SUBCASEs. Avoidance : Move SUBCASEs without DRSPANs to the bottom of the case control deck 1-18835942 2005.0.2 Documentation/QRG - PBUSH Remarks 4 and 5 under the PBUSH description in the Quick Reference Guide should be improved to read as follows: 4. The element stresses are computed by multiplying the stress coefficients with the recovered element forces. Stress = F * SA, or M*ST. 5 The element strains are computed by multiplying the strain coefficients with the recovered element displacements. Strain = El_disp*EA or El_rot*ET. 1-18859441 2005.0.2 Adams Modal Neutral File - ADAMSMNF, PARAM,GRDPNT,0 - Wrong inertia values The nastran to adams flex interface, ADAMSMNF command, with param,grdpnt,0 and coordiantes will cause wrong inertia values Avoidance: Apply the following dmap alter: compile admflex $ alter 'TYPE PARM,,LOGI' TYPE PARM,,RS,N, W $ TYPE PARM,,CS,N, CW $ alter 'GPWG BGPDTS,CSTMS','' IF ( GRDPNT>=0 ) THEN $ $ REMOVE WTMASS: W = 1./WTMASS $ CW = CMPLX(W) $ ADD MGG,/MGGBW/CW $ $ CHECK MASS IN BASIC COORDINATES, WITH WTMASS REMOVED: IF ( ADMCHECK<>0 ) THEN $ MESSAGE //' MJJEW CHECKOUT:' $ MATGPR GPLS,USET,SILS,MGGBW//'G'/'G' $ ENDIF $ GPWG BGPDTS,CSTMS,,MGGBW,,/OGPWGW/ 0/1.0//SEID $ CALL HARDWIRED TO ORIGIN OF BASIC SYSTEM WITH WTMASS=1.0 ENDIF $ GRDPNT>=0 1-18892014 2005.0.2 Aeroelastic Analysis - AEPARM - In the Quick Reference Guide, Remark 2 for the AEPARM entry states the UNITS label is optional. However, IFS13P produces a fatal error unless character data is entered. Avoidance: Place data in the UNITS field. This is used for labelling and does not effect numerical results. 1-18895621 2005.1 Element Strain Energy - ESE, TINY - Filter does not work PARAM,TINY is being ignored after the first subcase and the summaries are not prined. Negative strain energies due to roundoff cause the associated elements to produce a large percent of the "negative energy". NJ Teng: There is an initiation problem in subroutine IFP1E. 1-18905291 2005.0.2 Superlements - EXTSEOUT - Bad DMIG matrix leads to UFM 316 in a subsequent assembly run An external superlement (EXTSEOUT) run may produce a bad K4AAX DMIG matrix, leading to failure with USER FATAL MESSAGE 316 in a subsequent assembly run. 1-18907271 2005.0.2 ACMS - SOL 103 with Matrix Domain ACMS may fail (System Fatal Message 4276, QOPEN) SOL 103 with Matrix Domain ACMS may fail with SYSTEM FATAL MESSAGE 4276 (QOPEN) if no loads are pressent. Avoidance: Include the following DMAP alter: compile modefsrs alter 'if (novasprc = -1)', '' $ paraml pg//'null'////s,n,nullpg $ if (novasprc = -1 and nullpg > -1) then $ endalter 1-18908795 2005.0.2 Superelements - EXTSEOUT - Extra Output An EXTSEOUT SE creation run outputs the K4 damping matrix even though only the stiffness and mass matricies were explicitly requested to be output. Similar problems occur if the user requests only stiffness or mass matrix to be output Avoidance: Insert the following DMAP alter: compile phase1dr alter 'extfs' $ type parm,,logical,n,extstif $ alter 'extmass'(2,-1) $ extstif =(MOD(extseout ,2)>0) $ alter 'extmass'(3,-1) $ extstif=true $ alter 'call extout','' $ if (extstif) then $ equivx kaa/kaax/-1 $ else $ delete /kaax,,,, $ endif $ if (extmass) then $ equivx maa/maax/-1 $ else $ delete /maax,,,, $ endif $ if (extdamp) then $ equivx baa/baax/-1 $ else $ delete /baax,,,, $ endif $ if (extk4) then $ equivx k4aa/k4aax/-1 $ else $ delete /k4aax,,,, $ endif $ if (extloads) then $ equivx pa/pax/-1 $ else $ delete /pax,,,, $ endif $ call extout kaax,maax,baax,k4aax,pax,gpak,gdak, eqexins,uset,bgpdts,cases,got,goq,gm,msf, bsf,ksf,k4sf,cmlama,ects,sils,uoo,cstms, mpts,dit,ett,est,ibulk,vgfs,aaa/ dum/lusets $ 1-18926554 2005.0.2 Loads - GRAV, TEMP(INIT) - Wrong Answers In MSC.Nastran Version 2005, if a TEMP(INIT) references a temperature load with the same ID as a GRAV load the GRAV load will be doubled. Avoidance: Remove TEMP(INIT) or use a unique load id for TEMP(INIT). 1-18933661 2005.0.2 SOL 600 - Missing output for adaptive method Through both the MSC.Patran and MSC.Nastran SOL 600 interface, when the user asks for output for "each increment" of results, SOL600 will only produce the 1st and final increment of results. 1-18973169 2005 Elements - SNORM, CQUAD4 - Inconsistent Corner Stresses The default value of SNORM was changed to 20.0 in Version 2001. Setting SNORM to 0.0 in Version 2001.0.7 (2001r3) through Version 2004.5 (2004r3) could lead to incorrect QUAD4 corner stresses. Avoidance: Leave SNORM to the default value, do not set to 0.0. 1-18976345 2005.0.2 SOL 600 - PARAM,TSTATIC, NLAUTO - NLAUTO impropely translated in SOL 600 In SOL 600,129 NLAUTO should not be used for SOL 600 dynamics problems except in the special case where there are no dynamic loads (initial conditions only). In that case it is acceptable (but not recommended) to use NLAUTO. Furthermore, in SOL 600,129 it is not possible to handle TSTATIC, so it is skipped after issuing the approporate warning. 1-18988374 2005.0.2 SOL 600 - Severe translator error NONLINEAR LOAD not supported If the 1st word AFTER a "$" comment demarkation in the Case Control is the word "Nonlinear" as in: SUBCASE 100 $ Nonlinear Subcase Then SOL 600 in v2005 will have a SEVERE translator error and complain that you have a NONLINEAR Load Case Control request when in fact there isn't one. Avoidance: Have ANYTHING else as the 1st word - or add a "-" or other charachter in front. 1-19000411 2005.0.2 SOL 600 - Gravity Loads, Cylindrical or Spherical Coordinate System leads to Wrong Answers. SOL 600 does not support material coordinate systems specified in cylindrical o