Databases
StackOverflow2013
Postsdbo
POConvert MIndiGolog fluents to the IndiGolog causes_val format
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POConvert MIndiGolog fluents to the IndiGolog causes_val format
    primarykey
    data
    text
    <p>I am using <em>Eclipse</em> (version: Kepler Service Release 1) with <em>Prolog Development Tool</em> (PDT) plug-in for Prolog development in Eclipse. Used these installation instructions: <a href="http://sewiki.iai.uni-bonn.de/research/pdt/docs/v0.x/download" rel="nofollow">http://sewiki.iai.uni-bonn.de/research/pdt/docs/v0.x/download</a>.</p> <p>I am working with <em>Multi-Agent IndiGolog</em> (MIndiGolog) 0 (the preliminary prolog version of MIndiGolog). Downloaded from here: <a href="http://www.rfk.id.au/ramblings/research/thesis/" rel="nofollow">http://www.rfk.id.au/ramblings/research/thesis/</a>. I want to use MIndiGolog because it represents time and duration of actions very nicely (I want to do <em>temporal planning</em>), and it supports planning for multiple agents (including concurrency).</p> <p><em>MIndiGolog</em> is a high-level programming language based on <em>situation calculus</em>. Everything in the language is exactly according to situation calculus. This however does not fit with the project I'm working on.</p> <p>This other high-level programming language, <em>Incremental Deterministic (Con)Golog</em> (IndiGolog) (Download from here: <a href="http://sourceforge.net/p/indigolog/code/ci/master/tree/" rel="nofollow">http://sourceforge.net/p/indigolog/code/ci/master/tree/</a>) (also made with Prolog), is also (loosly) based on situation calculus, but uses fluents in a very different way. It makes use of causes_val-predicates to denote which action changes which fluent in what way, and it does not include the situation in the fluent!</p> <p>However, <strong>this is what the rest of the team actually wants</strong>. I need to rewrite MIndiGolog so that it is still an offline planner, with the nice representation of time and duration of actions, but with the causes_val predicate of IndiGolog to change the values of the fluents.</p> <p>I find this extremely hard to do, as my knowledge in Prolog and of situation calculus only covers the basics, but they see me as the expert. I feel like I'm in over my head and could use all the help and/or advice I can get.</p> <p>I already removed the situations from my fluents, made a planning domain with causes_val predicates, and tried to add IndiGolog code into MIndiGolog. But with no luck. Running the planner just returns "false." And I can make little sense of the trace, even when I use the GUI-tracer version of the SWI-Prolog debugger or when I try to place spy points as strategically as possible.</p> <p>Thanks in advance,</p> <p>Best, PJ</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USfalse
    1. USPJvG
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POConvert MIndiGolog fluents to the IndiGolog causes_val format
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POConvert MIndiGolog fluents to the IndiGolog causes_val format
      1. USCapelliC
      1. VTFavorite
    3. VO
      singulars
      1. POConvert MIndiGolog fluents to the IndiGolog causes_val format
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIndeed, a daunting task ! My compliments, and I wish you all the best of luck.
      singulars
      1. POConvert MIndiGolog fluents to the IndiGolog causes_val format
      1. USCapelliC
    2. COI fear the GUI tracer make little sense, maybe you're going better with `?-leash([-all]),trace.` and then enter an *extremely* simple query you know should succeed. You will have chance to examine the execution sequence and see where it fail.
      singulars
      1. POConvert MIndiGolog fluents to the IndiGolog causes_val format
      1. USCapelliC
    3. COI wonder why you're departing from Mozart ?
      singulars
      1. POConvert MIndiGolog fluents to the IndiGolog causes_val format
      1. USCapelliC
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload