Menu
▾
▴
animl-develop
|
From: Burkhard S. <b_...@us...> - 2004-12-16 14:04:11
|
Mark, >>>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. > > I don't think that is completely true. The only ValueSet that absolutely > requires a length is the AutoIncrementedValueSet as you cannot AutoIncrement > without knowing how many times to increment!! I agree that we need to know how many times to increment. How can we find out in the current structure? Calculate endOffset-startOffset in the AutoIncrementedValueSet. Proposal: - make startOffset and endOffset required for all valuesets (they are optional right now) - leave the number *ValueSets at unbounded (as is) Justificatin: We need the offsets anyway in the case of sparse / non-continuous data. If we make them mandatory, we can use them not only to "align the data points" but also to determine the number of values to generate in the AutoIncrementedValueSet. > The number of increments is > being taken from the VectorSet @length. However, if each > AutoIncrementedValueSet has a different number of increments, then we are > stuck. There are options: Taking the length from endOffset-startOffset will do it. One less point of possible inconsistency in the file. > take care, I look forward to your recursive parser in an infinitely flexible > AnIML kingdom! AnIML kingdom -- nice. ;-) Best wishes, Burkhard |
|
From: Stuart C. <sc...@un...> - 2004-12-17 12:12:29
|
I like this idea > Proposal: > - make startOffset and endOffset required for all valuesets > (they are optional right now) > - leave the number *ValueSets at unbounded (as is) However, a limitation of XML is that there is no way for enforcing that startOffset is less than endOffset. This needs to be done in the software that generates and uses the XML files. -- Stuart Chalk, Ph.D. Phone:904-620-1938 Associate Professor of Chemistry Fax:904-620-1989 Department of Chemistry and Physics "The Flow Analysis Database" University of North Florida http://www.fia.unf.edu/ 4567 St. Johns Bluff Road S. "The Analytical Sciences Digital Library" Jacksonville FL 32224 USA http://www.asdlib.org/ --------------------------------------------------------- This mail sent through UNF Webmail: https://horde.unf.edu |
|
From: <Ton...@wa...> - 2004-12-17 13:42:13
|
Hi, there is no logical reason why startOffset should be less than endOffset Tony -------------------------------------------------------------- Waters Informatics Europaallee 27, D-50226 Frechen, Germany Tel. +49 2234 9207 - 0 Fax. +49 2234 9207-99 Reply to: ton...@wa... http://www.creonlabcontrol.com http://www.watersinformatics.net -------------------------------------------------------------- WATZIP "Stuart Chalk" <sc...@un...> Sent by: To animl-develop-adm "Burkhard Schaefer" in...@li... <b_...@us...> rge.net cc "Mark F. Bean" <sa...@co...>, "AnIML Developer List" 17.12.2004 13:10 <ani...@li... t> Subject Re: [Animl-develop] Re: Vector Length Issues I like this idea > Proposal: > - make startOffset and endOffset required for all valuesets > (they are optional right now) > - leave the number *ValueSets at unbounded (as is) However, a limitation of XML is that there is no way for enforcing that startOffset is less than endOffset. This needs to be done in the software that generates and uses the XML files. -- Stuart Chalk, Ph.D. Phone:904-620-1938 Associate Professor of Chemistry Fax:904-620-1989 Department of Chemistry and Physics "The Flow Analysis Database" University of North Florida http://www.fia.unf.edu/ 4567 St. Johns Bluff Road S. "The Analytical Sciences Digital Library" Jacksonville FL 32224 USA http://www.asdlib.org/ --------------------------------------------------------- This mail sent through UNF Webmail: https://horde.unf.edu ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Animl-develop mailing list Ani...@li... https://lists.sourceforge.net/lists/listinfo/animl-develop =========================================================== The information in this email is confidential, and is intended solely for the addressee(s). Access to this email by anyone else is unauthorized and therefore prohibited. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. =========================================================== |
|
From: Burkhard S. <b_...@us...> - 2004-12-17 16:10:00
|
Hi everybody, > there is no logical reason why startOffset should be less than endOffset We have to remember that startOffset and endOffset are actually indices. That's why we renamed them in yesterday's phone conference to startIndex and endIndex. They indicate the index of the 1st and the last data point the associated *ValueSet should map to. So the start index actually has to be smaller than the end index. Building a ValueSet where the endIndex is smaller than the startIndex would be very confusing. What would it mean? Should the values be mapped in reverse order? So I believe that the startIndex <= endIndex constraint actually makes sense. Best wishes, Burkhard |
|
From: Burkhard S. <b_...@us...> - 2004-12-17 16:03:54
|
Am Freitag, den 17.12.2004, 07:10 -0500 schrieb Stuart Chalk: > I like this idea > > > Proposal: > > - make startOffset and endOffset required for all valuesets > > (they are optional right now) > > - leave the number *ValueSets at unbounded (as is) > > However, a limitation of XML is that there is no way for enforcing that > startOffset is less than endOffset. This needs to be done in the software > that generates and uses the XML files. That's true. I think we could live with that. Best regards, Burkhard |
Thanks for helping keep SourceForge clean.
X