-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PRE REVIEW]: DelayDiffEq: Generating Delay Differential Equation Solvers via Recursive Embedding of Ordinary Differential Equation Solvers #109
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post. For a list of things I can do to help you, just type:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
PDF failed to compile for issue #109 with the following error:
|
@whedon generate pdf from branch paper |
|
PDF failed to compile for issue #109 with the following error:
|
Strange, it worked locally (and with Github CI) by following the instructions of the template. Possibly a different ruby version? I'll try to fix it in the next few days. |
I'm not sure how to debug and test this issue locally. I can't reproduce it with the JuliaCon instructions and ruby script. I installed ruby 2.6.0 locally and |
Still haven't managed to reproduce this locally, is there really no simple way to run the build pipeline locally? Debugging with CI seems a bit suboptimal... However, I found https://github.com/openjournals/whedon/blob/92346a0773a4003bf0ef361b661dc2787f492936/lib/whedon/author.rb#L69-L70 and https://bugs.ruby-lang.org/issues/12451, so maybe that's the underlying issue. I tried to address that, let's see if the paper can be compiled now. |
@whedon generate pdf from branch paper |
|
PDF failed to compile for issue #109 with the following error:
|
OK, so the first issue is fixed. So what's the common approach here? Adding the LaTeX sty files to the repo? And is there a list with the LaTeX packages that are available when compiling with whedon? |
I found #79 (comment) - should mathtools be added to the list of available LaTeX packages, similar to openjournals/heroku-buildpack-tex#2, or should it be added to the repo? I'm also not really sure what would have to be added to the repo - it seems there is not mathtools.sty in https://www.ctan.org/tex-archive/macros/latex/contrib/mathtools? |
1 similar comment
The easiest solution is just to remove the dependence on |
I always use/load |
@whedon generate pdf from branch paper |
|
PDF failed to compile for issue #109 with the following error:
|
Well well, these LaTeX issues are a bit annoying - my feeling is that this could be improved a bit 😄 Even more so since the paper compiles just fine with standard TeXlive installations (as it was the case for the initial submission and all updates) and at least to me it is still unclear what exactly is supported and why (not). I guess the easiest solution to the latest error is to include the orcidlink.sty file. |
@whedon generate pdf from branch paper |
|
PDF failed to compile for issue #109 with the following error:
|
Just use the minimal set of packages. Do you really need all the extras? The bot uses a Docker image with a fixed set of packages. There's essentially zero free time on the editorial team to improve things. @vchuravy was looking at it... and from what I understand, it wasn't an enjoyable experience. If you have time, he can probably point you in the right direction. |
|
It seems the main culprit was the acknowledgement environment provided by |
@whedon generate pdf from branch paper |
|
Finally 🎉 @odow With some fixes of the |
🎉 dear god almighty. Thanks @devmotion for driving this. |
Hoorah. Any suggestions for reviewers? |
I can have a look but can't promise having enough time for a thorough review in March |
Yeap I'd be happy to review this! |
OK, @Datseris is now a reviewer |
@devmotion if you're happy to wait a while for @ranocha I can assign and start the review? Otherwise we can find someone else. |
I think @ranocha would be a good reviewer, so I'm happy to wait a while 🙂 |
OK, @ranocha is now a reviewer |
@whedon start review |
OK, I've started the review over in #125. |
Submitting author: @devmotion (David Widmann)
Repository: https://github.com/SciML/DelayDiffEq.jl
Version:
Editor: @odow
Reviewers: @Datseris, @ranocha
Managing EiC: Valentin Churavy
Author instructions
Thanks for submitting your paper to JCON @devmotion. Currently, there isn't an JCON editor assigned to your paper.
The author's suggestion for the handling editor is @carstenbauer.
@devmotion if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JCON and may be suitable for this submission (please start at the bottom of the list).
Editor instructions
The JCON submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:
The text was updated successfully, but these errors were encountered: