Technical Reports

Reports by Year

 

 

2012

  1. MobiShare: Cloud-enabled Opprtunistic Content Sharing among Mobile Peers, IIITD-TR-2012-009, Kuldeep Yadav, Vinayak Naik, and Amarjeet Singh, October 2012.
  2. Securing the Uncharted Territory: Transaction Receipts in Branchless Banking, IIITD-TR-2012-008, Saurabh Panjwani, Mohona Ghosh, Ponnurangam Kumaraguru, and Soumya Vardhan Singh, July 2012.
  3. Take Control Over your SMSes: A Real-World Evaluation of a Mobile-based SpamSMS Filtering System, IIITD-TR-2012-007, Kuldeep Yadav, Anshu Malhotra, Ponnurangam Kumaraguru, Rushil Khurana, and Dipesh Kr. Singh, July 2012.
  4. Incremental Subclass Discriminant Analysis: A Case Study in Face Recognition, IIITD-TR-2012-006, Hemank Lamba, Tejas I. Dhamecha, Mayank Vatsa, and Richa Singh, March 2012.
  5. Using Twitter Sentiments and Search Volumes Index To Predict Oil, Gold, Forex and Markets Indices, IIITD-TR-2012-005, Tushar Rao and Saket Srivastava, March 2012.
  6. Twitter Sentiment Analysis: How To Hedge Your Bets In The Stock Markets, IIITD-TR-2012-004, Tushar Rao and Saket Srivastava, March 2012.
  7. ChaMAILeon: Simplified Email Sharing Like Never Before, IIITD-TR-2012-003, Prateek Dewan, Mayank Gupta, and Ponnurangam Kumaraguru, March 2012.
  8. On Simultaneous Latent Fingerprint Matching, IIITD-TR-2012-002, Anush Sankaran, Mayank Vatsa, and Richa Singh, February 2012.
  9. Recognizing Surgically Altered Faces, IIITD-TR-2012-001, Himanshu S. Bhatt, Samarth Bharadwaj, Richa Singh, and Mayank Vatsa, January 2012.

2011

  1. Tring! Tring! Usability Study of a Voice Based Information System, IIITD-TR-2011-011, Siddhartha Asthana, Pushpendra Singh, Ponnurangam Kumaraguru, Amarjeet Singh, and Vinayak Naik, December 2011.
  2. @Twitter Credibility Ranking of Tweets on Events #breakingnews, IIITD-TR-2011-010, Aditi Gupta and Ponnurangam Kumaraguru, November 2011.
  3. Low Energy and Sufficiently Accurate Localization for Non-Smartphones, IIITD-TR-2011-009, Kuldeep Yadav, Vinayak Naik, Amarjeet Singh, and Pushpendra Singh, November 2011.
  4. Context-aware IVR: Challenges and Opportunities, IIITD-TR-2011-008, Siddhartha Asthana, Pushpendra Singh, Amarjeet Singh, and Vinayak Naik, November 2011.
  5. 140 Characters of @Hate and #Protest, IIITD-TR-2011-007, Ashish Sureka, November 2011.
  6. Memetic Approach for Matching Sketches with Digital Face Images, IIITD-TR-2011-006, Himanshu S. Bhatt, Samarth Bharadwaj, Richa Singh, and Mayank Vatsa, October 2011.
  7. Twitter Explodes with Activity in Mumbai Blasts! A Lifeline or an Unmonitored Daemon in the Lurking? IIITD-TR-2011-005, Aditi Gupta and Ponnurangam Kumaraguru, August 2011.
  8. MELOS: A Low Cost and Low Energy Generic Sensing Attachment for Mobile Phones, IIITD-TR-2011-004, Abhishek Bharadwaj, Pandarasamy Arjunan, Amarjeet Singh, Vinayak Naik, and Pushpendra Singh, March 2011.
  9. Can Humans and Automatic Algorithms Recognize Look-Alike Faces? IIITD-TR-2011-003, Hemank Lamba, Ankit Sarkar, Mayank Vatsa, and Richa Singh, March 2011.
  10. Privacy of Location Obfuscation, IIITD-TR-2011-002, Debajyoti Bera, Vikram Goyal, and Anuj S. Saxena, March 2011.
  11. Stegobot: A Covert Social Network Botnet, IIITD-TR-2011-001, Shishir Nagaraja, Amir Houmansadr, Vijit Kumar, Pragya Agarwal, and Nikita Borisov, February 2011.

2010

  1. Attacking the Tav-128 Hash Function, IIITD-TR-2010-001, Ashish Kumar and Somitra Kumar Sanadhya, Updated on November 15, 2010.

Purpose

Technical reports are written to convey recent research development to the community. There are several purposes that are served by a technical report.

  • Timely dissemination: Journals and conference proceedings may take a long time in reviewing the papers and publishing them online. Getting a technical report for the work provides a mechanism of providing a date to the unpublished ideas, research results and intellectual property.
  • Availability: IIIT-D will always provide online link to technical reports that will be available to all in the open forum.
  • Supplement material: Any supplement material can be submitted later and it will be available with the report in the form of additional/supplement with the original report. The date of submission for the supplement material will also be made available.

Policy

To ensure the integrity of these technical reports, there are certain policies that the institute will follow.

  • The institute will keep a record of the technical reports and ensure proper backup and maintenance.
  • Once a report is published, its contents cannot be modified.
  • Request for publishing technical reports can only be made by faculty members.
  • Since the institute does not perform review of the technical reports, the institute cannot guarantee that authors will not post material that violates a copyright. It is up to the individual submitting a technical report to ensure that to the best of his or her knowledge, the publication does not violate any copyright constraints. The author will be responsible for any questions that may arise due to the work and IIIT-D does not have responsibility.
  • If there is a request for the report to be withdrawn, IIIT-D will permit it and not make it available on the web. However, the title of the report, authors and technical report number will be listed online along with the notification that the report is withdrawn.

Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission.This copyright is identical to the standard copyright notice currently used on ACM publications.

Procedure

The technical report (in pdf format) should be submitted to the Library Committee. There is no prescribed format to submit the report but it is expected that the report should have broad arrangement as Motivation/Introduction, Method, Results, and Conclusion. The librarian will assign the technical report number as IIITD-TR-Year-Num (e.g. IIITD-TR-2010-001). The last three digits represent the serial number of this technical report among all report received in that particular year.