Re: A new query

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: A new query

Jomi Fred Hubner-4
Hi Carlos,

yes, it is possible to know which plan caused the failure. The internal action .current_intention(I)  allow us to get all the stack of plans (intended means).

it follows an excerpt of the demo/failure example that illustrate the use:

-!g3(failure)[error(ErrorId), error_msg(Msg), code(CodeBody), code_src(CodeSrc), code_line(CodeLine)] : true
  <- .print("Error ", ErrorId, " '",Msg,"' by ",CodeBody," in ",CodeSrc,":",CodeLine);
     .print("current intention is: ",I);
     I = intention(Id,[_|IntendedMeans]);
     .println("*  Intention #",Id, ", IM stack:");

  <- .println("*        ",Body,"      * unifier: ",Unif);

On 17/09/2012, at 14:50, Carlos Alberto Gonzalez-Alarcon wrote:

> Hi again
> I'm here, asking for your help, once more. :) I would like to know if there is a way for getting the tag plan of a plan, from a fail plan.
> For example, if I have these plans
> @plan_A
> +!te: ctxtA <-
>   acc_1.
> @plan_B
> +!te : ctxtB <-
>   acc2.
> @fail_Plan
> -!te: true <-
>   "-----------".
> I want to know in "-----------" if the plan was triggered by planA or by planB. I don't know if there is an internal action, or if I need to develop it.
> Once again, thanks, my best regards
> Carlos Gonzalez
> University of Valencia

Jomi Fred Hubner
Federal University of Santa Catarina
Department of Automation and Systems Engineering
PO Box 476, Florianópolis, SC
88040-900 Brazil

Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
Jason-users mailing list
[hidden email]