Mosquito behavior has a finite set of states (state space of model), within which there are certain biological functions that are always evaluated.
A bout is the actions taken by a mosquito between a launch and landing; mbitesBRO_oneBout
handles all the biological imperatives that occur during a bout,
while specialized bout action methods handle the events that occur due to the purpose of the bout.
mbitesBRO_boutB
: blood feeding bout
mbitesBRO_boutR
: blood feeding bout
mbitesBRO_boutO
: blood feeding bout
1 |
The generic bout runs necessary updates of timing, state, survival, energetics, and queue checks prior to calling the nested
specific bout action, and checks that the mosquito is alive/active before calling the bout. It updates tNext
and stateNew
.
This corresponds to the following Gillespie-style algorithm:
tNow is set to tNext from previous bout
moveMe: movement between point classes (if needed)
boutFun: run bout function
run energetics and check if alive
run landingSpot and check if alive
run surviveResting/surviveFlight and check if alive
update tNext
update state to stateNew which is determined in the bout
This method is bound to MicroMosquitoFemale$oneBout()
.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.