Machinima Project: Alexis in Wonderland

Please enjoy the amazingly random machinima that Alexis, Greg, and I worked hard on.

Filming was a bit tricky because for some reason Second Life was running a bit choppy on my (the robot’s) computer. We scrambled around the past 12 hours trying to get all of the voiceovers together.

Alexis in Wonderland!

Alexis played by Alexis Anthony

E^2 (a.k.a. M.C.) played by Emil Evans

Wiz Kha-Leaf-ah/ Poh the Panda Bear played by Greg Baroni

Editor: Alexis

Writer: Greg

Director: Emil

 

Course Evaluations

I know you are all super sad that the semester is ending….but cheer up. You now get to complete your official University of Maryland course evaluations.

We’ve been asked to communicate the following things:

the CourseEvalUM website (https://CourseEvalUM.umd.edu) is open from today through Wednesday, December 12.

all evaluations are confidential.

you can find the summarized results at the same location once those are released.

the system does not identify to any of the instructors whether or not you submitted an evaluation.

We ask the following things of you:

1) You complete the evaluation so that we can improve the class the next time it is offered.

2) That your feedback be constructive. If you don’t like things, be specific about what you don’t like, why you don’t like it, and how it could be improved for next time. If you like things, be specific about what things you like, why you like it, and whether it could be improved.

3) That you try to offer feedback on the class as a whole as well as individual lessons where possible.

 

If you have any questions, let me or one of the other instructors know. Otherwise, we are looking forward to reading your rough drafts…due this thursday!

Planning the Project Timeline

It’s been a week since you started working on your project proposals. You should have a good idea of what you want to do and what it might take to do it. I want to take some time and share with you how I approach time management when planning programming projects here in MITH.

The two principles I work from when managing time are: we don’t want to get into a death march project, and we want the highest priority requirements to be met at the end of the project.

The first principle, that we don’t get into a death march, means that we only work forty hours a week or so and don’t work overtime. Studies have shown that working overtime too much leads to less work getting done than if you only worked a forty hour week for the same number of weeks. No use risking burnout if it means you’ll be turning out poor work.

If we want to limit ourselves to the time we have available for a project, then we have to know how much time we have, how much time we think we need for each thing we need to do, and the relative importance of each item so we know what we can leave undone if we run out of time.

For your project, you have fourteen hours, more or less, so you want to figure out how to fit your todo list into those fourteen hours and make sure you get the things done that will have the highest impact on your grade.

When we start a project at MITH that might take months to complete, we break it into a sequence of milestones that can take a week or more each. We have a rough idea of what needs to be done, but we recognize that we learn a lot along the way and don’t want to be too specific in the beginning about what we’ll be doing in six months if we’re going to have to redo the planning anyway because of stuff we learned during the earlier milestones.

You only have one milestone: your project and fourteen hours of work.

At the beginning of each milestone, we get together and walk through what we need to do to accomplish the milestone. This is our todo list that we will prioritize and check off as we do each item.

Beside each item, we write a single letter denoting how difficult we think the item will be: Quick, Easy, Moderate, or Hard. We assign each one a time: quick is 30 minutes, easy is an hour, moderate is two hours, and hard is four hours. If we think it’ll take more than four hours, then we know we need to break it down into simpler steps.

The reason for not allowing ourselves to take on anything that will take more than four hours to accomplish is so that we don’t have to stop in the middle of a task and go home, then come back in the morning and take time figuring out where we were. If we have a two hour block of time, we can pick something from the list that is moderate or easier.

Of course, you’re not working on this as part of an eight hour workday. Knowing how long you expect a task take will help you fill in those odd hours here and without having to stop in the middle of something and hope you can come back to it later.

Once you have your todo list and how much time it will take to do each item, you can prioritize the items. Which items are fundamental to your project? Which ones add flavor? Which are at the core and which are expanding on the central theme?

After prioritizing, you can run down the list adding up the time for each item. When you hit fourteen hours of work, you know what you can expect to have done by the end of the semester.

After you finish your project in December, you can look back and see how well you guessed your time requirements. Computer work is notoriously difficult to estimate, so don’t be surprised if you’re off. The rule of thumb is to double the estimate from an expert in the field.

Link to our Machinima

Whew, Second Life is very difficult to manipulate, especially when the computer is running slow. I tried to edit out lags and user interface (chat/command menus) as best as I could. (I also made the video private but you should be able to access it with the link. Let me know if you can’t.)

