Menu
▾
▴
Re: [Animl-develop] Allowed Values in AnIML
|
From: Dominik P. <dom...@ni...> - 2004-03-07 02:31:16
|
Hi Maren, the discussion that I started was supposed to be on the technique layer.=20 This is the only place where we can set "Allowed Values." The "allowed=20 values" won't influence the Part11 compliance issue because they do not=20 directly restrict the AnIML file. You just use them for validation=20 issues. For example: Let's say a technique developer creates a specific parameter with an=20 allowed value range in his technique definition. Sombody then makes a=20 measurement where that parameter value is out of range, and after that=20 he validates his resulting AnIML file against that technique definition=20 from that particular technique developer. What would happen is that the=20 validator will indicate an exception, i.e. that the AnIML file is not=20 valid against that definition because the measured value is out of=20 range. And that is what we would want, beacause the developer of the=20 technique said that the results must be in a particular range, otherwise=20 the file is incorrect. Regardless if the data is out of range or not,=20 the original AnIML contains only the raw, measured values without=20 further manipulation, which should be fine for Part 11. The same can be=20 true for vectors if we decide to add "Allowd Values" to the vectors too. Regarding the other mail, with the idea to allow ranges of "allowed=20 values," we still have the ability to set just one value (e.g., string=20 or number), or better yet let's say any simple type. We can do this by=20 just assigning a value to the minimum tag while leaving the maximum tag=20 free, or write the same value in both tags. So this is just a question=20 of modelling. -- Dominik Mar...@cr... wrote: >Dear Dr. Chalk, > > =20 > >>Both MP and BP (shouldn't they be MeltingPoint and BoilingPoint) are in >>most cases ranges of numbers. >> =20 >> >The ability to store this is a matter of the technique definition, not o= f >the Core schema (to which Dominik was referring). >As I am currently writing prototype technique definitions, I will gladly >incorporate this. Thank you for reminding me! > > =20 > >>As a general note I am stating to work on implementing animl in my lab >> =20 >> >and > =20 > >>I have many other questions. >> =20 >> >Forgive my curiosity: What do you mean by "implementing"? > > =20 > >>Would it be possible to set up CVS for animl development? >> =20 >> >This is generally possible on SourceForge, and used to work, but as far = as >I know there has been some kind of problem. Some people started to try a= nd >make it work again after this was requested at the last working meeting.. >Maybe someone can update us on the current status. > > =20 > >>When I say bugs I mean XSD issues that are either too limiting or are n= ot >>well enough defined. Just a thought. FYI: I can help with both.... ;) >> =20 >> >The animl-develop mailing list is exactly the place to discuss this. So >let's hear your bug reports! > >Best regards, > >Dr. Maren Fiege >Product Manager > >------------------------------------------------------------------------= --------------------- > >CREON=B7LAB=B7CONTROL AG >a subsidiary of Waters Corporation >Europaallee 27-29, D-50226 Frechen, Germany >Tel. +49 2234 9207 0 >Fax. +49 2234 9207 99 > >http://www.creonlabcontrol.com > >For up-to-date information subscribe to our free newsletter at >http://www.creonlabcontrol.com/news/news_archive.htm >------------------------------------------------------------------------= --------------------- > > > = =20 > Stuart Chalk <sc...@un...> = =20 > Sent by: To: Dominik= Poetz <dom...@ni...> =20 > ani...@li... cc: AnIML M= ailing List =20 > eforge.net <animl-announ= ce...@li...>, AnIML Mailing =20 > List <animl-d= ev...@li...> =20 > Subject: Re= : [Animl-develop] Allowed Values in AnIML =20 > 05.03.2004 10:47 = =20 > = =20 > = =20 > > > > >The same is true in the parameter data for a SampleSet > >Both MP and BP (shouldn't they be MeltingPoint and BoilingPoint) are in >most cases ranges of numbers. > >As a general note I am stating to work on implementing animl in my lab a= nd >I have many other questions. Would it be possible to set up CVS for ani= ml >development? Then people can report bugs and have those bugs worked on.. >When I say bugs I mean XSD issues that are either too limiting or are no= t >well enough defined. Just a thought. FYI: I can help with both.... ;) > >Stuart Chalk, Ph.D. **NEW** Phone:904-620-19= 38 >Associate Professor of Chemistry Fax:904-620-38= 85 >Department of Chemistry and Physics "The Flow Analysis Databas= e" >University of North Florida http://www.fia.unf.ed= u/ >4567 St. Johns Bluff Road S. "The Analytical Sciences Digital Librar= y" >Jacksonville FL 32224 USA http://www.asdlib.or= g/ > >On Thu, 4 Mar 2004, Dominik Poetz wrote: > > =20 > >>Hi everybody, >> >> >>I hope everyone is doing well. >> >>At the last AnIML Working Group meeting, we discussed wanting to allow >>multiple, single "allowed values" for parameter values in the technique >> =20 >> >layer. > =20 > >>Instead of multiple, single "AllowedValue" values, we might do better t= o >> =20 >> >allow > =20 > >>ranges of "AllowedValue" values. For example, with temperature it woul= d >> =20 >> >be > =20 > >>better to allow this "AllowedValue" to range between a minimum value an= d >> =20 >> >a > =20 > >>maximum value. To specify a single value we would have to put the valu= e >> =20 >> >in > =20 > >>both, Min and Max fields or maybe the Max field would be empty. But thi= s >> =20 >> >is a > =20 > >>design detail that is not so important at this point. >>The usage of that could be for vendors to specify their devises in thei= r >> =20 >> >vendor > =20 > >>extensions if they want. >> >>On another subtopic, shouldn't we add a flag (attribute) to >> =20 >> >"AllowedValue" to > =20 > >>reverse it's sense and let us list non-allowed values? >>This wouldn't cost us much, and it gives us more flexibility in designi= ng >>techniques. To promote better understanding, we might choose to rename >> =20 >> >the > =20 > >>"AllowedValue" to maybe "RestrictedRange" or "QualifiedRange." >> >>In addition, do we need a similar notation for vectors? >> >>It would be nice to get some more ideas about this. >> >>Hope to hear from you, >> >>Dominik >> >>------------------------------------------------ >>Dominik Poetz >>U.S. Department of Commerce >>National Institute of Standards and Technology 100 Bureau Drive >>227/A157, MS 8394 >>Gaithersburg, MD 20899 >>Phone: 301-975-4645 >>Fax: 301-977-0587 >>Email: dom...@ni... >>------------------------------------------------ >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: IBM Linux Tutorials >>Free Linux tutorial presented by Daniel Robbins, President and CEO of >>GenToo technologies. Learn everything from fundamentals to system >>administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dc= lick >>_______________________________________________ >>Animl-develop mailing list >>Ani...@li... >>https://lists.sourceforge.net/lists/listinfo/animl-develop >> >> =20 >> > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcl= ick >_______________________________________________ >Animl-develop mailing list >Ani...@li... >https://lists.sourceforge.net/lists/listinfo/animl-develop > > > > > > > =20 > |
