Reviewer #1

I’m around 3 years into my PhD at this point and so far, I have reviewed for a couple of journals as well as conferences. Mostly journals. But recently I was approached to review for a highly selective conference. And with great paper selectivity comes great hatred towards reviewers.

Of course, I wanted to use this new great power with great responsibility, so I took upon myself, the role of the open minded, somewhat timid, yet trying-hard-to-do-justice, reviewer #1. Which also happened to be my assignment for 4/5 papers that I had to review (I was reviewer #2 for the last paper).

My past experiences with reviewing have been comparatively less challenging. Most of the journal papers that I was asked to review had a good amount of overlap with my own research; plus the review time for journal papers is way more flexible.

Of course, as years have passed I find that my critical thinking abilities have improved, at least in the area that I’m working on. I have cultivated the skill of being able to discern a good idea from a bad one.

Which is all good, but reviewing for this particular selective conference was a whole new challenge. Firstly, the trope. The memes. The reputation. You know what I’m talking about, right?

Well if you’re late to the reviewer’s banquet, there exists a Facebook page with around 22k members at this point, called Reviewer 2 Must Be Stopped! Also brilliantly written blog posts on how not to be reviewer 2. The struggle is real. From my understanding of this meme, there are 2 broad categories of reviewers. Reviewer #1 is the nice, possibly new kid on the block who is kind and appreciative of the paper. Most possibly a frustrated grad student, she is very understanding of the position of the authors. Not too critical but brings up good points. Reviewer #2 (or interchangeably reviewer #3) is the bad cop. The one that puts the authors in deep existential crisis. That makes them question, why they even started pursuing the idea. Reviewer #2 is the dreaded one.

If I wanted to play into the stereotype of reviewer #1, I would have needed to review very responsibly for this conference.

Secondly, I don’t consider my knowledge base to be very broad. I was assigned five different papers with 4 different themes. The themes of course had a fair amount of overlap and I wasn’t allotted a paper that I found myself blanking out on. It was definitely a lot of information to take in, however, I wouldn’t consider that to be a problem. If anything, I only learned from the papers I read. And I did manage to critique a few things based on my understanding, to the extent of my ability. I think reviewing or critiquing, much like anything else, is a skill that one gets better at with practice.

I think reviewing also gave me an insight into how stochastic the process of getting a paper accepted can be. When I told one of my friends about me being a reviewer for this conference, he was taken aback and acted dismissively. He said that this was exactly why the academic reviewing process wasn’t as good as it needed to be. Because of not-so-competent PhD students instead of only well-versed researchers and professors reviewing papers.

I don’t agree. I think it makes sense to have a paper inspected by researchers with various levels of expertise. It’s only good outreach for the paper if it is readable and appeals to a bigger section of the audience. Also, this is exactly how we get trained to become better reviewers. So, I’ll say, reviewer #2, keep doing you. Maybe one day, I’ll be reviewer #2 myself. Until then, I’m happy to get to be good cop and also appear cool on my CV. (I swear, reviewers need more incentives).

As I say all of this, I anxiously await reviews for my own paper submission to the same conference. So here’s hoping I haven’t disappointed of reviewer #2 that much. And so the grind continues.

Meme courtesy

The NIPS experience: Newbie edition

Over the past week, I attended (and presented at) one of the biggest conferences in Machine Learning: Neural Information Processing Systems (NIPS) 2017 at Long Beach, California, and the experience was nothing short of exhilarating. There were a number of themes that I made note of, and one blog post is not enough to illustrate them all. So I’ll try to enforce some structural sparsity here to reduce the complexity of this text.

1. NIPS 2017 was humongous.

About 8000 people from academia and industry, thronging to the Long Beach Convention (epi)Center to talk about ground breaking research. It was chaotic. Took me an hour of standing in line to just get my registration badge!

2. Star studded. Both in terms of people and sponsor companies.

3. GANs were an audience favorite. You know something is the new buzz word when companies turn it into a catchphrase and print it on a t-shirt (yes, I did manage to get one for myself!).

You can’t find a better endorsement! There was an entire track of talks specially dedicated to recent advancements in GANs.

4. Bridging the gap between Theory and Practice.

