> Discrete Optimization > Early Tardy Scheduling > Understanding the Data File |
Understanding the Data File |
INDEX PREVIOUS NEXT |
The data for this problem are available online with your installation of the product in the file yourCPLEXhome/examples/data/etsp.dat
.
In this particular example, the number of activities of a job matches the number of resources. However, you can easily modify the application to accommodate a different number of jobs and resources.
In the file for this particular example, the first number (10) indicates the number of jobs and resources and thus the number of activities per job. Each of the other lines of the file corresponds to the description of a job. In a line, each pair of numbers corresponds to one activity. In each such pair, the first number represents the index of the resource that must process this activity. The second number in each pair indicates the duration of the activity. For example, if you look at job0
, you see:
2 41 0 32 4 72 1 65 3 53 9 99 7 35 8 46 5 53 6 2 983 3 10 |
That line means that activity0
of job0
must be processed by resource2
and it lasts 41 units of time, activity1
of this job must be processed on resource0
and lasts 32 time units, and so forth.
The last three numbers of a line indicate the due date, the earliness cost, and the tardiness cost. For example, if job0
finishes by date 983, then no costs are incurred. If it finishes at 981, then it incurs an earliness cost of (3x2) = 6. If it finished at 985, then it incurs a tardiness cost of 20.
Copyright © 1987-2003 ILOG, S.A. All rights reserved. Legal terms. | PREVIOUS NEXT |