Recent changes to bugs

try different efficiency calculation

2005-10-26T05:34:22Z

calculate efficiency by:

average netGenerationEnergy / "systemEnergy"

where the "systemEnergy" is the highest energy a bug
could receive

average netGenerationEnergy is the average energy
gained (or lost) by the set of bugs

=======================
efficiency used to be calculated by

average "generationEnergy" / ( "systemEnergy" +
baseEnergy)

where generationEnergy was the total energy a bug had
minus the carryover energy. (At the beginning of the
generation the generationEnergy would be equal to the
baseEnergy).

"carryover energy" is energy kept by the winners of the
previous generation.

baseEnergy was the energy given to each bug at the
beginning of the generation

This formula caused the generation efficiency graph to
initially start out at some percentage. ie, for the static
light Epoch, the initial efficiency was equal to the
baseEnergy / (energy of the light source + baseEnergy ),
or around 30-50%. Within a few turns (~20 ish) the
efficiency would drop to ~10% since it would take the
bugs a while to move close enough to the light to get
energy. Then the efficiency would increase and plateau
as more and more bugs swarmed around the light.

This new formula would cause the efficiency to start out
at around 0. Probably, in static light Epoch's initial turns
the efficiency would be negative since the bugs would
have to exert energy to reach the light. Then the
efficiency should increase and plateau again.

BugVector sortByEnergy

2005-10-26T05:10:40Z

* sort using the netGenerationEnergy. (This bug is
dependant on the creation and management of
netGenerationEnergy)

* give precedance to live bugs over dead bugs (ie a bug
which is alive will be above a bug which is dead, even if
the dead bug has more energy.)

a bug which is alive may have a negative
netGenerationEnergy if they have used more energy than
they have gained. (Since bugs start with a base energy
and carryover energy from the previous generation)

gui updating

2005-10-26T05:06:17Z

each window in the simulation uses a different method of
updating/refreshing themselves.

the JOGL Canvas uses an Animator which regularrly
refreshes it.

the map panels use Swing, and rely on a manual
update() call to be repainted. (And Swing will update the
maps if there is enough CPU time available)

the Graph panels are updated whenever a value is added
to the graphs (whether the graphs are showing or not).
The Graph panels somehow get precedance over the
map panels when they get refreshed. The graph panels
also suck up a significant portion of CPU as the
simulation slows down a LOT when the graphs are
showing.

Investigate what is the best method to update the GUI
with, and clean up the repainting so it gets done well.
(Everything should get refreshed regularly, and no window
should get preferrence over another).

ServerGUIEngine method of GUI updating

2005-10-26T04:59:40Z

Currently the ServerGUIEngine uses a "hack" of sorts in
order to display the GUI.

It uses the client map panels, but doesn't transmit the
Environment over TCPIP. To do this the
ServerGUIEngine manually sets the ClientGUIEngine's
environment object to the current environment.

Ideally, there would be some way to separate the
dependance of the ServerGUIEngine and the
ClientGUIEngine, preferrably without having to write
separate map classes for each.

new energy types & calculations

2005-10-26T04:55:35Z

implement structure for different energy types

storage energy & instantaneously available energy

allow for calculations in a common form to be able to get
a common measure of "total energy"

allow for conversion between energy types

survivor efficiency

2005-10-26T04:50:42Z

track survivor efficiency, or the efficiency of all the living
bugs

change generationEnergy

2005-10-26T04:49:48Z

generationEnergy will be called "netGenerationEnergy"
and will represent the total energy gained or lost by a bug
in a generation.

netGenerationEnergy = totalCurrentEnergy -
baseStartingEnergy -
carryoverEnergyFromPreviousGeneration

EnvironmentCell.getImpedance

2005-10-26T04:45:50Z

create a separate functions
getTerrainImpedance() return impedance of the land type
getTotalImpedance() return impedance of the land type
and a bug
getBugImpedance() return impedance caused by the bug
in the cell (if there is a bug)

instead of sending a boolean argument to getImpedance

remove "m_" from beginning of variables

2005-10-26T04:40:25Z

Pasha wrote some classes and used "m_" at the
beginning of a lot of variables to designate member
variables. Although this is a convention, it is not
consistent with the rest of the project, and a bit
confusing. Need to go through and remove the "m_" at
the beginning since it isnt' really necessary.

add Phases

2005-10-25T09:21:14Z

Add Phases to the simulation.

A phase is a set of generations. Multiple phases make
up an Epoch. A phase represents some adjustment of the
environment in order to reach the goal set by the Epoch.

Implement a Phase class, and a PhaseEngine