(SARBayes)	Main	Related Pages	Class List	Hierarchy	Methods	Files

Todo List

page SORAL Developer's Guide

Right now, only on unix systems, so you may have to link statically. -"make libinstall" will eventually put libsoral.a and the header files in convenient places. -"make test" is the same as "make exec" except that it sets the TESTMODE flag, generating lots of debug info. If any of those don't work, please contact us immediately. Chances are, you caught us during some active patching.

Consider a soral namespace. See dcAPI page 7.

This is just an example of a ``To-Do'' item.

Member Allocation::~Allocation ()

ASO 12mar03 Should this exist? We removed most fo the other "unuseful" destructors. Now we are using the vector class, the clean up is taken care of by the vectors destructor. So we don't have to "delete [] myCoverage;" etc.

Member Allocation::calcAllocation ()=0

Define here? Inline?

Member Allocation::getCoverage (int areaNum)

Once upon a time these were virtual. Any reason to change back?

Member Allocation::getCoverage (int areaNum)

OK, I've been persuaded that initializing to "-1" has several advantages. Change the implementation and the polemic.

Member Allocation::getEffectiveness (int areaNum, int resourceNum)

Define here? Inline?

Member Array2D::Array2D (const int p_rows, const int p_columns, const valarray< double > p_array1D)

Change assertion to proper exception.

Member Array2D::Array2D (const Array2D &p_base, const Array2D &p_extension, const joinType p_joinTo)

Throw an exception if arrays are the wrong size.

Member CharnesCooper::firstArea (const int Resource) const

: It would be better if it threw an exception

Member CharnesCooper::firstArea (void) const

: It would be better if it threw an exception

Member CharnesCooper::firstRes (const int Area) const

: It would be better if it through exceptions, or used enums.

Member CharnesCooper::nextArea (const int Resource, const int currentArea) const

: It would be better if it threw exceptions or enum NO_MORE_AREAS?

Member CharnesCooper::nextArea (const int currentArea) const

: It would be better if it threw exceptions?

Member CharnesCooper::nextRes (const int Area, const int currentResource) const

: Perhaps we should NOT suggest that this one throw an exception. Maybe return a "warning" exception: "No more resources"

Member UserDef::firstArea (const int resource) const

It should throw an exception if the resource is invalid.

Member UserDef::firstRes (const int area) const

: Throw exception on invalid input

Member UserDef::firstRes (const int area) const

Throw exception here.

Member UserDef::nextArea (const int resource, const int currentArea) const

: Throw exception on invalid input

Member UserDef::nextArea (const int resource, const int currentArea) const

Throw exception here.

Member UserDef::nextArea (const int currentArea) const

: Throw exception on invalid input.

Member UserDef::nextArea (const int currentArea) const

Throw exception here.

Member UserDef::nextRes (const int area, const int currentResource) const

: Throw exception on invalid input.

Member UserDef::nextRes (const int area, const int currentResource) const

Throw exception here.

Member Washburn::optimum ()

Check: Do we we need to check divide by zero here?

Member Washburn::solveEqn (int p_index, double p_maxTime, int &p_pivot)

Check: Do we need to check whether effectiveness is nozero?

Member printAssignments (const Allocation &theAllocation)

Remove printAssignments from here?

Member printAssignments (const Allocation &theAllocation)

Remove printAssignments from here?

Member matches (const Allocation &theAlloc, const Array2D &answer, const int numAreas, const int numResources)

Use a more rigorous tol.

---

(SARBayes)	Main	Related Pages	Class List	Hierarchy	Methods	Files