Skip to content
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]: BenchmarkDataNLP.jl: Synthetic Data Generation for NLP Benchmarking #7844

Open
editorialbot opened this issue Feb 25, 2025 · 7 comments
Assignees
Labels
Julia review TeX Track: 5 (DSAIS) Data Science, Artificial Intelligence, and Machine Learning

Comments

@editorialbot
Copy link
Collaborator

Submitting author: @mantzaris (Alexander V. Mantzaris)
Repository: https://github.com/mantzaris/BenchmarkDataNLP.jl
Branch with paper.md (empty if default branch): main
Version: v.1.0.0
Editor: @jromanowska
Reviewers: @oxinabox, @TheCedarPrince
Archive: Pending

Status

status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/f2b3e3efb0fd234665e864d64551e5d8"><img src="https://joss.theoj.org/papers/f2b3e3efb0fd234665e864d64551e5d8/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/f2b3e3efb0fd234665e864d64551e5d8/status.svg)](https://joss.theoj.org/papers/f2b3e3efb0fd234665e864d64551e5d8)

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

@oxinabox & @TheCedarPrince, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review.
First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @jromanowska 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

Checklists

@oxinabox, please create your checklist typing: @editorialbot generate my checklist

@TheCedarPrince, please create your checklist typing: @editorialbot generate my checklist

@editorialbot
Copy link
Collaborator Author

Hello humans, I'm @editorialbot, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

✅ OK DOIs

- 10.46298/arima.1956 is OK
- 10.1109/HPEC58863.2023.10363447 is OK

🟡 SKIP DOIs

- No DOI given, and none found for title: Applying natural language processing techniques to...
- No DOI given, and none found for title: Generalized context-free grammars

❌ MISSING DOIs

- None

❌ INVALID DOIs

- https://doi.org/10.1016/j.tcs.2016.05.030 is INVALID because of 'https://doi.org/' prefix

@editorialbot
Copy link
Collaborator Author

Software report:

github.com/AlDanial/cloc v 1.98  T=0.02 s (697.5 files/s, 108078.6 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Julia                            8            498            434           1391
Markdown                         3             46              0            102
YAML                             2              7              0             63
TeX                              1             10              0             41
TOML                             2              4              0             17
Text                             1              5              0             16
-------------------------------------------------------------------------------
SUM:                            17            570            434           1630
-------------------------------------------------------------------------------

Commit count by author:

    40	mantzaris
     4	a.v.mantzaris
     2	fan

@editorialbot
Copy link
Collaborator Author

Paper file info:

📄 Wordcount for paper.md is 706

✅ The paper includes a Statement of need section

@editorialbot
Copy link
Collaborator Author

License info:

✅ License found: MIT License (Valid open source OSI approved license)

@editorialbot
Copy link
Collaborator Author

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@jromanowska
Copy link

👋🏼 @mantzaris @oxinabox @TheCedarPrince, this is the review thread for the paper. All of our communications will happen here from now on.

As a reviewer, the first step is to create a checklist for your review by entering

@editorialbot generate my checklist

as the top of a new comment in this thread.

These checklists contain the JOSS requirements. As you go over the submission, please check any items that you feel have been satisfied. The first comment in this thread also contains links to the JOSS reviewer guidelines.

The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, the reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention openjournals/joss-reviews#7844 so that a link is created to this thread (and I can keep an eye on what is happening). Please also feel free to comment and ask questions on this thread. In my experience, it is better to post comments/questions/suggestions as you come across them instead of waiting until you've reviewed the entire package.

We aim for reviews to be completed within about 2-4 weeks. Please let me know if any of you require some more time. We can also use EditorialBot (our bot) to set automatic reminders if you know you'll be away for a known period.

I encourage you to over-communicate and let everyone know that you're on the task every now and then, instead of waiting several weeks to collect all your comments, questions, or suggestions.

Please feel free to ping me (@jromanowska) if you have any questions/concerns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Julia review TeX Track: 5 (DSAIS) Data Science, Artificial Intelligence, and Machine Learning
Projects
None yet
Development

No branches or pull requests

2 participants