Decision Optimization

Decision Optimization

Delivers prescriptive analytics capabilities and decision intelligence to improve decision-making.


#Analytics
#DecisionOptimization
#DecisionOptimization
 View Only
  • 1.  Can I ask a question here?

    Posted 05/24/11 11:36 AM

    Originally posted by: Lamber1


    In Demo program(V12) of ETsp.cs, what is the meaning of "1" and "2" in the piecewise function in line 91 and 92:

    double[] points = {1, data.dueDate[j]};
    double[] slopes = {2, -data.earlinessCost[j],
    data.tardinessCost[j]};

    is this the number of points or number of slopes? I checked other examples, there is no such numbers for example in transport.cs.

    In addition, I think the explanation of resources required for activity is misleading in manual P700, V12.

    Thanks,
    #CPLEXOptimizers
    #DecisionOptimization


  • 2.  Re: Can I ask a question here?

    Posted 05/26/11 09:52 AM

    Originally posted by: Lamber1


    Why nobody answers my question, is it too simple? but I just feel very confused about ".net" document since they only give short explanation and it is difficult to follow. Thank you for your patience.
    #CPLEXOptimizers
    #DecisionOptimization


  • 3.  Re: Can I ask a question here?

    Posted 05/26/11 10:25 AM

    Originally posted by: SystemAdmin


    I am not sure yet but I think the numbers '1' and '2' you mention should not be there.
    When you look at the same example for C++ (etsp.cpp) then you can see that in the C++ version they specify the number of breakpoints and slopes. However, in C# there is no need to explicitly specify this length. When you look at the description of the C++ example then it is pretty clear that the breakpoint array should have 1 element and the slopes array should have 2 elements.
    I think this is a copy-and-paste error that was done when the C++ version of the example was extended to C# (and Java). You should just ignore (or even better remove) those two numbers.
    Thank you for finding this bug!
    #CPLEXOptimizers
    #DecisionOptimization