|
From: <pl...@pi...> - 2013-09-05 10:49:01
|
On 09/04/13 21:33, sfeam <Ethan A Merritt> wrote: > The thing is, I don't think your proposal would actually work in practice > for the "fit" part of this. If every cycle of L-M fitting requres re-reading > the original files through an intermediate layer of data presentation, > my guess is that the throughput would become so awful as to be > unusable. > > I suppose it's fair to answer that we won'e know the throughput limitations > until an implementation exists. I also suppose that I should spend more > time exploring whether this task can be done in R or Octave. Anyhow, > thanks very much for the feedback. I'll continue to ponder alternatives. > > Ethan I started using R but it has a nasty habit of modifying the data to what someone "thinks" you need without even flagging it. eg changing the end date of a timeseries beyond the end of data in the file extended the data up to the nearest 128 points block length. I never bother to work out where it copied the extra points from since I really don't care where FALSE data comes from. I don't want it. The worst part of this is that it is not even flagged. I have had similar warnings from others. AFAIAC, if I can't trust software not to do this kind of stupidity and have to start auditing everything I do to make sure it has not happened , it's not even worth starting. Caveat emptor! === The idea of "fitting" one data file to another is something I've needed too. Since this sort of task implies some strict checking of continuity and compatibility of xdata intervals , it could be a bit of minefield to get into, though it would be nice to have. Peter. |