HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:
1 n7 }5 v5 \/ A5 P
' y! k4 ^* C, T# Y# Y9 z: F$ ~ public Object buildActions () {
' N' I; y$ D% S& F( Y super.buildActions();$ F, n4 T3 X8 ~, Y% U- i
, U5 k4 h" a; S
// Create the list of simulation actions. We put these in; n' c T2 b2 J7 S: b+ X7 \
// an action group, because we want these actions to be, M; D6 S6 R" c% P/ E
// executed in a specific order, but these steps should0 [" u6 C- y" S! Y0 c% U7 ^- f
// take no (simulated) time. The M(foo) means "The message
! O8 v3 u( f0 f6 v1 ?7 M // called <foo>". You can send a message To a particular/ X$ N' j f8 n6 B( i
// object, or ForEach object in a collection.( V8 I" n& N+ c+ R9 b
; I4 Y8 g7 L- d& }' M3 s0 j# k
// Note we update the heatspace in two phases: first run6 u: r, ^+ m4 b8 Z$ _. q" d! G
// diffusion, then run "updateWorld" to actually enact the0 J9 r+ T! ~' p" P" ^
// changes the heatbugs have made. The ordering here is
, l4 I+ I" C3 ~6 u$ L // significant!' S U( I6 g& c t4 y
8 I1 m& \! E& l2 U( s5 o1 n // Note also, that with the additional
J; t% K$ v! @1 @ // `randomizeHeatbugUpdateOrder' Boolean flag we can
$ c6 n4 q# \5 N, ~6 M0 U$ W // randomize the order in which the bugs actually run
% Z" K! U" C1 {- s // their step rule. This has the effect of removing any
% i% w. [0 e- G/ D1 o9 R // systematic bias in the iteration throught the heatbug8 [3 ?$ ~# g3 p B
// list from timestep to timestep
8 j: U( m. q! [8 a9 W4 `" \
$ h) t& y2 ?# Z" X1 C# z: F, U // By default, all `createActionForEach' modelActions have
5 X, O: V" E* l% K // a default order of `Sequential', which means that the. [1 O0 {) k* e8 A5 n9 I
// order of iteration through the `heatbugList' will be+ ~ e( i5 A5 N9 w
// identical (assuming the list order is not changed
7 a3 j7 s. y: z // indirectly by some other process).
7 ?. P: D3 R$ c. \) b: T- N5 ^3 _ 1 M/ Y# G) Y5 H3 [9 K' r: z
modelActions = new ActionGroupImpl (getZone ());6 l9 ?% p9 l+ x
- l1 |; ^2 v e* {7 b3 k( @ try {$ q0 l4 I- L. [3 e! C* k. M! L
modelActions.createActionTo$message! A" y4 H+ c( r* m3 }# t
(heat, new Selector (heat.getClass (), "stepRule", false));* ], X! h4 Z7 ~: o: S: N; ~/ e( @0 {
} catch (Exception e) {8 Z/ c/ c5 Q' f$ }- C9 e7 _
System.err.println ("Exception stepRule: " + e.getMessage ());: f" n8 V) W% G, f! E6 f
}
* y1 F/ |9 `) g: e7 Z/ U }2 q% C+ V9 v
try {/ [2 t- [- d) T/ \# A
Heatbug proto = (Heatbug) heatbugList.get (0);) v8 G; l( f3 h( `9 }, M) K, H
Selector sel =
3 B, ?" d$ {8 U" P# Z new Selector (proto.getClass (), "heatbugStep", false);
: C V/ v) B. O actionForEach =
2 W( a, Q$ W4 d8 x- e/ S$ } modelActions.createFActionForEachHomogeneous$call
' t- O, ?5 t' X (heatbugList,# V" c) T9 ~9 z: W$ u: X
new FCallImpl (this, proto, sel,
1 }' U+ G1 z* \ E( [/ Q new FArgumentsImpl (this, sel)));% w0 P' |' [' z |
} catch (Exception e) {
# _9 R9 v/ J' i: D, S2 B. c e.printStackTrace (System.err);' N- \: t* d' @4 X$ o( o2 U7 @
}
& @6 i0 V+ Y6 R! t4 j. T / ?9 P4 P' R$ o* c: E
syncUpdateOrder ();
8 [2 z/ ~9 `: x' r& Z% x9 i8 C2 C2 M) u. w5 Q- A/ P
try {
% }: E' ^: M* A5 y3 n modelActions.createActionTo$message
' \ @5 P$ I7 E; B# H5 l$ S( [+ ? (heat, new Selector (heat.getClass (), "updateLattice", false));0 b) D+ r8 J$ M. s1 j
} catch (Exception e) {# \* r$ @, H% }' c7 P6 D5 I
System.err.println("Exception updateLattice: " + e.getMessage ());
7 p% [1 t& I+ y4 C { }/ w3 x7 W* e5 q K5 ]9 D1 ~6 T% Y" E
0 F, j. h1 t- B4 {- Z
// Then we create a schedule that executes the& t& S8 d# Z7 E. O+ m, n: e
// modelActions. modelActions is an ActionGroup, by itself it( _! X6 n; L0 K! b7 @# k- l l
// has no notion of time. In order to have it executed in
9 o2 j( z2 o- \$ V // time, we create a Schedule that says to use the# g( @' j- Y2 q& ~0 T
// modelActions ActionGroup at particular times. This0 r- g# I, U6 x) O
// schedule has a repeat interval of 1, it will loop every- u r9 r$ A7 q- w
// time step. The action is executed at time 0 relative to
: L* S& k9 ^6 ~+ C9 ]3 g // the beginning of the loop.
! N% c, G3 X4 f4 {) `2 B* z" A, L' `# o! S
// This is a simple schedule, with only one action that is H5 y( P$ P6 Q7 z/ `$ a5 ]
// just repeated every time. See jmousetrap for more
' L& z" B2 K8 p2 ^5 J // complicated schedules.5 w& M6 f N6 G8 C7 C/ y* }; O
9 h* ] _ r2 R( j& E+ D; C
modelSchedule = new ScheduleImpl (getZone (), 1);" @4 s9 }6 u- } p6 @9 V
modelSchedule.at$createAction (0, modelActions);0 H3 @8 T! s u. i! y! o6 e
7 Y' j; {+ J( S" \9 r return this;0 ?5 X9 b: O1 o" c) ?2 ?4 p! w" V# w
} |