#include <chromo.h>
Collaboration diagram for tupleinfo_t:
Data Fields | |
char * | name |
Name of the event. | |
int | tupleid |
Tuple ID of this tuple. | |
int * | resid |
Array of resource IDs that are used by this event. | |
domain ** | dom |
Array of pointers to domains for this event. | |
int | dependent |
Is this event dependent on another event? |
int* tupleinfo_t::resid |
Array of resource IDs that are used by this event.
This array hold the static information that was loaded from the XML configuration file.
Length of array is equal to the number of resource types defined dat_typenum. The first element in the array defines the resource with resource type ID 0 and so on.
If an element of this array is equal to INT_MIN then the information about this resource type was not included in the XML file. This value is always different from INT_MIN for constant resource types
Array of pointers to domains for this event.
Length of array is equal to the number of resource types defined dat_typenum. The first element in the array defines the domain for the resource type ID 0 and so on.
Is this event dependent on another event?
An event can be marked as dependent if its variable resources depend on which variable resources have been assigned to some other (independent) event.
Variable resources for a dependent events are set by a special function and are not handled by the genetic algorithm.
Set to 1 if this event is dependent. Set to 0 if this event is independent.