HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:* P2 S- P' B: J4 z: K5 z
; _6 s. T$ c8 l( Y. v* p6 b- l
public Object buildActions () {; K1 j* D. H% _4 N% ^+ d! O
super.buildActions();; ]- ]. Z4 B( [' { _( G
7 O$ B0 o. X! r( i! H6 r
// Create the list of simulation actions. We put these in; o3 U2 l" `2 n" y$ q
// an action group, because we want these actions to be
6 ]9 v( X" [- _7 h$ F // executed in a specific order, but these steps should# r. \2 }) f* u( n% U
// take no (simulated) time. The M(foo) means "The message4 X* A" ~1 \! {* F1 r6 h
// called <foo>". You can send a message To a particular* V j6 G9 Q' G- k" J/ B8 q
// object, or ForEach object in a collection.8 I9 Y! V% n9 W7 c* G- M* z
. _! x1 @8 O) W3 k+ \* M- [! d // Note we update the heatspace in two phases: first run6 J5 P7 T$ R5 t0 }
// diffusion, then run "updateWorld" to actually enact the
% v; o, ^ ]# [, R9 L: z // changes the heatbugs have made. The ordering here is* y3 v+ D) F- N) p* L: N
// significant!0 j. e* d' m; R' b1 ~
& D# H2 A' Y; T( a // Note also, that with the additional
/ u8 H- ^( Z7 R' V! |. R$ k // `randomizeHeatbugUpdateOrder' Boolean flag we can
( e9 w' S5 T& W7 @" C0 A. | // randomize the order in which the bugs actually run
' T- |+ M7 A& \; m1 s0 R' { // their step rule. This has the effect of removing any
$ @0 D9 \/ t, c! k // systematic bias in the iteration throught the heatbug8 }# y' r6 y/ k* G c
// list from timestep to timestep
% ]' l: `) R+ i1 _( v
# Z5 O. T# ~6 ?; j // By default, all `createActionForEach' modelActions have( H2 N5 g' [4 ^
// a default order of `Sequential', which means that the
" e6 O4 m% U& D" k! b3 w4 @1 h // order of iteration through the `heatbugList' will be; C5 ]6 E! c) O( y: `' ^# [
// identical (assuming the list order is not changed0 q( s, l' Y5 m/ {
// indirectly by some other process).% ]1 S7 o( c& t
: ^7 F1 b( d* _; Y' j' ~, m. C modelActions = new ActionGroupImpl (getZone ());
8 A* N6 B1 k0 g" `$ I2 U/ K$ l; h- t6 @
try {
+ K5 n$ k6 T9 M" a' u; X modelActions.createActionTo$message
( w# Q, S- @8 _. W (heat, new Selector (heat.getClass (), "stepRule", false));
* V$ k: z. o h0 t } catch (Exception e) {
2 f) O" O+ Q, ?- |+ y3 ` System.err.println ("Exception stepRule: " + e.getMessage ());* w7 O9 B- _( P& {: r8 W8 P7 L
}3 d y x @9 Y( N+ ^2 j
/ ~0 E* k5 O" h( |0 }
try {( J0 j6 P4 q0 m9 n0 b! a# \
Heatbug proto = (Heatbug) heatbugList.get (0);
; X" U* o9 \; y4 {5 D Selector sel =
6 O5 D' c7 \2 L new Selector (proto.getClass (), "heatbugStep", false);! b$ f( Q7 y& _+ o6 ^* v* l0 r
actionForEach =
9 L7 U. G& Q3 p* z' r7 f. } modelActions.createFActionForEachHomogeneous$call" k% I' B! B3 w6 E2 _, U
(heatbugList,/ v) m4 A5 V9 V4 ~
new FCallImpl (this, proto, sel,
0 r# M9 s8 B5 x) i) m new FArgumentsImpl (this, sel)));' w5 P8 b9 S g! k
} catch (Exception e) {5 Y7 c/ {* m$ a$ D5 [. W
e.printStackTrace (System.err);
: `4 Q# W% r- r' T1 A$ Y }0 i% f: n+ Q( M+ K. v8 D
. r; X# i. G* T0 _0 D$ _/ ?6 ] syncUpdateOrder ();+ Y8 i0 x8 ?/ K \/ w$ z+ r
" J/ W# h+ V' m4 m9 W- a1 K! [
try {% Y+ A2 M# P, o# l) d; h- z/ j
modelActions.createActionTo$message
$ ~: Q B9 M; K (heat, new Selector (heat.getClass (), "updateLattice", false));
0 F+ A5 }: D V } catch (Exception e) {
/ Q- H) `5 r0 ]! X$ }; m3 M System.err.println("Exception updateLattice: " + e.getMessage ());
8 C# A" b# ^ f6 C! [ }
) ]- A, S R( l; M6 d1 Y d* [
3 c3 W1 ~1 |' k; K // Then we create a schedule that executes the
; j$ X1 i: c# d z4 W( f1 G // modelActions. modelActions is an ActionGroup, by itself it
' i# C! {0 [+ v7 ]- w // has no notion of time. In order to have it executed in Q- Y& ]5 S0 I% l
// time, we create a Schedule that says to use the
: h8 `# e7 d! P& W% G9 z // modelActions ActionGroup at particular times. This: Y- g6 O" ^& _* K
// schedule has a repeat interval of 1, it will loop every* l4 |2 h, s! ~, v& p$ B
// time step. The action is executed at time 0 relative to1 A; G. h& w" N/ s9 f7 Z5 s
// the beginning of the loop.2 ~0 v- f& i E3 T' z& e9 R4 h
) Q2 b$ k0 |. W% q+ H // This is a simple schedule, with only one action that is
) y6 P4 R" h! @9 a+ s6 C // just repeated every time. See jmousetrap for more
7 c6 y5 K( r* `7 M // complicated schedules.
" x- n; ~) l3 N2 ? k; i # {. j4 H! Q& \6 B! @, ]
modelSchedule = new ScheduleImpl (getZone (), 1);+ K7 Y& M! ]6 j3 z
modelSchedule.at$createAction (0, modelActions);
8 l2 g" S0 l) ^9 N0 x) X( K4 e ! ~) x8 b( ~7 P5 [! U+ R
return this;
" g; N" S$ w- O- y } |