Having more time to do research, of course! With the pressures and schedules of classes over, students everywhere are turning to a dedicated stretch of research work, either on their own theses and dissertations, or for paid research jobs, or internships. That means, with Laura and I graduating, there should be a new student taking over the Cyberlab duties soon. However, the other thing that summer means is the final push to nail down funding for the fall, and thus, our replacement is not yet actually identified.

In the meantime, though, Laura and I have managed to do a pretty thorough soup-t0-nuts inventory of the lab’s progress over the last couple years for the next researchers to hopefully pick up and run with:

Technology: Cameras are pretty much in and running smoothly. Laura and I have worked a lot of the glitches out, and I think we have the installation down  to a relatively smooth system of placing a camera, aligning it, and installing it physically, then setting it up on the servers and getting it set for everyone’s use. I’ve got a manual down that I think spells out the process start to finish. We’ve also got expanded network capability coming in the form of our own switch, which should help traffic.

Microphones, however, are a different story. We are still torn between installing mics in our lovely stone exhibitry around the touch tanks or just going with what the cameras pick up with built-in mics. The tradeoff is between damaging the rock enclosure or having clearer audio not garbled by the running water of the exhibit. We may be able to hang mics from the ceiling, but that testing will be left to those who follow. It’s less of a crucial point right now, however, as we don’t have any way to automate audio processing.

Software development for facial recognition is progressing as our Media Macros contractors are heading to training on the new system they are building into our overall video analysis package. Hopefully we’ll have that in testing this next school year.

Eye-tracking is really ironed out, too. We have a couple more issues to figure out around tracking on the Magic Planet in particular, but otherwise even the stand-alone tracking is ready to go, and I have trained a couple folks on how to run studies. Between that and the manuals I compiled, hopefully that’s work that can continue without much lag and certainly without as much learning time as it took me to work out a lot of kinks.

Exhibit-wise, the wave tanks are all installed and getting put through their paces with the influx of end-of-year school groups. Maybe even starting to leak a little bit as the wear-and-tear kicks in. We are re-conceptualizing the climate change exhibit and haven’t started planning the remodeling of the remote-sensing exhibit room and Magic Planet. Those two should be up for real progress this year, too.

Beyond that, pending IRB approval due any day for the main video system, we should be very close to collecting research data. We planned a list of things that we need to look at for each of the questions in the grant, and there are pieces that the new researcher can get started on right away to start groundtruthing the use of video observations to study exhibits as well as answering questions about the build-and-test nature of the tsunami wave tank. We have also outlined a brief plan for managing the data as I mentioned a couple posts ago.

That makes this my last post as research assistant for the lab. Stay tuned; you’re guaranteed to hear from the new team soon. You might even hear from me as I go forth and test using the cameras from the other side of the country!

 

The lab has purchased a bunch of relatively expensive equipment for use by our researchers at HMSC, students who may work mainly at the main campus in Corvallis or on their dissertations elsewhere, and our collaborators in other states and countries. Creating a system that allows for easy movement of the physical systems yet maintains the integrity is proving to be a complicated task for many reasons.

First, the equipment resides mainly at HMSC in Newport. Right now, only Shawn actually lives and works probably 75 percent of the time in Newport. Mark lives in Corvallis (about an hour away) but spends maybe half his week, roughly, in Newport, and Laura and I live in Corvallis but usually spend less than half the week in Newport.  For all of us, the schedule of Newport vs. Corvallis vs. elsewhere work time is not at all regular. This means that no one is a good go-to person for handling the check-in and -out of the equipment unless a user is enough of a planner to know they need something (and know exactly what they need) in advance to ask one of us to bring it back to Corvallis.

And in reality, we don’t really want to have to act like overlords hoarding the equipment and doling it out when we feel like it. We’d like to have a system where people can access the equipment more freely but responsibly. But our shared spaces have other people going in and out that make it difficult to restrict access enough with the limited number of keys to the cabinet we have yet work without a main gatekeeper. Plus, things have just gone walkabout over the years since no one does keep track. People forget they have something, forget where it came from, leave the school and take it with them, not maliciously, but out of lack of time to worry about it and frankly, no one with interest in keeping up with the equipment. This especially happens with Shawn’s books. Full disclosure: I’m pretty guilty of it myself, at least of having things I borrow sit on my desk far beyond the time that it might be reasonable for me to keep them. No one else may be asking to use them, but if the resources aren’t on a shelf or in a database for browsers to know they’re available, it’s not really available in my eyes.

So we’ve struggled with this system. I tried to be the one in charge for a while, but I wasn’t travelling back and forth to Newport regularly, and it was a burden for people to come to me then me to find someone who was in Newport to pick it up and bring it to me to turn over to the borrower, and basically reverse the process when stuff was returned. Technically, the school probably wants us to have people sign off on taking equipment, even things with the small dollar values of these items, but that’s another layer of hassle to deal with.

Plus, the database programs we’ve tried to use to keep track have proved annoying for one reason or another. Again, most of the database programs are linked to one computer, so one person had to be the gatekeeper. For now, we’ve settled on a paper sign-out system on the door of the cabinet holding the equipment, but that doesn’t integrate with any computerized system that would be easy to track what’s out and in at any given time and when things are due back. The school multimedia system on campus uses barcode scanners, but the cost of implementing a system for our small use case is probably prohibitive. Peer-to-peer lending systems have the owners responsible for their own stuff, but even they often use online databases to track things. Suggestions welcome!

It’s just another thing that most people don’t think about that’s behind-the-scenes in the research process. And then when you go to do research, you spend way too much time thinking about it, or stuff gets lost.

Just a few quick updates on this holiday about how lab is progressing.

-We’re re-thinking our microphone options for the touch tanks. We’re reluctant to drill into our permanent structure to run wires, so we’re back to considering whether the in-camera microphones will be sufficient or whether we can put in wireless mics. With the placement of the cameras to get a wide angle for the interactions and the loud running water, the in-camera mics will probably be too far away for clear audio pickup, but the wireless mics require their own receivers and audio channels. The number of mics we’d want to install could rapidly exceed the amount of frequency space available. Oh, and there’s the whole splashing water issue – mics are not generally waterproof.

-We finally got a lot more internet bandwidth installed, but now we have to wait for on-campus telecommunications to install a switch. We’re creeping ever closer … and once that’s done, we can hopefully re-up the frame rate on our cameras. Hopefully we’ll also be able to export footage more easily, especially remotely, as well. I’ll be testing this out myself as part of my new job and future research.

-I installed a NAS network drive of five 2 TB hard drives that will probably be our backup system. It needed about 40 hours to configure itself, so next week we should hopefully be able to get it fully in place.

-We took the whole system down for about an hour to replace the UPS as the old one was just shot.

-We’re looking into scheduling to accommodate school groups that don’t give permission for taping, as well as evening events. This should be possible through the Milestone Management software, but it’s not something we’ve explored yet.

-Remote desktop access to the servers is next (hopefully). This is also waiting on the campus telecom network switch.

-We’re migrating our exhibit software from Flash to HTML 5 in order to be more easily updated as well as incorporating the key/screen press logging code.

Happy Memorial Day!

Yes, we failed to change the default password on the cameras we installed. Someone managed to get ahold of the IP addresses, and guess the login and password. We escaped with only minor headaches, as all that happened was that they uploaded a few “overlay” images that appeared on some of the camera feeds, and a few text messages that seemed to be mostly warning messages to us about cybersecurity.

The hacker did change a few of our passwords for the cameras, so there were some from which we could not just delete the images. This has meant various levels of hassle to reset the cameras to default. For the white brick cameras, 30 seconds of holding a control button while the power cycles was sufficient. I didn’t even have to reset the IP address. For the dome cameras, it’s a bit more complex, as the IP address has to be reset, and I wasn’t around for that part originally so I’ll have to consult IT.

However, it makes us wonder about the wisdom of having even the camera views available without a password on the web, which we hadn’t considered was available before. You’d have to have the IP address to go to the view, but once you were there, our IP addresses are mostly sequential (depending on the day and which cameras are installed), so you could go visit each of them if you liked. There seems to be an option to turn this off, however, which I have also gone through and switched so that now you need not only the IP address, but the username and password in order to even view the feed.

Moral of this part of the story? Explore the default settings and consider what they truly mean. Be a Nervous Nellie and a bit of a cynic, assume the worst so you can plan for it.

UPDATE 5/16/13: I couldn’t get the 3301 dome cameras reset despite following the unplug, hold control button, re-plug power sequence. Our IT specialist thinks the hacker may have actually reset the default password via the firmware, since they should have automatically reset themselves to the same IP addresses using DHCP. So those two cameras have been pulled and replaced while the hacked ones are off to the IT hospital for some sleuthing and probably a firmware reset as well. I’ll let you know what the resolution is.

The wave tank area was the latest to get its cameras rejiggered and microphones installed for testing, now that the permanent wave tanks are installed. Laura and I had a heck of a time logging in to the cameras to see their online feeds and hear the mics, however. So we did some troubleshooting, since we were using a different laptop for viewing over the web this time, and came up with these browser-related tips for viewing your AXIS camera live feeds through web browsers (when you type the camera’s IP address straight into the address bar of the browser, not when you’re viewing through Milestone software):

When you reach the camera page (after inputting username and password), go to “Setup” in the top menu bar, then “Live View Config” on the left-hand menu:

First, regardless of operating system, set the Stream Profile drop-down to H.264 (this doesn’t affect or matter to what you have set for recording through Milestone, by the way – see earlier posts about server load), and then Default viewer to “AMC” for Windows IE, and “Server Push” for Other Browsers.

Then, to set up your computer:

Windows PCs:
Chrome: You’ll need to install Apple’s QuickTime once for the browser, and then authorize QuickTime for each camera (use the same username and password as when just logging into the camera)
Internet Explorer: you’ll have to install the AXIS codec once you go to the camera page (which may require various ActiveX permissions and other security changes to Windows defaults)
Firefox: Same as for Chrome, since it uses QuickTime, too
Safari: we don’t recommend using Safari on Windows

Mac:

Chrome: QuickTime needs to be installed for Chrome

Firefox: Needs QuickTime installed

Safari: Should be good to go

IE:  Not recommended on a Mac

Basically, we’ve gone to using Chrome whenever we can since it seems to work the best across Windows and Macs both, but if you have a preference for another browser, these options should get both your video and your audio enabled. And hopefully save you a lot of frustration of thinking you installed the hardware wrong …

If you google “record phone call” or “digital audio recorder+phone,” you may end up watching spy videos.  Thanks for the entertaining spy videos Google, but I’m just trying to do my thesis.  I’m trying to figure out how to record my phone interviews, and this won’t be done secretly.

The OSU Student Media Services desk at the library is extremely helpful, and they have a ton of equipment to check out.   They have a device that connects to the Zoom H2 digital audio recorder, and plugs into your ear.  Both me and the person on the phone will be recorded.  Unfortunately, it’s broken!  They said they will try to order another device soon, along with some other types of leads (things that plug into my phone and the recorder).

I’ve heard it’s good to have 2 recorders working, just to be safe, so  I’m also looking into apps that record calls.  I’ve seen a few for iPhones, but I have an Android.  Free Android apps include Record My Call, Call Recorder, and Auto Call Recorder.  One question… What are the privacy rules with these apps?  Will any outside party be able to access the recording?

If anyone has suggestions for recording phone interviews, PLEASE (!) let me know!  Thanks 🙂