HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:! j8 J1 I3 {4 |$ r; O' H8 J( k: j* A
2 _* N* ?+ J, y2 h. s' @2 ?6 ?2 q public Object buildActions () {
0 \3 l- O3 l% B& J1 ^. w super.buildActions();# s4 u# D* _ e* D1 S& R
. n4 Q# ?5 j: q9 ^: ` // Create the list of simulation actions. We put these in4 H3 T( X: _3 t; ^* ~+ H& V
// an action group, because we want these actions to be5 P1 p" m4 P$ ]. F0 p
// executed in a specific order, but these steps should
# E0 [$ A% |4 V$ q9 D# x // take no (simulated) time. The M(foo) means "The message7 ]: n4 U1 o+ u" J0 Q- f" o+ k
// called <foo>". You can send a message To a particular4 @7 H5 K& Q: j3 l
// object, or ForEach object in a collection.. _: j! V. E( e4 K" `- ?
/ ?! _6 f E' `, a. E // Note we update the heatspace in two phases: first run
' D) c4 w, g9 n% n: @6 O // diffusion, then run "updateWorld" to actually enact the
( H( e8 @1 R y // changes the heatbugs have made. The ordering here is
8 x: }% [3 `; u0 z6 r // significant!
& y" | M F7 J* g ^0 |2 Z4 |3 e: _ ' }) Y/ E3 U- |( t
// Note also, that with the additional
: _, M# S% d% [; L9 z // `randomizeHeatbugUpdateOrder' Boolean flag we can; n& u H- X/ A+ \! D4 k
// randomize the order in which the bugs actually run* w/ F7 _! X$ v
// their step rule. This has the effect of removing any
* s7 m: }6 I: e; m& G) }8 q' h$ y$ @" T // systematic bias in the iteration throught the heatbug/ h* p$ M" _6 {: Z1 W" [
// list from timestep to timestep, j6 `: v" z( W! K9 ]( d
7 }' Y$ W: b+ M. Q3 L
// By default, all `createActionForEach' modelActions have4 M5 [6 {& ?+ [3 w5 w: n
// a default order of `Sequential', which means that the3 z. D0 c5 X: |, v
// order of iteration through the `heatbugList' will be
- F* o* F1 y& M* [4 D3 m2 T // identical (assuming the list order is not changed
) p" w8 d- q _( ] // indirectly by some other process).
- V ?9 t0 ]- i. H
4 F8 u2 ]# E. B8 K4 K7 u. P% k modelActions = new ActionGroupImpl (getZone ());
% ?# u( U) w$ S4 A9 Y
7 e o7 q/ [5 v+ j8 ?; b, b/ B, R try {
- H/ c2 @! \! M% I& {6 V modelActions.createActionTo$message. _. c6 z9 Z% t$ k. ~ ~+ ]
(heat, new Selector (heat.getClass (), "stepRule", false));
\3 S: a8 T9 d& t+ Z } catch (Exception e) {( S' y* Z" \1 }3 Z% K- @! e
System.err.println ("Exception stepRule: " + e.getMessage ());- O I9 J9 T! I/ H! E, M
}
+ a. {! g* L& Z7 D: {) T0 u1 K; ^/ `& a
try {
9 q/ i' i7 d/ g Heatbug proto = (Heatbug) heatbugList.get (0);& j7 b3 N- e8 O$ \. ~$ Y" W
Selector sel = " p! ^( G. K( {- |( A
new Selector (proto.getClass (), "heatbugStep", false);9 d' P2 s X: J, r$ f' j
actionForEach =$ O2 p3 E, R7 }
modelActions.createFActionForEachHomogeneous$call( A i; b% d; T9 f' i* u
(heatbugList,
( x: A. _& V }; M new FCallImpl (this, proto, sel,/ z( ]' u" D5 M6 m' w" _
new FArgumentsImpl (this, sel)));
; s- ?# ^# w. a } catch (Exception e) {
+ L l R9 n# W) S e.printStackTrace (System.err);
0 P* u; Z% T6 }. ?- j- e }5 F+ G/ n7 T+ z+ p: T+ y+ V
+ H% e: D' W% w
syncUpdateOrder ();
+ A8 J5 v4 I# n# B/ B% V. `4 q
7 a- R, ^4 f: L% ?( d9 `% c try {
- q7 k, _- y0 U* G8 H2 r$ ]1 s0 s modelActions.createActionTo$message 9 @) n4 A/ x3 M) V3 r, Q
(heat, new Selector (heat.getClass (), "updateLattice", false));
6 Y& {& [- h: x4 ^" j& g } catch (Exception e) {. J& K$ u( K* s- J" a
System.err.println("Exception updateLattice: " + e.getMessage ());
7 n) b+ W* ]" q7 z% c% m }
. t$ T6 \$ V1 y9 B+ V ) k$ R$ q& A& B8 \7 b
// Then we create a schedule that executes the
' H d" t! G' w) V5 T // modelActions. modelActions is an ActionGroup, by itself it
/ g! Q6 y6 M2 @4 [% g5 D; y9 R( M // has no notion of time. In order to have it executed in! M* K" w+ D3 g9 K
// time, we create a Schedule that says to use the
" ~& h/ d0 ^4 ?7 m // modelActions ActionGroup at particular times. This
& _4 ?* g! k2 ], G/ Y // schedule has a repeat interval of 1, it will loop every5 ?& C( h5 G8 n# F$ a* ~' B6 O
// time step. The action is executed at time 0 relative to
0 k$ i3 g# [0 U9 d4 Q // the beginning of the loop.
% e* k5 G6 m' B
% @$ E9 f. C; z7 Z. j! F) h // This is a simple schedule, with only one action that is
3 O; l: _( @, G# [ // just repeated every time. See jmousetrap for more2 k1 W2 F5 l. {7 d/ K3 q
// complicated schedules.2 g$ t- S7 e! W# V) {
* ?) [: k/ Q) u( ^; A) Z
modelSchedule = new ScheduleImpl (getZone (), 1);! j5 }2 v% U4 C& ?4 u
modelSchedule.at$createAction (0, modelActions);: v& D- l, E$ X- Y( X/ t
" m* K: n/ q% E( r' b, Q return this;0 ~+ U4 [; r/ ~% ` Z: z
} |