frepple::Problem Class Reference

A problem represents infeasibilities, alerts and warnings in the plan. More...

#include <model.h>

Inheritance diagram for frepple::Problem:
frepple::utils::NonCopyable frepple::utils::Object frepple::ProblemBeforeCurrent frepple::ProblemBeforeFence frepple::ProblemCapacityOverload frepple::ProblemCapacityUnderload frepple::ProblemDemandNotPlanned frepple::ProblemEarly frepple::ProblemExcess frepple::ProblemLate frepple::ProblemMaterialExcess frepple::ProblemMaterialShortage frepple::ProblemPlannedEarly frepple::ProblemPlannedLate frepple::ProblemPrecedence frepple::ProblemShort

List of all members.

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
HasProblemsgetOwner () const
virtual const MetaClassgetType () 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 MetaCategorymetadata

Protected Member Functions

void addProblem ()
bool operator< (const Problem &a) const
void removeProblem ()

Protected Attributes

ProblemnextProblem
HasProblemsowner

Friends

class const_iterator

Detailed Description

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.


Constructor & Destructor Documentation

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.

See also:
addProblem

Definition at line 842 of file model.h.

virtual frepple::Problem::~Problem (  )  [inline, virtual]

Destructor.

See also:
removeProblem

Definition at line 848 of file model.h.


Member Function Documentation

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.

See also:
removeProblem

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.

Definition at line 870 of file model.h.

virtual const DateRange frepple::Problem::getDateRange (  )  const [pure virtual]
virtual string frepple::Problem::getDescription (  )  const [pure virtual]
HasProblems* frepple::Problem::getOwner (  )  const [inline]

Returns a pointer to the plannable object that owns this problem.

Definition at line 901 of file model.h.

virtual const MetaClass& frepple::Problem::getType (  )  const [inline, virtual]
virtual double frepple::Problem::getWeight (  )  const [pure virtual]
virtual bool frepple::Problem::isFeasible (  )  const [pure virtual]
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):

  1. Entity
    This sort is to be ensured by the client. This method can't compare problems of different entities!
  2. Type
    Each problem type has a hashcode used for sorting.
  3. Start date

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.

See also:
addproblem

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.


Friends And Related Function Documentation

friend class const_iterator [friend]

Definition at line 834 of file model.h.


Member Data Documentation

Each Problem contains a pointer to the next pointer for the same owner. This class implements thus an intrusive single linked list of Problem objects.

Definition at line 916 of file model.h.

Each Problem object references a HasProblem object as its owner.

Definition at line 911 of file model.h.


The documentation for this class was generated from the following files:

Generated on 25 Sep 2009 for frePPLe by  doxygen 1.6.1