| Age | Commit message (Collapse) | Author |
|---|
|
Source files are meant to be indented 4 spaces. This makes sure files
are displayed correctly in GitHub.
|
|
This seems to be the correct way to print individual characters. Salis
now keeps correct background colors through SSH.
|
|
[#20] The 'fireup.py' plugin can load one, or several, pre-saved
simulations and restart them automatically, each inside its own tmux
session.
|
|
[#19] I felt it was too easy to quit the simulation accidentally. Now,
a user has to type 'q' or 'quit' on the console in order to exit.
|
|
This solves issue [#18].
|
|
[#17] After having removed organisms' reward/punishment mechanisms,
the number of executed instructions will always match the number of
processes. No need to keep this.
|
|
[#12] Allowing to toggle the IP layer (white) can help the user
better visualize of the underlying memory block structure.
|
|
[#16] Allowing organisms to EAT information is causing huge reefs to
form too early and occupy most memory space. Here we replace EATB/F
with the old shift left/right. This is done to compare simulation
stability.
|
|
This fixes issue [#13].
|
|
|
|
An user may now specify simulation's auto-save interval during
initialization. This works for both new and loaded simulations.
|
|
|
|
[#8] We compress all auto saved files via a subprocess call to 'gzip'.
Saved files are reduced to around 25% of their original size.
|
|
|
|
[#5] Whenever terminal gets resized with the console open, we call the
Printer.on_resize() method to adequately query the new window size.
|
|
[#4] Modules now utilize better naming conventions for
differentiating between public and private members and methods. We no
longer make use of properties.
|
|
I've found that allowing organisms to eat from everywhere (including
addresses owned by other organisms) made the simulation too unstable.
Organisms may now eat from either free memory, or from self-owned
memory.
|
|
[#1] Cursor process selection loop was searching for processes under
the cursor by iterating based on process count, instead of process
queue capacity.
|
|
|
