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
[REVIEW]: Extending JumpProcess.jl for fast point process simulation with time-varying intensities #133
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @gdalle it looks like you're currently assigned to review this paper 🎉. 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. ⭐ Important ⭐ If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/JuliaCon/proceedings-review) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews 😿 To fix this do the following two things:
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:
|
@whedon generate pdf from branch juliacon |
|
PDF failed to compile for issue #133 with the following error:
|
|
@whedon generate pdf from branch juliacon2023 |
|
PDF failed to compile for issue #133 with the following error:
|
there we go |
thought we'd never get there 🤣 |
same 😬 |
OK, @mschauer is now a reviewer |
Disclaimer: I am collaborating with Chris on related topics, @matbesancon and I discussed shortly and decided that I will accept this review request. |
👋 @gdalle, please update us on how your review is going (this is an automated reminder). |
Can you turn on line numbers? |
Here is the paper with line numbers to facilitate your review: paper.pdf. Hope the review is going well. Thanks for doing it! |
I'm sorry I was completely swamped lately. I'm gonna try to take a first look tomorrow |
|
|
@editorialbot recommend-accept |
|
|
@matbesancon @lucaferranti any chance the CLI issues around publishing the paper in the official proceedings page have already been resolved? Our paper is not yet listed in the proceedings page, but there is a new paper that has been published 4 days ago. |
The main issue is that while the paper is not listed in the JuliaCon proceedings webpage it becomes harder to discover it. For instance, it is not listed in Google Scholar. |
@editorialbot recommend-accept |
1 similar comment
@editorialbot recommend-accept |
|
|
@editorialbot recommend-accept |
|
|
👋 @JuliaCon/jcon-eics, this paper is ready to be accepted and published. Check final proof 👉📄 Download article If the paper PDF and the deposit XML files look good in JuliaCon/proceedings-papers#88, then you can now move forward with accepting the submission by compiling again with the command |
@gzagatti this is now fixed! Long story short, since Now everything works! I'll let @matbesancon pull the final trigger to accept the paper, since he's the editor in charge here |
Thanks a lot! |
@editorialbot accept |
|
🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JCON! 🚨🚨🚨 Here's what you must now do:
Any issues? Notify your editorial technical team... |
🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉 If you would like to include a link to your paper from your README use the following code snippets:
This is how it will look in your documentation: We need your help! JuliaCon Proceedings is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:
|
Awesome thanks for all involved in this thread! I am really happy to have the paper finally published! One minor comment. The |
Submitting author: @gzagatti (Guilherme Augusto Zagatti)
Repository: https://github.com/SciML/JumpProcesses.jl
Branch with paper.md (empty if default branch): juliacon2023
Version: v9.9
Editor: @matbesancon
Reviewers: @gdalle
Archive: 10.5281/zenodo.10786561
Status
Status badge code:
Reviewers and authors:
Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)
Reviewer instructions & questions
@gdalle, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @matbesancon know.
✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨
Review checklist for @gdalle
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Paper format
paper.tex
file include a list of authors with their affiliations?Content
The text was updated successfully, but these errors were encountered: