HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:' ?. S o6 ^$ t" n+ C; P
0 y; ?7 d5 ?* s public Object buildActions () {( g. v, |1 v1 M& f+ B! \& V
super.buildActions();
A+ T, V6 e% o/ ~6 s, n6 v9 g6 E : \# `/ a3 o! |8 \* s* e3 b( f
// Create the list of simulation actions. We put these in
3 C# N; {' z; P, x" i // an action group, because we want these actions to be% |6 J1 i7 M: e" n6 I- c1 |! l
// executed in a specific order, but these steps should
) i, h3 M4 U# b$ P) W6 ]& r // take no (simulated) time. The M(foo) means "The message
" R0 R# m T/ P! E0 z! [ // called <foo>". You can send a message To a particular
1 l7 f3 P3 ^6 T9 A T' @ // object, or ForEach object in a collection.
3 ?, N @' R5 A+ L, N0 l" Q * H- n1 U- I K9 X& }' Y
// Note we update the heatspace in two phases: first run
4 r/ R p6 s2 K. o! V // diffusion, then run "updateWorld" to actually enact the) P: }/ J( P; n. U) w( D, v
// changes the heatbugs have made. The ordering here is8 T4 ?; ^# [1 S, P- |3 {8 R
// significant!* S/ E/ y6 b, V% b" v1 d
! L9 Q x, ~2 c. R- g7 t // Note also, that with the additional
9 n o7 Y! \1 e; S# ~) v // `randomizeHeatbugUpdateOrder' Boolean flag we can0 |( k$ X4 l3 i8 a" `( t- ?3 U
// randomize the order in which the bugs actually run3 W, g+ J8 q0 Q1 V
// their step rule. This has the effect of removing any
+ c% [+ G( `) o$ J8 @8 _& D/ \2 b& S& Z // systematic bias in the iteration throught the heatbug
5 }# K) D" ~' G" \, n3 K* I // list from timestep to timestep: O+ k2 w* r- `' y: F, R- U1 k
9 R& ~1 x' l4 a; T; w0 ]
// By default, all `createActionForEach' modelActions have
, F% f, A) }- f7 @. n9 W // a default order of `Sequential', which means that the
, m5 q* q& J/ x- L& W v( T // order of iteration through the `heatbugList' will be
3 E* I% D+ `& V8 c // identical (assuming the list order is not changed- ~, @$ ]2 p4 Y2 J8 j9 `
// indirectly by some other process).
# y+ I, }: X7 i* F! a
; ]! q5 w$ o5 F# I modelActions = new ActionGroupImpl (getZone ());$ }0 S6 R S1 b
, D- o. f @/ a! r try {
6 N8 J9 C* x; n3 U& X3 z& [2 Z( F modelActions.createActionTo$message" l$ s$ s! a" D/ ?7 Q
(heat, new Selector (heat.getClass (), "stepRule", false));
! m. l3 m& _4 G; F1 i& m } catch (Exception e) {! Y0 S I9 _& a
System.err.println ("Exception stepRule: " + e.getMessage ());- Z6 T) \- B3 }2 R
}
* D( H4 X) q- h0 R0 B& \2 d, m
# S0 L, a+ M3 [. M6 U( S, b try {" w: P. W9 M# i& W! t: j1 R
Heatbug proto = (Heatbug) heatbugList.get (0);* a2 g( V' |7 f8 |" H, w. n* f
Selector sel =
2 w H B1 R- l9 m* t6 I$ Z new Selector (proto.getClass (), "heatbugStep", false);- P1 W" e3 y7 e, J& h2 c* ]
actionForEach =
f8 C5 C2 d$ g! e modelActions.createFActionForEachHomogeneous$call
& d* H6 m/ V) [; a* N (heatbugList,/ C3 J0 \) Z0 L" [% i4 b( |( _
new FCallImpl (this, proto, sel,5 V3 `" l9 s A& k3 X
new FArgumentsImpl (this, sel)));
& g0 I( }( k3 l; R& M; O } catch (Exception e) {
( j2 s+ k g2 p% W; U7 f, ~ e.printStackTrace (System.err);
& X; E8 B4 k3 d+ E9 E }" `/ e# C/ y w* X
: t( l o2 _4 y" p* u2 o3 M, ^/ O
syncUpdateOrder ();. X( i# w% j+ U) x/ |
7 a1 Z, T0 B2 f+ v2 r3 H& |- y
try {7 q; x, t1 Z* D* ~
modelActions.createActionTo$message 7 D2 @9 N6 H6 x0 I3 `
(heat, new Selector (heat.getClass (), "updateLattice", false));. q4 Q: O, H3 i7 [* M% S! Z* b/ J
} catch (Exception e) {
: l0 Q3 h/ Z+ Q% N System.err.println("Exception updateLattice: " + e.getMessage ());+ U- w7 ]( p# ^) R" w4 J
}
3 U* Z: l J/ N2 b4 X 6 _. q8 j* W( ]4 |3 P2 o
// Then we create a schedule that executes the0 ^. ]8 b' x# c' N6 K h/ b Q
// modelActions. modelActions is an ActionGroup, by itself it
( h3 Y7 F# G6 n2 }( F: f // has no notion of time. In order to have it executed in+ q. l) F! f4 h% T6 P6 \/ A3 P \
// time, we create a Schedule that says to use the( V! @! ~0 @2 N. N% u2 X M
// modelActions ActionGroup at particular times. This. Y' U, J- K0 j9 I& i( B1 T( d
// schedule has a repeat interval of 1, it will loop every
0 Z" |5 D2 P$ U( X( G. u4 A // time step. The action is executed at time 0 relative to
. m, C+ l9 Z2 m. |. }5 F8 t // the beginning of the loop.
% I9 L- V! A; e/ b; T
& a \/ p$ |+ O" c. E3 { // This is a simple schedule, with only one action that is5 n% j7 E( \8 t/ I1 O: `/ T( n
// just repeated every time. See jmousetrap for more7 O) u4 l2 W* a8 W, [0 A
// complicated schedules.
- ~2 l2 G, ^$ m 6 i. j5 `! H1 d
modelSchedule = new ScheduleImpl (getZone (), 1);
J- h R- U" d& Z modelSchedule.at$createAction (0, modelActions);
! v' L, l: L/ h; z# _- T( a3 p( ? " d9 k# q$ n: p8 j. [& E: h0 J, |. p
return this;% X& X+ P- Y9 @
} |