fastglow

fastglow t1_j0zqs33 wrote

It sounds like your issues are more about PyTorch than Python itself. The need for vectorization is not specific to a language, though some libraries make it easier than others. If you want automatic vectorization, have a look at Jax, which has grown tremendously in the past couple years.

15

fastglow t1_iyeylms wrote

I agree with your concerns. ICLR's reviewer's guide states that "During the discussion phase, reviewers, authors and area chairs engage in asynchronous discussion, and authors are allowed to revise their submissions to address concerns that arise." Note the word asynchronous. I think everything should be done on OpenReview, not through outside, off-the-record discussions. I would express my concerns to the AC, and perhaps to the PCs if necessary.

23

fastglow t1_iusllds wrote

I see it mainly as one of my responsibilities as a researcher: I submit papers, so I should also review papers. If not us, then who?

But I think it does benefit me in that I have gotten better at distinguishing good research ideas from bad ones, and good experimental protocols from bad ones, good reporting from bad reporting, etc.

39

fastglow t1_itlyz8a wrote

SBert is for comparing sentences/phrases. No reason to use that over a regular transformer encoder-decoder for language modelling, and getting that to process 2000 tokens in less than 4 seconds would be challenging without efficiency-augmenting methods like quantization, pruning, distillation, etc.

2