-
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]: FlowFPX: Nimble Tools for Debugging Floating-Point Exceptions #135
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:
|
Failed to discover a |
Wordcount for |
|
Failed to discover a valid open source license. |
PDF failed to compile for issue #135 with the following error:
|
|
@whedon assign @lucaferranti as editor |
OK, the editor is @lucaferranti |
HI @ashton314, 👋 thank you for the submission. I will be your editor and will start looking for reviewers. Meanwhile, it seems the latex compilation is failing for your paper. Would be good if you could look into it and try to fix it. Note also that there seem to be a few missing DOIs. If you have any questions, do not hesitate in letting me know. |
looking at the error
it seems like a missing library file from the repository |
Hi Luca! Thanks for helping me out with this!
I think |
DOIs:
|
@whedon commands |
Here are some things you can ask me to do:
|
@whedon generate pdf |
PDF failed to compile for issue #135 with the following error:
|
@whedon generate pdf |
PDF failed to compile for issue #135 with the following error:
|
@whedon generate pdf |
PDF failed to compile for issue #135 with the following error:
|
Alright, @lucaferranti I'm a little stuck on this: I'm not sure what this error is saying. Have you seen this before? |
The references check is not perfect and can have some false-positives sometimes (like in this case). Great that you double-checked! If you find no DOI, it's ok to leave it this way.
ouch, those can be a bit challenging sometimes. are you able to compile the paper locally with I have not seen that specific error before, but it seems to indicate that some file (maybe some font) is missing. Googling your error, I found this: https://www.mrunix.de/forums/showthread.php?61988-pdflatex-psyr-und-pcrr7t-not-found (discussion is in German unfortunately, but google translate apparently can translate the page pretty well), which seems to indeed to refer to some missing fonts. You don't import many packages in the paper \usepackage{amsmath}
\usepackage{cleveref}
\usepackage{microtype}
\usepackage{pifont} and Here a quick debugging I could get done on Friday night, hopefully it helps. Let me know how this proceeds. :) |
Well, it was very helpful with the other two missing DOIs that it found! I can build the paper locally with (I actually speak German, so that page was very helpful! :) |
Looks like the Do you know of a way to add fonts? I suppose I could just drop the font file in the repo but that seems a little… overkill. I don't really like the default fonts anyway… I'd love it if I could use JuliaMono for the code samples—it'd be appropriate, no? |
@editorialbot commands |
Hello @arfon, here are the things you can ask me to do:
|
@editorialbot generate pdf |
I should maybe also point out that this submission has a bit of a peculiar structure, in the sense that the paper is not a |
@lucaferranti - it looks like the migration of all of the review issues only happened for the ones under active review (i.e., not pre-reviews) so I think we need @xuanxu to re-run his script for the issues like this one as the metadata structure at the top of the issue is currently incorrect. |
cool, thank you for the help in debugging! |
@editorialbot generate pdf |
@ashton314 new infra ready and paper compilation working 🎉 It seems the paper is missing hte references, could you look into it |
Hi @JeffreySarnoff 👋 , would you be interested in reviewing this submission for the JuliaCon proceedings? You can find reviewer instructions here and you are of course also welcome to ask any questions you may have. |
1 similar comment
Hi @JeffreySarnoff 👋 , would you be interested in reviewing this submission for the JuliaCon proceedings? You can find reviewer instructions here and you are of course also welcome to ask any questions you may have. |
Hi @oscardssmith 👋 , would you be interested in reviewing this submission for the JuliaCon proceedings? You can find reviewer instructions here and you are of course also welcome to ask any questions you may have. |
@editorialbot generate pdf |
Thanks everybody + robot, the PDF looks great now! |
This is nice work, and much appreciated. With regard to "8-bit formats are on the rise", please consider adding this reference: |
@JeffreySarnoff , does this mean you are interested in reviewing this submission? This issue is at the moment a pre-review, once I find two reviewers, I will start a review issue, where reviewers will have a checklist of things to check and can leave feedback. Reviewing for JuliaCon proceedings is in general more lightweight (and enjoyable) than normal academic reviews. :) |
sure |
@editorialbot add @JeffreySarnoff as reviewer |
@JeffreySarnoff added to the reviewers list! |
Thanks Jeff, review will start once I find a second reviewer |
ok .. let me know
…On Thu, Apr 11, 2024 at 9:48 AM Luca Ferranti ***@***.***> wrote:
Thanks Jeff, review will start once I find a second reviewer
—
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM2VRTI36ILESXN2YFO6RDY42IDPAVCNFSM6AAAAAA6SWKNBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBZG4ZTMMZSGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Found a second reviewer! 🎉 |
@editorialbot add @dpsanders as reviewer |
@dpsanders added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #148. |
Submitting author: @ashton314 (Ashton Wiersdorf)
Repository: https://github.com/utahplt/juliacon2023-paper
Branch with paper.md (empty if default branch):
Version:
Editor: @lucaferranti
Reviewers: @JeffreySarnoff, @dpsanders
Managing EiC: Mathieu Besançon
Author instructions
Thanks for submitting your paper to JCON @ashton314. Currently, there isn't an JCON editor assigned to your paper.
The author's suggestion for the handling editor is @lucaferranti.
@ashton314 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: