Addison Slick TLR #Last

For my final trick, I will examine two of my current extracurricular DH projects.  The first is my personal website, and the second is the updating of my board games to be “not s***.”  I am using CSS for the former and Adobe Illustrator for the latter.

My website still somewhat nebulous in that it is unpublished (and on another computer — I’m on my tablet right now).  My ultimate goal is to host my own content on the site for free download to the public (you shouldn’t have to pay money for the crap I make), hopefully getting at least a few people to play them.  I’ve thought about trying to reformat them for the web, or even a desktop or mobile app, but I feel like the medium helps my intended metaphor so I’d rather keep them as they are for now.
I’ve also been using Illustrator to make custom graphics for the site to give it a more directed feel.  Because the medium I’ve used the most is board games, I want the site to have a feeling sort of like that.  Presently, my site’s pages are presented on a sort of banner made of generic game spaces.  I’m hoping to expand that theme into other elements of the CSS.

For my games, I’ve been trying to improve my narrative text and rework mechanics to make it more choice-based than the current edition.  Right now, they both feel a bit like Candy Land and that’s awful.  In the depression game, I’m changing the path choices to allow the player to skip and event to represent memory repression. I also want to change the dice mechanic to allow the player to choose between 2 outcomes; this not only gives players more control, but means that removing that control causes a greater panic and anxiety in the player later in the game.  It should be fun.

The games will be available as .pdfs on my site by [TBD].


TLR #5

So I don’t suppose looking at things like Homestuck counts as having made progress for a Technical Learning Report, does it? It’s the thing Addison mentioned when we first started the Interactive Fiction group, and while I can understand what he meant when he said that Homestuck is an example of interactive fiction, I doubt this is what we will end up trying to go for, at least I hope this isn’t what we are trying to achieve.

The interactive fiction idea we are going for seems more inline with the wikis that are made for basically every fandom in existence. I’ve been looking at wikis of things that are familiar to me such as Star Wars or Game of Thrones and it looks like every detail, major and minor, of these things gets recorded on these wikis and while you can change it at any time, if the information is inaccurate, someone else on the website is quick to come in and fix it. I mention all this as the idea that Addison and the rest of us discussed for interactive fiction is to create a wiki for a fictional world and  move backwards from there, so I just wanted to see and experiment a little with previously established wikis.

As for the coding which I have been doing this semester, I have been going over both HTML and CSS off and on over the past few weeks just to make sure I don’t forget everything I got out of going over them the first time (It’s only been a few years and I remember next to nothing about coding with C++). I think I’ll be establishing a consistent schedule to use both HTML and CSS once the semester is over, as I think that knowing both could be very useful in the future and one the semester is over I will have much more time to do with them as I wish. I mentioned in my last TLR that I had also started trying to learn Java just to add to a potential coding arsenal (I wish). Since my last TLR, while I have gone over some more Java related tutorials, I have not done as much with it as I had previously intended to. Due to the work over the past couple weeks, both in and out of school, my progress on Java has been very slow. Like with HTML and CSS, however, I intend to spend more time learning Java once the semester is over and I have a chance to breathe. The way that we are planning out the Interactive Fiction group project at the moment, it looks like I won’t need to use a lot of coding for that, at least not advanced coding. Even so, I would like to continue learning and practicing with these coding languages even after this class is finished. Though I had briefly considered trying to learn Python before this class had ended, the way it stands now it would probably be best to save that for much later.

CDechsi – TLR 5

This time I decided to experiment with audio and visual combination in Adobe Premier Pro and Audacity. Basically, I took pictures, like screenshots or animated environmental effects, and layered a track of audio behind them. This effect is basically supposed to provide a sense of engrossment to the viewer/reader, which may or may not have a place in my part of the interactive fiction project.

I used Audacity to experiment with my audio only method. I combined certain sounds, like clock ticking, with a hollow wind that people would probably hear from a drafty old house. Balancing the audio was a bit of work but the end result sounded good enough. The problem is deciding which one I will go with, whether it’s simple video and audio work or audio only. Both will be somewhat challenging just fixing everything together, but we’ll see what happens.

– Champ

TLR#5 Asia W

I have began to explore a new site called Moovly provides more animating options than scratch. Users can create animated videos, banner ads, presentations, infographics, e-cards, and videoclips.The purpose of the creations on this site are to demonstrate, explain, and/or entertain. That being said it appears that it will be of more assistance in our final group project.

When you begin you are offered a large library of  objects to animate. This tool has been much easier to use than scratch. Unfortunately, all of the features are not free to use. The tutorials available on the website helped me to present information in a fun way. I am given the option to begin from scratch, edit an existing animation, or duplicate one and edit the copy.

For our final project, we are working with a water bottle. I decided to take the image of a  bottle from the library and figure out all of the things I could make it do. It wasn’t necessary for me to understand graphing like with scratch instead I could use previously set directions to control my object’s movements.

After understanding how to make the generic bottle function I attempted to animate a water bottle more relatable to our project. I uploaded the image of an actual water bottle. More real than the sketch, it was also more difficult to animate. After trying various uploads I was able to work with the most flexible image.

Adding sound to the animation was more difficult. A library was not offered to me instead I had to use my own productions and downloads. Playing around with different sounds to see what was most appropriate for the animation I was developing was not difficult but time consuming. I suppose if I were to create the sounds myself I would have the ability to produce the most fitting sound.

Adjusting the timing of the appearance of the images and sound was much easier on Moovly. Instead of guessing I was able to see a storyboard of all of the things I created and could adjust the timeline according to how I wanted things to appear.

Scratch and Moovly are very similar platforms. Moovly is much more user friendly. The skill I developed on Scratch helped me to operate Moovly quickly but anything I didn’t understand how to do, a tutorial explained very comprehensibly how I should move forward. Unlike with scratch, the animations I create with Moovly will be easy to embed in our final project. Anything I create on Moovly can be downloaded to my personal computer and uploaded elsewhere.

TLR 5 Corey Kirk

Learning how to code in Python is a lot harder than I originally thought. I thought I would learn it just as fast as HTML but I’m just not. One of the main reasons for this is that I hit the part where I am supposed to know a little bit of math. I can barely pass the math classes that I am in now at school, let alone the stuff that I need to learn for the language. However, there is a bit of silver lining in it. Several people I know, including those who have actually made games that they have shown a conventions like PAX East, have offered to help me learn to program in Python. So whatever I can figure out, I will be able to go to them for additional explanation on how to actually create programs.

I am a bit surprised that what I have learn so far seems less practical for my purposes for this course. Sure, learning Python will help me make programs, but for the project we are working on in my group, and for any web based applications, my previous knowledge of HTML, CSS, and the little skills in JavaScript are helping a lot more. Although, that’s not to say that I don’t want to learn. I still want to get very good at Python so that I can move onto C++, which is the standard language for creating video games, which is my ultimate goal.

Since this is my final TLR for the semester, I will say this; this semester provided me with more understanding of code, but I gained an unmeasurable amount of knowledge about how code affects the world in which we find ourselves living day to day. I am grateful that I had an opportunity to take this class because it opened my viewpoint wider than it has ever been in the past.

Analysis of a DH project: BEARINGS of Baltimore, Circa 1815


BEARINGS of Baltimore, Circa 1815 is an interactive 2.5 billion pixel image that was created by UMBC’s Imaging Research Center (IRC). BEARING stands for “Bird’s Eye Annotated Representational Image/Navigable Gigapixel Scene”. The image visualizes the city of Baltimore in 1815, during the aftermath of the British attack on Fort McHenry. As we know, the attack of Fort McHenry is a moment that was immortalized by Francis Scott Key when he penned the Star Spangled Banner after the battle.

The image was completed in the fall of 2013, after two years and 5,000 hours of work. UMBC’s IRC worked in collaboration with the Maryland Historical Society (located in Baltimore), and the Maryland Division of Tourism, the 1812 Bicentennial Commission, and the Robert W. Deutsch Foundation provided funding.


The display at the Maryland Historical Society


The image can be seen on your browser (Google Chrome required) or on a large display at the Maryland Historical Society. For this review I will focus on the browser experience. The first glimpse of the map may require a second glance. The familiar tall buildings and interstate system are absent and the map is oriented in a way that most have probably never viewed the Baltimore landscape. The user overlooks Baltimore aimed in the direction of Fort McHenry. This is view, looking down river, is the city as Francis Scott Key would have seen it in 1815. A user can manipulate the map just like they would Google maps on the computer (the display in the Maryland Historical Society is touch screen). The user can zoom in and out of every available part of the image, almost to part of being able to see clearly, individual trees.

Screen Shot 2014-11-01 at 11.04.50 PM

The image as seen on Chrome browser. Visit

At the bottom of the page the user can select from a list of “Hotspots”, which are shortcuts that automatically zoom the user into certain places of historical significance. Some of these locations are still components of the city circa 2014, such as the Lexington Market. Hotspots also include things that no longer make up the fabric of the city such as the “mud machine”, a contraption that would dredge the harbor, and the multiple “ropewalks”, extremely long and narrow buildings that made ropes. These Hotspots provide some insight to the nature of the city’s burgeoning harbor industry at the time.

When zoomed into a Hotspot a user can click the underlined text to reveal pop up windows that provide information about the Hotspot and often include images of artifacts, or transcriptions of relevant primary source documents. Did you know that Lexington market is the oldest continually running market in the country? From the Hostpots users can learn information about the places they may have interacted with before in everyday life. Currently there are 24 hotspots. The map also allows the user to toggle on and off, a feature that will overlay important landmarks that exist today:  Camden Yards, interstate 95, Domino Sugar factory, etc.

Screen Shot 2014-11-01 at 11.13.08 PM

Overlaid landmarks of Baltimore in 2014

What makes this DH?

According to Matthew Kirschenbaum in his chapter of the book Debates in the Digital Humanities, “The digital humanities, also known as humanities computing, is a field of study, research, teaching, and invention concerned with the intersection of computing and the disciplines of the humanities”. In keeping with this definition, BEARINGS is clearly an example of a DH project. This is made clear by a video of how the IRC team created the predecessor and proof of concept for the image of Baltimore, a visualization of DC.

In the video, Dan describes the primary challenge of creating the base map: the layer of the image that consists of cartographic information based on data pulled from early paintings, drawings, and documents about the area. This phase represents how computation and the humanities intersect in the creation of new scholarship. Mapping and animation software are able to stitch together disparate pieces historical information that has been gathered by a team of “architectural historians, cartographers, engineers, and ecologists to assess the often unreliable eye-witness accounts “.  In 1815, photography was not invented and so it was difficult for the animators and mapmakers to ascertain what the area actually looked like. There are illustrations from the time but most professionals at the time were educated in the romantic landscape tradition and thus their work does not provide accurate topography, and spatial information. After digging through documents like detectives, the IRC worked with UMBC’s Center for Urban Environmental Research and Education (CUERE) to create an accurate topographic map also portrays the spatial data of buildings in three dimensions.

Critiques and ideas for future functionalities

        Dan Bailey from the IRC team mentioned in an interview with WYPR that the BEARINGS project is not meant to be a static form of scholarship.  The project is meant to grow throughout the years and serve as a framework for further kinds scholarship, similar to how Google Maps provides more functionality than just that of a traditional map by including information/reviews of restaurants, etc.

As a giga pixel image, BEARINGS very clearly adheres with the following DH definition from Short Guide to the Digital_Hummanites:

Digital Humanities marks a move beyond a privileging of the textual, emphasizing graphical methods of knowledge production and organization, design as an integral component of re-search, transmedia crisscrossings, and an expanded concept of the sensorium of humanistic knowledge.

However, I wish that beneath the initial visual layers of information in the BEARINGS gigapixel, there were more content, including text. I do believe that DH projects need to push past relying on text to carry the day but I also think that text and even long form writing components should always be included in some way. Articles can provide depth on certain topics that can aid further discoveries by the user in the image. To no fault of their own, the user is oblivious to many of the historical details included in the gigapixel. For example, consider the following excerpt from a press release about the visualization written by the Maryland Historical Society.

A historically accurate paint scheme was used for the shutters. Notice how the shutters were louvered on the upper floors – their purpose was for ventilation from the hot, dusty street below. On the first floor, the shutters were paneled, for privacy from passersby. A hand-painted sign, a replica of what hung outside the hotel, was the final touch.

Screen Shot 2014-11-04 at 10.13.43 PM

The furthest you can zoom in, it is difficult to notice historical significance of the blind design.

I did not notice the detail about the shutters from my exploration of the image. I simply didn’t know that this level of detail was possible in the image, and even if I had noticed it I would not have understood the historical significance. I think this information is important because it allows the image to connect to an aspect of the lived experience that is still relevant to Baltimore. Current residents who deal with the sweltering summer months can surely relate with past residents who made design modifications to help aid ventilation in homes.  The fact that this interesting detail is not integrated into the image itself supports my belief that the image needs greater amounts of interaction.

I would include more text boxes at certain levels of the information hierarchy in this project. This would serve as a curating force, helping users to understand what they’re looking at. Future iterations of the project could allow users additional opportunities to interact with buildings. Rather than only being presented with a blurb to read when looking a Hotspot,  the text could could be related to the object itself in some way. For example users could be prompted to click on the blinds of a certain building and learn about the reason for their design in 1815.

Screen Shot 2014-11-04 at 10.14.23 PM

“BEARINGS of Baltimore, Circa 1815 also includes accurate representations of the area’s vegetation, including plants that have since become scarce and even extinct. The American Chestnut Tree, for instance, was prevalent in 1815 Maryland before being wiped out by blight between the late 1800s and the mid 1950’s.” Read more from the Maryland Historical Society press release linked above.

Another further form of interaction that I think is missing is the ability of the image to connect to additional scholarship outside the image itself. Could there be a kind of API for the project? The image can then serve as a gateway to further information relating to Baltimore and help create a discourse community that would co-create an understanding of Baltimore’s past. Open source components could be a powerful addition to the project. This has succeeded with maps before. Consider Waze, a navigation mobile app recently acquired by Google, which relies on user-generated content to present users with relevant information about such as traffic conditions and the location of speed traps (I’ve never heard of an open source gigapixel so I will have to do further research).

Besides increased methods of interaction, I do wish that the creators of the project incorporated reflexivity into the image to help us understand how the map was made from archive material. For example, users should be able to easily view what documents serve as evidence for why buildings exist in their given locations. As Johanna Drucker explains in her article “Humanities Approaches to Graphical Display”, it is important that in DH projects, data be portrayed as qualitative and not given truths. By providing access into their data analysis process, the team behind BEARINGS would add transparency to their analysis and in the process also make the archive of documents from the Maryland Historical Society accessible in a totally new way. If each Hotspot in the image linked to relevant archival documents, the project will also create a method of locating historical information that is not possible through traditional catalog search functions. The map could be a form of visually searching the historical arhcive of the Maryland Historical Society.

These additions I have proposed will require time, of course. Dan Bailey has expressed that the project will continue to grow over the years so it will be exciting to see how image, and our understanding of the city of Baltimore, changes over time. Please comment below if you have any additional suggestions for Dan Bailey and his team.