-
-
Notifications
You must be signed in to change notification settings - Fork 41
[PRE REVIEW]: Decomposing Gaifman Structures #7687
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
Comments
Hello human, 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:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
Checking the BibTeX entries failed with the following error:
|
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: ✅ License found: |
Five most similar historical JOSS papers: PyDGN: a Python Library for Flexible and Reproducible Research on Deep Learning for Graphs CORA and LOGIGRAM: A Duo of Python Packages for Combinational Regularity Analysis (CORA) DAFSA: a Python library for Deterministic Acyclic Finite State Automata TLViz: Visualising and analysing tensor decomposition models with Python Clustergram: Visualization and diagnostics for cluster analysis |
👋 @balqui Could you explain this statement a bit? Why was the refactoring done and is any of the original code used directly in your work? Thanks.
|
Missatge de Chris Vernon ***@***.***> del dia dv., 17 de gen.
2025 a les 14:20:
👋 @balqui <https://github.com/balqui>
Could you explain this statement a bit? Why was the refactoring done and
is any of the original code used directly in your work? Thanks.
Author: Jose Luis Balcazar, ORCID 0000-0003-4248-4528, relying in large
parts on the functionality of code by Marie Ely Piceno
<https://github.com/balqui/labgaif>, although fully rewritten.
Sure. First, let me point out that Ely is also a coauthor of this
submission. As indicated in the paper, her original code was not really
usable by anyone else. It was developed hand-in-hand with the research
process constituting her PhD, of which I was the advisor, and was full of
dead ends, inefficiencies, deprecated code, and undocumented behavior.
Instead of cleaning it up, I decided to reconstruct it fully. A handful of
lines of her code (labgaif GitHub repo, MIT License) may remain in the
current submission, with her authorization, but no full function (or method
or class as the OO-structure is now different). Similarly, the third author
created a wholly different implementation of which no code remains at all
but her ideas were deemed worth of coauthorship; that was for her
graduation project of which I was also the advisor. All three coauthors
contributed nontrivially to the conceptual intuitions that support the
algorithmics implemented by the current code. The same three authors sign
the 2018 paper where these ideas were first proposed and the 2021 paper
where applications are described (both cited in the submission).
Thanks for your efforts on JOSS.
José.
Message ID: ***@***.***>
… |
@editorialbot invite @matthewfeickert as editor @balqui please reduce the word count of your paper to at or lower than 1000 words. Thank you. |
Invitation to edit this submission sent! |
@editorialbot assign @matthewfeickert as editor |
Assigned! @matthewfeickert is now the editor |
@balqui thanks for your submission to JOSS. Before I request any reviewer time to be spent on the submission though I'm going to ask you to reread the Submitting a paper to JOSS docs in detail as there are multiple problems with the submission that would result in it being automatically declined without large amounts of revisions by reviewers. It might be helpful for you to read the Review Criteria docs but at a glance your submission has:
Please address all of these issues within one week (by 2025-02-13) if you would like to continue with a review. My suggestion given the scope of work that would need to be done is that you instead withdraw your submission for now and resubmit in the future whenever you have had the time to carefully go through and prepare the project. That's totally fine and we would very much welcome a future submission from you if you chose to do so. |
@editorialbot query scope |
Submission flagged for editorial review. |
Understood, Matthew and Chris. We will follow the advice of withdrawing and possibly resubmitting as the issues raised require clearly more than one week to solve. Thanks for your help. José Luis Balcázar (@balqui) |
@editorialbot withdraw |
I'm sorry @balqui, I'm afraid I can't do that. That's something only eics are allowed to do. |
Sorry, I am told that I cannot withdraw through the editorial bot, and I cannot find on the submission page (which to me looks like https://joss.theoj.org/papers/2bc1b254b01c7202572d4d2d1dc07fb7) a way to withdraw. I do see a "paper actions" section with some text in it but no actual action available to perform. How should we do that? |
As the error message says, Editors-in-Chief (eics) can do this, as I will now. |
@editorialbot withdraw |
Paper withdrawn. |
Submitting author: @balqui (José Luis Balcázar)
Repository: https://github.com/balqui/degais/
Branch with paper.md (empty if default branch):
Version: V1.4
Editor: @matthewfeickert
Reviewers: Pending
Managing EiC: Chris Vernon
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @balqui. Currently, there isn't a JOSS editor assigned to your paper.
@balqui if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: