|
From: Burkhard S. <b_...@us...> - 2004-12-16 03:47:25
|
Oops, one thing I have overlooked: > Perhaps Burkhard missed the point here (probably because my emails have been > confusing). The problem originated when Mark Mullins wanted to put > segmented chromatogram vectors in AutoIncrementedValueSets - which just > isn't going to work unless we allow more than one AutoIncrementedValueSet - > which AnIML does. Having done that, the problem became knowing how long > each Vector segment was - and so the changes started to snowball. I > recommended that he simply encode the data as an EncodedDataSet and not > worry about the space saving, Makes sense. > and that we restrict AutoIncrementedValueSet > and EncodedDataSet to 0 to 1 per Vector. If we do NOT do that, the > VectorSet length becomes problematic as there is no guarantee that all > ValueSets in a Vector are the same length. I think my example illustrates that not all ValueSets need to share the same length. We are currently allowing an unlimited number of ValueSets per Vector to permit storage of data with "holes" / sparse data. 4:47 am... ;-) Burkhard |