Ali Rahimi’s talk before accepting the Test of Time award was something that was recommended for multiple viewings by multiple people to me. And the entire focus of the talk was about bettering the current brittle algorithmic frameworks, by theoretically analyzing the entire optimization problem, and not treating it like alchemy. There was also an entire workshop dedicated to this theme.

5. “Where’s the party tonight?”

I was asked by at least 5 different people if I was attending a certain sponsor after-party. I had actually got invites to most and RSVP-ed as well, but I found myself extremely exhausted (also, running out of mingling-with-random-strangers stamina). In fact there were people who were particularly interested in the parties and had no clue about what the next talk was about. I guess beyond a point, certain level of sponsor involvement could get worrisome.

6. “Do you want some swag?”

With so many sponsor booths, they had to try different strategies to attract the best minds around. Which meant, flashy sponsor swag (translation: goodies). You could collect enough t-shirts to get through 2 weeks without laundry. These companies certainly know their target, deprived grad students, well.

7. Orals, spotlights and posters.

So much information to gather! NIPS this year, had a record 678 accepted papers, with main themes being Algorithms, Theory, Optimization, Reinforcement Learning, Applications, GANs.

8. Even more orals and posters, in the form of numerous workshops. Also guest appearances from the Women in Machine Learning (WiML) community.

9. Debates and panels.

An interesting debate on the relevance of studying the interpretability problem, sparked a conversation on the various interpretations of the term itself, and whether the problem was motivated well enough, to begin with.

10. A free flow of ideas from every corner.

Some highlights were talks (that I managed to attend) by Bertsekas, Goodfellow, etc. Couldn’t attend some of the morning ones though! And of course, there was a lot to take away from several of the posters sessions. I think I also learnt how to sell an idea better, through my own poster presentation.

I think overall, it was a great learning experience and incredible exposure for a first-timer like me. Hopefully, I will get a chance to visit again! I’m also going to write a part 2 of my experience, which will focus more on some of the more technical ideas that caught my attention at NIPS 2017. Should make a good follow up read after this one! Watch out!

Optimization in Life

I’ve been doing a lot of optimization related work and courses, for my PhD, most notably in convex optimization and non-linear programming. They say that the best way to learn theory is to implement it in real life, and so I thought that it wouldn’t hurt to find ways to optimize… life… eh? On that optimistic enough thought, here we go:

  1. The steepest descent is not necessarily the fastest. A common thing that people do when they are in an unwanted situation is to do starkly opposite of what they were initially doing, i.e. -\nabla f(x). This seems to be a go-to solution for minimizing conflict. However, it is well known that to reach the point of minimum (conflict), steepest descent can take far more number of iterations than other gradient based methods. So take it easier, guys. Extremeness is not a smart option.
  2. When bogged down by multiple issues, solve one-problem at-a-time. Coordinate descent is an approach in which the objective (life’s problems) is minimized w.r.t a fixed coordinate at a time. It’s known for its simplicity of implementation.
  3. The apple does not fall far from the tree. So when Newton came up with his method for optimizing functions, the initial estimates did not fall far from the optimum, most notably in the case of quadratic functions. Turns out, it helps to approximate functions at each point with quadratic estimates, and then to minimize that quadratic estimate. Basically, take a problem and convert it into an easier sub-problem that has a known minimum. Move on to the next sub-problem. This fetches you the global optimum much faster.
  4. While positive definiteness is ideal, positive semi-definiteness is good too. If the Hessian of the function to be minimized is positive semi-definite, then the function is convex and can be minimized easily (its local optimum is the global optimum). So keep calm (and kinda positive) and minimize issues.
  5. Often when there are too many parameters to handle, we tend to overfit a fairly complicated model to our life. In such cases, it is a good idea to penalize over-complication by adding a regularization term. Regularization also helps in solving an ill-posed problem. If we tend to focus on only a specific set of problems, we forget other facets of life, which leads us into making poorer choices. The key is to find the right balance or trade-off.
  6. Some problems actually have closed-form or unique solutions. There’s just one possible answer which is apparent enough. In that scenario the optimal strategy should be to stop optimizing. Stop contemplating, just go-get-it!
  7. On a closing note, heuristically speaking, one would need to try out a bunch of optimizing techniques to find the optimal optimization technique.


To make this post even more meta, how optimal would it be if the moral of this post converged to this statement?