[Oz] Help: pointers for non-unary resource scheduling ...
H Jansen
H.Jansen at fel.tno.nl
Tue Nov 2 15:49:07 CET 1999
Just an idea (from a new Oz user with scheduling interest):
Isn't the problem that simple that you could use two cascaded
schedulers: the first one sees all resources of the same type as one,
and the second one distributes the tasks over the same-type resources.
Henk.
--
= = Henk Jansen ======== H.Jansen at fel.tno.nl = =
= == TNO Physics and Electronics Laboratory == =
= ==== PO Box 96864 === 2509 JG The Hague ==== =
= ============= The Netherlands ============== =
= Phone: +31 70 374 0215 Fax: +31 70 374 0654 =
= ============================================ =
>From - Wed Nov 3 12:28:53 1999
Received: (from majordomo at localhost)
by grizzly.ps.uni-sb.de (8.9.1a/8.9.1) id JAA04268;
Wed, 3 Nov 1999 09:17:18 +0100
Date: Wed, 3 Nov 1999 09:17:18 +0100
From: owner-oz-users at ps.uni-sb.de
Message-Id: <199911030817.JAA04268 at grizzly.ps.uni-sb.de>
X-Authentication-Warning: grizzly.ps.uni-sb.de: majordomo set sender to owner-oz-users at ps.uni-sb.de using -f
To: tmueller at ps.uni-sb.de
Subject: BOUNCE oz-users at ps.uni-sb.de: Approval required:
>From tmueller Wed Nov 3 09:17:17 1999
Received: from sangam.ncst.ernet.in (sangam.ncst.ernet.in [202.41.110.33])
by grizzly.ps.uni-sb.de (8.9.1a/8.9.1) with ESMTP id JAA03930
for <users at mozart-oz.org>; Wed, 3 Nov 1999 09:10:22 +0100
Received: from konark.ncst.ernet.in (konark.ncst.ernet.in [202.141.151.1])
by sangam.ncst.ernet.in (8.9.1/8.9.1) with ESMTP id NAA27971;
Wed, 3 Nov 1999 13:46:07 +0530 (GMT+05:30)
Received: from ss575.ncst.ernet.in (ss575.ncst.ernet.in [144.16.2.110])
by konark.ncst.ernet.in (8.9.3/8.9.1) with ESMTP id NAA23579;
Wed, 3 Nov 1999 13:13:56 -0500 (GMT)
Date: Wed, 3 Nov 1999 13:24:12 +0500 (GMT)
From: P Ravi Prakash <ravi at konark.ncst.ernet.in>
X-Sender: ravi at ss575.ncst.ernet.in
To: Tobias =?iso-8859-1?Q?M=FCller?= <tmueller at ps.uni-sb.de>
cc: users at mozart-oz.org
Subject: Re: [Oz] Help: pointers for non-unary resource scheduling ...
In-Reply-To: <38197387.566AF7F at ps.uni-sb.de>
Message-ID: <Pine.GSO.4.20.9911031312260.345-100000 at ss575.ncst.ernet.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi Tobias,
Thank you for the reply. I had already gone thru the pointers you
gave. All the examples given are using unary resources only. May be I
was not clear in my previous mail.
For example, the constraint, "all the tasks which use the same resource
should be serialised", can be specified using,
Schedule.serializedDisj. As I understand, we cannot use the same
propagator for non-unary resources. My query was, is there a
propagator for this purpose, or we have to specify that using reified
constraints?
I am doing it as follows.
{ForAll TaskList
proc{$ TaskI}
{ForAll TaskList
proc{$ TaskJ}
if (TaskI and TaskJ are different) then
{FD.impl
{FD.conj ((TaskI.date + TaskI.duration)
>: TaskJ.date)
((TaskJ.date + TaskJ.duration)
>: TaskI.date)}
(TaskI.resource \=: TaskJ.resource)
1}
end
end}
end}
Please let me know if there is a better solution.
> have a look at
>
> http://www.mozart-oz.org/documentation/system/node27.html#chapter.schedule
>
> and
>
> http://www.mozart-oz.org/documentation/fdt/node46.html#chapter.scheduling
>
> You ought to find appropriate information there.
>
> I hope that helps
> -- Tobias
> Just an idea (from a new Oz user with scheduling interest):
>
> Isn't the problem that simple that you could use two cascaded
> schedulers: the first one sees all resources of the same type as one,
> and the second one distributes the tasks over the same-type resources.
>
> Henk.
Henk,
I am doing the same thing right now. Wondering whether there is a
better way of doing it.
Regards,
Ravi
-
Please send submissions to users at mozart-oz.org
and administriva mail to users-request at mozart-oz.org.
The Mozart Oz web site is at http://www.mozart-oz.org/.
More information about the mozart-users
mailing list