Differences

This shows you the differences between two versions of the page.

--- people:demitri_maestas:work_log [2017/09/30 05:44] – Formatting chucho2
+++ people:demitri_maestas:work_log [2017/09/30 06:08] (current) – chucho2
@@ Line 8: / Line 8: @@
 Thanks to some old guy who doesn't sleep, I was able to implement an elegant solution for an inversion of the C2D x and y. The following was sent to me by Dr. Ackley:
 <code>
-C2D offset = whatever();
+C2D offset = someFunction();
 C2D opposite = -offset;
 </code>
@@ Line 15: / Line 15: @@
 **Accomplishments**:
-  * Heavily worked on the scouting mechanism to help a nucleus determine its relative location compared to the Neural structure (or lack thereof) and determine the best course of action.
+  * Determined that in the spirit of keeping stigmergy a thing, The system will move a little slower than an optimized neuron.
   * Re-formatted my worklog on the wiki
@@ Line 21: / Line 21: @@
 **Questions**:
-   * What is the "best" way to work with coordinates? More specifically, what is the best way to work with getting a direction opposite to you in a robust way? Let's say I'm moving in (1,1) each step. How can I determine that I should be going (-1,-1) If I want to switch directions? I can think of some solutions, but they are not very elegant.
+   * What's a good way to determine how much information I should hold in a single neuron? There is 91 bits in our atom, which means 2^(91) (or something like that) possible combinations of bits in our memory. What if we don't need that much? How do we determine a re-structuring if we find out we need more than we've engineered for?
 **Comments**:
   * I'll make sure to verify that the off-by-one error will fix not affect performance.
+  * You're never too old for trix.
+ --- //[[chucho2@unm.edu|Demitri D Maestas]] 2017/09/30 00:08//
 ----