joss
joss copied to clipboard
Make .tex source of paper available
As mentioned in openjournals/joss-reviews#24, it would be great to make the .tex source of the compiled paper available (maybe it is and I'm just blind...) to enable things like uploading the paper to arXiv.
Thanks for making all this work!
We don't actually persist this anywhere currently but we could. We generate the PDF using this command: https://github.com/openjournals/whedon/blob/master/lib/whedon/processor.rb#L152-L171, the Pandoc tex template is here https://github.com/openjournals/whedon/blob/master/resources/latex.template
I might be missing something, but what's the reason for uploading a JOSS paper to arXiv? The PDF generated by JOSS is citable with a DOI, and should persist.
I was wondering about that too. Is there a reason a very short arXiv paper with an arXiv URL is better than a JOSS paper that has a DOI and is indexed?
@arfon: Yeah. I ran the pandoc command with output paper.tex
and that worked but it might be convenient to add that as part of the build process. Your call!
@kyleniemeyer: In astronomy, papers pretty much don't exist unless they're on arXiv so I wanted to post it there to make it available to the community (and advertise JOSS 😄).
Note: people would cite JOSS but they would find the paper through arXiv.
Gotcha, sounds good.
@dfm - I'm just revisiting this. What would you need for an arXiv submission - would it simply be the paper.md
file compiled into a paper.tex
file? We could certainly add this as an output and commit it to the joss-papers
repo: https://github.com/openjournals/joss-papers/tree/master/joss.00024
@arfon I'm looking at this as well for the paper I'm submitting.
We'd need a paper.tex
file along with a way to get the .sty
file to get the styling of the generated arxiv submission to match the JOSS internal styling. That's not necessary of course, I could just use a regular article document style, but that makes the final paper on the arxiv look less nice and professional.
Here's the details about how to upload a LaTeX document to the arxiv: https://arxiv.org/help/submit_tex
… and also the .bbl file, if that is generated from the .bib — arXiv will process this and add the bibliography.
Max Ogden has a good write up here https://gist.github.com/maxogden/97190db73ac19fc6c1d9beee1a6e4fc8 of how to do this.
I think you need to modify the Whedon pandoc command to generate LaTeX as an alternative output. I'm not sure if that will produce .bbl
files but it's a start.
This may not be the best place to ask, but: I was just wondering if anyone has successfully submitted a JOSS paper to arXiv? I tried submitting my paper to the arXiv today, but just got this email from them:
Dear arXiv user,
arXiv only accepts complete, self-contained, research article submissions in a format appropriate for publication in a conventional journal.
Your submission did not appear to be complete and, as a result, has been removed. Please feel free to resubmit a complete paper.
For more information, see: ref: http://arxiv.org/help/primer ref: http://arxiv.org/help/moderation
Regards, arXiv admin
As a side note: I created my .tex source file using this Makefile.
It looks like @dfm ran into similar issues back in 2016, since corner.py never got an arxiv submission as far as I can see:
http://adsabs.harvard.edu/abs/2016JOSS....1...24F
Someone would have to contact arxiv to be sure, but my guess is that the 1-2 page typical JOSS paper is not something that arxiv is likely to consider sufficiently weighty/lengthy.
@ngoldbaum yeah, I'd noticed that for corner.py too.
@danielskatz I'd guess so. It's a shame that arXiv won't accept JOSS papers, but I suppose it's not too much of a big deal. As @dfm mentioned before, it would be nice if they would accept them to advertise and provide more exposure for JOSS, but it's probably not worth pushing too hard.
I'm planning to submit a more substantial paper (~10 pages typeset) this week or next week. I will comment here about whether it gets through the arxiv moderation.
I asked Steinn Sigurdsson (the arxiv scientific director) on twitter about this. He pointed me to the moderation policy which notes:
Abstract-only submissions, presentations, book announcements, book reviews, submissions without references, calls for papers, or advertisements may be removed.
So I guess that's the issue here. I expect a longer paper would make it past the moderators.
But ... that list of criteria doesn't seem to cover JOSS-style papers, IMHO. Maybe arxiv would change their policy if petitioned and made aware that JOSS papers really are typically short yet complete?
@mhucka - I've appealed my arXiv rejection with the following email:
Dear arXiv-moderation,
My submission submit/XXXXXXX was rejected and I presume this was due to the paper being very short. This is a paper that has been peer reviewed and accepted by the Journal of Open Source Software (JOSS) http://joss.theoj.org/ - which, although not a conventional journal, is becoming quite widely used, and may in the future be partnering with the American Astronomical Society. Typically, papers for this journal are very short, and as such what is included in the arXiv abstract field may represent the bulk of the paper, but they are complete and reviewed.
Would it be possible to reconsider this rejection for this article, and look at allowing JOSS papers for submission in the future?
Regards,
Matt Pitkin
I'll let you know what response I get.
My paper got posted: https://arxiv.org/abs/1806.02417
I ended up using @mattpitkin's makefile, which was very useful (and could probably be integrated into the JOSS submission instructions).
I'm happy to report that the moderators accepted my appeal and my JOSS paper is now on arXiv (as is another JOSS paper I'm author on :smile:).
In case this is any use to anyone, I submitted the .pdf of the JOSS paper, and appealed to arXiv to let me use this for the submission rather than the LaTeX files, due to the standard JOSS procedure not giving access to those files. They accepted my appeal and so I uploaded the .pdf to arXiv
Has anything changed or is the above Makefile still the recommended workaround? I'd prefer to submit LaTeX to arXiv rather than the PDF, if possible.
Nothing has changed sorry.
Simply providing the .tex
file would be great. I was successful with using the Makefile, but it is slightly outdated and this overall felt like an unneccesary exercise.
FYI: My preprint got rejected even after appealing with a reference to arxiv's policy on short works.
I was able to reproduce my JOSS paper using latex. It took some tinkering, but they accepted the latex version. https://arxiv.org/abs/2010.03031v1
For those who continue to stumble across this:
@rodluger and I worked out yet another way to generate the .tex file for a JOSS manuscript using GitHub actions. I'm sure it would be possible to use the official action, but the way that we're doing it is (assuming the manuscript is in a directory called joss
):
jobs:
tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: TeX
uses: docker://openjournals/paperdraft:latest
with:
args: joss/paper.md --to=latex --output=paper.tex
env:
GIT_SHA: $GITHUB_SHA
JOURNAL: joss
- name: PDF
uses: docker://openjournals/paperdraft:latest
with:
args: joss/paper.md
env:
GIT_SHA: $GITHUB_SHA
JOURNAL: joss
- uses: actions/upload-artifact@v2
with:
path: joss
See it in action here: https://github.com/rodluger/starry_process
The above action worked and created a .tex file for me, thanks a bunch @dfm and @rodluger! I was curious if we can somehow apply this workflow to the most up-to-date draft in the review process?
@tarleb – might be good to adapt this Action to optionally include a .tex output https://github.com/openjournals/openjournals-draft-action ?
I was curious if we can somehow apply this workflow to the most up-to-date draft in the review process?
@ashleychontos – the content in the joss-papers
repo you link to above is mostly for operating the journal so I don't really want to add .tex outputs there. That said, I'm definitely interested in making it easier for authors to generate a .tex version of their paper for their own needs.
@arfon oh whoops, yeah that definitely makes sense. Like many others in this thread, I was just having issues uploading the current draft to arXiv. I imagine adding that action would definitely be helpful for others in the future