Week 7-8: Start of Second Quarter
Welcome back to my blog. I had a wonderful relaxing break and have begun my second term at WPI. Fall also occurred suddenly in Worcester, which some of the trees on campus took quite literally.
Recap of First Quarter
Last term, I met and worked with both the IQP team and the graduate student mentor, Caitlin, several times a week. Our goal was to become well-acquainted with the project and start some initial designs such that we could start the second term at full speed. I am happy to say that we are all quite familiar with the topic now and have some great drafts of the user interface (please refer to the blog of my teammate, Diana, at diana.matters-creu.com).
One of the difficulties I experienced last term was the sensation of being pulled in two directions. On one side, I was working with the IQP team on cracking the LineUp code and designing the user experience. On the other, I was working one-on-one with Caitlin to define research questions upon which we could formulate a paper. Unfortunately, task-management is one of my weaknesses, and I fell into a trap of un-productivity.
![]() |
Like the pair of jeans in the Levi Strauss & Co. brand, I felt like I was being pulled in two directions. Image source: Photobucket.com |
I discussed this matter with the faculty advisor, Elke, as well as Caitlin and the IQP team and we decided it would be best if I focused my attentions on working with Caitlin for the research objectives.
Objective for Second Quarter
With all that out of the way, I am excited to start this next term. In the past week, I met twice with Caitlin (in addition to the bi-weekly meetings with the IQP team and faculty advisor) to discuss plans for this term. My objective will be to produce a Python script that takes a dataset and partial ranking information from a user and learns a complete ranking (build-a-rank tool). To motivate this tool, Caitlin and I are considering implementing recently reported metrics that control for bias and fairness. These metrics will be available to a user and will safeguard the user from unintentionally biasing their results. In addition to creating the deliverable script for the RANKit application (under development by the IQP team), Caitlin and I hope to turn the results of our research into a paper.
Bias and Fairness
A 2016 paper by ProPublica caught the attention of the research community when it suggested that the COMPAS score, used by judicial courts to assess a defendant's risk of re-offense, was biased against black defendants. The company in charge of COMPAS, Northpointe, issued a report denying the bias, and a discussion ensued across the research community (read more about it here).
The plan is to incorporate the results of that discussion into our ranking toolkit. RANKit is designed to help users interact with their data and interpret the rankings. In that paradigm, it makes sense for our application to allow users to easily apply the various fairness metrics into their ranking and see how it impacts the results.
In the literature, bias and fairness are almost exclusively considered in classification settings (for example, black defendants versus white defendants). Without constraining the objects we rank into two groups, is there another way to apply the idea of fairness to a ranking? This is the question I hope to answer in my blog next week.
Until next week.
Comments
Post a Comment