You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing an enumerate design the default or assigned ‘top-level’ Display IDs are not fully enumerated across the set. This leads to unexpected ‘ghost’ permutations to appear with the top-level Display ID. If the sequence is defined as a component first (e.g. RBS F1) and then a combinatorial design is added with components other than F1, then the enumeration still has constructs with F1 present, but they are not fully enumerated across the set. So, the ‘top level’ Display id component is being treated differently from the other combinatorial components. The ‘top level’ components are included as a single design variant, whereas the combinatorial designs are fully enumerated across all variants.
e.g.
with 2 RBS sequences that each have combinatorial designs:
RBS1 – Display id: P3
Combinatorial variants: H1, S3
RBS2 – Display id: P1
Combinatorial variants: A1, E1
Enumerated design output: the ‘top-level’ Design ID single variant is the 4th row. Only the combinatorial RBSs are fully enumerated to give the 4 expected combinations. If all 3 RBSs for each component were fully enumerated there would be 9 designs.
Even if the Design id isn’t specified as a part, an extra variant appears with the randomly assigned Display ids.
This is a problem since there is no scenario I can think of where this top level would be desired in addition to the enumerated combinatorial designs.
The fact that it is there means that it would have to be pulled out of the CSV file before progressing to build and it always appears in random positions.
The text was updated successfully, but these errors were encountered:
When doing an enumerate design the default or assigned ‘top-level’ Display IDs are not fully enumerated across the set. This leads to unexpected ‘ghost’ permutations to appear with the top-level Display ID. If the sequence is defined as a component first (e.g. RBS F1) and then a combinatorial design is added with components other than F1, then the enumeration still has constructs with F1 present, but they are not fully enumerated across the set. So, the ‘top level’ Display id component is being treated differently from the other combinatorial components. The ‘top level’ components are included as a single design variant, whereas the combinatorial designs are fully enumerated across all variants.
e.g.
with 2 RBS sequences that each have combinatorial designs:
RBS1 – Display id: P3
Combinatorial variants: H1, S3
RBS2 – Display id: P1
Combinatorial variants: A1, E1
Enumerated design output: the ‘top-level’ Design ID single variant is the 4th row. Only the combinatorial RBSs are fully enumerated to give the 4 expected combinations. If all 3 RBSs for each component were fully enumerated there would be 9 designs.
Pro_XdV5 S3 CDS_VRSi A1 CDS_cNXb
Pro_XdV5 H1 CDS_VRSi A1 CDS_cNXb
Pro_XdV5 S3 CDS_VRSi E1 CDS_cNXb
Pro_XdV5 P3 CDS_VRSi P1 CDS_cNXb
Pro_XdV5 H1 CDS_VRSi E1 CDS_cNXb
Even if the Design id isn’t specified as a part, an extra variant appears with the randomly assigned Display ids.
This is a problem since there is no scenario I can think of where this top level would be desired in addition to the enumerated combinatorial designs.
The fact that it is there means that it would have to be pulled out of the CSV file before progressing to build and it always appears in random positions.
The text was updated successfully, but these errors were encountered: