More math. I have a solution for the midpoint that involves a whole bunch of odd terms and whatnot, so I have to find some slightly more advanced algebra resources to determine how to resolve that to one side clean, one side icky but solvable.

Frustration about the math model is building, and I'm going to log off and spend some time with my old friend pen and paper to work the kinks out and get the proper formulas translated into Perl.

This math model may be wrong, it may be totally wrong, it may be completely counter to what Kosko meant when he wrote the damn thing, but by Chao it is going to *sing* and *dance* when I code it up.

Okay, despite every worst effort on my part I've managed to locate the heart of this thing. It's the curve-calculator that I'm about to write, and was previously an ucky thing that deviated behavior based on the number of incoming points.

Translation: I've started to work on the general method that will actually work, instead of the hacky-specific method that didn't really work at all.

I'm demoralized but I'm going to fix things later today.

The new "average" is going to be the midpoint in terms of area, the bisecting point, instead of what had previously appeared to be correct (which was the point where the curve is "average").

I wish I wasn't such a math doofus sometimes...

Okay.

Apparently I have botched the implementation of this model so badly OR I have misunderstood the model to the point that this thing is, as stands, completely unusable.

My worst nightmare is true -- I've modified things so that right-triangle rules can be handled the same way as isosceles triangle rules, but there's one firing position that produces a curve well above the average.

This can't be right. It's got to be half the volume on each side, otherwise these results can't possibly exist in some cases. Having said that, I'm going to recode it tomorrow that way.

I'm working through the one-rule now, and it's not as easy as I remembered it being when I dismissed it a week ago. Dammit.

I suppose this would be a good rule of thumb, eh? "One of the first three things you don't bother doing at the beginning of the code because it's so trivial will take up the last 30% of your time."

Anyway, it's slow going but some of the handling subs I wrote in the two-rule version are helping me through the one-rule, so I guess that's a good sign.

Okay. Two-rule dealt with. Reasonable results returning.

Now, I deal with the fact that I incompletely dealt with the single-rule case. Sigh.

On the other hand, I feel reasonably close to a model of how to deal with X rules firing, which would be a nice thing to have. Very, very nice thing.

I'm thinking also that if this thing is too slow, I may be able to write a ponder sub to precalculate values and store them in an easy lookup table. (While this violates the malleability of the fuzzy systems, it could still incorporate learning by having cycles -- experience cycles where precomputed values are compared to optimal results (as determined by actual humans, perhaps) and then a learn process where adjustments are applied to the rules through a statistical method, then another ponder cycle to precalculate for speed, then...you get the idea. Rinse, repeat.)

Well, there's good news and bad news.

Good news: Last night I figured out how to solve my problem (thanks again for the help, but my knowledge of calculus is miniscule, so I'd end up researching a lot more of those terms than with this homebrew which is, probably, the same damn formula. I don't eschew knowledge, I just want to finish this thing ASAP) by scribbling all over a piece of paper for several hours. I got to bed around 5.

Other good news: Flare, for one, because I honestly think it could have some interested repercussions. Lots of neat stuff could be done with Flare that would have a natural storage solution with XML data storage, and lots of neat stuff could be done with existing XML data as Flare data structures, IMHO.

I'm not smart enough to do it -- yet -- but I will be, dammit. Flare. I can't say it enough.

So, my next step here is to code the rest of the solution I whanged out last night and then start refactoring, assuming I can make the solution work immediately. My main problem is one that I believe was discussed in the assistance one diary entry provided, that of curves with two intersections with the average point and no more. (The two "end" intersections don't count for my purposes, so I need to figure out how to make sure there's a middle, and my model doesn't cover what to do if there isn't one.) I'm considering a few attempts at proving it's possible, just to make sure that this is something I should be worrying about. (With my incoming data, it probably isn't. The truly worrisome case I could see is where there are MULTIPLE points past two, seven or eight averages in the middle that I need to worry about. Sigh.)

So if this doesn't pan out then I'm going to take the tougher plan and figure out a way to bisect it, which should provide the results I need no matter how many "average" points there are. Goddamn modes.

Okay, now I'm actively angry.

This is a *really simple thing* and I cannot figure/remember how to do it.

I have a set of points which provide me with a really jagged "curve". I need to calculate the point on the X axis that, if a line were drawn through it parallel to the Y axis, it would bisect this "curve" into two curves of equal area.

Now, I can imagine a series of approximation algorithms to calculate this, but I have strong suspicions that optimizing them for speed will be long, hard, and ultimately solve the problem more slowly. I cannot help but get the feeling that some sort of algebraic solution exists that I'm not aware of.

I could see using the known values of parts of the curve (because I do have the curve sectioned into between 5 and 4 sections) and determining first which section the bisect would occur in, then trying a few values and eventually narrowing it down. This is, frankly, not easy to comprehend and even more difficult to imagine coding.

Next, it occurs to me that the sections can be divided into triangles, and each section is composed of possibly three identical triangles (only in the zero case, where the sides of all triangles is zero) or two identical and one non identical (where the non identical one OR the two identical have area, at least one but not necessarily both.) This doesn't simplify anything, as far as I can tell, though.

So I have a set of points, I have the area, and I have the average value of the curve. I have no way to convert any of this into the value I NEED, the bisection point, that I am aware of.

Anybody with advice about this, please, help.

It occurs to me that a Perl module built to provide a simple interface for turning text files into "Note Pad" files on Palm OS would be really handy for me. The further thought continues that, since it might be handy for me, it could be handy for others, and if that's the case, there's a 50% chance someone already built it. (And if someone didn't write the exact thing I'm thinking of, there are 20% odds that something in there is 80% of what I need.)

Whew. All these percentages!

Anyway, that's on the back burner until I get the fuzzy stuff done. I just wanted to note it while I was thinking about it.

**New HTML Parser**: The long-awaited libxml2 based HTML parser
code is live. It needs further work but already handles most
markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!