-
-
Notifications
You must be signed in to change notification settings - Fork 38
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]: Curio: Unsupervised Topic Modeling in Swift #7597
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:
|
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: ldaPrototype: A method in R to get a Prototype of multiple Latent Dirichlet Allocations corporaexplorer: An R package for dynamic exploration of text collections rtweet: Collecting and analyzing Twitter data textnets: A Python package for text analysis with networks ADaPT-ML: A Data Programming Template for Machine Learning |
@editorialbot invite @jbytecode as editor 👋 @jbytecode do you think you can take this one on as editor? |
Invitation to edit this submission sent! |
Hi @crvernon, My latest experiences with Swift on Linux were terrible. I don't even know if every single package created on macOS can run and can be tested on other operating systems. @JimWallace - Have you performed tests in Windows and Linux machines? If it is not so, it could be a hard constraint in finding suitable reviewers. This would also be a major obstacle to the widespread adoption of the software by the entire community. The second thing is that the working with GitLab is the other constraint, one of the reviewers of my other submission was struggling with sending pull requests. But we can resolve this difficulty. I'm now waiting a response from our author. |
tldr; This is not intended to run on Windows or Linux. Windows and Linux support is getting better in Swift, but it's not there yet IMO. Some of the code works cross-platform, and I had a linux CI/CD up and running for quite a while. It's not currently active because I shifted focus towards Apple-specific hardware. Cross-platform BLAS, etc. is not yet mature in Swift. So, unfortunately, a lot of the code depends on MLX, which is M-series chip only. There are some really nice benefits from this in terms of edge computing, supporting most Apple laptops, but indeed I can see how this might make it harder to find reviewers. I would, however, argue that it's possibly a strength in terms of adoption, since this is providing somewhat unique functionality via the state-of-the-art (and also rapidly evolving) MLX framework. I'm expecting to build a bunch of new features using MLX's LLM support next year, and was hoping that might be of interest to other folks. I'd spoken with some co-authors about sending this over to GitHub, too. My institution provides some really nice gitlab support, so that hasn't been a priority. |
@editorialbot assign me as editor |
Assigned! @jbytecode is now the editor |
@JimWallace - Okay, thank you for the clarification. We don't have an issue with platform independence now and we can move forward. I'm the handling editor of this submission. First, we'll try to find suitable reviewers. The editorialbot suggests us some similar publications. We can consider their authors. (Given in the post #7597 (comment)). The other tool is the reviewer search, given in the link https://reviewers.joss.theoj.org/lookup. You can use this tool to filter some suitable reviewers. In the first stage, whether using the suggestions and lists or not, I'm asking you to suggest suitable reviewers. If you provide their GitHub accounts, please don't use the Do you have any suggestions for suitable reviewers? |
@JimWallace - While we are searching suitable reviewers, could you please fix the missing DOI issue stated in the report: #7597 (comment) |
Thanks, rtweet corporaexplorer both look like similar projects, and I'd expect they'd be a good way to find reviewers. I'd point to either those authors, or the folks that reviewed those projects as suitable. I believe that I've fixed the DOI issue. |
@editorialbot check references |
|
@editorialbot generate pdf |
Five most similar historical JOSS papers: ldaPrototype: A method in R to get a Prototype of multiple Latent Dirichlet Allocations corporaexplorer: An R package for dynamic exploration of text collections rtweet: Collecting and analyzing Twitter data textnets: A Python package for text analysis with networks ADaPT-ML: A Data Programming Template for Machine Learning |
👋👋👋 Dear @mkearney, @kgjerde 👋👋👋 Would you be willing to assist in reviewing this submission for JOSS (Journal of Open Source Software)? JOSS publishes articles about open source research software. The submission I'd like you to review is titled: [PRE REVIEW]: Curio: Unsupervised Topic Modeling in Swift You can find more information at the top of this Github issue (#7597). The review process at JOSS is unique: it takes place in a GitHub issue, is open, and author-reviewer-editor conversations are encouraged. If you have any questions please let me know. This is the pre-review issue. After setting at least 2 reviewers we will start the review process in a separate thread. In that thread, there will be 23 check items for each single reviewer. Thank you in advance! |
Submitting author: @JimWallace (James R. Wallace)
Repository: https://git.uwaterloo.ca/jrwallace/curio
Branch with paper.md (empty if default branch):
Version: 0.0.10
Editor: @jbytecode
Reviewers: Pending
Managing EiC: Chris Vernon
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @JimWallace. Currently, there isn't a JOSS editor assigned to your paper.
@JimWallace 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: