HeatbugModelSwarm中buildActions部分,3个try分别是做什么?查了下refbook-java-2.2,解释太简略,还是不懂,高手指点,谢谢!代码如下:4 @, \3 ]) `* T3 I" c
, V* z3 Z: u* E- c
public Object buildActions () {1 ]* o/ c( p# n) c1 e4 z/ }
super.buildActions();
5 l* P: G: |7 x4 \; x l' K 2 k- ?2 V8 y) I
// Create the list of simulation actions. We put these in) F7 M' w5 P; N( v+ p* V
// an action group, because we want these actions to be
: c9 O# m4 v' m. R // executed in a specific order, but these steps should3 }- c7 V0 d* H* C+ g; V
// take no (simulated) time. The M(foo) means "The message/ ?5 e9 e! X" _! z1 @" \9 @
// called <foo>". You can send a message To a particular7 k& D8 M4 c( `/ y H* f3 c( X
// object, or ForEach object in a collection.
" v% ?. _3 G( W3 c4 Z; J/ y
9 w6 `9 k1 g0 r // Note we update the heatspace in two phases: first run
0 F( P' e: h9 b# f: B // diffusion, then run "updateWorld" to actually enact the
4 T, U/ p$ L t! O* X1 ?; Y // changes the heatbugs have made. The ordering here is u$ E2 ^5 a* I
// significant!1 k9 i" \0 R I! s* Y
T- F/ j9 [5 w$ F# v. w$ ?' c // Note also, that with the additional
( q4 y+ B9 \" S9 e) S+ s // `randomizeHeatbugUpdateOrder' Boolean flag we can
1 K } n1 q; @# B9 e- X) W6 v% p, ~9 G // randomize the order in which the bugs actually run' H# @' `4 }8 [
// their step rule. This has the effect of removing any
1 q( v, C; b- Q* o0 h/ N // systematic bias in the iteration throught the heatbug+ _( h ]# [! s. z3 X3 \3 B6 |
// list from timestep to timestep
' d3 X: h: b5 L! ~; S K* C+ _5 {9 f& y) R' N
// By default, all `createActionForEach' modelActions have
: |* Z0 C2 J0 ~) R8 T, ~. y, S // a default order of `Sequential', which means that the
" ` j( n' n2 i2 F // order of iteration through the `heatbugList' will be
+ Z* C/ }) B7 P // identical (assuming the list order is not changed' Q9 f4 w" }7 t' }; |
// indirectly by some other process).7 B7 G+ \9 o% g* K/ S1 i$ H
; _4 O3 g( _. O2 W% t4 Q modelActions = new ActionGroupImpl (getZone ());
# X1 Y# ~4 t$ v4 V
( o% a: o7 {! d. i7 W try {! t: K0 @% T- G9 |0 u5 O! q
modelActions.createActionTo$message. Q( }1 z; g8 S. s& T
(heat, new Selector (heat.getClass (), "stepRule", false));' E6 T" y" W- f* {* R+ H4 S; e% K3 S
} catch (Exception e) {8 M+ V9 i6 C t& \6 K& H
System.err.println ("Exception stepRule: " + e.getMessage ());: X3 Q; ]! `- |7 P
}1 j" B% k8 ?9 w/ d/ @
9 T/ @/ J1 I0 x# w3 B+ V
try {
6 a X1 Y, r. c) U" y4 r, f. n% y Heatbug proto = (Heatbug) heatbugList.get (0);8 I. x2 d( m& i2 k! S( o
Selector sel =
6 M( L2 }" Q4 _& i2 b( Q* Y new Selector (proto.getClass (), "heatbugStep", false);
8 w. R5 e! J Z actionForEach =3 U( t% L/ I8 O, \2 U D
modelActions.createFActionForEachHomogeneous$call
9 |, |( ], n! Y* ^1 p (heatbugList,
$ o1 U, H% s& c, |) o, d) ~ new FCallImpl (this, proto, sel,8 Q/ u+ M! l3 W0 M8 ]3 _
new FArgumentsImpl (this, sel)));
k+ b! \6 a4 n' f } catch (Exception e) {, p( O' p6 Q: y: Q' G
e.printStackTrace (System.err);
2 C- H0 x( O4 D2 [1 T% L }
1 m' @2 l+ f" O/ y/ e- ^
+ T4 T% I5 ]' E# y# f% v syncUpdateOrder ();2 l" O# Q0 o: p
- n; y' M4 \7 L; L& C2 @# C
try {
. ?+ }* z6 T. B0 n5 H$ z& c8 z0 n modelActions.createActionTo$message / L1 H4 I ?" N& g/ g& S: v
(heat, new Selector (heat.getClass (), "updateLattice", false));2 g5 G" k$ y/ N+ T- I3 w3 R
} catch (Exception e) {3 X: B4 ? U3 ^3 @ }2 R4 X$ N
System.err.println("Exception updateLattice: " + e.getMessage ());
7 s. F4 _& x& c }
# x. b) g# @6 F- N 2 M& Q9 r0 C# r" U
// Then we create a schedule that executes the9 _8 y. ~) k$ k2 C# h# C
// modelActions. modelActions is an ActionGroup, by itself it7 ^7 }9 O2 q J* T
// has no notion of time. In order to have it executed in
5 k+ u& \ t% Y5 N // time, we create a Schedule that says to use the
- G' m! L$ X4 G9 i* h // modelActions ActionGroup at particular times. This
+ s9 P* S3 S/ t, |& o, L$ K2 ? // schedule has a repeat interval of 1, it will loop every* x. @2 t6 ?0 U U! n
// time step. The action is executed at time 0 relative to/ T" E& e9 M5 I8 I5 d
// the beginning of the loop.- m9 N* C# R/ S; I7 a/ E
9 A2 Q# C5 g$ h- |+ a- V
// This is a simple schedule, with only one action that is* S4 J4 k! B+ _/ s
// just repeated every time. See jmousetrap for more6 F( B; u4 g- ^# Z% o6 p' Y
// complicated schedules.
& O/ }) a2 f, i6 z9 z4 W
4 u/ t3 c; L* T9 |# l5 }$ z modelSchedule = new ScheduleImpl (getZone (), 1);' i* h3 d+ P: \% U
modelSchedule.at$createAction (0, modelActions);
1 N$ { X$ o7 c
( Q4 x8 z7 b+ E! p+ ~6 ~ return this;
* e" _$ C. ?0 G } |