I present… Expectations/Reality!

http://www.youtube.com/watch?v=KR4G9NoNulI&feature=youtu.be

Script by: Ed

Direction by: Tess

Editing by: Kelsey

Project Proposal Guidelines

Below is the Final Project Proposal Guidelines and Worksheet that was passed out in class yesterday. Let one of the instructors know if you have questions.

Your final project for this course is an opportunity for you to demonstrate your understanding of narrative elements, digital technologies, its potential benefits and constraints, and your ability to construct a narrative.

As part of your final project, we are asking for a two page project proposal that outlines exactly what you plan to do for your final project. Your final project will be evaluated based on four criteria: understanding and use of narrative elements, appropriateness of platform for your narration, use of the technology, and quality of the overall project. The total point value available for the final project is 70 points. This proposal is worth an additional 20 points. It is due:

either by email (to guiliano@umd.edu) or by paper copy to Jen’s MITH desk by 4:00pm EST on November 29th.

To aid you in writing your proposal, here are potential questions that we expect you to answer in your written proposal:

Statement of Significance: explain–in terms comprehensible to a general audience- the significance of your proposed project. What will your project contribute to your understanding of persuasive storytelling? What type of audience might be interested in your project? How would you reach out to your potential audience?

Statement of Objectives: what specific objectives or deliverables will this project offer (e.g. an X page long story, X pages of html code, X visualizations, X graphics, etc. where X is the amount/length of material)? You must itemize your objectives. We are looking for an outline that accounts for the components of your project and gives a clear statement on what final product will be. It is not sufficient, for example, to say that you will write an e-lit story that is 10 html pages long. You should outline the elements of the story—character, motivations, climax, etc–and how your links will be integrated in that story.

Workplan: once you’ve outlined what you are going to do and what you want to deliver, we would like a timeline of how you are going to complete your project by NOON on December 14th. You might break down a to-do list into days or by how many hours it will take you. At minimum, you must set a week by week plan of what you will accomplish. Make sure to describe the specific tasks that will be accomplished, identify the computer technology to be employed and where specific areas where you might need help in accomplishing a to-do item (e.g. I need help building x tech feature). We will provide feedback on this workplan.

REMEMBER THAT THIS PROJECT SHOULD REPRESENT TWO WEEKS OF CLASS TIME PLUS THE TIME YOU WOULD HAVE SPENT PREPARING FOR A FINAL EXAM (PER PERSON INVOLVED IN THE PROJECT). In our estimation based on the mid-semester evaluations you completed, we are expecting your project to represent at least 14 hours of effort (2 weeks x 3 hours of class preparation per week + 5 hours of class time + 3 hours for your final exam).

Final Product Plans: How do you intend to disseminate your final project? Is this a website that you are hosting? Do you plan to turn in files? How will you point your classmates to your final project?

For projects where you have a classmate/partner working with you, you should also include a section outlining who is responsible for what and showing that this work adds up to twice the amount of a single-person project’s hours.

We will provide you with comments on the proposal. You will then be expected to do a short presentation for class on December 6th. That presentation is worth 10 points.

Your final project:

Instead of a final exam, your final project is due in by December 14, 2012 at noon EST.
Please do both of the following:

1. Email guiliano@umd.edu either the files constituting your project (if applicable) or a link to your final project (if published online).

2. Publish a blog post on this course site that links your classmates to your final project (if it’s online) or contains screenshots, an explanation, and/or downloadable files for your project (if it isn’t online).

Long Live

She had a favorite room in the public stem closest to her apartment. It was narrow, but the walls were covered with cloth and the dash was all lit in red, and the kick they gave you there always went down gentle as a lamb. It had a soothing, homey feel, the kind she might arrange if she had a room of her own.

All a girl needed in life, or so they said: a room of one’s own.

But Rexa didn’t have that sort of credit, and the room in the close-by stem was for pleasure, not business. For business she kept on the move, and on that last day she chose a stem downtown, riverside, that had larger rooms but more stark and gray décor. As Rexa set up her deck, she reflected that she liked the extra space, but the place had no romance; it lacked imagination.

A lack of imagination, in Rexa’s opinion, was the world’s greatest malaise.

Once she was plugged in, deck to dash and sensors to skin –and she needed to go full-body for this job—she sat waiting to be greenlit and checked over her programs one last time. Silver, green, and red, the reasons she called this job “Christmas” in her head, all fit neatly into the top of her deck (never the dash ports; her deck had its own mask for public plug-ins). She had to touch them each before she was satisfied, and brushed her fingertips lightly over a blue cartridge resting half in her deck’s side port. At last the light came on the dash blinking once—she sat back in her chair. Twice—she closed her eyes and breathed deep. Three times—there was a faint buzzing sound, and the grid rose up around her.

***

For this job, she needed live bait. Her mark met her at the edge of an actualization of the stacks, here arranged as rooftops, towers separated by long and shadowy drops. He wore a knight done up head-to-toe in black lacquered armor; she wore an impossibly large tabby cat, not an anthro but the actual animal scaled up, with the mouth animation outfitted for speech movements. It looked exactly as disconcerting as she had hoped.

“Hello sir,” she said, mouth stretching in the too-wide smile the animation mod allowed. “Are you ready to begin your journey?” The cat came with a naturally arch, crisp voice that begged for a little theater.

“Don’t speak unless you have to,” the knight said quickly. “Lead the way.” The deep, gravelly voice he put on evened out any tremor in his tone, but Rexa had already hacked his vitals. His heart rate was through the roof, and she smiled even wider at him just to watch the feedback from his eyes twitching.

“As you wish,” she said, and took off.

The silver cartridge laid out their path, shifting the stacks beneath their feet. They tunneled under all the appropriate channels without a hitch, allowing her to keep one idle eye on her mark’s feed. The knight was in reality seventeen, and considerably less muscular than the skin he wore on the grid. He reminded Rexa fondly of her first job, back when she was in school: the destruction of Eurolink’s biggest game server. They never fully got it running again, which was a point of pride for her, but she had since realized the job had been a waste of her time. Taking toys from children no longer interested her.

The kid she led through the stacks, however, wasn’t looking to play games. She didn’t know why he wanted access to local police records—to erase some youthful misdeed, if she had to guess—but she had no intention of leading him there. He stuck close, clueless, sensing only that everything in this corner of the grid smelled official.

“Are we there yet?” he whispered, the knight’s voice brought down to a rasp.

“Just about!” Rexa said, and in some suburban stem just north of the city, a gaunt young man flinched at her volume.

The silver came to a close and the green came online, walking them in place while the shunt loaded. They stood before—or, to the knight, seemed to approach—one of the world’s most brutal security systems, but the knight had no way of knowing that. Rexa could tell that he scarcely dared to breathe as it was, intimidated by the mere sight of the set of soaring crystalline green towers with pulsing blue forcefields between them, stretching as far as the eye could see.

The green interrupted Rexa’s amusement to inform her that the shunt had successfully loaded. She turned abruptly and gave the knight the most ghastly, glorious grin the cat could muster, calling as the shunt took them:

“Many thanks for the escort, dear sir.”

And they say chivalry is dead, Rexa thought. The knight began to scream as the grid seemed to drop into the darkness around them.

***

The shunt dropped them well inside the barrier, and expelled the knight from her mask immediately. The vector she used for him had been unusual, a fragment of a horrorsim that involved waking up during open heart surgery (she’d be lying if she said that wasn’t a bit of her own humor coming through). His chainmail hand was still pawing at his breastplate when they came to take him, dozens upon dozens of white-lights. No mere nanny programs or scan-and-sears, but government grade anti-cyberterrorism drones that flickered with a every security measure code there was in existence, glowing and indistinct. They attached themselves all over the knight and tore the armor from him, leaving his raw data construct, a crackling green, faceless humanoid. They took his voice when they took his armor, but Rexa could almost hear the shrill, staccato beat of his heart feed as the white-lights lifted his spiky, sparking body up into a tower for processing. The green fixed a rider on the nearest white-light and she rose with them, silent as a ghost. From the boy’s raw data construct there were periodic bursts of physio input, which she figured to be him screaming somewhere in his stem room

Rexa thought the whole spectacle pretty, and terribly funny.

***

An admin had to take the boy for processing, and at its appearance Rexa triggered the red. Quicker than she could blink the red copied the admin’s clearance and used its protocols to meet the next highest admin, and then copied that program’s clearance, and so on until the red could find no higher clearance in the construct. When it returned to her, she wrapped it around herself like a cloak and ascended from the top of the security tower, straight to the highest-clearance operation room in the entire system of the federal government of the United States.

She had the satellites.

She had the nukes.

She had the world.

The construct for these keys to the world was a wide, smooth white chamber. The systems appeared before as glowing blue holograms, open, asking, waiting patiently to do as she willed. The red delivered her the CIA’s pathways into Russia, China, France, Germany, the U.K., and every single other system worth caring about. Then it sent scramblers down every channel and pathway below the chamber, and the security systems were shot up and shut down. Even if somebody knew she was up here, there was no one now on Earth with the clearance to get in. She had all the time in the world (the world that now lay at her feet).

Rexa sighed, allowing the cat’s tail to flick restlessly. This particular job lacked the subtlety and freshness of her last venture. She’d gone after shipping routes and grocery stores—this job would not exhibit the same quirky satisfaction of seeing her local supermarket baffled by 25 large shipments of duck meat, suffering the same mis-orders as countless others around the continent.  Still, for sheer magnitude of challenge, this entry couldn’t be beat.

But the question remained as to just what she would do now that she was up here. Her original plan had been to carefully re-knit all communication routes to the wrong destinations, but the idea suddenly seemed drab. She trolled the security feeds of government stems while she waited for a notion with more flair to strike her. Every office was in chaos and on every screen her signature sneered out at the people thrown into a blind panic. This time, however, she’d made a little adjustment to the image. Where her little exercises were normally signed with the image of a jester kissing a king’s hand, bearing the words “LONG LIVE THE KING,” there was now the image of the jester in the king’s throne with her feet propped upon his back, reading “LONG LIVE THE QUEEN.”

Queen indeed.

Rexa surveyed her new domain, ticking off all the major systems now under her control…and realized she was not alone.

“Now this isn’t the sort of activity a young lady should be enjoying,” came a voice directly into her head–someone not only with a comm line, but in the chamber itself with her. Somewhere, in a drab stem room by the river, her heart may have skipped a beat.

“Inspector!” she said cheerfully, turning the cat’s head a perfect 180 degrees and letting its smile show as many teeth as possible. “Have you come to see the show?”

“I think I’ve seen enough, Jester,” he said, “although I must admit you’ve impressed me. This time he took the form of s slim young man with a close-trimmed beard and glasses, with the affectedly fashionable garb of a university student. He was looking younger than he usually preferred. Rexa wondered if looking that way made him feel fresh for the chase, and then wondered if feeling fresh was something her inspector was even capable of.

“I’ve got you figured out, you know,” she said, letting the cat lounge back as though at ease. Her rabbit program had started the moment she registered police presence, but it would take time for the emergency shunt to find a randomized location to spirit her away to. Until then, she had to keep him talking.

“Do tell,” he said. He made no move to apprehend her, which made her uneasy.

“You’re AI,” Rexa said, and the cat’s tongue–too long–flicked out to lick its lips. “The best they’ve got, because they’d need it for me, but a bot all the same. It’s how you figured me out so quick, and why you’re so stuffy all the time.”

“I’m heartbroken to think you find me boring,” he said. She began to grow nervous. The rabbit wasn’t built for worming its way out of something this secure. The program lagged on and on, and Rexa knew she was running out of time.

“Things like you don’t have a heart,” she shot back.

“People say the same thing about you, little girl,” he said. Something about that gave her pause. She stood and faced him fully, the cat’s hackles rising despite herself.

“I’m sorry, that wasn’t fair,” he amended, raising one slim hand. “You’re hardly little, aren’t you? Twenty years old already, and about 5’5″ besides. That’s fairly average.”

Technically, she could not feel cold on the grid, or start to sweat, or go pale, but she felt it all the same. She felt her stomach drop right out through her shoes.

“You have my vitals!” she shrieked. That was it, she was over. They had her completely. “You hacked my freaking vitals!” Somewhere downtown her left arm jerked, slamming the blue cartridge into her deck until it clicked. The chamber exploded into bits of light and sound and static, cracked wide open, and the rabbit whisked her away.

***

