ArrayAlign | ArrayAlignHierarchy | ArrayAlign_ConstantRange | ArrayAlign_Equal | ArrayAlign_Multiply | ArrayAlign_PermutationCycle | ArrayAlign_Power | AudivolvNetwork | AudivolvSummary | Brainwaves | CodeSimian | CodeTree | Func | FuncPurpose_MeasureOtherFunc | FuncPurpose_SoundColorMouse | FuncPurpose_Unknown | HardCoded_CodeTree_BreedFunction | HeapQueue | HighStandards | Hypercube | Javassist | LongTermGoalsOfAudivolvDesign | MindReadingHelmet | MovementScore | NeatVsScruffy | NoSpying | Node | NormedCodeTree | PermutationCompilerAndInterpreter | Plugin | ShortTermGoalsOfAudivolvDesign | SoundCardPart | Template | TuringTests_per_second | flo | int | ob

Audivolv - NeatVsScruffy

Neats Vs Scruffies - Audivolv is Neat (except for roundoff error) at the low level
and Scruffy in its intelligence. "In artificial intelligence,
the labels neats and scruffies are used to refer to one of the continuing philosophical
disputes in artificial intelligence research. This conflict is over a
serious concern: what is the best way to design an intelligent system?
Neats consider that solutions should be elegant, clear and provably correct.
Scruffies believe that intelligence is too complicated (or computationally intractable)
to be solved with the sorts of homogeneous system such neat requirements usually mandate."

No part of Audivolv can be truly Neat if roundoff-error is allowed.
If roundoff error becomes a problem, I will start using the strictfp Java keyword
to be truly Neat. Neat and scruffy have advantages on different problems, and Audivolv
should use each where it works best. That is a scruffy sentence because I can not prove
that combination works best. A completely Neat person would not try to save your life until
proving that you are alive. Scruffy usually thinks if it works, do it,
and take chances if you're "feeling lucky".

Low-level things should be Neat (100% predictable):
+ Testing.
+ Whitespace in strings of code.
+ Behaviors of compiled code, except speed.

High-level things should be Scruffy (IF it works, do it. Take chances if you're "feeling lucky".):
+ Speed of compiled code.
+ Evolving Java code.
+ Graphics.
+ Interaction with the user.
+ Strategy of keeping sound-card buffer just empty enough to not skip sound.