HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:5 i7 I; r' V3 b( o- E
( n) M- I/ Q' ]- \& f. Z public Object buildActions () {4 ^7 S4 m K. c f+ ?& U. e& W6 i+ u
super.buildActions();
' @. c/ q5 i2 f# q3 ?! V
4 U3 h+ S! R- V' O/ z // Create the list of simulation actions. We put these in6 a1 t$ x- k5 H( e& A9 E
// an action group, because we want these actions to be# v) S9 V0 F' w' z+ V7 e6 z
// executed in a specific order, but these steps should, d, j- [; ~* g% U, I
// take no (simulated) time. The M(foo) means "The message
) y* Y q- A* E: \- D$ _ // called <foo>". You can send a message To a particular. e5 A5 c% |. W' ~ R) U
// object, or ForEach object in a collection. F q5 K& R: G, x2 Y5 p1 U; E
4 L9 ~6 E& `$ g& T7 m) E/ R // Note we update the heatspace in two phases: first run
- j* {9 R4 _# ~. X @& a; [+ r // diffusion, then run "updateWorld" to actually enact the
) X4 p n% T; u) f3 q // changes the heatbugs have made. The ordering here is/ K% I8 K6 S% Y
// significant!( k( f, P. G: x( M
0 k" {2 b& s) x. Q9 k# E // Note also, that with the additional
* F+ Z9 y7 ?2 Q% z7 B // `randomizeHeatbugUpdateOrder' Boolean flag we can3 u0 L7 W# R. S9 M B5 }
// randomize the order in which the bugs actually run
7 D4 A" p" I+ ]" n7 T+ M |& X- | // their step rule. This has the effect of removing any
, c. g. a2 y6 [2 r4 o // systematic bias in the iteration throught the heatbug
|& Z- G9 \" n" y9 c, N* ] // list from timestep to timestep
9 C) n1 g. t) {& o/ r
# ]. J S8 K8 O // By default, all `createActionForEach' modelActions have
7 Q+ }' s H/ ]( {4 Y4 | // a default order of `Sequential', which means that the" T" ^ i( V( e
// order of iteration through the `heatbugList' will be
/ j/ {4 \6 m% t! Q6 l) }$ ` // identical (assuming the list order is not changed
9 R/ F7 F) S" p& }. o [' l // indirectly by some other process).
4 S! x9 Y% l$ F3 m& A' h( H % {9 T% ]0 f6 i' l0 A4 u& o& \
modelActions = new ActionGroupImpl (getZone ());5 M4 n6 m% @2 u8 |
1 K0 V8 V8 Z/ b3 ^" |6 N
try {. ~, _- c- J7 p$ G; W0 \- b
modelActions.createActionTo$message
7 A! t# I2 Z% h) {2 s# `/ ^ (heat, new Selector (heat.getClass (), "stepRule", false));+ Q5 x+ A/ I- U2 `& a' a
} catch (Exception e) {- \" `1 {/ K/ ]& ?
System.err.println ("Exception stepRule: " + e.getMessage ());
j& A3 i( ^# Z } F- G0 N. S: Y$ \8 y
3 o# c# z7 o$ O7 w C. e$ X try {
6 e: H* L! L8 H( h$ Y7 \6 H" m6 a% H# g Heatbug proto = (Heatbug) heatbugList.get (0);
6 K* K& R- C3 k( \( ~ Selector sel =
- K1 D, _+ H' s$ { w! U: F+ k new Selector (proto.getClass (), "heatbugStep", false);
! C+ [$ m. S5 s& A+ I2 z actionForEach =
8 G0 ?) m* n0 N3 T h; K modelActions.createFActionForEachHomogeneous$call( I M3 r5 ?% v6 A/ L4 U0 I, E
(heatbugList,+ h9 v) j. X, H" f7 O0 d$ d T
new FCallImpl (this, proto, sel,! C+ b) X( F: Q
new FArgumentsImpl (this, sel)));0 x( m" n/ J/ J2 k5 X1 p1 ~
} catch (Exception e) {
2 ?0 i$ v+ P+ Z+ B% @ e.printStackTrace (System.err);
! f2 A e2 A" S [ }# |+ d: F' j3 M; C1 {# D. g
9 ]% Z- {8 h( b. ]: ^ o$ f. o- N syncUpdateOrder ();
- D9 c; e7 a# w2 u- o$ J
# a7 Z" o) X9 P5 L try {7 x+ G# f: \8 v- Y' G9 B
modelActions.createActionTo$message ) s* x$ r" Z2 ] [$ [8 C
(heat, new Selector (heat.getClass (), "updateLattice", false));
X% l" _( i& B3 `* v' X" ] } catch (Exception e) {
3 e; _- \. J9 U* L System.err.println("Exception updateLattice: " + e.getMessage ());
0 s' T$ C( ?( a! x$ \ }8 ]2 B- p4 e+ s+ K
6 {$ E9 X4 ]3 T; }
// Then we create a schedule that executes the6 ~# w( o% E% r. g; {) g7 h& T
// modelActions. modelActions is an ActionGroup, by itself it
% c1 u: v; X1 g8 S // has no notion of time. In order to have it executed in
9 G( u' D1 g9 J // time, we create a Schedule that says to use the0 h; g2 W9 Z2 t
// modelActions ActionGroup at particular times. This9 l1 N3 M7 x8 k# [
// schedule has a repeat interval of 1, it will loop every
& s2 e' n4 `! ?) o5 E" m // time step. The action is executed at time 0 relative to, o, O6 s+ a; @# i E( i2 E" U
// the beginning of the loop.
' Z* V1 W0 d M: z" [* J9 @4 j
5 _+ [9 d) L, ?6 H( \& T9 D$ | // This is a simple schedule, with only one action that is
) q% \8 V5 V# D, k& w // just repeated every time. See jmousetrap for more
; h9 E" J0 _8 @1 u( {$ O/ G // complicated schedules.
3 l% p% x3 G2 o/ u* ]/ x
/ J0 R. ]2 N! ~" Q modelSchedule = new ScheduleImpl (getZone (), 1);+ ~; h5 c& G9 ?% q
modelSchedule.at$createAction (0, modelActions);
$ T# ^7 g3 ^, e& b" f3 E5 K7 {
$ p8 t+ Y( z3 R \ return this;/ [ u7 m% e5 h# [
} |