HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:
: j8 z* D; Y; r" L& O- Z: J3 O! b9 j3 C" O, e
public Object buildActions () {2 {9 p6 f" L; p' @0 F
super.buildActions();; ]. c; m C& q: \, \5 X, w. Q
( i. Q* A& W2 X // Create the list of simulation actions. We put these in p- S0 t( ^. g7 N9 {/ }1 g
// an action group, because we want these actions to be
8 W9 J3 O7 c) @# B1 E3 }. V // executed in a specific order, but these steps should
. s" q# Z9 G+ E v. H: s9 K4 Q // take no (simulated) time. The M(foo) means "The message% S: H: z- T$ I( n6 c4 H- a1 Q
// called <foo>". You can send a message To a particular
+ M% ~6 U/ D6 v2 x3 r% C7 `3 Y# _ // object, or ForEach object in a collection.8 P1 ^& I0 E! o
+ q% u. q$ G4 e8 V
// Note we update the heatspace in two phases: first run
5 M% ^( K! Y: z% a // diffusion, then run "updateWorld" to actually enact the, e h; ~2 k' J K& i
// changes the heatbugs have made. The ordering here is
- J4 s: N! M( Q8 B; }7 ] // significant!
; ?. {% H" z$ z6 [3 t: w) U$ [$ f. ? . j* D* }1 l v( A6 h$ ]! l
// Note also, that with the additional
2 F0 G# c$ s5 `: x9 d" t$ { // `randomizeHeatbugUpdateOrder' Boolean flag we can% M! w: Y$ t& j( P9 c4 c
// randomize the order in which the bugs actually run8 x A/ _5 p. @1 t, ^" b+ O/ p! @0 n
// their step rule. This has the effect of removing any. s6 p+ X V9 ?- S
// systematic bias in the iteration throught the heatbug
3 |7 }+ e+ }3 v! @# Q1 ` // list from timestep to timestep, L- r, c8 y- C; N7 X
6 ^- B1 G7 l) A5 v( J // By default, all `createActionForEach' modelActions have. Q5 c* b0 W: n
// a default order of `Sequential', which means that the7 V' i3 ~" _, n, ]1 K
// order of iteration through the `heatbugList' will be
6 c& s5 }) x( M9 W // identical (assuming the list order is not changed
+ Z8 {" Y# [2 U: \ // indirectly by some other process).! r, {5 A2 h, _. I) ]) W
# h" ^, _# v Z ~9 f, _* I; T
modelActions = new ActionGroupImpl (getZone ());! u) Y" Z4 ~+ A
. g0 L" ]. }# ~8 t5 t
try {8 j* [! ^* F' S, e( z
modelActions.createActionTo$message
7 f' O6 D- V$ b R0 X7 W (heat, new Selector (heat.getClass (), "stepRule", false));
2 `5 L* N8 ]- b6 ?& j! [ } catch (Exception e) {- x, q4 {! ^) Y& Y
System.err.println ("Exception stepRule: " + e.getMessage ());- c" \8 M1 I. S9 c
}
; L& z5 i# n' `" _3 K' h' t, K. N' B+ }- A9 i2 L
try {' Q) H8 B+ U$ K1 `
Heatbug proto = (Heatbug) heatbugList.get (0);
, w$ W. g5 I5 E8 X! x Selector sel =
1 K0 K8 @# n8 z1 b, S' o0 v1 Z new Selector (proto.getClass (), "heatbugStep", false);* {9 j1 q! F; [: [# A
actionForEach =
/ w0 G3 j' i& T' L/ f& z% G; X modelActions.createFActionForEachHomogeneous$call& x7 ?5 R, \ h0 \
(heatbugList,
, W1 n0 a8 e |7 D/ j3 R0 X new FCallImpl (this, proto, sel,# T2 U3 s' m; E
new FArgumentsImpl (this, sel)));% X# u) S1 R- u" D! \
} catch (Exception e) {, L" C; M$ Y! o: y; r7 ~; w
e.printStackTrace (System.err);0 @9 N& _3 z% u+ n L, h! ~
}
4 i/ O5 J- o" L( F* J9 f+ o
8 s, k* P' @1 X$ u. C; Z syncUpdateOrder ();
7 g# v L7 [2 @# ~! R7 }$ M5 D' C6 B/ `7 A& c8 d& ~0 _
try {( _/ n( Y5 }* A- y1 ~( J N* P
modelActions.createActionTo$message . w# g8 o3 @9 g0 k2 ?
(heat, new Selector (heat.getClass (), "updateLattice", false));
% e1 m$ b: E( M) J } catch (Exception e) {3 J5 V* Q, r( _
System.err.println("Exception updateLattice: " + e.getMessage ());2 `. ]2 X( t2 W
}
; W. G7 L7 @$ m% u% ~# V3 K& p2 J / c$ T9 _0 n h2 t
// Then we create a schedule that executes the# _% I$ a& t+ F
// modelActions. modelActions is an ActionGroup, by itself it4 y$ X! E+ m# F V
// has no notion of time. In order to have it executed in
4 [! H" s; h2 u7 j, Z6 h! N // time, we create a Schedule that says to use the1 `" k, a# q6 j( N% R) P0 L
// modelActions ActionGroup at particular times. This
- r; `8 l. o0 }" O$ N // schedule has a repeat interval of 1, it will loop every
, x8 j2 G1 Z( P" V6 n- N // time step. The action is executed at time 0 relative to
' J' K) B( C: ~6 ]+ Y: M/ j) j* i( c& J5 H // the beginning of the loop.1 d+ H) { w/ `/ O8 B
: M8 r+ k4 ]1 ^1 |) u // This is a simple schedule, with only one action that is
4 L+ C8 X. {6 P7 ~$ L // just repeated every time. See jmousetrap for more8 d! j; y1 Q- H8 Y- B
// complicated schedules.* y/ R$ X a) N7 o
8 S i" ^4 a1 ~& V
modelSchedule = new ScheduleImpl (getZone (), 1);2 y9 R2 y; h O1 [* I4 E. C' Z( h2 S+ ?
modelSchedule.at$createAction (0, modelActions);3 [' I0 Y% \: w5 B0 Z
8 T% ~2 k& b2 C) R5 t return this;
o9 `5 G$ }( `; h- y: w' _0 T } |