I finally (after how many months?) got around to going down to GYGO and picking up a replacement A/V cable for my Dreamcast. (Unrelatedly, there actually seem to be people playing board games down there during the summer - and now I actually have free time! Maybe I should go see about that.) The very next day Doug decided to do a cleanup of all the cables lying around the TV, and, guess what, we found the old A/V cable for it, sitting on top of the television. So, uh, now we have two Dreamcast A/V cables. In case, y'know, someone else brings a Dreamcast, but doesn't have an A/V cable, and we want to use both at once. Y'know. Just in case.
So I don't think I mentioned that we now have a copy of Metal Slug Anthology for the Wii, which means, yes, Metal Slug 3. But unlike the Xbox Metal Slug 3, this is emulating the arcade versions of the games... and the options are rather restricted. The only options for how many continues you get are "limited" and "unlimited". Let's say I play Metal Slug 3, on easy, with "limited" continues. It gives me
30 of the things. Maybe that goes down if I set the difficulty higher, but, well, I don't want to do that. Now for what it's worth, unlike when playing the Xbox version, these continues are only 3 lives, not 5. But also unlike it, you don't have to restart the level when you use one. Which is much more important than the number of them - of course I could beat the game, given just 25 lives! If I still really knew the game, of course - I don't remember it so well. With 60, though, it should just be trivial. There's like, no tension. It just isn't fun. I did see a copy of the Xbox Metal Slug 3 at GYGO - maybe I should go see how much it costs...
In the "news I feel compelled to report even though I have a hard time caring about it" department, Sega is delaying Sonic 4. Considering how for many years Sega's business plan seems to have been "Make shitty games that are rushed to market", this is good news. But I still have a hard time caring about it. They've also announced a strange-looking game called "Sonic Colors", which... eh, go look it up. It's undeniably strange.
OK! Now we get to the original main point of this post. Let's talk about integer complexity. After a semester of having no time, followed by several weeks of procrastinating, I finally sat down and completed the
classification of numbers n with d(n)≤20d(2). I'm going to do one more iteration of this, to get to 21d(2), because that gets me to 2+2d(2) and hence allows me to classify all numbers n with D(n)≤1. Will it be anywhere near as nice as my classification of n such that D(n)=0? Probably not. Will it be terribly tedious to do? Yes. But it's so close... earlier I was considering going to 22d(2), because along the way we should find the lowest-defect instance (other than the trivial example of 3) of a number n with n=3k, f(n)≠f(k)+3, but that would just be too tedious. We can demonstrate that without computing out the whole thing, if we can just get to 21d(2) - in fact, we probably have enough to demonstrate that already! And no more than a bit of trivia anyway. (For the record, the number in question is 2049.)
So what am I going to do then? Well, for one thing, I could start thinking more seriously about how to automate this process, so we can truly push it as far as it can go. Everytime I've thought about this before it's looked like one giant programming clusterfuck with no obvious solution. If I intend to do this, I'm not going to be able to do it alone; when I get to that point, expect me to post here a call for help with problem details, exactly what process I'm trying to automate, why it seems hard, etc.
But I should probably also at that point start writing things up. Josh wants to move into the writing-things-up-phase; he's apparently written up a draft of his 2.639log_2(n) upper bound (that's how far he's gotten it). Though I suppose there's not much to write up - writing up the theorems involved will just require going back over Josh's and my old interpersonal communications and extracting the relevant parts, fixing the errors, and adding our more recent developments, describing the procedure I used for hand computation, and then appending the big table. Maybe make a note on the older "enormous tree" method that
you'll recall I wrote up earlier, but which we don't intend to put in our final version due to our newer methods mostly obsoleting it. Hm, I guess I'd need to write up a base case or two as well, to get it method started - we used the results of the "enormous tree" method as base cases here, but if we're not going to use that we'll have to prove the first few inductively.
But we're not out of ideas yet! As I said, I do want to at least try looking into automating this process, and meanwhile Josh has a new idea for bringing his upper bound all the way down to (5/2)log_2(n). We'll have to see whether it works out.
OK! Now for the strange part! The other day Josh IMs me with the question, "Do you know who this is and what language it is in?", linking to
this site. It discusses integer complexity, and mentions me by name, linking to what stuff I had put up on the web, and to my LJ - strangely, it does not mention Josh by name, despite mentioning old upper bound results of his. (Hm, I really should get around to tagging the integer complexity entries - if I've actually got guys looking through here to find out about it, they must be pretty annoyed!)
Josh notices that the domain name ends in ".lv" and hence it's presumably Latvian. OK, that's one mystery solved. Now - who are these people? I comment how fragmented this seems - we're working on this in English, there's the stuff Arias has written on it in Spanish, and now these guys in Latvian... (which reminds me, I never did sit down and try to read much of Arias's paper. Later I should also go back and take a better look through the literature, now that I have a better idea as to how I might find some of it.)
Eventually, Josh makes the suggestion - could this be some Latvian PROMYS-like program? And I have to say this seems pretty likely. A lot of their ideas seemed decidedly, uh, implausible. They did have one result we hadn't seen elsewhere, though, that we hadn't seen elsewhere: A neat upper bound on f(2^n-1), showing that the amount by which it exceeds 2n, is at most logarithmic in n. Though, they hadn't extracted the maximum strength possible from their proof. Neither had they thought to generalize it to f(a^n-1) (the proof does generalize, though the bound gets a little weaker). I won't state what it is here in case they are by some chance reading this, as it's pretty straightforward and they should work it out for themselves. :) (If we want to write about this, I do have to wonder what the proper way to credit them would be...)
Also, in case they are reading this:
Hello! My collaborator's name is Joshua Zelinsky; he is responsible for those general upper bounds you cite! He is also responsible for many of the ideas that I am currently using to classify numbers of low defect! Also, your upper bound on f(2^n-1) can be strengthened, and also generalized to f(a^n-1) (in a somewhat weaker form!).
I don't find it very likely that they'd actually still be reading this, but, may as well. For good measure, I should probably translate it into Latvian, too! Of course, I don't know Latvian, and I'm not sure I know anyone who actually does, so as a poor substitute I will run the above paragraph through Google Translate. Not that they were incapable of doing that themselves, but... ah, hell, I admit it, I don't have any real justification for this other than my own amusement. So, here is the above paragraph, in Google's version of Latvian:
Hello! Mans līdzstrādnieks vārds ir Joshua Zelinsky, viņš ir atbildīgs par šo vispārējo maksimālo robežas jums citēt! Viņš ir atbildīgs arī par daudzām idejām, kas es esmu pašlaik izmanto, lai klasificētu skaitu ar zemu defektu! Arī jūsu augšējā robeža attiecībā uz f (2 ^ n-1) var stiprināt, kā arī vispārējas līdz f (a ^ n-1), (jo nedaudz vājākā formā!).
Hm. Running it back through Latvian -> English, it calls Josh my "assistant" rather than "collaborator". Yikes. Oh well...
-Harry