The kick came like a brick to the face. She was jerking out of her chair and tearing off her cords before she had fully regained her sight or sense of balance. She slammed her deck shut and jammed it in her bag, the blue cartridge still smoking in its port. Her heart was pounding, her hands were shaking, and she tasted copper on her tongue. Both her nose and her lip, where she had bitten it, were bleeding. With her gear packed and no police yet breaking down the door Rexa forced herself to take a minute and look less like she had just dynamited her way out of a government construct.

By the time she left the room she had wiped off almost all the blood, but she still trembled and smelled like burnt plastic. There was nobody in the hallway to see her, police or otherwise. She began to feel hope as she took the stairs down to the lobby: had she really escaped? Had she blown the inspector to bits for good? If so, she’d miss his constant hounding. In Rexa’s opinion, if everything came easily, then nothing was ever fun.

***

Rexa made it all the way to the last row of chairs in the lobby of the stem. There in the last chair before the revolving doors sat a woman of about forty in a blue pantsuit, with shoulder-length blonde hair. As Rexa approached the woman stood and looked down at her with clear blue eyes, and she knew.

“You’re not a  man,” she sighed, defeated.

“And you’re not a demon cat or a fool,” the inspector replied. “Although the latter is debatable. You know we’d only got the vitals data off the mask, not the stem? We’d only placed you within the city. If you hadn’t tripped your physio reaching for the blast pack, well…” She spread her hands and shrugged. “Who knows?”

“Am I going to jail now?” Rexa asked, dropping her bag. She refused to cry in front of this woman.

“God, I hope so. Which reminds me: hands on your head. Lorexa Baisemain, you are under arrest for cyberterrorism, fraud, illegal software configuration, theft, treason…”

Sirching

“Dr. Sirch?”

He was a tiny dot in a room about the size of heaven. The back wall was covered with monitors that flickered every few seconds and Sirch clicked, absorbed, then changed to a new webpage. Sirch didn’t budge from his row of twenty monitors on the back wall of the Big Room. Maybe if he made no movement at all, she would stop calling his name and his headache would go away. And then he could sit and surge all day. And then -

“Doctor? Are you in there?”

The clacking of shoes approached. Sirch sighed, burying his hands in his sleek, jet black hair, trying to stop his headache and keeping his eyes glued to the screens.

Sirch drank a swig of backup juice for his head – the pain was starting to make his eyes water. Massaging his temples, he could feel the metal, the wires and the routers of New Brain, that he’d put in himself when he was five to keep his life while people plagued kids without cyberparts. Those were dark times. These were dark times. Twenty-one years had gone by and it had never ached as badly as this.

He absorbed and swung to the next set of monitors: the Void. He looked. Pictures of his father. His mother. His love, Demetria. The Void had taken them years ago. But the question lingered: Where were they?

Maggie, his assistant, pushed open the door without knocking. She hated when he took the Big Room, even though he insisted he was far more comfortable in wide spaces.

Time, Sirch thought, only half-listening, surging through the web pages on his one hundred monitors that lined the back wall of the huge white-walled room. Time was the problem. Because if there was more of it, he thought, massaging his head, his set of 100 monitors and his New Brain could help him surge frequently, and keep going, keep trying to find the Void -

“Doctor. Pierre Fander is here to see you.”

Sirch looked up.

“Doctor.”

The word slithered out of Fander’s mouth, making Sirch feel slimy.

He came with a stack of papers, forced Sirch to turn in his automatic swivel chair and pushed them into Sirch’s hands. Sirch saw a photo of a little girl shoved into the file with a brown bob and beaming eyes. She looked like a younger Demetria.

Sirch’s heart sunk.

“Fander,” he stuttered. “No. Please, no. Not her – ”

Fander paused, watching Sirch blubber as he realized who Fander’s next victim was.

“Alvin Sirch. Remember our little deal? I make you famous – the most famous researcher the world will see. I will do everything for you. The world will revere you. People will travel far and wide to see you.” Fander adjusted the claw on his right hand, which Sirch knew turned into a gun on command.

“Under one condition: you do all my research, exactly as I lay it out, which involves destroying the human race, child by child. Or your family and your girlfriend in my hiding explode into smithereens with the press of this button.” Sirch knew Fander wanted children just as every ruler of the Death did: because they didn’t have metal parts yet.

His New Brain pounded. He took a breath, unable to see clearly anymore, took the stack of paper and started netizen – searching all 100 monitors for the girl’s information, location, whereabouts. He felt sicker than ever. Surging the Void would have to wait.