Format Description for FRCPSP Lower Bounds

Your solution must have a header surrounded with equal signs (7 or more =). The header shall have the name of the instance set (Instance Set), the name of the problem instance (Instance Name) and also the lower bound (Lower Bound). Please note that Instance Set is the same as you have in instance set files without any suffix (for f10.zip, Instance Set is f10 for example). Also, Instance Name is the same as the name of the file contained in instance set file without the ending '.xml' suffix. For example, for NetworkGen75.xml, Instance Name will be NetworkGen75:

    ==========================================
    Instance Set    :f10
    Instance Name   :NetworkGen75
    Lower Bound     :153
    ==========================================

After the header, you must have lines like the following:

    a=1 t=0  r1=0.0  r2=0.0  r3=0.0  r4=0.0
    a=2 t=1  r1=6.888    r2=4.443222858557518    r3=5.020465423337185    r4=5.621872157121637
    .
    .
    .
    a=12    t=89     r1=0.0  r2=0.0  r3=0.0  r4=0.0

Each line represents an activity (a=2), a time period (t=1) and resource demands for each resource type (for resource type r1, the demand is 6.888 for example).
Activity numbers must be written in a non-decreasing order. Also, time periods within a particular activity must be in an increasing order.

NOTE: while activity and resource numbers may start from 1 in instance sets, they must start from zero in your solution file. So, activity N in your solution file would correspond to activity N-1 in instance set. And, the same thing applies to resource numbers.

After submitting your solution, you should get the result report from the system. The system will tell you whether your solution is correct or not. In case of incorrect solution, you would get the reason that your solution is not correct. Your solution may be incorrect in its format or in its feasibility.

Some possible format error descriptions are:

    Error on line 45 of solution for NetworkGen75: activity numbers are not in increasing order.
    Error on line 45 of solution for NetworkGen75: time period numbers for activity 5 are not in increasing order.

Some possible infeasibility descriptions are:

 Your Lower Bound (300) for NetworkGen75 is greater than the longest possible makespan of the project which is 146.
 Your Lower Bound (12) for NetworkGen75 is less than the shortest possible makespan of the project which is 40.
 Your lower bound for NetworkGen75 is not better than the current one and has not updated our archive.

In case your solution and your lower bound is correct, you should get the following message:

 Your lower bound for NetworkGen75 has updated our archive.