[RavenclawDev 171] Re: reopening concepts

[Dan Bohus]

Hi Svetlana, 

 

There's a ReOpenConcepts() method class on each agent. If you call it,
all the concept contained in the subtree starting at that agent will be
reopened.

 

Reopen pushes the values into the history. It does not set the concept
to UNAVAILABLE. 

A concept is AVAILABLE if a value exists for that concept somewhere
(current value or in history)

A concept is UPDATED if a value exists for that concept in the current
value. So once you Reopen in general the concept will still be available
but it will no longer be updated. 

 

The answer to the last question escapes me right now (I'll have to look
at the Roomline task tree). I suspect that either there is some reason I
might still want to hold on to the histories for some reason, or it
might be just a poor implementation issue...

 

Hope this helps,

-Dan

 

________________________________

From: ravenclaw-developers-bounces at LOGANBERRY.srv.cs.cmu.edu
[mailto:ravenclaw-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] On
Behalf Of Svetlana Stenchikova
Sent: Friday, October 27, 2006 11:42 PM
To: ravenclaw-developers at cs.cmu.edu
Subject: [RavenclawDev 169] reopening concepts

 

Hi,

is it possible to REOPEN all concepts that are declared in the above
agent without explicitly specifying each concept?

I understand that REOPEN concept pushes the concept value into the
history.
Does it also set the status of the concept to UNAVAILABLE? 


In Roomline you also call ClearExplicitlyConfirmedHyp() and
ClearExplicitlyDisconfirmedHyp() in ResetTask. 
Why not call clear() which is supposed to clear everything for the
concept?


thank you,
Svetlana

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/ravenclaw-developers/attachments/20061104/c2c61d1c/attachment.html