search

fredpy / trex2-agent

An architecture for goal directed control of autonomous agents
BSD 3-Clause "New" or "Revised" License
14 stars 13 forks source link

Log managing and replaying mechanism #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. run a mission
2. realize that there's no way to replay this mission for debugging

What is the expected output? What do you see instead?

missions should be providing some log mechanism that allow to reproduce it for 
debugging. It used to be the case on former versions of trex.

Please use labels and text to provide additional information.

As we added dynamic reactors creation support it, the former logging mechanism 
we had in order to replay a mission became in-adapted. Still such feature 
proved to be crucial for debugging a failure of the agent (or one of its 
reactors) on the aftermath of a mission

Original issue reported on code.google.com by fre...@gmail.com on 21 May 2011 at 6:34

GoogleCodeExporter commented 9 years ago

Original comment by fre...@gmail.com on 21 May 2011 at 7:10

GoogleCodeExporter commented 9 years ago

Original comment by fre...@gmail.com on 22 May 2011 at 5:29

GoogleCodeExporter commented 9 years ago 
TREX::transaction::TeleoReactor::Logger provide an XML serialization on all the 
public transactions of a reactor while supporting dynamic connection to the 
system. 

It ewill probably need to be refined but the idea is there

Original comment by fre...@gmail.com on 21 Sep 2011 at 11:01

GoogleCodeExporter commented 9 years ago 
commit 199 improve the support and now fully integrate a good logging mechanism 
along with the ability to replay observations. What is missing is :
  -replaying request and recalls
  - allowing to replay timeline operations when they happen during the mission

Original comment by fre...@gmail.com on 27 Oct 2011 at 4:43

GoogleCodeExporter commented 9 years ago 
revision r200 includes now a "complete" TransactionPlayer able to play a full 
mission with observarions, requests and recalls from a former log.

This will need some extra test but the code is there and did appear to work 
fine on initial test

Original comment by fre...@gmail.com on 31 Oct 2011 at 7:13