Difference between revisions of "Dr.Octo"
From WA2IAC Wiki
(→Version 4.4) |
|||
| Line 27: | Line 27: | ||
Work on this version began on the unique date of 11/12/13. | Work on this version began on the unique date of 11/12/13. | ||
| + | |||
| + | == Version 4.2 == | ||
| + | A great deal of development was done during the year following version 4.1. | ||
| + | |||
| + | * This release represented code cleanup, breaking the system into smaller, less monolithic pieces. | ||
| + | * A function library was created. | ||
| + | * Startup and shutdown processes were improved and stabilized. | ||
| + | * An extensive logging system was added to allow extremely fine-grained control over logging. | ||
| + | |||
| + | |||
| + | == Version 4.3 == | ||
| + | Version 4.3 | ||
| + | |||
| + | * A web server based UI was created, which focused on reporting from the RDBMS, but also allows for some control of the system. | ||
| + | * The web server was leveraged to provide some integration of all the pieces of the system that have developed. | ||
| + | * A hybrid data approach allows the system to run with nearly full functionality if RDBMS connections fail for any reason. | ||
| + | * Support for multiple, communicating instances was implemented but is not yet used in production. | ||
| + | * The rate of development steadily built from April, 2014, reaching a peak toward the end of 2014 and the release of Version 4.4 | ||
== Version 4.4 == | == Version 4.4 == | ||
A great deal of development was done during the year following version 4.1. | A great deal of development was done during the year following version 4.1. | ||
| − | * Dr. Octo molted (was rehosted) onto more capacious hardware and a newer OS release. | + | * Dr. Octo molted (was rehosted) onto more capacious hardware and a newer OS release during 2/2015. |
** Rehosting was a pleasant experience. The RDBMS did not move. | ** Rehosting was a pleasant experience. The RDBMS did not move. | ||
** The changeover was transparent to listeners and to functionality. | ** The changeover was transparent to listeners and to functionality. | ||
| + | ** Mysteriously, the hourly "ding" added in version 4.3 ceased working after the molt. Cause still unknown. | ||
* A web server based UI was created, which focused on reporting from the RDBMS, but also allows for some control of the system. | * A web server based UI was created, which focused on reporting from the RDBMS, but also allows for some control of the system. | ||
* The web server was leveraged to provide some integration of all the pieces of the system that have developed. | * The web server was leveraged to provide some integration of all the pieces of the system that have developed. | ||
| Line 40: | Line 59: | ||
* The software was altered to allow it to self-modify both synchronously and asynchronously. Both modes are required as Linux doesn't fully support this implementation. | * The software was altered to allow it to self-modify both synchronously and asynchronously. Both modes are required as Linux doesn't fully support this implementation. | ||
* Sections of the code that could not support self-modification were re-written. This effort is ongoing. | * Sections of the code that could not support self-modification were re-written. This effort is ongoing. | ||
| − | * Many knobs, dials, and switches were added. | + | * Many real-time knobs, dials, and switches were added, a benefit of the work on supporting self-modification to support AI. |
* Many program features, such as timechecks were added. | * Many program features, such as timechecks were added. | ||
* Scheduling features were added, although the system continues to be 100% "scheduled" in real time. | * Scheduling features were added, although the system continues to be 100% "scheduled" in real time. | ||
| − | + | ||
This update was added 3/18/2015 | This update was added 3/18/2015 | ||
