Search This Blog

Week 19: Getting Back to Work

Applying for and receiving the approval for the IRB, left us with only one major task: make sure our website is bug and typo free, clean, and usable for everyone.

Our faculty advisor, in testing out our web application, ran into a problem. In our dataset selection screen, we have a hover over functionality on each dataset square that flips over an option between the Build and Explore tools. However, on our faculty advisor's laptop, hovering over with the mouse did nothing, and neither did clicking on the dataset block.

I took up the task of resolving this bug. Turns out, that none of the group members had a touch screen laptop, what our faculty advisor had, and so this problem was left unnoticed. While normal clicking and moving around did not get a response, what did seem to work is using the touch screen and touching the dataset block. Upon doing so, the flap flips over with different tool options. However, this behavior wasn't intuitive, and so I fixed the code such that the flap was always visible.

Furthermore, another bug was discovered. In the pairwise method, whenever you would put an item back into the dataset pool, the item does not disappear (and so you have multiple occurrences of one item).

Also, the backend crashed whenever an item had a colon in its name.

After fixing all of the bugs, I was done with my weekly tasks (and all the known bugs were fixed).

Get link

Facebook

Twitter

Pinterest

Email

Other Apps

Comments

Post a Comment

Popular posts from this blog

With the Rankit paper submitted, it was time for me to change gears and dive into the research with MaryAnn.

For me, this week revolved around getting up to speed with the fair ranking research. I read over the current in progress fair ranking paper and attended meetings where MaryAnn and Caitlin helped familiarize me with the code base and research that they've completed.

After formulating an experimental plan, we needed to have some datasets to run those experiments on. There are some requirements that classify a good dataset for this task: it must be non-trivial in size, needs to include a protective attribute (such as gender or race), and it must have some true ranking. While it is possible to find a datasets that satisfies two out of the three requirements, it becomes difficult to satisfy all of the requirements.

Encompassing a dataset from Rankit, list of Fifa 2018 players was added as a possibility. It contained 17981 players, has a protective attribute (age and nationality), and potentially has a true ranking. The true ranking can be based on goals scored, or money earned by the player. Some ranking data can also be found over this datasets, although it does not encompass all of the players.

Hospitals and doctors also have a significant amount of data, both attribute and entity-vise. However, finding a true ranking might prove to be impossible.

Taking into account the feedback received from the our mentors, we updated the section analyzing the outcome of the online user study. We updated the machine learning section to include more references and added more charts to the whole paper.
The team also discussed the next steps and observed new features to be implemented.