3.1 MB - Evernote

More documents

Recommendations

Info

47 Implementation can easily be modelled in any simulation model using an additional GENERATE and TERMINATE block. For instance if a simulation is supposed to be terminated when it reaches a simulation time of 10,000 then an additional GENERATE block is added that generates a single Transaction for the simulation time 10,000 immediately followed by a TERMINATE block that stops the simulation when that Transaction is terminated. This additional set of GENERATE and TERMINATE block can either be added to the end of an existing partition or as an additional partition. All other TERMINATE blocks in such a simulation will need to have a decrement parameter of 0. The following GPSS code shows an example model that will terminate at the simulation time 10,000. PARTITION Partition1,1 sets Termination Counter to 1 … original model partition GENERATE 1,0,10000 generates a Transaction for time 10000 TERMINATE 1 end of simulation after 1 Transaction 5.2 Implementation Phases The following sections will describe the four main development phases of the parallel simulator. 5.2.1 Model Parsing The classes for parsing and validating the GPSS model read from the model file can be found in the package parallelJavaGpssSimulator.gpss.parser. A GPSS model file is parsed by calling the method ModelFileParser.parseFile(). This method returns an instance of the class Model from the package parallelJavaGpssSimulator.gpss that contains the whole GPSS model as an object structure. The Model instance contains a list of model partitions represented by instances of the class Partition and each Partition instance contains a list of GPSS blocks and lists of other entities like labels, queues, facilities and storages that make up the model partition. Global GPSS block references GPSS simulators require a way of referencing GPSS blocks. A TRANSFER block for instance needs to reference the block it should transfer Transactions to. Sequential simulators often just use the block index within the model to refer to a specific block.
48 Implementation But in a parallel GPSS simulator each Logical Process only knows its own model partition. Still a block reference needs to uniquely identify a GPSS block within the whole simulation model and ideally it should also be possible to determine the target partition from a block reference. The GlobalBlockReference class in the package parallelJavaGpssSimulator.gpss implements a block reference that fulfils these criteria and it is used to represent global block references and also block labels within the runtime model object structure and other parts of the simulator. Parser class hierarchy A parallel class hierarchy and the Builder design pattern [22] is used in order to separate the code for parsing and validating the GPSS model from the code that represents the model at the runtime of the simulation. This second class hierarchy is found in the parallelJavaGpssSimulator.gpss.parser package and contains a builder class for all element types that can make up the model structure at runtime. Figure 13 shows the UML diagram of the two class hierarchies including some of the relevant methods. When loading and parsing a GPSS model file the instance of the ModelFileParser class internally creates an instance of the ModelBuilder class, which for each partition found in the model file holds an instance of a PartitionBuilder class and the PartitionBuilder class holds builder classes for all blocks and other entities that are found in the partition. The parsing and validation of the different model elements is delegated to these builder classes. In addition the Factory design pattern [22] is used by the BlockBuilderFactory class that creates the correct builder class for a GPSS block depending on the block type keyword found in the model file. All builder classes have a build() method that returns an instance of the corresponding simulation runtime class for that element. These build() methods are called recursively so that the ModelBuilder.build() method calls the build() method of the PartitionBuilder instances it contains and each PartitionBuilder instance calls the build() method of all builder classes it contains. This delegation of responsibility within the class hierarchy makes it possible to return an instance of the Model class representing the whole GPSS model just by calling the ModelBuilder.build() method. As mention above the package parallelJavaGpssSimulator.gpss.parser is only used to load, parse and verify a GPSS model from file into the object structure used at simulation runtime. For this reason the only class from this package with public
Page 1 and 2:
TRANSACTION-ORIENTED SIMULATION IN
Page 3 and 4:
Table of Content II Table of Conten
Page 5 and 6: IV Table of Content 6 VALIDATION OF
Page 7 and 8: Figures VI Figures Figure 1: Ad Hoc
Page 9 and 10: Tables VIII Tables Table 1: Change
Page 11 and 12: 2 Introduction synchronisation algo
Page 13 and 14: 2 Fundamental Concepts Fundamental
Page 15 and 16: Figure 1: Ad Hoc Grid architecture
Page 17 and 18: 8 Fundamental Concepts In continuou
Page 19 and 20: 10 Fundamental Concepts Two other a
Page 21 and 22: 12 Fundamental Concepts known as st
Page 23 and 24: 14 Fundamental Concepts event execu
Page 25 and 26: 3 Ad Hoc Grid Aspects 16 Ad Hoc Gri
Page 27 and 28: 18 Ad Hoc Grid Aspects resources an
Page 29 and 30: 20 Ad Hoc Grid Aspects means that a
Page 31 and 32: Parallel Transaction-oriented Simul
Page 33 and 34: 24 Parallel Transaction-oriented Si
Page 35 and 36: 4.2 Synchronisation algorithm 26 Pa
Page 49 and 50: 5 Implementation 40 Implementation
Page 51 and 52: 42 Implementation confirm a provisi
Page 53 and 54: 44 Implementation large numerical p
Page 55: 46 Implementation A detailed descri
Page 59 and 60: 50 Implementation GPSS test models
Page 61 and 62: Simulation Controller side 52 Imple
Page 63 and 64: 54 Implementation technique describ
Page 65 and 66: Implementation Euclidean distance b
Page 67 and 68: 58 Implementation chain at the corr
Page 69 and 70: 60 Implementation The algorithm wil
Page 71 and 72: No Start Is Active Object body acti
Page 73 and 74: 5.3.2 GVT Calculation and End of Si
Page 75 and 76: 66 Implementation provisional simul
Page 77 and 78: Implementation relatively basic per
Page 79 and 80: 70 Implementation log4j.logger.para
Page 81 and 82: proactive-log4j 72 Implementation T
Page 83 and 84: 74 Implementation Memory Allocation
Page 85 and 86: 76 Validation of the Parallel Simul
Page 93 and 94: 6.4 Validation 4 84 Validation of t
Page 97 and 98: … LpccEnabled=true LpccClusterNum
Page 99 and 100: Validation 5.2 Validation of the Pa
Page 105 and 106: 7 Conclusions 96 Conclusions Even s
Page 107 and 108:
References 98 References [1] Amin K
Page 109 and 110:
[19] Krafft G. Parallelisation of T
Page 111 and 112:
Appendix A: Detailed GPSS Syntax 10
Page 113 and 114:
Reserved word: DEPART Syntax: [] DE
Page 115 and 116:
Reserved word: SEIZE Syntax: [] SEI
Page 117 and 118:
Setting: LpccClusterNumber Default
Page 119 and 120:
Appendix C: Simulator log4j loggers
Page 121 and 122:
Logger: parallelJavaGpssSimulator.l
Page 123 and 124:
114 Appendix D: Structure of the at
Page 125 and 126:
Appendix E: Documentation of select
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
!"#"$$%$&"'"(!))*+,-$"./#0$! 1$"))
Page 133 and 134:
Page 135 and 136:
!/+/.7/8$ Appendix E: Documentation
Page 137 and 138:
Returns: Appendix E: Documentation
Page 139 and 140:
!"#$%&''$()*)")$ +',)$-)$. #,/. !"#
Page 141 and 142:
!"#$%&'()#%*+,"-*.# Appendix E: Doc
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Constructor Detail !"#$%&'$(#$)*$%+
Page 155 and 156:
Page 157 and 158:
Validation 1.1, output of simulate:
Page 159 and 160:
Validation 2, output of LP: Appendi
Page 161 and 162:
Appendix F: Validation output logs
Page 163 and 164:
Validation 2, output of simulate: A
Page 165 and 166:
Validation 3.1, output of LP1: Appe
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Validation 4, output of LP1: Append
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
simulation for time 2000) (628) 20:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Validation 4, output of simulate: A
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
(135) 19:37:56,477 Total transactio
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
(68) 19:37:56,619 by the transactio
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
(1295) 14:25:22,740 Simulation stop
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
(68) 14:25:22,888 by the transactio
Page 239 and 240:
Validation 6.2, output of LP2: (1)
Page 241:
(32) (1,2) 0 765 Block: TRANSFER 0.
show all

3.1 MB - Evernote

Create successful ePaper yourself

Delete template?

Save as template?