Replies: 1 comment 1 reply
-
This is actually a subtle and tough question to answer. I'm leaning towards having them be entirely different classes. At the very least, they should be separate copies. The difficulty resides in the fact that trace generation will need action objects, sometimes, depending on how the traces were produced. And the observation tokens may not contain any action info (even worse -- the data may have come from something without action info as well!). The model extraction, on the other hand, has a requirement for very rich action expressiveness (we may get to the point of needing distributions over possible action effects on a single action object). So it feels like they deserve different treatment. Can you remind me during our macq meeting this week to chat about this with the full group? |
Beta Was this translation helpful? Give feedback.
-
Should the
Action
objects in aModel
be the same object references from theTraceList
, or copies?Is it problem that the
Action
objects inTraceList
get mutated by model extraction?Beta Was this translation helpful? Give feedback.
All reactions