讲义课件msc培训section8

Section8FileManagementSectionFileManagementSectionPAGETheNASTRANStatement4FileManagementSection(FMS)6FMSOverview8DBSETs9RequiredDBSETs11TypicalFilesGenerated12Restarts14AutomaticRestarts(SOLs101-200)15RestartExample17PartialColdStartF04File18PartialColdStartF06File20FileManagementSection(cont.)PAGERestartExample–Method121RestartExample–Method223PartialRestartF04File25PartialRestartF06File27RestartExampleSummary28ManipulatingTheDatabase29ASSIGNandINITStatements31Examples–ASSIGNandINIT33EXPANDStatement36Example–EXPANDStatement37Example–AssigningaFORTRANFile39THENASTRANSTATEMENTTheNASTRANstatementisamemberoftheFMSandisoptional.Itshouldbeusedtomodifyoperationalparameters(systemcells).Ifused,itisbesttoplaceitasthefirstentryintheinputfile.Usedonlyinexceptionalcircumstancesandisnotneededformostruns.Forexample,tochangethebuffsize,addeitherNASTRANBUFFSIZE=12929

or

NASTRANSYSTEM(1)=12929THENASTRANSTATEMENT(Cont.)Forexample,tochangethebuffsize,addeitherNASTRANBUFFSIZE=12929

or

NASTRANSYSTEM(1)=12929SeetheMSC.NastranQuickReferenceGuide,Section1,foracompletelistinganddescriptionofthemachine-independentsystemcells.FILEMANAGEMENTSECTION(FMS)TheFMSisoptionalandmaynotbeneededformanyproblems.UsedtoinitializeorattachexistingMSC.NastrandatabasesandFORTRANfilesTheFMScommandsworksthesameforallplatformsFILEMANAGEMENTSECTION(FMS)TypicalapplicationsInitializingthedatabase(name,size,location,etc.)Splittingupadatabaseintoseveralsmallerdatabasesets,whichallowslargeproblemstobesolvedonmachineswithlimiteddiskspaceExpandanexistingdatabase.RestartControl.SeeSection2oftheMSC.NastranQuickReferenceGuidefordetaileddescriptionoftheFMS

FMSOVERVIEWProvidesuserdynamicfileallocationCreation/attachmentofdatabasefilesCreation/attachmentofFORTRANfilesProvidesdatamanipulationRestartingInitializingandexpandingthedatabaseManagementofdataonthedatabaseDatabasedirectoryprintsProvidesmeansofattachingexternaldatabasesDBSETSADBSETisacollectionoffileswhichareusedforapurposebytheprogramTheMSC.NastrandatabaseconsistsofseveralDBSETswhichareautomaticallycreatedbytheprogram:MASTER-Masterdirectory-containsthedescriptionofthedatabase,alistofallfilescontainedinallDBSETsusedbytherun,anda"tableofcontents"foreachDBSETs.DBALL-PermanentdataisstoredherebydefaultDBSETS(cont.)SCRATCH-Temporaryworkingfilesforscratchdatablocks-automaticallydeletedattheendoftherunSCR300-Temporaryworkingfilesforthemodules-automaticallydeletedattheendoftherunREQUIREDDBSETSMASTERandDBALLmustberetainedifthedatabaseistobeusedinasubsequentrestartrun.Ifnorestartisplanned,theymaybedeleteduponcompletionoftherun.ForautomaticdeletionofMASTERandDBALL,usePARAM,DBALL,SCRATCHorsubmitwithscr=yes.TYPICALFILESGENERATEDFilesgeneratedbysubmittingtheinputfiletest.dat:

test.MASTER

test.DBALL

test.f04

test.f06

test.log test.pch test.plt

test.op2

test.xdbtest.pch(punchfile),test.plt(plotfile),test.op2(output2file),andtest.xdb(xdbfile)arecreatedbyuserrequests.TYPICALFILESGENERATED(Cont.)Ifnorestartsordatabasemanipulationareplanned,theusermayspecifythatthescratchdirectorybeusedforMASTERandDBALL,filesonthesubmittalcommand.Theyareautomaticallydeleteduponcompletionoftherun.Example

nastrantestscr=yesRESTARTSRigidFormatSolutions(SOLs1thru12)Thesesolutionsnolongersupportrestarts.StructuredSolutions(SOLs101,103,etc)IncludeautomaticrestartcapabilitiesMinimaluserinputrequiredforrestartsProgramdetectswhathaschangedinthemodelandprocessaccordingly.AUTOMATICRESTARTS(SOLs101-200)Eachrestartresultsinanewversiononthethedatabase.ThepreviousversionbeingusedforrestartisdeletedattheendoftherununlesstheuserspecifiesKEEPontheRESTARTentry.TheentireBulkDataisstoredonthedatabase.OnlychangesandadditionstotheBulkDataarerequiredintheinputfilefortherestart.ThenewBulkDataentriesaremergedwithacopyoftheBulkDataonthedatabase.Allsolution-relatedCaseControlcommandsmustbeintherestartfile.TheprogramcomparestheBulkDataandCaseControlfortherestartrunwiththatforthepreviousversionthatistoberestarted.Theprogramdecideswhatneedstobecalculatedorrecalculatedforthecurrentproblem.AUTOMATICRESTARTS(SOLs101-200)(Cont.)Onlythenecessaryoperationsareperformedtosolvetheproblem.RestartsareinvokedusingtheRESTARTstatementintheFMS.RESTARTEXAMPLE

