Submitting author: @glouppe (Gilles Louppe)
Repository: https://github.com/diana-hep/carl
Version: v0.2
Editor: @arfon
Reviewer: @betatim
Archive:
Status badge code:
HTML: <a href="http://joss.theoj.org/papers/26a9ffd9e7b98b1911d89d2ceb268f37"><img src="http://joss.theoj.org/papers/26a9ffd9e7b98b1911d89d2ceb268f37/status.svg"></a>
Markdown: [](http://joss.theoj.org/papers/26a9ffd9e7b98b1911d89d2ceb268f37)
[x] Archive: Does the software archive resolve?
[x] Installation: Does installation proceed as outlined in the documentation?
[ ] Performance: Have the performance claims of the software been confirmed?
[x] A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is? diana-hep/carl#53
[x] Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support diana-hep/carl#53
[x] Authors: Does the paper.md file include a list of authors with their affiliations?
Hi @glouppe. Many thanks for submitting to JOSS!
The next step is to look for a couple of reviewers - if you have any suggestions please add them here. :rocket:
@jakevdp - this do you have any suggestions?
maybe @dfm @betatim
Compiled paper PDF: paper.pdf
Thanks @whedon would be nice if arxiv showed up in bib. should we edit bib or change style for latex?
@cranmer This is the command that we're running to compile from Markdown to PDF: https://github.com/openjournals/whedon/blob/master/lib/whedon/processor.rb#L64 and this is the latex template: https://github.com/openjournals/whedon/blob/master/resources/latex.template
Any suggestions/modifications that would make arXiv show up very welcome 馃槃
As a reviewer should I do things beyond what is listed in the initial comment on this PR or is that it? If it is only those questions I can review this and use this opportunity to declare that I am a good friend of @glouppe but don't think this creates a conflict of interest.
If it is only those questions I can review this and use this opportunity to declare that I am a good friend of @glouppe but don't think this creates a conflict of interest.
Thanks for the heads up.
@betatim - basically we just need you to work through the checklist under Reviewer questions. If anything isn't clear please shout.
Also, there are some additional notes here (http://joss.theoj.org/about#reviewer_guidelines) but the review checklist should represent these guidelines.
Also, thanks so much for helping out!
UI question: how do I tick off things from the list? I think technically it is impossible to organise for me to be able to edit @whedon's comment. Had a scan around openjournals/whedon to try and find the raw MD but couldn't find it sad 馃惣.
edit: should all be in the first comment now
A few "trivial" comments are included inline. I haven't yet tried to answer the "functionality" questions.
re: statement of need in the PDF. It states "support inference in the likelihood-free setup, including density ratio estimation algorithms, parameterized supervised learning and calibration procedures". This could be improved by stating a few concrete problems, that your average researcher can recognise as problems they have, to which it is the solution. Right now I think you have to already know that carl can solve your problem to realise that it solves your problem.
The first paragraph of the PDF is a bit longer than what is in the README so I would copy/sync them once a few specific problems are added to it.
Otherwise everything looked good to me.
Thanks Tim! Changes proposed are https://github.com/diana-hep/carl/pull/53
Note: this back and forth between two github repos is not the most convenient :s :hamster:
Thanks Tim
UI question: how do I tick off things from the list? I think technically it is impossible to organise for me to be able to edit @whedon's comment. Had a scan around openjournals/whedon to try and find the raw MD but couldn't find it sad 馃惣.
@betatim - this is great point (that I didn't consider until now) - you need to be able to edit the issue too :-) I've added you to the joss-reviewers team which means you should be able to update the original issue.
Archive: Does the software archive resolve? Comment: see openjournals/whedon#1
This should should be fixed :soon:
Also, thanks for the rapid review :zap:
I've moved everything to the first comment. Most of the missing 鈽戯笍 are being dealt with in diana-hep/carl#53. Then there is the missing DOI in the generated PDF, do you take care of that @arfon?
Then there is the missing DOI in the generated PDF, do you take care of that @arfon?
Yep, tracking that in https://github.com/openjournals/joss/issues/56
I made further changes at https://github.com/diana-hep/carl/pull/53 (now merged). Is it possible to regenerate the PDF?
Updated paper PDF: paper.pdf
I don't see what the default bib style is in the wehedon resources:
but it looks like \bibliographystyle{utphys} might give a nice format for the arxiv link in the reference
http://tex.stackexchange.com/questions/243636/mendeley-and-arxiv-citation-style
Updated paper PDF: paper.pdf (now including the archive DOI and software repository address)
Installing works, automated tests pass, and ran some of the examples.
There are no performance claims (as in runs faster than X) so I don't think that reviewer question applies.
Only outstanding issue is rendering of references in the pdf.
@betatim - awesome thanks.
Only outstanding issue is rendering of references in the pdf.
@cranmer @betatim how do you feel about this rendering? paper.pdf
I've not managed to get the utphys biblio-style working but have managed to format the reference more generically to get the arXiv URL included:
@article{Cranmer:2015-llr,
author = "Cranmer, Kyle and Pavez, Juan and Louppe, Gilles",
title = "{Approximating Likelihood Ratios with Calibrated
Discriminative Classifiers}",
eprinttype = {arxiv},
version = {2},
eprint = {http://arxiv.org/abs/1506.02169v2},
url = {http://arxiv.org/abs/1506.02169v2},
date = {2016-03-18},
}
LGTM. I use the arXiv ID/DOI as a simple way to find the article in google, if you directly link me there even better (appeals to the efficient German in me)
Sorry I missed this earlier. LGTM too.
Ok then I think we're done here. Congrats @glouppe and @cranmer on our first accepted paper!
I'll finish up the editorial pieces this evening.
馃殌
Woo hoo!
We can provide a testimonial on the review process if you want.
Congratulations to you and the JOSS team. 馃帀
Great, thank you all :)
Whoop! 馃弫
Our work here is done, closing the issue.
Actually, where do we click to toggle the badge from under review to published?
Actually, where do we click to toggle the badge from under review to published?
@betatim - I have to do this (for now).
I'm so excited!
This is now accepted and live on JOSS!
It seems like the reference is still broken - there's no DOI or URL or way to know where the reference was published or is available
It seems like the reference is still broken - there's no DOI or URL or way to know where the reference was published or is available
Which reference sorry?
Compare https://github.com/openjournals/joss-papers/blob/master/joss.00011/10.21105.joss.00011.pdf (from the journal page) to the last PDF you posted in this issue. The only reference in the PDF has a link to the arxiv in the version you posted here but not in the journal version
Compare https://github.com/openjournals/joss-papers/blob/master/joss.00011/10.21105.joss.00011.pdf (from the journal page) to the last PDF you posted in this issue. The only reference in the PDF has a link to the arxiv in the version you posted here but not in the journal version
Gotcha. Not sure what happened there. Will investigate.
OK, this is fixed in the online PDF now. The PR to fix the bibtex is here: https://github.com/diana-hep/carl/pull/56