HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:9 }$ a/ Q: `4 p% t2 h3 L D
J' P; K, q) @ public Object buildActions () {8 i6 ]3 G m: W- ^/ o" E
super.buildActions();, X" n+ x5 \/ i% K/ w1 Q
7 n4 z; b. F9 ~( x3 l- @+ b // Create the list of simulation actions. We put these in
: L$ Q" T( v- c' B! D9 s2 h // an action group, because we want these actions to be$ @, ^4 e; ^6 x4 N8 ?
// executed in a specific order, but these steps should
+ Z* f6 g/ N. `% G8 G) y* e( d) z // take no (simulated) time. The M(foo) means "The message
" w: s$ n% f* f // called <foo>". You can send a message To a particular
6 ?# E' L2 T" W% w$ l) e q- s& f // object, or ForEach object in a collection.+ e5 k0 X ]/ R3 a1 G; K
! |9 C0 U: x. J [" e% r // Note we update the heatspace in two phases: first run
' K2 { u, \0 g# F0 s, H // diffusion, then run "updateWorld" to actually enact the. K: o/ Y2 d6 x' F* L
// changes the heatbugs have made. The ordering here is# P+ N! }6 |. p2 i
// significant!
8 U+ N9 d$ y# b! i8 }1 d |) q 3 ~% T5 |, p0 E9 v, `3 X9 U
// Note also, that with the additional8 K" ^* h! l4 N5 ?
// `randomizeHeatbugUpdateOrder' Boolean flag we can
: |$ G: |) E, N) S' e // randomize the order in which the bugs actually run4 k5 Q' A& ? E$ N2 M7 ^4 ^
// their step rule. This has the effect of removing any
5 O& U! k, L" I* {% R* j // systematic bias in the iteration throught the heatbug% O6 g" j* M6 T0 z7 O4 x ?
// list from timestep to timestep8 S( d3 ^8 Y- m" ]1 v3 @5 `( P
$ F* Q V' P7 X: n // By default, all `createActionForEach' modelActions have
R, s1 U: S; G1 f# k8 F' @ // a default order of `Sequential', which means that the L" w. O) `8 z2 I8 S x1 U
// order of iteration through the `heatbugList' will be+ M8 B( i5 r, l- t& _3 l
// identical (assuming the list order is not changed2 m: G1 h4 Y% R2 H+ t3 q
// indirectly by some other process).
; D+ h( H5 v- n0 O$ E2 c ' C5 a1 Q9 S. P& ~9 l6 S. t- o
modelActions = new ActionGroupImpl (getZone ());
# y1 u. s4 ~% i) D) t ~( E3 W, i7 U+ M: q `& C* \
try {
& ]6 h# }: A; b8 j3 \: a modelActions.createActionTo$message
! b ]* y' t* Q Y! o# _% X (heat, new Selector (heat.getClass (), "stepRule", false));1 F- P& o! @; b" l% P, Z
} catch (Exception e) {
, R: [, i& z" p) B' Z& A; {- F System.err.println ("Exception stepRule: " + e.getMessage ());' r& l2 V+ f( ]) G* }
}
7 T6 [2 d# G7 P, {, m
3 I# t( v- X4 |! y! U try {* i4 t* ~$ [+ {
Heatbug proto = (Heatbug) heatbugList.get (0);
7 f, U p# I+ A" w6 F2 n$ @/ e Selector sel =
( }/ o6 ]' b ~3 U3 h5 J new Selector (proto.getClass (), "heatbugStep", false);
2 L% x6 f8 e- u! ? actionForEach =3 m: b0 S( i# L/ ~* |& v2 R3 T
modelActions.createFActionForEachHomogeneous$call
, _+ N4 s; [7 Z! B4 `1 d1 P! C- ] (heatbugList,
! u. e* J2 f: s! L new FCallImpl (this, proto, sel,% G) c% C9 k4 x+ c
new FArgumentsImpl (this, sel)));
/ U4 o! r$ ` l9 P } catch (Exception e) {
3 t& y! }) O% R e.printStackTrace (System.err);
6 w1 m0 }0 R" ]8 S [1 P }4 G1 o; V: u0 m* \/ D% K) Y& t h
' U- R9 Q' w+ X7 M syncUpdateOrder ();. K; R" U& u; r, Z W( F
; T. p" C- v9 V2 |/ Q
try {) S9 |4 C7 R( U
modelActions.createActionTo$message
5 [; {, X2 ^1 ~ (heat, new Selector (heat.getClass (), "updateLattice", false));
4 z9 S" g b9 {9 K! i+ h Y7 S% l } catch (Exception e) {
9 j6 a% w$ p; f System.err.println("Exception updateLattice: " + e.getMessage ());
& O" w9 P. \) Z8 ` }
2 A* h8 I1 Y" j$ D * `3 a" B5 F7 e6 W8 R. [4 j
// Then we create a schedule that executes the- c3 X v8 [5 A' ~7 {9 U
// modelActions. modelActions is an ActionGroup, by itself it1 O; q- k2 q% B7 @& P' \
// has no notion of time. In order to have it executed in
! u4 p7 }1 V1 v/ \& a' K2 n // time, we create a Schedule that says to use the
$ w# M! F" g7 E- v7 N ?, K // modelActions ActionGroup at particular times. This1 b& V6 M1 d, n
// schedule has a repeat interval of 1, it will loop every! i& F' ^% q% C
// time step. The action is executed at time 0 relative to" ?4 u h" @4 ^0 U# |% d
// the beginning of the loop. X' q/ Y% z. i( l/ t0 {6 e" N
' J& A' j( U. B // This is a simple schedule, with only one action that is
, R% X! |: ], @3 t // just repeated every time. See jmousetrap for more
, u8 } _/ Z# F0 ]) A* E // complicated schedules.4 x" U9 O( S; v# X( A
/ s, ]6 H& w, f1 Q' ]+ W* D modelSchedule = new ScheduleImpl (getZone (), 1);! ]8 V& `! t+ U' B4 j8 { c
modelSchedule.at$createAction (0, modelActions);
" V8 q/ _/ u6 J% v i$ r5 N $ N+ u3 D9 P6 n6 A# u( i5 V' V
return this;
$ W; n( z* R: ^; i" Q' @. K } |