Issue1176

Title Accept less restrictive sas file format as input
Priority wish Status chatting
Superseder Nosy List jendrik, malte, tanja
Assigned To Keywords
Optional summary
We want the search component to accept a less restrictive format of .sas files as input.
- Allow variables with just one domain value.
- Components need not be sorted by variable, see also issue1158.
- Support trivially solvable and unsolvable tasks, see issue1160.
- Allow operators with no effect.

Created on 2025-02-11.12:12:08 by tanja, last changed by malte.

Summary
We want the search component to accept a less restrictive format of .sas files as input.
- Allow variables with just one domain value.
- Components need not be sorted by variable, see also issue1158.
- Support trivially solvable and unsolvable tasks, see issue1160.
- Allow operators with no effect.
Messages
msg11784 (view) Author: malte Date: 2025-02-11.12:42:52
Thanks for starting this.

Now that we've started going down this path, I think we should remove all restrictions that don't have a strong justification.

Other examples of restrictions without strong justification are not allowing duplicate conditions, requiring conditions to be grouped by variable and not allowing contradictory conditions. (You mention dropping this restriction for the goal, but I would then also drop it for preconditions, effect conditions and axioms.)

An example of a justified restriction is the semantic restriction that mutexes must indeed be mutexes because we cannot efficiently verify this.
History
Date User Action Args
2025-02-11 12:42:52maltesetstatus: unread -> chatting
messages: + msg11784
2025-02-11 12:21:22jendriksetnosy: + malte, jendrik, tanja
2025-02-11 12:12:08tanjacreate