HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:
+ x% z7 a; Z Z& G3 B- G
% m7 E; [5 m4 f: p N( w public Object buildActions () {0 L U J0 ~ m- [& l; i: R+ Y
super.buildActions();, r3 v, h& U& l
3 Z' k: J6 a6 m6 B // Create the list of simulation actions. We put these in
C# m4 n _# ?& d8 O5 w* o( \ // an action group, because we want these actions to be
: Y* W' D& Z" P8 ]& E // executed in a specific order, but these steps should [; \/ j( u4 F3 U& x% y/ o' G
// take no (simulated) time. The M(foo) means "The message
+ r6 L* X9 b4 \, f" \; s0 O // called <foo>". You can send a message To a particular4 o' R+ m, {; R5 ]# U* [" L
// object, or ForEach object in a collection.
8 E7 e/ N0 q" S- |: } " u1 c. U/ E# @6 v W- i6 L
// Note we update the heatspace in two phases: first run( I) \( q, s s6 o' w
// diffusion, then run "updateWorld" to actually enact the9 C. @( Q+ K |( L ?
// changes the heatbugs have made. The ordering here is
5 l3 H& @ G, N; q* G8 B // significant!0 k ^2 k7 t$ [" F
& n+ U* N W2 a" V9 H, n3 z& R3 s
// Note also, that with the additional& g; R2 U' d" C/ d" N/ c
// `randomizeHeatbugUpdateOrder' Boolean flag we can
6 A/ A: ~( m: w# K* v6 _ // randomize the order in which the bugs actually run3 ^" o9 P! x8 P2 F3 }1 L* p+ d
// their step rule. This has the effect of removing any, G) G9 T. e, e" X2 z& f4 b
// systematic bias in the iteration throught the heatbug, X3 y" h; X: C2 G# f
// list from timestep to timestep
$ b8 |7 D5 w7 W" A
7 y t! W6 Y$ k4 l- h) b# D' ?0 { // By default, all `createActionForEach' modelActions have
2 a' @9 W6 U- w) | s8 \1 o // a default order of `Sequential', which means that the
$ M( s7 e: @7 g" x5 d( B // order of iteration through the `heatbugList' will be
8 x* @9 G$ O |" A // identical (assuming the list order is not changed" r; |2 D& ~- ?( C
// indirectly by some other process).7 N/ ?4 a! M4 g/ I
; J9 {9 L( P& g
modelActions = new ActionGroupImpl (getZone ());
( S ?3 Q* Q( \0 O% Q+ w* i! y0 g: X6 l4 R) n
try {
- h4 P* V+ C! u$ `4 @4 M modelActions.createActionTo$message
& c: O Q$ W; e. T% I1 s! Y2 l (heat, new Selector (heat.getClass (), "stepRule", false));
3 ^1 f* z) I; b" D- u% c6 t } catch (Exception e) {
, {; y# \! ]. V& c System.err.println ("Exception stepRule: " + e.getMessage ());
# N( C- ^, E* Y }0 g( N- B5 y1 N: R8 \
0 u; Y4 q1 W" V/ N. u! V
try {
" l Z7 J% E4 ?7 |; h1 i% o Heatbug proto = (Heatbug) heatbugList.get (0);
. H9 V* P3 `! S$ x9 Y Selector sel =
- K- H% C/ l+ f% z new Selector (proto.getClass (), "heatbugStep", false);* n: H, N/ B) h: k/ f& ~
actionForEach =9 g+ w% k$ C7 H: d# x0 a$ P% p4 B
modelActions.createFActionForEachHomogeneous$call
& |" C9 n6 [/ G (heatbugList,
- s! I0 W; s5 V, Y; U) M new FCallImpl (this, proto, sel,
# S; l; `- ^4 ?* g: R I new FArgumentsImpl (this, sel)));
1 `: }/ ]; v, E( J" M } catch (Exception e) {
E- B( V' K+ k- C7 _ e.printStackTrace (System.err);
1 b0 j, V- n! }. P: g# I4 n }
P7 J) Q( F6 d* o2 [5 B 8 m4 Y4 F8 r3 M3 M
syncUpdateOrder ();
6 r5 ?* x- }% K
- i8 `5 q( M) u" o s1 B4 E7 ~ try {
& h3 D- p7 |& V. D9 T/ d! P modelActions.createActionTo$message 0 ?/ o C& ^/ |# I
(heat, new Selector (heat.getClass (), "updateLattice", false));* X2 i# \/ J( A! U9 U- X; r# a# z5 e
} catch (Exception e) {
7 v" a* Y( K+ p! ]* i% Y System.err.println("Exception updateLattice: " + e.getMessage ());0 K5 D* T( P% V* D
}: g. A$ F/ r3 W; I
6 W2 s1 J' x& k3 |
// Then we create a schedule that executes the' N* P! L, l# i5 i
// modelActions. modelActions is an ActionGroup, by itself it5 ^; ?+ G7 S- W: m
// has no notion of time. In order to have it executed in
! j9 M0 ~' H% e3 G) e( T1 W // time, we create a Schedule that says to use the$ i/ s5 N# N$ o# r
// modelActions ActionGroup at particular times. This' ~, b: p+ J1 U" \. y) S j
// schedule has a repeat interval of 1, it will loop every" N# y& D, T0 V v
// time step. The action is executed at time 0 relative to, s* S0 R9 ?' M
// the beginning of the loop.
$ t6 s! f! _# y4 C1 Q x+ |) I3 E- `; u9 ?3 F) g
// This is a simple schedule, with only one action that is
5 I( G% K' [. o0 _# ]- | // just repeated every time. See jmousetrap for more3 a8 Y2 D0 G6 \4 i7 g
// complicated schedules.
3 O+ N7 C* t: A6 g 7 _1 O, {$ f3 G; j, s
modelSchedule = new ScheduleImpl (getZone (), 1);5 s! f3 x+ c& s+ B5 z
modelSchedule.at$createAction (0, modelActions);
+ O5 |( ]. ~# |& ]6 F+ M
+ ]0 A' P6 T! P6 M( W return this;( e) J1 p5 w+ _% C6 S
} |