[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-glpk] Modelling Advice Request - Project Tasks

From: Jeffrey Kantor
Subject: Re: [Help-glpk] Modelling Advice Request - Project Tasks
Date: Fri, 22 Jan 2010 08:41:52 -0500

Hi Yingjie,

The 'BigM' piece was there in my first version as a way of having the solver calculate the position[a] data.  I was being lazy.  My later version avoided this by computing position in a post-processing step after the solver.  This problem doesn't actually need BigM at all.

I agree, this would be a nice problem to include in the example set.


On Fri, Jan 22, 2010 at 3:21 AM, Yingjie Lan <address@hidden> wrote:
Hi Tawny,

My pleasure, surely enjoyed the problem as well. ;)
Probably should contribute this thing into the example set
that ships with GLPK, and maybe I will also add an exampel
in PyMathProg, once GLPK has it (which means GPL, hehe).

> > Big-M: M = 15 - 1 given 15 tasks.

> param BigM := 100;

Usually too big an M slows down the solver,
it might be good to make it as smaller as you can.

If you really have a huge model, say with
200 tasks, row generation suggested by others
might be a must, my rough guess.



Help-glpk mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]