Monitoring Gofish Agents' Behaviour

Demo 1: detecting design error Instead of waiting at home, Sue shows up at the distribution center and made a pickup attempt. This "external" event may have been unforeseen by the designer. Thus a design error is detected by Agent Monitor. Monitor writes an error log file, and clearly points to a situation missed in the Gofish MAS design. Demo 2: detecting coding error Suppose the message log of Gofish MAS shows that after "DropOff", a message "send_ziptozip" is followed. However in the actual code, "add_packages" should be executed in order to update the database. Although this doesn't result in a livelock, Monitor detects this coding error and generates the error log file.

Click to view demonstrations!                                        Demo 1 (design error)                           Demo 2 (coding error)   Click "Stop" button or "Esc " key to stop the animation; click " Reload " button to restart   ( make sure your browser is set to allow animation;   Note some of the new Betas of Netscape do not allow you to stop these crazy animations...)

BACK