A problem represents infeasibilities, alerts and warnings in the plan. More...
#include <model.h>
Classes | |
class | const_iterator |
This class models an STL-like iterator that allows us to iterate over the named entities in a simple and safe way. More... | |
Public Member Functions | |
void | endElement (XMLInput &, const Attribute &, const DataElement &) |
virtual const DateRange | getDateRange () const =0 |
virtual string | getDescription () const =0 |
HasProblems * | getOwner () const |
virtual const MetaClass & | getType () const |
virtual double | getWeight () const =0 |
virtual bool | isFeasible () const =0 |
Problem (HasProblems *p) | |
virtual void | writeElement (XMLOutput *, const Keyword &, mode=DEFAULT) const |
virtual | ~Problem () |
Static Public Member Functions | |
static const_iterator | begin (HasProblems *, bool=true) |
static const_iterator | begin () |
static void | clearProblems (HasProblems &p, bool setchanged=true) |
static void | clearProblems () |
static const const_iterator | end () |
static void | writer (const MetaCategory *, XMLOutput *) |
Static Public Attributes | |
static const MetaCategory * | metadata |
Protected Member Functions | |
void | addProblem () |
bool | operator< (const Problem &a) const |
void | removeProblem () |
Protected Attributes | |
Problem * | nextProblem |
HasProblems * | owner |
Friends | |
class | const_iterator |
A problem represents infeasibilities, alerts and warnings in the plan.
Problems are maintained internally by the system. They are thus only exported, meaning that you can't directly import or create problems.
This class is the pure virtual base class for all problem types.
The usage of the problem objects is based on the following principles:
Definition at line 831 of file model.h.
frepple::Problem::Problem | ( | HasProblems * | p | ) | [inline, explicit] |
Constructor. Note that this method can't manipulate the problem container, since the problem objects aren't fully constructed yet.
virtual frepple::Problem::~Problem | ( | ) | [inline, virtual] |
void frepple::Problem::addProblem | ( | ) | [protected] |
Adds a newly created problem to the problem container. This method needs to be called in the constructor of a problem subclass. It can't be called from the constructor of the base Problem class, since the object isn't fully created yet and thus misses the proper information used by the compare method.
Definition at line 50 of file problem.cpp.
Problem::const_iterator frepple::Problem::begin | ( | HasProblems * | i, | |
bool | refresh = true | |||
) | [static] |
Return an iterator to the first problem of this entity. The iterator can be incremented till it points past the last problem of this plannable entity.
The boolean argument specifies whether the problems need to be recomputed as part of this method.
Definition at line 460 of file problem.cpp.
Problem::const_iterator frepple::Problem::begin | ( | ) | [static] |
Returns an iterator to the very first problem. The iterator can be incremented till it points past the very last problem.
Definition at line 453 of file problem.cpp.
void frepple::Problem::clearProblems | ( | HasProblems & | p, | |
bool | setchanged = true | |||
) | [static] |
Erases the list of problems linked with a certain plannable object.
If the second parameter is set to true, the problems will be recreated when the next problem detection round is triggered.
Definition at line 191 of file problem.cpp.
void frepple::Problem::clearProblems | ( | ) | [static] |
Erases the list of all problems. This methods can be used reduce the memory consumption at critical points. The list of problems will be recreated when the problem detection is triggered again.
Definition at line 179 of file problem.cpp.
const Problem::const_iterator frepple::Problem::end | ( | ) | [static] |
Return an iterator pointing beyond the last problem.
Definition at line 471 of file problem.cpp.
void frepple::Problem::endElement | ( | XMLInput & | , | |
const Attribute & | , | |||
const DataElement & | ||||
) | [inline, virtual] |
Called while restoring the model from an XML-file.
This is called when the corresponding close element tag is encountered, and the Data() member of pElement is valid.
Implements frepple::utils::Object.
virtual const DateRange frepple::Problem::getDateRange | ( | ) | const [pure virtual] |
Returns the duration of this problem.
Implemented in frepple::ProblemBeforeCurrent, frepple::ProblemBeforeFence, frepple::ProblemPrecedence, frepple::ProblemDemandNotPlanned, frepple::ProblemLate, frepple::ProblemEarly, frepple::ProblemShort, frepple::ProblemExcess, frepple::ProblemPlannedLate, frepple::ProblemPlannedEarly, frepple::ProblemCapacityOverload, frepple::ProblemCapacityUnderload, frepple::ProblemMaterialShortage, and frepple::ProblemMaterialExcess.
virtual string frepple::Problem::getDescription | ( | ) | const [pure virtual] |
Returns a text description of this problem.
Implemented in frepple::ProblemBeforeCurrent, frepple::ProblemBeforeFence, frepple::ProblemPrecedence, frepple::ProblemDemandNotPlanned, frepple::ProblemLate, frepple::ProblemEarly, frepple::ProblemShort, frepple::ProblemExcess, frepple::ProblemPlannedLate, frepple::ProblemPlannedEarly, frepple::ProblemCapacityOverload, frepple::ProblemCapacityUnderload, frepple::ProblemMaterialShortage, and frepple::ProblemMaterialExcess.
HasProblems* frepple::Problem::getOwner | ( | ) | const [inline] |
virtual const MetaClass& frepple::Problem::getType | ( | ) | const [inline, virtual] |
Return a reference to the metadata structure.
Implements frepple::utils::Object.
Reimplemented in frepple::ProblemBeforeCurrent, frepple::ProblemBeforeFence, frepple::ProblemPrecedence, frepple::ProblemDemandNotPlanned, frepple::ProblemLate, frepple::ProblemEarly, frepple::ProblemShort, frepple::ProblemExcess, frepple::ProblemPlannedLate, frepple::ProblemPlannedEarly, frepple::ProblemCapacityOverload, frepple::ProblemCapacityUnderload, frepple::ProblemMaterialShortage, and frepple::ProblemMaterialExcess.
virtual double frepple::Problem::getWeight | ( | ) | const [pure virtual] |
Returns a double number reflecting the magnitude of the problem. This allows us to focus on the significant problems and filter out the small ones.
Implemented in frepple::ProblemBeforeCurrent, frepple::ProblemBeforeFence, frepple::ProblemPrecedence, frepple::ProblemDemandNotPlanned, frepple::ProblemLate, frepple::ProblemEarly, frepple::ProblemShort, frepple::ProblemExcess, frepple::ProblemPlannedLate, frepple::ProblemPlannedEarly, frepple::ProblemCapacityOverload, frepple::ProblemCapacityUnderload, frepple::ProblemMaterialShortage, and frepple::ProblemMaterialExcess.
virtual bool frepple::Problem::isFeasible | ( | ) | const [pure virtual] |
Returns true if the plan remains feasible even if it contains this problem, i.e. if the problems flags only a warning. Returns false if a certain problem points at an infeasibility of the plan.
Implemented in frepple::ProblemBeforeCurrent, frepple::ProblemBeforeFence, frepple::ProblemPrecedence, frepple::ProblemDemandNotPlanned, frepple::ProblemLate, frepple::ProblemEarly, frepple::ProblemShort, frepple::ProblemExcess, frepple::ProblemPlannedLate, frepple::ProblemPlannedEarly, frepple::ProblemCapacityOverload, frepple::ProblemCapacityUnderload, frepple::ProblemMaterialShortage, and frepple::ProblemMaterialExcess.
bool frepple::Problem::operator< | ( | const Problem & | a | ) | const [protected] |
Comparison of 2 problems.
To garantuee that the problems are sorted in a consistent and stable way, the following sorting criteria are used (in order of priority):
The sorting is expected such that it can be used as a key, i.e. no two problems of will ever evaluate to be identical.
Definition at line 37 of file problem.cpp.
void frepple::Problem::removeProblem | ( | ) | [protected] |
Removes a problem from the problem container. This method needs to be called from the destructor of a problem subclass.
Due to the single linked list data structure, this methods' performance is linear with the number of problems of an entity. This is acceptable since we don't expect entities with a huge amount of problems.
Definition at line 76 of file problem.cpp.
void frepple::Problem::writeElement | ( | XMLOutput * | , | |
const Keyword & | , | |||
mode | = DEFAULT | |||
) | const [virtual] |
Called while writing the model into an XML-file. The user class should write itself out, using the IOutStream members for its "simple" members and calling writeElement recursively for any contained objects. Not all classes are expected to implement this method. In instances of such a class can be created but can't be persisted. E.g. Command
Reimplemented from frepple::utils::Object.
Definition at line 227 of file problem.cpp.
void frepple::Problem::writer | ( | const MetaCategory * | c, | |
XMLOutput * | o | |||
) | [static] |
Definition at line 211 of file problem.cpp.
friend class const_iterator [friend] |
const MetaCategory * frepple::Problem::metadata [static] |
Storing metadata on this class.
Reimplemented in frepple::ProblemBeforeCurrent, frepple::ProblemBeforeFence, frepple::ProblemPrecedence, frepple::ProblemDemandNotPlanned, frepple::ProblemLate, frepple::ProblemEarly, frepple::ProblemShort, frepple::ProblemExcess, frepple::ProblemPlannedLate, frepple::ProblemPlannedEarly, frepple::ProblemCapacityOverload, frepple::ProblemCapacityUnderload, frepple::ProblemMaterialShortage, and frepple::ProblemMaterialExcess.
Problem* frepple::Problem::nextProblem [protected] |
HasProblems* frepple::Problem::owner [protected] |