Skip to content

Illegal combination given when o:1 set #40

Description

@CL749

Hi Jacek,

I seem to be getting an illegal output but only when I've got the order set to 1 (version 3.3.8.0).

Here is my model file:
CCC: H, L
A0: 0,1
A1: 0,1
B0: 0,1
B1: 0,1
L0: 0,1
L1: 0,1
BIG: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32

IF [CCC] IN {"H"} THEN
([A0] = 1 OR [A1] = 1) AND ([B0] = 1 OR [B1] = 1);

IF [CCC] IN {"L"} THEN
[L0] = 1 OR
[L1] = 1;

If I run with /o:1 then I end up with cases where "CCC" is "H" and both A0 and A1 are 0.

If I run with /o:2 or above I don't get this issue.

I thought I'd let you know in case there is a bug in the tool or incase I'm doing something wrong.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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