NavBar

Showing posts with label organization. Show all posts
Showing posts with label organization. Show all posts

Thursday, June 16, 2011

Suicidal Computers

In case it hasn't been clear before now, let me make one thing very clear: I love computers. Tooling around with them is incredibly fun, challenging, and rewarding. That word challenging, though, is a fickle one. Today (and last night-ish), for example, I was presented with two challenges: my main webserver died, then my laptop decided it had had enough of my shenanigans. Despite the stress presented by both events, though, it's been a particularly interesting (and challenging) learning experience.

My laptop's mini-suicide is the least involved, so I'll start there. I was doing some animation cleanup and sprite-sheet compositing in Photoshop, and it was certainly pushing my system hard. Moving the layer groups around was taking upwards of 10 seconds per update, but I figured that it would be ok once I finished my task, saved, and shut down the program. I got a little weirded out when my cursor changed from an arrow to a bizarre vertical dotted line for no apparent reason, but it functioned normally otherwise, so I continued to work. Then this happened:



I honestly have no idea as to the actual cause of that. My only guess is that I was pushing the system too hard, it overheated, and gave up the ghost. I'm thankful that after I let it cool down a while, it started back up just fine.

The real kicker was my server dying. It was originally a desktop box, but its CPU heatsink isn't entirely stable, so I relegated it to less stressful jobs. I had a bios password enabled on it, and forgot to take it off when I installed the server OS. For a desktop, the boot-up password wouldn't be a problem, but on a server it means that I can't do any sort of remote reboot. Easy enough to fix, I thought. Boot up to the bios screen, remove the password, reboot to the OS, and everything will be dandy. And it was, until it didn't boot the OS.

I admit that I panicked a bit at first. I tried reinstalling the OS to reuse the existing partitions, and that didn't work. That freaked me out a bit more, so I mounted a usb key and pulled off all the critical data (website, subversion repositories), and tried a full format and reboot. That didn't work, so I transferred the salvaged data to my secondary server and went home to sleep.

I spent the next morning configuring the secondary server's Apache to replace the old server. Honestly, I was surprised at how quickly it went. It took me several hours over many days to figure out how to get it all set up the first few times. Even though it was much easier and much less painless than I expected, it really drilled into me that I need to get a good backup system in place. Looks like I'll be doing an rysnc/cron crash-course soon.

After work, I discovered the most anti-climactic solution to my server's startup issues. I flashed the bios. I don't know what it changed, but it must have fixed something, because it boots just fine now. Since I re-formatted and re-installed the OS, it'll at least give me a fresh start on building it up more efficiently. Also, my dad gave me a bunch of old drives to use. I'm going to shove a few each into the servers to see if I can't stave off any more massive failures.

Also, as an added bonus, here's a crappy ipod photo my current workspace:


A. is my Lenovo T60p laptop, "Cacofonix". It has a 32-bit Core2Duo 2Ghz CPU,3Gb RAM, an ATI FireGl v5250 graphics card, a 100Gb primary drive, 250Gb secondary drive, and runs on Vista Business.

B. is my main work machine, "Fulliautomatix", custom built. It has a 64-bit Core2Quad 2.66Ghz CPU, 8Gb RAM, a GeForce 275GTX, a 150Gb primary drive, a 375Gb secondary drive, a 1.5Tb storage drive, a 300Gb scratch drive, and runs on Windows 7 Pro.

C. is the webserver, "Shoggy" (formerly a desktop named "Tragicomix"), that crapped out on me. It has a 32-bit Core2Duo 2.66Ghz CPU, 2.5Gb RAM, a 250Gb drive, and runs Ubuntu Server 11.

D. is a mystery-box :3 It's not mine, I don't get to keep it, but it was really cool to play around with expensive enterprise-class hardware.

Not shown is my other server, "Merrt" (formerly a desktop named "Asterix"), which is one of my dad's old desktops. It has a 64-bit 2Ghz dual core AMD CPU, 2Gb RAM, a 150Gb drive, and also runs Ubuntu Server 11.

