From 4e8d37b002c9d16fce5c787db69e053915042285 Mon Sep 17 00:00:00 2001 From: Markus Klinik Date: Fri, 24 May 2019 13:14:33 +0200 Subject: [PATCH] data type definitions --- implementation.tex | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/implementation.tex b/implementation.tex index 4b4853e..c469fa0 100644 --- a/implementation.tex +++ b/implementation.tex @@ -13,13 +13,17 @@ Phase two uses these assignments to build schedules. \subsection{Instance Definition} A C2 instance definition consists of a list of resource definitions, a list of task definitions, a list of resource frame definitions, and a list of weights. +A resource definition consists of a name and a list of skills. +A task definition consists of a name, a duration, a list of skill requirements, and a list of predecessors. +A weight is a floating point number. + Resource frames specify resource affinity constraints. -A resource frame has a list of task definitions and a list of resource requirements. +A resource frame has a list of tasks and a list of resource requirements. Every resource requirement of a resource frame is by definition a resource requirement of all tasks inside the frame, and assigning a resource to a frame requirement automatically assigns it to all tasks in the frame. See \cref{fig:resource-frames} for an example. There are two tasks, Prepare and Deploy, which both require an Operator. The tasks are inside a resource frame that requires a Transport. -The meaning of this is that both tasks also require a Transport, and that the transport assigned to both tasks must be the same one. +This means that both tasks also require a Transport, and that the transport assigned to both tasks must be the same one. \begin{figure} -- GitLab