HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:' T) P9 D" c7 H- W# U, O, j( ?
/ F1 {; b+ C8 ~: }" e3 ?
public Object buildActions () {. x* k$ |* O, B s4 G& V
super.buildActions();
2 l* O0 V' G( ?: B2 {3 O5 ^
. j7 N. `. @* Y+ E$ `' k, W // Create the list of simulation actions. We put these in$ N Y$ u+ O1 |3 _+ H4 \ a
// an action group, because we want these actions to be
- ]4 g6 ^/ v s& c( o( H2 p // executed in a specific order, but these steps should
, D) T9 v7 Q$ O3 v% u // take no (simulated) time. The M(foo) means "The message: X% Z* X/ W7 q- u; w/ k* n
// called <foo>". You can send a message To a particular
4 [( n- Z# J" z // object, or ForEach object in a collection." G6 B) L8 Z$ f% J& V/ I; |! ?
% Z1 N3 N: C: ^- k
// Note we update the heatspace in two phases: first run
6 L8 L0 t- x' @" W' N0 I. Y // diffusion, then run "updateWorld" to actually enact the
4 l2 b& u3 \' ?' D/ @" l // changes the heatbugs have made. The ordering here is
3 C9 N) C( J9 {2 u // significant!2 d" @2 i& {& `6 s
0 i0 Y$ t6 z* U* b8 s0 u" o( A // Note also, that with the additional
7 D1 ]. w9 @! J) {8 | }0 q# ]4 H // `randomizeHeatbugUpdateOrder' Boolean flag we can+ j) [( n% ~( v5 }$ |% m$ N4 c
// randomize the order in which the bugs actually run/ F( S* t. B9 t$ \
// their step rule. This has the effect of removing any
) i, x8 H. s7 G( |8 v // systematic bias in the iteration throught the heatbug" u4 v) [* I4 _1 Z$ i9 `
// list from timestep to timestep
2 z5 q# [+ t [9 W5 _ & \4 f$ E! ^* K6 D& I
// By default, all `createActionForEach' modelActions have
0 e, B: b% r, G% {4 e. u- b1 e // a default order of `Sequential', which means that the
4 g- a9 k3 V" S' M6 O // order of iteration through the `heatbugList' will be, g# a9 V1 M" n1 G* t# |
// identical (assuming the list order is not changed3 e; m3 Y! n Z* X
// indirectly by some other process).$ n" p6 h! M5 M9 z* `
8 m3 m$ M- t' G4 ~ modelActions = new ActionGroupImpl (getZone ());
, Z0 B, e, ~5 A* k! k/ ~* E$ L
7 b7 ^' J7 J; i2 v try {
5 n9 U# }/ \4 D" ^ modelActions.createActionTo$message9 @) d$ i- @) A& a' S
(heat, new Selector (heat.getClass (), "stepRule", false));
9 L* p1 n. f6 A3 ]( M% e } catch (Exception e) {2 ~& [, g1 H5 Q2 S
System.err.println ("Exception stepRule: " + e.getMessage ());
5 Y. t* _ O6 r5 y9 O1 z$ { }' F4 |( j/ n s) ]
4 C4 f. X8 _3 g* ~3 z9 r5 ~; B, r
try {/ _; X8 f! z# A3 i' D
Heatbug proto = (Heatbug) heatbugList.get (0);# c+ R1 ~) \" s$ g, N' u
Selector sel =
' K& t# G3 Y% ?* L# c- ~2 ] new Selector (proto.getClass (), "heatbugStep", false);
. T( M! v% T9 s' C actionForEach =( s" X/ U! e: o8 m; n0 q
modelActions.createFActionForEachHomogeneous$call
( u# g- J" O Z/ F6 n (heatbugList,
+ [: y V' E) B# q new FCallImpl (this, proto, sel,
$ F" \5 H/ y& m: Y6 h3 T; E; P new FArgumentsImpl (this, sel)));% S3 U+ O1 u$ Z
} catch (Exception e) {
& Q6 u% G* c0 b' k8 y e.printStackTrace (System.err);
: |" M0 ^# r; X6 N, G% T }
6 u0 `8 Q1 A( G$ [
0 h$ ] E+ k/ }8 C9 u syncUpdateOrder ();
5 W6 p& {4 n) B% A$ ?7 P. t, n) P- @
" i; J) z$ u7 u: Q Y try {; `- T5 }5 |% q
modelActions.createActionTo$message
4 j6 u! @* v9 o1 ]1 b8 W6 _ (heat, new Selector (heat.getClass (), "updateLattice", false));) I0 H* C$ ~9 g) d$ A7 W6 @. U# H
} catch (Exception e) {- v- `. F. v+ C& V% S- s
System.err.println("Exception updateLattice: " + e.getMessage ());
( w( n, |9 B4 n, X& G# w }
: V* ]1 U1 C: q! ? E! \5 ? - N5 R) |" k& k
// Then we create a schedule that executes the1 z* O% d) ]3 L
// modelActions. modelActions is an ActionGroup, by itself it
% k" y$ R" W, d; a7 \2 [ T // has no notion of time. In order to have it executed in8 S2 e8 q; U/ ^
// time, we create a Schedule that says to use the
V4 a- ^# s6 a& V; m // modelActions ActionGroup at particular times. This
* U( M; u! i3 i9 {/ A( X. f1 u // schedule has a repeat interval of 1, it will loop every) V/ B( v# x& P# s' ~
// time step. The action is executed at time 0 relative to
3 h6 d0 h! Z; d \5 V6 X9 ]+ A( K$ _ // the beginning of the loop.
2 l3 ]$ _3 F6 ]5 e! b+ H* h
3 v2 K' Q+ v, z+ l4 i // This is a simple schedule, with only one action that is
% y. Y8 U1 J: `% v- Y3 T // just repeated every time. See jmousetrap for more
4 l5 C l! e3 O6 | // complicated schedules.+ K0 ~/ G* r8 C+ O' b \$ T, `3 _
3 a8 C3 c" V; D) \
modelSchedule = new ScheduleImpl (getZone (), 1);
$ |. \1 B0 @3 g4 p. R modelSchedule.at$createAction (0, modelActions);3 I: U0 L/ S. ?; [3 X
; g1 V' k R1 r2 q0 f" u' r
return this;
/ y# ^ |2 }2 T( _ } |