RS01063: A SUB-TUPLE WHEN ADDED TO PARENT TUPLE'S SET COULD GIVE ERROR ABOUT TOO MANY COMPONENTS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • Consider model below that gives "Scripting runtime error: Too
    many components for tuple, expecting 3, found 5: , " <"1" 1 8
    0>" " <"1" 1>" "1"."
    
    Issue is specific to sub-tuple using "with" reference,
    along-with reference assignment of tupleset along-with entire
    sub-tuple being added instead of just the keys.
    
    
    tuple Task {
       key string id;
       int start;
       int end;
       int mandatory;
    }
    {Task} Tasks = {<"1",1,8,0>, <"2",1,5,0>};
    
    tuple TaskWrapper {
      key Task t;
      int val;
    }
    {TaskWrapper} WrappedTasks = {<t, 1> | t in Tasks};
    {TaskWrapper} WrappedTasks1 = WrappedTasks;
    
    tuple Machine {
       key string id;
       int capacity;
    }
    {Machine} Machines = {<"1",1>, <"2",1>};
    
    tuple Assignment {
       key Task t;
       key Machine m;
       int value;
    }
    
    {Assignment} forcedAssignment with t in Tasks, m in Machines;
    //not using with reference for Task also works
    
    execute
    {
     var machine = Opl.first(Machines);
     for(var wt in WrappedTasks1) { //looping over WrappedTasks
    instead of WrappedTasks1 also works
       var task = wt.t;
       forcedAssignment.add(task, machine, 1);
       //adding just the key component works
       //forcedAssignment.add(task.id, machine.id, 1);
     }
    }
    

Local fix

  • Adding just the key component instead of the complete tuple
    helps as below:
    
    forcedAssignment.add(task.id, machine.id, 1);
    

Problem summary

  • This issue has been resolved and fix will be available in CPLEX
    Optimization Studio v12.5.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    RS01063

  • Reported component name

    ILOG ODM ENT

  • Reported component ID

    5724Y0400

  • Reported release

    360

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-17

  • Closed date

    2012-07-26

  • Last modified date

    2012-07-26

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R360 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Decision Optimization Center

Software version:

360

Reference #:

RS01063

Modified date:

2012-07-26

Translate my page

Machine Translation

Content navigation