tir, 02 06 2009 kl. 14:12 -0500, skrev dmelliott: > The idea of this routine is that it integrates existing data in its most > ususal form. That is, it does not need a function to call, and, since, for > better or for worse, most data comes on a domain of equally sized steps, > this is what it uses. This is an attempt to make it compatable whith most > experimantal data, and the outputs of other routines, e.g. sales by week, > Fourie analysed amplitudes by frequency, actuarial data by age, etc. The > patrial interval integrals, including cumulative, can be achieved by looping > or otherwise manipulating the endpoint values.
Sounds sensible. Most of the data I work with are equidistantly spaced, so I can related :-) > The best way to see its worth is to compare it to the available routine > for existing data, by editing the "integrator_verifier" to use the "trapz" > routine. The latter is only of first order, and even for as many as 500 > points on [0,1] yields a 2.01e-6 relative error for the next higher order, > the second. For higher orders higher than second it is even more useless. > There probably should a caution appended to the instructions about this. OK. It would probably be wise to write a bit about this in the documentation of the function. Could you do this? > The problem with a copyright in the U.S. (it is different in many other > places) is that if you do not want to spend the money to register and fight > a challange, you may end up with a legal record of having lost a copyright > infringement suit. The government here does not proctively protect > copyright claims, even if registered. My knowledge about (and interest in) copyright law is very limited. I think it is perfectly fine if you don't want to claim copyright of some of your work. What is wrong with putting your work in the public domain, then? Then you're bypassing copyright law (as far as I understand). > With respect to the name, perhaps integratores for "integrator, even > steps", or some such thing, would be more suitable. I note that the names > in the integration package go by internal workings insted of giving a clue > as to what they are for. That is probably because several of the functions are trying to solve the exact same problem, so it is hard to come up with discriminative names for the different algorithms. Does your approach have a standard name? Can it be explained in terms commonly used in numerical integration? If so, then it might be easier to come up with a name. Also, does it work in N-dimensions? If it is only for 1D data, then it should probably end with '1' to signal this. > What is the name of the "ø" character? I have asked all my second > generation Dansk relatives, but they do not know for some reason. Well the character is named "ø" :-) The English name for the character is "o slash" (i.e. an "o" with a slash through). The sound of the character has no corresponding sound in English. Basically, that sound is not part of the English language. You can hear the different pronunciations of the letter at http://udtale.dansk.nu/ Recently, it was pointed out that we have a bug in Octave in the 'fscanf' function, that could be triggered by the letter "ø" :-) Søren ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
