HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:
8 M- q6 ]5 o7 q1 n$ @5 z4 X- X5 d8 [' s0 b
public Object buildActions () {" J' w: V! R- O) [8 l+ }& r' ]
super.buildActions();0 h, c, W' }' a* ~) y
0 @. T1 T( {7 w' a* N
// Create the list of simulation actions. We put these in d. v& ?; }6 Q* r7 o" E
// an action group, because we want these actions to be
/ r, x3 I0 H- q8 C4 Z& i; l // executed in a specific order, but these steps should6 V: ?& |0 n8 `8 ]' _6 ^6 a
// take no (simulated) time. The M(foo) means "The message
# Q# z" g3 I3 e; R1 d2 | // called <foo>". You can send a message To a particular
& C* Z+ {# o4 G- f: q- P0 B // object, or ForEach object in a collection.4 P$ Y% ~4 X0 l
4 S: g: I9 x4 c ^2 ]2 f- ` // Note we update the heatspace in two phases: first run
N" X$ J9 |+ S& L6 S // diffusion, then run "updateWorld" to actually enact the
3 j" Z/ Y2 k+ l2 w3 ^& T' C, K, q // changes the heatbugs have made. The ordering here is
( p, g! N% o4 ?8 ?( P // significant!
. U* A7 b$ z% n % B: [" V) U$ l1 U
// Note also, that with the additional6 U' K( K% l! d& q- L
// `randomizeHeatbugUpdateOrder' Boolean flag we can, F! \" {3 m: u+ j2 c! X; ~
// randomize the order in which the bugs actually run% [. [4 ^: X/ d' v# i
// their step rule. This has the effect of removing any8 C; x9 ~* j& f! m
// systematic bias in the iteration throught the heatbug
4 x- a+ {! M7 V5 | // list from timestep to timestep
2 h# F. T! t/ E/ h8 S) B; t' J
. B7 n9 v$ e6 f7 i // By default, all `createActionForEach' modelActions have
, h* e8 G1 M( r+ m% ^ // a default order of `Sequential', which means that the. @7 W. n& e5 J( Q( w
// order of iteration through the `heatbugList' will be6 l. V& i, e- T: l; f
// identical (assuming the list order is not changed C1 m S& l2 \3 W: j* n* h
// indirectly by some other process)./ _- U( Q$ [/ N
: c2 i; C- U- ~! F/ `- I modelActions = new ActionGroupImpl (getZone ());# o' ~5 h7 e: n1 n8 z
( ~% g1 W. U; ]" c. ~- {4 \( L; S try {; w- s$ D! ?; z: r% T
modelActions.createActionTo$message' W7 F- p3 g: K- s: o1 F a2 e
(heat, new Selector (heat.getClass (), "stepRule", false));, c6 T$ z) } Q* v7 b
} catch (Exception e) {& }" w9 B( y9 ]. D
System.err.println ("Exception stepRule: " + e.getMessage ());
* j8 m/ V n k, q3 E# N, E! Y }5 _' _6 e- m1 u ^& h6 D: R
7 n6 A Q( c+ `) s: e1 p try {3 {9 A% X) i% u6 X2 ~. Z
Heatbug proto = (Heatbug) heatbugList.get (0);% A& Q9 x# Z1 X
Selector sel = ; x( H: r7 `. k! s9 x4 N
new Selector (proto.getClass (), "heatbugStep", false);
9 I- V" R) K2 ` actionForEach =
2 f+ y% L% s ~6 @- m modelActions.createFActionForEachHomogeneous$call C7 Y1 X P I5 n
(heatbugList,. r4 `, ~4 }) \! N: d( L
new FCallImpl (this, proto, sel,6 y. x7 G6 d& b& t. C$ l
new FArgumentsImpl (this, sel)));
& f( K1 `2 D) A0 S* P' l% K7 V } catch (Exception e) {$ R# e; ^1 f. ?. L
e.printStackTrace (System.err);/ b* B- C+ o9 ^+ ~
}
# F7 `7 x* ^; I' s
% l1 v3 H: Q$ D6 L syncUpdateOrder ();7 {2 q: X' @. Y4 }' e
! _! ^+ h% {- K7 @5 ~# _) f; u try {
9 t& A6 T+ ~2 a/ c4 } k( h! L7 U modelActions.createActionTo$message ) x2 H* P: N+ M4 r, \/ K8 d
(heat, new Selector (heat.getClass (), "updateLattice", false));. S1 M& M/ q" B* v+ B
} catch (Exception e) {
5 P! h4 E- l- M7 r/ R; r System.err.println("Exception updateLattice: " + e.getMessage ());
/ N6 R' l$ y9 n9 j( {# H/ a }
' |+ R- x/ H- T6 A( b ; r( P" b6 A! a$ z8 t& O* u' P3 W
// Then we create a schedule that executes the. Z$ u8 r6 E; s
// modelActions. modelActions is an ActionGroup, by itself it
! ^4 ~6 j& m' S3 L; _3 z' e // has no notion of time. In order to have it executed in! @ U9 m6 a1 H" q3 _# n+ V" B
// time, we create a Schedule that says to use the
6 h; ]% S) p+ E; ?6 N+ _: h& } // modelActions ActionGroup at particular times. This: e. N' J. e& d/ k
// schedule has a repeat interval of 1, it will loop every. \' x) N3 o" x7 d8 ?! E
// time step. The action is executed at time 0 relative to
5 Q' c5 T; T; F2 h- S // the beginning of the loop.5 |. Q3 j& } |5 N, [& c G6 B
. J0 k/ h* l' T& P( ^* M8 [5 N; e; f // This is a simple schedule, with only one action that is' Z+ n: l$ |5 r8 t
// just repeated every time. See jmousetrap for more! o& h! r8 ]$ L
// complicated schedules.0 j2 e$ T* {3 m% }' _
9 t& G& P5 h" W* ~! W modelSchedule = new ScheduleImpl (getZone (), 1);
1 C' V9 e' w4 n1 }# n" [ modelSchedule.at$createAction (0, modelActions);1 ]$ {' F4 C( Y% c5 T) n5 P
1 n* U8 |; W/ Z2 T$ T& ]
return this;
/ J( V# h5 H) J [; O9 l } |