HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:4 o( X& H* L) B6 |9 g) ^" T
9 r+ I' q) s9 y; c public Object buildActions () {# o, N( t1 j9 [7 p) D
super.buildActions();! l( ^" q4 O5 ?& c0 X/ L' F6 V+ o
4 b) r9 b# W [" z2 h: {
// Create the list of simulation actions. We put these in
0 y7 s: L. Z, O+ ^ // an action group, because we want these actions to be8 R# F+ o3 G$ ?' I7 P
// executed in a specific order, but these steps should4 e5 I/ z3 L t- v
// take no (simulated) time. The M(foo) means "The message
" y. u" j3 u; Z% i7 X- t // called <foo>". You can send a message To a particular
! F, p! d) W% t2 w. Y // object, or ForEach object in a collection.. n/ |5 o( ~" y" R4 B. e M% d
, P* Y7 [* [5 `9 Q" }! v // Note we update the heatspace in two phases: first run o" [% F# s- T- F0 [" _' u6 g
// diffusion, then run "updateWorld" to actually enact the
: d. V/ O: @, U1 p7 {8 |: { // changes the heatbugs have made. The ordering here is# |- X6 m( H2 K# [* a# ]0 h9 z
// significant!6 V7 w+ l9 z. U2 D+ x1 S
- w' t" W7 Z# Q7 C; T e! b7 k2 n
// Note also, that with the additional# P" ?; m# c/ c. \5 f
// `randomizeHeatbugUpdateOrder' Boolean flag we can
8 z- W; a) e4 l. a. a6 e! Y // randomize the order in which the bugs actually run5 q- F" C$ k/ N* e8 `8 C( i
// their step rule. This has the effect of removing any
0 \( ?6 }2 r5 ?) K9 r/ `' }1 r // systematic bias in the iteration throught the heatbug
3 Q" p! F5 M6 x' ` // list from timestep to timestep
; ~3 t& q# s4 x' h: E ) P* O. U3 L. E0 p# x7 K: q
// By default, all `createActionForEach' modelActions have+ p5 k# G4 c: Y
// a default order of `Sequential', which means that the
& }$ ?7 q. O: x, a$ b+ c, i // order of iteration through the `heatbugList' will be
+ x2 A. G0 o! s! J/ | // identical (assuming the list order is not changed" t% Z2 U( L4 |) s9 z
// indirectly by some other process)." N8 L; p; c+ E
# y: R. E" U N$ f' _* r modelActions = new ActionGroupImpl (getZone ());; p/ b0 ^+ y x Y+ X
- j+ u. L& D4 c( u3 | try {' w- o0 S+ A' o1 c5 G/ B# ~6 n1 C
modelActions.createActionTo$message
! T" f3 O- x, G6 I! F @$ F4 L (heat, new Selector (heat.getClass (), "stepRule", false));
/ E# ]: |0 n) B! i } catch (Exception e) {; k! b2 i. i h
System.err.println ("Exception stepRule: " + e.getMessage ());( K; [* s S' S* e9 ]3 U
}! b- P3 ]8 \0 H) P. y
1 u7 k9 h: ?! F
try {( H8 S. s7 Y+ u+ J8 |8 u
Heatbug proto = (Heatbug) heatbugList.get (0);
! H! m) K' m ? Selector sel = # ]- F& b+ D+ G9 O0 O1 ^
new Selector (proto.getClass (), "heatbugStep", false); b, Y8 z7 h+ g; u2 E$ a1 _/ \
actionForEach =
1 F1 X% Y& z6 I; T+ ^+ r- L modelActions.createFActionForEachHomogeneous$call7 T2 Q6 P. a3 r: L v( \
(heatbugList,3 y Y7 H1 Z0 ?* X9 q
new FCallImpl (this, proto, sel,
, C5 p- j; A& s3 R- J new FArgumentsImpl (this, sel)));
b4 ?& {' s- v2 I. Z } catch (Exception e) {& J G7 n; {2 E! z" R# ^; X- S
e.printStackTrace (System.err);- A7 Q7 ?4 V3 |1 h( d
}
, k! N N' a) q: T3 d# Q- I: k; d 0 c7 p% ~9 d0 x) P
syncUpdateOrder ();
. R6 R; O3 X: D$ y) N4 Y) d5 H. O- R; e0 D; k
try {
0 y( m; t! I0 N& V# y2 a modelActions.createActionTo$message . l( r8 o8 m$ G; i6 M
(heat, new Selector (heat.getClass (), "updateLattice", false));
' V4 W0 u; W% ~% b' r } catch (Exception e) {1 @; O# x+ R! J2 D1 j
System.err.println("Exception updateLattice: " + e.getMessage ());2 y6 C! \1 m1 L- i+ r: U+ B. D9 b
}
1 M7 ]/ ?8 E1 i) ?, Q; }
o/ \0 H: K, H7 F/ Y // Then we create a schedule that executes the1 \$ I- b1 v& }1 R& P9 Y
// modelActions. modelActions is an ActionGroup, by itself it
6 G+ [% C( C* K# G, v // has no notion of time. In order to have it executed in: n# J9 Q# Y: |, o* C
// time, we create a Schedule that says to use the
( t" K/ s; i9 s; c: Y6 J // modelActions ActionGroup at particular times. This, L! K( b6 q: l/ p H P( D8 Z
// schedule has a repeat interval of 1, it will loop every. t& \8 I/ J" n! X4 z) p
// time step. The action is executed at time 0 relative to( }0 l( w, h' g( x% u
// the beginning of the loop.. y) l3 K) h, r4 K9 o8 E
' D* N# W4 b9 T // This is a simple schedule, with only one action that is
6 e8 \: g5 i2 f4 [2 ^ // just repeated every time. See jmousetrap for more- a& Q n" o3 _# v H
// complicated schedules.
6 r+ X- _! W6 e) ]' A* v , L9 ~0 G1 g/ T
modelSchedule = new ScheduleImpl (getZone (), 1);
6 X1 P% ]- h7 `( L8 A' M& ? modelSchedule.at$createAction (0, modelActions);2 c7 w |6 K) i
# r" H7 {' U0 [! ~ return this;1 ?1 X" s8 x, F4 E) `- d- Q: e6 z
} |