microsoft / microsoft/pict

Combinations lost of it

Open
#41 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.5k
Forks
323
Avg merge
2h 5m
Merged PRs (30d)
4

Description

CONTENT OF PICT INPUT FILE(test.txt):
A: a1
B: b1
C: c1,c2
D: d1,d2
E: e1,e2
F: f1,f2
G: g1,g2,g3,g4
H: h1,h2,h3,h4
I: i1,i2,i3,i4,i5

{A,B,C,E,D}@5
{F,G,H,I}@1

if [E] in {"e1"} then [G] in {"g1","g2"} else [G] in {"g3","g4"};
if [D] in {"d1"} then [I] in {"i1","i3"} else [I] in {"i2","i4","i5"};
if [E] in {"e1"} then [H]="h4" else [H]<>"h4";

AFTER GENERATION BY PICT:(command is: pict test.txt /o:1)
A B C D E F G H I
a1 b1 c1 d2 e2 f2 g3 h3 i4
a1 b1 c2 d1 e1 f1 g2 h4 i1
a1 b1 c2 d2 e2 f2 g4 h2 i2
a1 b1 c1 d1 e1 f1 g1 h4 i3
a1 b1 c2 d2 e2 f1 g4 h1 i5

parameters:ABCDE as@5 have 8 combinations and FGHI as@1 have 5 combinations. We predicted that the combinations of the two submodels have at least 8 results. But when we read and research the source codes of PICT we found that some random pick values of FGHI and constraints had confilcted with the 8 values of ABCDE combinations.

But in fact, we DO have some combinations to stay all of the 8 combination of ABCDE, such as:
A B C D E F G H I
1 | a1 | b1 | c1 | d1 | e1 | f2 | g2 | h4 | i1
2 | a1 | b1 | c1 | d2 | e2 | f1 | g3 | h1 | i2
3 | a1 | b1 | c1 | d1 | e2 | f2 | g4 | h2 | i3
4 | a1 | b1 | c1 | d2 | e1 | f1 | g1 | h4 | i4
5 | a1 | b1 | c2 | d2 | e2 | f2 | g3 | h3 | i5
6 | a1 | b1 | c2 | d1 | e1 | f2 | g2 | h4 | i1
7 | a1 | b1 | c2 | d2 | e1 | f1 | g1 | h4 | i5
8 | a1 | b1 | c2 | d1 | e2 | f1 | g3 | h1 | i3

So in this situation, do we have some method to fix it still using PICT? Do we have other method to generate them? Or we must change the source code of PICT to generate them?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied test.txt input and the pict test.txt /o:1 command, then compare the generated rows with the eight ABCDE combinations listed in the issue. Read the PICT source code that handles submodels, constraints, and output selection; done means establishing whether the behavior is expected or identifying a scoped change that preserves the requested combinations.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
testing-qa, tooling
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.