Skip to content

DLV specific option being used for other solver too #33

@Farfi55

Description

@Farfi55

The --filter=predicate/arity options exists only for the dlv executable, but if we try to run a brain using clingo for example, it won't recognize it and fail execution.

// inside ASPReactiveExecutor
protected override List<OptionDescriptor> SpecificOptions()
{
    List<OptionDescriptor> options = new List<OptionDescriptor>();
    options.Add(new OptionDescriptor("--filter=setOnActuator/1 "));
    return options;
}
// inside ASPPlannerExecutor
protected override List<OptionDescriptor> SpecificOptions()
{
    List<OptionDescriptor> options = new List<OptionDescriptor>();
    options.Add(new OptionDescriptor("--filter=applyAction/2,actionArgument/3 "));
    return options;
}

A possible fix would be to add #show setOnActuator/1. for the reactive Executor and #show applyAction/2. #show actionArgument/3. for Planner executor.

This won't guarantee that the only predicates received in output by the ThinkEngine are the ones specified in the filter, as the user can also use the #show ... functionality for other predicates.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions