[OS-tickets] [Optimization Services] #38: Discrepancies between OSgL schema and C++ implementation in OSDataStructures
Optimization Services
coin-trac at coin-or.org
Wed Sep 22 16:01:17 EDT 2010
#38: Discrepancies between OSgL schema and C++ implementation in
OSDataStructures
-------------------------+--------------------------------------------------
Reporter: Gassmann | Owner: somebody
Type: task | Status: new
Priority: major | Milestone:
Component: component1 | Version: 2.0
Resolution: | Keywords: OSgL schema, implementation, constitution
-------------------------+--------------------------------------------------
Description changed by kmartin:
Old description:
> SparseVector in OSDataStructures has
> int* indexes;
> double* values;
>
> For consistence with OSgL it should be
> IntVector* idx;
> DoubleVector* nonz;
>
> Kipp Comment -- I think it would be a mistake to have to define an object
> for each element in an array. For example,
>
> IntVector* idx;
>
> seems far more cumbersome than
>
> int* indexes;
>
> Having a constructor and destructor called for each nonzero could take a
> lot time for large problems.
New description:
SparseVector in OSDataStructures has
int* indexes;
double* values;
For consistence with OSgL it should be
IntVector* idx;
DoubleVector* nonz;
Kipp Comment -- I think it would be a mistake to have to define an object
for each element in an array. For example,
IntVector* idx;
seems far more cumbersome than
int* indexes;
Having a constructor and destructor called for each nonzero could take a
lot time for large problems.
There is also a discrepancy between the implementation of the int and
double vectors in C++ and in the OSgL schema.
--
--
Ticket URL: <https://projects.coin-or.org/OS/ticket/38#comment:2>
Optimization Services <http://projects.coin-or.org/OS>
An interface for Web services implementing optimization.
More information about the OS-tickets
mailing list