Let’susethestiffenedplatemodel(workshop#5)forarestartexampleDatabasemustbesavedinthecoldstartrune.g.submittalcommand(assumingfilenameissoln5.dat)nastransoln5scr=noPARTIALCOLDSTARTF04FILEPARTIALCOLDSTARTF04FILE(cont.)

PARTIALCOLDSTARTF06FILE

RESTARTEXAMPLE—METHOD1DATARECOVERYRESTARTREQUESTFORELEMENTFORCEOUTPUTRESTARTEXAMPLE—METHOD1(cont.)SubmittalCommandnastransol5adbs=soln5Theabovesubmittalcommandassumesthatthecoldstartfilenameissoln5.datandtherestartfilenameissoln5a.datRESTARTEXAMPLE—METHOD2DATARECOVERYRESTARTREQUESTFORELEMENTFORCEOUTPUTRESTARTEXAMPLE—METHOD2(cont.)SubmittalCommandnastransol5bTheabovesubmittalcommandassumesthatthecoldstartfilenameissoln5.datandtherestartfilenameissoln5b.datNotethattheattachmentofthedatabaseisdefinedinsidethefilesoln5b.datusingtheanassignstatementPARTIALRESTARTF04FILE

PARTIALRESTARTF04FILE(cont.)

PARTIALRESTARTF06FILE

RESTARTEXAMPLESUMMARYThepreviousrestartusedthesamedatabaseasthecoldstart.Version1onthedatabasewasdeletedbecausetheKEEPoptionwasnotused.Ifanotherrestartisperformed,itdefaultstothelatestversiononthedatabasewhichisVersion2.Onlydatarecoveryprocessingwasperformedfortherestartruninthissample.USEAUTOMATICRESTARTS-ITCANSAVETIMEANDMONEY!MANIPULATINGTHEDATABASEAllFMSdefaultscanbemodified;however,thedefaultsareadequateformostanalyses.ThelocationandmaximumsizeofthefilesusedforeachDBsetsmaybespecifiedbytheuser.Thedatabasemaybesplitacrossmultiplephysicalfilelocatedondifferentdiskpacksordifferentmachinesmountedonanetwork.MANIPULATINGTHEDATABASE(Cont.)CommonFMSstatementsASSIGN-AssignsphysicalfilenamestoDBsetsorFORTRANfilestobeusedbyotherFMSstatementsorDMAPmodules.INIT-CreatestemporaryorpermanentDBsetsEXPAND-ConcatenatesadditonalDBsetstotheexistingpermenantDBsets.UsedonrestartswhenthepreviousrunfillstheallocatedDBsetsDBCLEAN-DeletespreviousversionsfromthedatabaseDBDIR-PrintsthedatabasedirectorySeeSection2oftheMSC.NastranQuickReferenceGuideforcompletedescriptionoftheFMSstatements.ASSIGNANDINITSTATEMENTSFormat(simplified) ASSIGNdbset_member_name=physical_file_name

INITdbset_nameLOGICAL=(dbset_member_name(p),...)

wherep=maximumnumberofblocksallocatedforthemember-maybespecifiedasBLOCKS(default),megabytes(mb),megawords(mw),kilobytes(kb),orkilowords(kw)Example:

INITDBALL,logical=(DB1(1000mb),DB2(1000mb))

willcreateaDBALL,set,consistingoftwofiles,eachofwhichmaygrowtoamaximumsizeof1000megabytesBlocksizeismachinespecific;seeTheConfigurationandOperationsGuideforthecomputeryouareusing.ASSIGNANDINITSTATEMENTS(Cont.)ThemaximumsizeofthefilesusedinthepermanentDBsetscannotbemodifiedonarestart.AnyDBset(forexample,DBALL)maybeexpandedonarestartbyaddingadditionalfilesusinganEXPANDentry.YoushouldremovetheASSIGNandINITstatementsforexistingpermanentDBSETSontherestart.ThescratchDBsetsmayneedtobeallocatedforeachrunifthedefaultisnotadequate.TheINITstatementmaybeusedwithouttheASSIGNstatementtoallocateaspecificsizetothedefaultDBsetnames.EXAMPLES-ASSIGNANDINITInitializingascratchfilewithamaximumsizeof1000mbblocksontheSCR2directory ASSIGNSCR=’/scr2/test.scratch’

INITSCRATCH,LOGICAL=(SCR(1000mb))

.

.

.InitializingtheDBALLwith2DBseteachwithamaximumsizeof500mbandSCRATCHwith3DBsetseachwithamaximumsizeof2000mbEXAMPLES-ASSIGNANDINIT(Cont.)

ASSIGNDB1=’/home/mydir/sample.db1’

ASSIGNDB2=’/home/hisdir/sample.db2’

ASSIGNSCR1=’/scr/sample.scr1’

ASSIGNSCR2=’/scr/sample.scr2’

ASSIGNSCR3=’/scr/sample.scr3’

$

INITDBALL,LOGICAL=(DB1(500mb),DB2(500mb))

INITSCRATCH,LOGICAL=(SCR1(2000mb),SCR2(2000mb),

SCR3(2000mb))

.

.

.EXAMPLES-ASSIGNANDINIT(Cont.)Note: LowercaseisshownforUNIXmachines.U