A side bit of fun for me: computer naming. My family has always been a fan of the Asterix and TinTin comic books, so our computers have always been named after things, usually characters, relating to them. I remember at one time, my dad had a trio of servers at his job which he'd named Uderzo, Goscinny, and Herge, after the authors and artists of those two comic series. At home we've had computers named Asterix, Getafix, Geriatrix, Fulliautomatix, Lutetia, Cacofonix, Dogmatix, Tragicomix, Unhygenix, and Panacea.

While I've always loved my family's naming scheme, I've wanted to start differentiating my systems as I starting to create my own networks and administrating my own servers. Thus, I've been naming all my new machines after characters from the Warhammer 40K Gaunt's Ghosts series. With so many good characters to choose from, I have attempted to pair my servers with characters who share similar traits.

The character Shoggy was a trooper who lost his eyes and had them replaced with mechanical ones. He's good at a few things, but can't perform up to the same standard as the rest of the soldiers. Similarly, the server Shoggy has an unreliable heatsink, so I don't trust it to do any heavy lifting, like rendering stuff in 3d.

The character Merrt was an excellent sniper who took a jaw-shot, and had it replace with a mechanical one. He still fights well, but he's no crack shot anymore, and he has confidence issues. Merrt the server was hot stuff when my dad first got him. It was our first 64-bit system, and had an internal RAID system. But as time wore on, he became less shiny, the RAID system started corrupting stuff, and he was finally replaced with new hardware.

I love taking old hardware and making it useful again.

Anyways, enough about computers for now. I hope to have some more fun art to post when I have more free time. :D In the meantime, check out Mighty Rabbit's Website and Facebook page to keep up with what we've been doing.

Monday, June 6, 2011

New Domain

You might notice, if you look at your address bar, that this blog has changed locations. I got a pretty sweet deal on my domain name by signing up through Google Apps. For $10, they registered my domain name and set it up with sub-domains pointing to the free apps they provide (email, calendar, docs, and sites). I had to set up the main site and blog manually, but that wasn't terribly difficult because the third party registrar Google used (www.enom.com) has a handy web interface that makes DNS configuration pretty simple.

I've also been having a lot of fun getting my Ubuntu server back up and running. After several months of being offline, I tried to resurrect it, only to have a failed update make the system unbootable. I was thankful to discover that you can install a fresh version of Ubuntu server over an old one using the "reuse partition" option, and you will retain most of your files. My MySQL databases were completely wiped, but I didn't have anything worthwhile in them anyways.

Since it had been a while since I'd gotten my hands dirty with server maintenance, there was a lot of fumbling around in the command line before I hit my groove again. Once I did, though, I got my Subversion safety nets set up for the various projects I'm involved with, and learned how to make them all easily and (sort of) securely accessible with Apache.

That said, there's still a number of bugs to iron out. My Wordpress testing site has mysteriously lost functionality. I can navigate to the pages, but they load up blank, and viewing source in my browser seems to tell me that there is no code being loaded. I may just scrap it all and just reinstall WP completely from the ground up. Also, with all the hack-y setup I was doing before I hit my groove, I really need to go back and fix permissions and consolidate password/access settings for Subversion.

Tuesday, April 6, 2010

I'm a tool (writer)

Things are getting pretty busy. The film is due for marks on Friday, and I'm busy trying to get something patched together for marks. To help try to meet that, I took some time today to write a little pair of tools to get me working faster.

