HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:
& T9 g$ F$ K0 M, D5 E# g$ s
' o$ u/ H6 L6 a: {$ ~. X public Object buildActions () {$ S3 v' P) {$ D O* e; c0 k) t6 B! \ q
super.buildActions();
& d; W; q; V; X8 |4 @
/ N& M$ R/ F4 q X+ f w // Create the list of simulation actions. We put these in `- L' f5 W- Y6 K1 q1 ^$ H6 U7 h
// an action group, because we want these actions to be: p6 L+ B6 V( x' G5 y4 A
// executed in a specific order, but these steps should# O! Y! G/ d* c0 i4 }
// take no (simulated) time. The M(foo) means "The message
! s0 j) \8 p3 V% N, i6 |' K // called <foo>". You can send a message To a particular
/ u+ D' f' V+ F+ ~0 g' C8 [& c // object, or ForEach object in a collection.
3 b, u$ I ~. h+ s+ @ z3 D, J
6 C" j( t5 V# d$ P$ J9 y // Note we update the heatspace in two phases: first run
3 E% v. { X+ c7 d9 a6 c8 b0 X* u // diffusion, then run "updateWorld" to actually enact the
4 O$ t* M+ V' P4 P. k8 r, O! C9 P // changes the heatbugs have made. The ordering here is, a9 K# ?: J- L9 U# A/ M
// significant!( d- V6 ^3 b4 ~, Q5 P; d
: f/ M( I, X) C, ^* D // Note also, that with the additional4 m& h! M; j/ A: n5 T
// `randomizeHeatbugUpdateOrder' Boolean flag we can
2 C) \* @" x! Y! R! @8 c" { // randomize the order in which the bugs actually run8 K* D2 B7 F/ j4 S* W. j* g
// their step rule. This has the effect of removing any3 K6 M4 f/ l" r s3 ~1 g; \3 m
// systematic bias in the iteration throught the heatbug0 d: i# j4 T: O$ [5 J6 h
// list from timestep to timestep
9 p6 O; g( h% L9 e $ \- l6 h" }+ J2 m3 i0 l, g
// By default, all `createActionForEach' modelActions have1 l% |0 y" x4 Z3 D0 l- }
// a default order of `Sequential', which means that the
' \. p5 M3 h" E: R // order of iteration through the `heatbugList' will be( M" F* A! P; X
// identical (assuming the list order is not changed
5 z6 A+ |9 G; p- p // indirectly by some other process)., \7 Z5 b' N& o3 H
: u6 I6 t" A3 Q1 H
modelActions = new ActionGroupImpl (getZone ());
' z- o( Y& Z% V* X& k1 @1 I' I7 g3 K5 p- n9 i1 E
try {9 T6 L& g- C! {' u, }$ {" O0 o1 P
modelActions.createActionTo$message; K' H4 E" k& d6 O
(heat, new Selector (heat.getClass (), "stepRule", false));2 v6 D8 {5 i6 C' E1 ^; I
} catch (Exception e) {
. e$ i, ?& ^; V+ s4 m4 ]0 p7 U+ N System.err.println ("Exception stepRule: " + e.getMessage ());
, U8 P3 m7 \( j5 Z* | }$ ^( v$ ~- | _- r( f
6 f6 y! B. U' s$ u: c& ?0 q' _
try {( p- x: S3 S6 {9 D) |2 m0 h
Heatbug proto = (Heatbug) heatbugList.get (0);7 f5 h9 ^( i# _; \
Selector sel = * x [% ^6 f. U T
new Selector (proto.getClass (), "heatbugStep", false);
* m+ T9 F7 ~. @$ M% R actionForEach =% s9 l: s8 h& Z* g
modelActions.createFActionForEachHomogeneous$call
4 G; ]2 g4 g( D7 F (heatbugList,
+ S, {0 s* B+ z new FCallImpl (this, proto, sel,8 w( }: d; u8 i/ y Z4 U
new FArgumentsImpl (this, sel)));
0 R/ }( A" K( t- @ } catch (Exception e) {
# z# }' Q! y/ q7 D) Q4 D e.printStackTrace (System.err);" E$ m+ U k; g0 M
}
2 b- Q6 F% n( H( B
# z0 H% x) W2 a0 B syncUpdateOrder ();( x4 t) J+ [3 r, H9 h/ S
; o1 D0 ^9 q3 T# X, L, d6 { try {
2 z7 c/ q( P: k modelActions.createActionTo$message & d: B, f9 \) k n7 x
(heat, new Selector (heat.getClass (), "updateLattice", false));4 }* Q* a! l# V8 N
} catch (Exception e) {; m5 Y- i% }9 O/ N; @) R
System.err.println("Exception updateLattice: " + e.getMessage ());1 c, `' |2 C2 `, V. T) ^
}) a& p9 @! V; E& |. i+ j
m- k- i7 c8 n
// Then we create a schedule that executes the- C& Z8 f' H( f
// modelActions. modelActions is an ActionGroup, by itself it% D G- N m/ F6 Z% p5 H5 C! @
// has no notion of time. In order to have it executed in1 K* [! _ A! w5 s/ p
// time, we create a Schedule that says to use the
' i& R# \9 @7 C) y" J // modelActions ActionGroup at particular times. This9 x3 I; ~, v, R$ @# [
// schedule has a repeat interval of 1, it will loop every
# z2 o8 }: q/ `& t9 _ // time step. The action is executed at time 0 relative to
+ Q$ ~/ w" J$ \ F9 s* `6 P. l // the beginning of the loop.2 i' B; H, t& E: @
, [. n: [9 _: k: C* W2 Z$ n
// This is a simple schedule, with only one action that is1 ~6 l7 N( D' c1 G# h X
// just repeated every time. See jmousetrap for more. O5 N% B) j) L* d% O7 W, G
// complicated schedules.
+ |2 ]/ B3 e u1 i: t1 W" d6 G6 C! F9 v . j4 ~- n- D' h5 U
modelSchedule = new ScheduleImpl (getZone (), 1);
7 ~' s3 Q; |3 G' | modelSchedule.at$createAction (0, modelActions);+ E# t9 L5 N7 P$ h/ ?4 F9 R- i. O
: u1 k+ _- v( `$ S
return this;% \, U/ j7 R( n3 B, b6 _" k. S
} |