HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:( F$ W, ^. E8 [+ J+ R- h
; O1 t# J3 Q B' h# x X
public Object buildActions () {" }9 J0 k+ ^& X: Y" o* z1 \
super.buildActions();8 m' U$ y7 `$ I7 x V$ k) N, u
4 b+ X" q G2 G7 G1 V) `
// Create the list of simulation actions. We put these in- S. O0 }( S" ?+ L1 i
// an action group, because we want these actions to be
9 [+ y4 a1 J8 j) M# f, H // executed in a specific order, but these steps should/ ^2 j1 k9 u8 O1 P' R; E
// take no (simulated) time. The M(foo) means "The message
8 F( e7 o1 ^) @6 t" @, R // called <foo>". You can send a message To a particular
" O& l* w* `& m4 b0 [ // object, or ForEach object in a collection.
2 J* S) i0 n1 i4 U. |" c; G: N) C
9 W* W7 Y, E2 A- u // Note we update the heatspace in two phases: first run
7 n, u- E7 Q) ` `' p( l // diffusion, then run "updateWorld" to actually enact the
7 R/ T8 [- d! f! g // changes the heatbugs have made. The ordering here is+ }( X# N2 D2 C' f5 A/ g6 _
// significant!: L# x$ d8 N R
5 X- a! v! X5 q% }% ]* F // Note also, that with the additional9 I e5 Z9 A; B# g' N' C* a
// `randomizeHeatbugUpdateOrder' Boolean flag we can% y) w: {% D$ `% r' ^5 C: H
// randomize the order in which the bugs actually run
: X1 S; f5 ^/ E4 | // their step rule. This has the effect of removing any$ f4 N# s0 k' W6 {" P$ {
// systematic bias in the iteration throught the heatbug5 x: Y6 X. ]( H4 q* q. U# M
// list from timestep to timestep# g* H# y! j. _ o Y) `4 m' K
& j9 N* r0 a4 X( C // By default, all `createActionForEach' modelActions have: ?. |3 ^$ s7 }, [6 I5 m3 W9 j; Z" \ o
// a default order of `Sequential', which means that the' V0 x0 O1 s+ F' g k3 y
// order of iteration through the `heatbugList' will be
# r% \* J8 C! T/ E- r% T // identical (assuming the list order is not changed
* R3 \0 r, d c( u: O3 Y // indirectly by some other process).
, d! q% ?' x. P( `
: J0 s) T) ^' S modelActions = new ActionGroupImpl (getZone ());
$ A1 D( _( Q. Q+ y
2 w% o+ u' n" E& ]. H6 L5 Y try {; \! y; N& P% G/ `7 Z) Y) n
modelActions.createActionTo$message
0 H( Z& g7 D# B1 }9 O) v (heat, new Selector (heat.getClass (), "stepRule", false));: ^+ X$ o; l' m
} catch (Exception e) {
. L% e& j) N5 K/ C/ e& |% q$ J System.err.println ("Exception stepRule: " + e.getMessage ());3 K' Q2 H; C- A+ M3 Y
}
% D4 ?# N7 [) E( j4 `* z4 h. ~$ F$ V, F# W% ^4 S
try {
# p* V$ j5 ?* X Heatbug proto = (Heatbug) heatbugList.get (0);! O; L/ R6 y3 m; a6 V
Selector sel = * p+ O1 f4 F$ X( x" G" Q0 f
new Selector (proto.getClass (), "heatbugStep", false); |) w4 ]' u0 p2 N
actionForEach =+ K" q) |6 h. Y% w
modelActions.createFActionForEachHomogeneous$call& x" V/ }- R- c+ J
(heatbugList,- ?% Z; k- B: F' i" v- e3 a! F* }' l
new FCallImpl (this, proto, sel,
/ ?1 \- n g% z3 Z$ b new FArgumentsImpl (this, sel)));
8 u, A# u6 k3 O% |4 ~0 B } catch (Exception e) {( B: ?1 L* T( U
e.printStackTrace (System.err);, G( a' s$ k' i8 ?# K' C
}% M& C9 g( N6 A7 K
$ u/ I7 u- V& m6 K0 ]# @6 @4 @ syncUpdateOrder ();6 ?% j* u* @8 o7 Q3 ^9 c
+ n2 ^; W9 N6 m try {: d* N0 z: E6 b
modelActions.createActionTo$message 4 p+ r8 O7 p( w, r9 w1 L
(heat, new Selector (heat.getClass (), "updateLattice", false));8 j. X+ Q/ n% r1 ` \9 I
} catch (Exception e) {( V2 o/ k2 I4 V# G; z
System.err.println("Exception updateLattice: " + e.getMessage ());
: d U( j8 ]0 |0 t, K" O; j }
* M0 x+ }7 ?! R6 P# M8 \' ^
% R$ n( m( j5 i( _$ ^; U6 d // Then we create a schedule that executes the
, n' P0 f, r% V5 j // modelActions. modelActions is an ActionGroup, by itself it1 w) |! ~9 S. ?: b9 |- S# w
// has no notion of time. In order to have it executed in
$ t8 j- Z6 O1 {/ k o // time, we create a Schedule that says to use the+ _5 Y$ T# z; U( |9 s
// modelActions ActionGroup at particular times. This
. Z% ^ O2 K0 c/ _ // schedule has a repeat interval of 1, it will loop every
1 F1 a$ S/ H: r$ Q( o( c // time step. The action is executed at time 0 relative to( G, H" Q" e# K8 [: ?% L
// the beginning of the loop.
. x r1 D: x0 M/ M" f: F. S
6 M! v' E/ b6 b$ W% a& L0 R // This is a simple schedule, with only one action that is2 R& m4 ~4 v- G# H. U1 f
// just repeated every time. See jmousetrap for more, z9 k5 V' C8 P$ Q9 h. N, R1 L# ^
// complicated schedules./ S! ^2 B+ X6 t1 v+ w$ N: m+ T- H/ }
+ K8 y# L+ i; n& J
modelSchedule = new ScheduleImpl (getZone (), 1);6 q! _% k" s! g9 \5 }0 i
modelSchedule.at$createAction (0, modelActions);
) ~5 {1 _1 A3 \4 x3 \& D$ n4 ?
3 V0 T6 p2 M9 I; c, b2 N return this;1 P( k+ n; s" W& X* C
} |