The UDK has a nifty command switch called "dumpmovie" which forces it to save every rendered frame to the screenshots folder. In combination with the "fps XX" switch (where XX is the number of frames per second), it essentialy performs like a batch render in Maya, except there's not automatic off. Instead, it plays in a game window, and stops recording when you exit the game. Of course, the options with this are very limited. You can't (as far as I'm aware) set the path for the screenshots, and it only saves in BMP format, but it works, and that's what's important. Since BMPs are uncompressed, they take up a lot of space. A 120-frame render weighs in just over 300Mb. With WinRAR, I can collect and compress those 120 frames into a single 20Mb RAR file. That's about a 93% storage savings.

With those facts in mind, here was my workflow for rendering out a scene:
  1. Save final map and assets in UDK, then close editor.
  2. Open command prompt and type in really long UDK shell command to start a Dumpmovie render. (example: C:\UDK\UDK-2010-03\Binaries\Win32\UDK MapName -dumpmovie -benchmark -fps 24 -resx=1280 -resy=720)
  3. Render out scene.
  4. Open Explorer to the UDK screenshots folder.
  5. Select all new rendered frames.
  6. Right click, "Add to archive."
  7. Set up WinRAR options.
  8. Delete leftover frames.
Not optimal at all.

So instead, I wrote two simple batch files. One does the rendering side, the other runs the archiving. The rendering one also has the option of calling the archiver as soon as the render finishes. This is my new workflow.
  1. Run UDK_Render.bat.
  2. Give map name, choose resolution (full or half 720p).
  3. Run render.
  4. Choose to archive (or not).
  5. Give archive name.
  6. Done.
This leaves me with a screenshots folder that has nicely organized archives for each shot, plus it deletes the source files after creating the archive, so the screenshot folder is clean and primed for the next render. This also makes it very easy extract each archive into its own folder to prep for rendering out an uncompressed AVI from AfterEffects so I can then throw it into Premiere for editing.

As a side note for comparing UDK render time against Maya: If we assume Mental Ray is rendering at 5 frames/minute and UDK at 15 frames/sec, the ratio is 4500:1!!
Render time essentially becomes a non-issue. I could render my entire film (if it were contained in a single map), check for errors, tweak the map, and re-render in about the time it would take MR to render 3-5 frames. This by itself is one of my major arguments for using real-time rendering engines (like game engines) for rapid film production work.

Wednesday, March 10, 2010

Organizational

I've been getting more organized this week. I found this article about how to be a productive artist. After some more research, I found two great articles: The Top 10 Sources of Interruptions and Getting Ready for 2010: My Moleskine Setup.

After reading these articles, I went out and bought two new notebooks: a small, red, lined Moleskine and a slightly larger blue Pentalic. I've set up the red one as a sort of Goalbook, organized like the third article mentioned above. I've got a list of my current projects, long term goals, short term goals, "someday maybe" goals, daily/weekly checklists, current tasks and related notes, and a section for information and reference. The blue one is a sort of thought-capture/brain-dump book that I'll be using for random thoughts and notes that distract me as I work.

Despite only having the books for a short time, I'm already finding my motivation levels higher. I have a difficult time working towards my goals unless I have them in a concrete form that I can check back on as needed, or tick off when done. Having them in a little book that I can keep with me and add to whenever new tasks pop up keeps me focused and gives me something to aim for. The blue book should be enormous help, too, since my worst distractions while working are the random thoughts that pop into my head and refuse to leave until I give them the attention they want, usually in the form of Wikipedia research. Having a place to write them down for later perusal should keep me much more focused, because I'll know that I won't forget to look up whatever it was that seemed so important at the moment.

The other fun part of getting the notebooks is personalizing them. Now that I'm accumulating more hard-bound notebooks, I feel like I need to label them and make covers for new ones as I get them. Thus, I took my Moleskines and the Pentalic, labelled the spines, and have created a cover for my Goalbook.



The art is by an artist who goes by Nivbed (one of the first artists I followed online, and I still absolutely love his work), and the piece is called Vigsen. I applied the image by printing out a copy on normal printer paper, brushing a couple layers of clear acrylic medium to form a tough skin, then wetting and rubbing off the paper. The result is a thin piece of flexible plastic with an imprint of the image on the backside. (When done with a greyscale print on white paper, the white becomes transparent, a la Flaming Pear's "Ghost" filter, allowing the ground's color to show through.) I added some acrylic gouache to the backside to highlight the outline and the eyes, then used more acrylic medium to bond the transfer piece to the cover of the book.

You can see from the inside shot that I've got the whole thing divided up using sticky tabs, and that I've got dedicated pages for certain types of data (in this image, Tasks on the left, related Notes on the right), plus indicators where tasks and data are related. I've also numbered most of the pages, leaving some blanks because I was lazy and I won't get to them in a while. I'm really excited about the whole notebook thing (notebooks, sketchbooks, nice paper, and quality writing materials are all guilty pleasures), and I'm hoping that this will help keep me on track. I may post some updates in the future to see how much use I've really gotten out of them.

Now to go get some of those items checked off...