|
XPUSP - Home | |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
This interface should be implemented by any class that implements a schedule generator. One should be aware that implementing classes should not hold persistent data on class variables, this because it is very common for calls on cleanUp, prepare, ... to be made on different instances of the implementation class. The reason for this is that several month could pass between one call and another. So that means that if cleanUp is needed, prepare should check if cleanUp was called, and so forth.
Method Summary | |
void |
cleanUp()
If there is a necessity to cleanup between one year and anotherone. |
void |
prepare()
If there is a need to perform preparation before starting to generate the solution, this method should implement that. |
void |
startSolving(Year year)
Start solving the problem. |
void |
stopSolving(Year year)
Stop solving the problem. |
Method Detail |
public void cleanUp() throws java.lang.Exception
Year.doStartpooling
to ensure that everything has been cleaned up.java.lang.Exception
- if there is a problempublic void prepare() throws java.lang.Exception
Year.doStoppooling
java.lang.Exception
- if there is a problempublic void startSolving(Year year) throws java.lang.Exception
Year.doStartsolving
you can assume that PoolResults have been calculated herejava.lang.Exception
- if there is a problempublic void stopSolving(Year year) throws java.lang.Exception
Year.doStopsolving
you can assume that PoolResults have been calculated herejava.lang.Exception
- if there is a problem
|
XPUSP - Home | |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |