Research Report

From CMSC798F Spring 2015
Jump to: navigation, search

Research Report (Team projects of 4 people)


Part 1: Write: Prepare a short report (6-10 paragraphs, approx 500 words) about a research project that one of you is involved in or one of our professors is doing. The audience is informed readers, but not technical specialists. Your goal is to make a readable, compelling report that might trigger interest to know more by students, science journalists, or business people. Include at least one figure, one citation, and several URLs to a website, person, or paper. At the bottom include your names, contact info, and the date. Post your report on the class wiki (Bottom of this page), possibly on the CS website (if invited to do so), or in another public location. (Due on Monday February 16, 2015, 6-10pm).


Part 2: Critique: Read one report (add your name on the Report Critique SignUp) and send an email (no attachment) critique to the team and ben@cs.umd.edu (Due Monday February 23, 2015 no later than 10pm). Your critique (100-300 words, include the title, URL of what you are critiquing), as a letter to the authors. Describe what you like and why, then make suggestions for improvements.


Part 3: Publicize: Open up Twitter accounts, follow each other (and the Dept), then tweet and retweet the stories posted by fellow students, and track the number of visits to the stories. This will continue through the semester, as we discuss what makes a report successful & what makes a research project interesting.

References on publicizing with Twitter:


Part 4: Track: See if you can trigger uptake of the stories by others outside the class, by retweets, facebook posts, blogs, general media, etc. And finally track if the URLs of the research website or the paper get downloaded more than other work in the department, or more than in the past (establish baseline). This is also exploratory, so we will work throughout the semester to refine our techniques.

State-of-the-Art in Automated Graphical User Interface Testing - Team 9: Andrew, Greg, Weiwei, and Zebao

Rule Extraction from Neural Networks - (Team 3, continued WIP) Brule, Gupta, Magen, Seddighin

NewsStand - Team 7: H. Esfandiari, N. Kofinas, M. Najibikohnehshahri, and H. Wei

Scaling Computation of Graph Structured Data with N­Scale - Team 4: K. Xirogiannopoulos, S. Herwig, B. Chen and M. Shao

CommentIQ Team 8: N. Fung, E. Kowalczyk, D.G. Park, Z. Xu

Diarrhea in young children from low-income countries leads to large-scale alterations in intestinal microbiota composition - Team 6: F. Dorri, A. Memory, X. Sun, U. Koc

Saliency-Assisted Navigation of Very Large Landscape Images - Team 10: Eric Krokos, Mohamed Gunady, Peter Sutor Jr, Brian Brubach

Social fabric fitness: the design and evaluation of wearable E-textile displays to support group running - Team 5: Karthik Abinav, Sina Dehghani, Arunesh Mathur, Alison Smith, Xi Yi

Baxter Robots are learning to Think, See, and Cook - Team 1: Benjamin Bengfort, Victoria Cepeda, Huijing Gong, Nicholas Labich, and Mahmoud F. Sayed

Report Temporarily removed: Janus: bleeding edge face recognition - Team 2: Josh Bradley, Ahmed Elgohary, Youndo Lee, Varun Manjunatha