Ben Goren wrote:
I'd very much appreciate something like this, too -- and for spotread as well.
Hi, I'm not sure what you mean WRT to spotread. Doesn't the -V option give you this sort of functionality ? <http://www.argyllcms.com/doc/spotread.html#V>
Perhaps, rather than create multiple files and have to deal with that, chartread and spotread could do the averaging in-memory before writing the final averaged values to disk? Unless one is interested in determining the behavior of the instrument, I don't see the advantage of hanging on to the intermediate values.
Writing multiple results to disk when being read interleaved would be complicated and messy. messy == unreliable code. Even doing averaging in memory means adding a degree of elaboration, since currently chartread saves readings directly to the CGATS object. Setting an outlier threshold value is not very desirable from a UI point of view, since it is yet another parameter that people will wonder how to set. I think it is possible to make a reasonable attempt to recognize outliers automatically using robust mean type function, if a sufficient number of readings is done - ie. you can't detect an outlier with less than 3 readings. Graeme Gill.