Hallelujah...

Just finished my Sudoku solver, I estimate I put in 40 hours and over 1500 lines of code. I'll give more specific stats later. Oh, and I still have to deal with the "Guess and Check" cases of those really hard puzzles. Ahh, relief... tomorrow I can concentrate on my research paper.

Ack...

I apologize for my tardiness. I think there are no more tests until finals, and thus I will try to post more. If you read this blog you probably already know. But you should ask me a question about what I'm doing next summer if you don't know. I don't think I'll post it because I'll only tell you if you care.

So I get back to Spokane today and my CS Lab is a little jumbled. There's construction happening next door and they moved stuff around in my room... arg. Well Spokane is white for good now, til spring. It should be a fun winter!

Week from Hell...

Last week pretty much just sucked. I was tired and life was busy, and it wasn't fun at all. This week is much better despite the two tests I have in the next two days and the paper I have to present on Friday. Bring it on Data Structs! You too, Database! (Actually I am kind of fearing the database test, one of its main points is embedded SQL - not my strong point.)

So last night I was doing my Assembler homework which included a problem where I had to write a program that checked if a number between 0 and approximately 4.5 billion was prime. I did that, but it made me curious... is there a better way to do this? Of course there is. My program immediately disregarded even numbers, then tried to divide by each odd number less than the square root of the test number, looking for a remainder of zero. If it did not find one, then we're finished, get out, it's prime. But why divide by all those odd numbers when only a few of them are prime? So I pulled out my C++ skills and wrote a measly 20 lines of code, which aimed to generate a file that held all primes that would fit in a 32-bit register. The program proceded to check a number, and if it were prime, then write it to a file. The program would use the numbers in this file to check the new numbers. (Given 2 is prime, the file started with a 2 in it.) I did not take into consideration the amount of time it takes to write to disk in my equation. So I broke the program (you may know it better as hitting the 'X') and checked my file. It only got up to primes around 65 million. So I started a program that only wrote to the file and never read from it, using the old odd numbered algorithm. I started it at 9:30 this morning, and it is still running. I don't even know how far it is because I forgot to program a cout into the code, and I can't open the file because it's in use. Hopefully it's close to being done. This afternoon, Kent Jones told me that I should write it to a .bin file. Apparently it will read and write a lot faster than the .txt I'm using. Next time I'll take that into consideration.

Well, I guess I'll get back to work now. I actually have work now.

First snow...

Well, today we got our first snow of the year. It's white. And wet. And slushy. I can no longer ride my longboard. Lame. At least it looks cool, until people walk on it.

-AZ

Bliss...

Bliss is having only one minute left on the ghost when it said 300 hours an hour ago.

Things keep getting worse...

So I have everything done except for one lab which is being more stubborn than anything I've ever messed with. As we speak the broadcast has 256 hours remaining. Which I guess is better than the 309 hours it started with. And this is probably the eighth time today that I've started a broadcast in that lab. If it doesn't jump down to under an hour soon, I'm going to give up. I'm convinced that there is either something horrendously wrong with the server or with the image, but only time will tell, and hopefully not 256 hours.

Ghosting is of the devil...

Well, continuing the work... I ended up single casting all of the computers in the library study lab (26) which took all day, but then they all worked fine, so that's cool. I'm currently ghosting the CS research lab, but things don't look so hot over there. I finished one, and it got stuck at the boot loader, so I'm praying at least one of the six will work. I guess my last post was right... all the trouble on Friday was just the beginning. Well, at least my boss will be back tomorrow so he can show me how to fix some of the errors I've run into this weekend.

A sign of things to come...

Well, I started my fall break shifts this morning, still 7 1/2 hours to go today. It started off trying to ghost the research lab, but the ghost boot disk failed and my boss is in a meeting so I can't get a new one yet. I really hope the rest of the weekend doesn't consist of a bunch of failed tasks.