-
-
Notifications
You must be signed in to change notification settings - Fork 36
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]: fABBA: A Python library for the fast symbolic approximation of time series #6294
Comments
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:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
Wordcount for |
|
👋🏼 @chenxinye @Karangupta1994 @allie-tatarian 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
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 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 of time. Please feel free to ping me (@lrnv) if you have any questions/concerns. |
@lrnv Thanks for the arrangement! |
Hi all, I'm not sure if this is the best place to this but I don't think it makes sense to post this as an issue because I think it's a problem on my end. When I try to use fABBA, I am consistently getting a "This installation is not using Cython" warning even though I do have Cython installed. @chenxinye is this something you have seen before? I cannot for the life of me figure out how to troubleshoot this. The fABBA library is still mostly working for me, but sometimes I get different outputs than the examples. |
@allie-tatarian Different output than the examples surely looks like an issue (unless the examples are explicitely random ?). Problem in the installation can also be reported as issues. @Karangupta1994 & @allie-tatarian, to guide you in the review, there is an automated checklist that you have to produce by commenting in this thread :
I think the standard checkpionts includes stuff such as the need for descriptive installation guidelines if some requirements are "non-standard". More generally, this is a very good place to discuss this thread is here for that purpose |
Hi @lrnv, I just sorted the doi in bib, many thanks! |
I just checked, found some output in README.md is consistent with the real output of software. I now corrected it! Please check. |
Thanks for pointing the issues. For the Cython issue, @lrnv @allie-tatarian, some users reported before, most of them have this issue since their machine have firewall or without VC++ installed. Could you please provide your machine specifications for me? I checked my three machines, all worked properly. I guess you use Windows without VC++ installed? |
Thanks @chenxinye, I do have VC++ installed, so I think the issue is with the firewall on my work computer. I will try everything again on my personal computer tomorrow and report back! |
You would need to install fABBA using:
|
Thanks @chenxinye, like I mentioned in the issue I did install using pip. It is working fine on my personal computer, so I think the issue is that the security on my work computer is not meshing well with cython. I wonder if it's worth putting a note about that in the docs for fABBA - I do think the issue is with cython, not fABBA, but looking around online it looks like I'm not the only one who has run into this issue and I haven't seen anyone spell out the solution as concisely as you did here! |
Hi @allie-tatarian Thanks for your suggestions! That's really a good idea, I will put a note there! |
@allie-tatarian Just added in https://fabba.readthedocs.io/en/latest/quickstart.html ! Many thanks |
Review checklist for @allie-tatarianConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
I did run into some issues when I was trying out the JABBA package, trying to follow the examples both in the README and the docs, but then I realized that JABBA isn't in the paper so I did the peer review following the functionality that is listed in the paper. @lrnv can you let me know if you think that is off-base? |
@editorialbot check references |
|
@editorialbot recommend-accept |
|
|
👋 @openjournals/dsais-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 openjournals/joss-papers#5181, then you can now move forward with accepting the submission by compiling again with the command |
Hi @lrnv I would need to add some comments in Acknowledgement, can I? ``Stefan Güttel acknowledges a Royal Society Industry Fellowship IF/R1/231032. Xinye Chen is supported by the European Union (ERC, inEXASCALE, 101075632). Views and opinions expressed are those of the authors only and do not necessarily reflect those of the European Union or the European Research Council. Neither the European Union nor the granting authority can be held responsible for them.'' Can I? |
Yes you can of course. |
Just regenerate the paper after that, and I'll re-recomand-accept |
Hi @lrnv We just proofreaded, now it is okay for us. Many thanks |
@editorialbot generate pdf |
@editorialbot recomand-accept |
I'm sorry human, I don't understand that. You can see what commands I support by typing:
|
@editorialbot recommend-accept |
|
|
👋 @openjournals/dsais-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 openjournals/joss-papers#5187, then you can now move forward with accepting the submission by compiling again with the command |
@editorialbot accept |
|
Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository. If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file. You can copy the contents for your CITATION.cff file here: CITATION.cff
If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation. |
🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘 |
🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨 Here's what you must now do:
Any issues? Notify your editorial technical team... |
@Karangupta1994, @allie-tatarian – many thanks for your reviews here and to @lrnv for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨ @chenxinye – your paper is now accepted and published in JOSS ⚡🚀💥 |
🎉🎉🎉 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! The Journal of Open Source Software 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:
|
Submitting author: @chenxinye (Xinye Chen)
Repository: https://github.com/nla-group/fABBA
Branch with paper.md (empty if default branch): master
Version: 1.2.1
Editor: @lrnv
Reviewers: @Karangupta1994, @allie-tatarian
Archive: 10.5281/zenodo.10885652
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
@Karangupta1994 & @allie-tatarian, 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:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @lrnv 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
📝 Checklist for @allie-tatarian
📝 Checklist for @Karangupta1994
The text was updated successfully, but these errors were encountered: