-
-
Notifications
You must be signed in to change notification settings - Fork 41
[PRE REVIEW]: Tesseract Core: Autodiff-native, self-documenting software components for Simulation Intelligence #8201
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:
|
Software report:
Commit count by author:
|
|
Paper file info:
✅ The paper includes a |
License info: ✅ License found: |
Five most similar historical JOSS papers: TensorFlow.jl: An Idiomatic Julia Front End for TensorFlow CoSApp: a Python library to create, simulate and design complex systems. TLViz: Visualising and analysing tensor decomposition models with Python giotto-deep: A Python Package for Topological Deep Learning flowTorch - a Python library for analysis and reduced-order modeling of fluid flows |
👋 @BoltzmannBrain - thanks for your submission. However, I don't think I really understand what the software here is, what it is used for, or who would use it. Is there something in the documentation or repo that walks through some type of a simple research use case? The paper currently is a little too abstract for me, and adding something more specific pointing to the documentation would be helpful. I suggest this because the paper is already too long, and adding more would not be a good fit for JOSS. In fact, if there's anything in the paper that can be removed in favor of pointing to the documentation or the repo, please do that as well. Additionally, and as a minor point in comparison, please see the JOSS example paper for how references that are directly addressed should be mentioned in the .md file. Please feel free to make changes to your .md file, then use the command |
Hi @danielskatz, thank you for the speedy follow-up and helpful comments! Yes we have tons of research use-cases:
We will address your other comments and push the updates ASAP this week. |
This comment has been minimized.
This comment has been minimized.
Five most similar historical JOSS papers: TensorFlow.jl: An Idiomatic Julia Front End for TensorFlow CoSApp: a Python library to create, simulate and design complex systems. Φ-ML: Intuitive Scientific Computing with Dimension Types for Jax, PyTorch, TensorFlow & NumPy TLViz: Visualising and analysing tensor decomposition models with Python flowTorch - a Python library for analysis and reduced-order modeling of fluid flows |
This comment has been minimized.
This comment has been minimized.
Hello @dionhaefner, here are the things you can ask me to do:
|
@editorialbot generate pdf |
Five most similar historical JOSS papers: TensorFlow.jl: An Idiomatic Julia Front End for TensorFlow CoSApp: a Python library to create, simulate and design complex systems. JAXbind: Bind any function to JAX Φ-ML: Intuitive Scientific Computing with Dimension Types for Jax, PyTorch, TensorFlow & NumPy SICOPOLIS-AD v2: tangent linear and adjoint modeling framework for ice sheet modeling enabled by automatic differentiation tool Tapenade |
@editorialbot check repository |
Software report:
Commit count by author:
|
Paper file info:
✅ The paper includes a |
License info: ✅ License found: |
@danielskatz Thanks for the feedback! I went ahead and added a section with more concrete example use cases to the "Statement of need", and deleted some other sections to make up for it – at least the paper didn't get even longer this way. Let us know in case you need anything else to elucidate potential use cases or make this a better fit for JOSS. |
This is useful. Could the paper text point to this?
I'm sorry, but when I look at that page, I don't see anything about scientific machine learning or differentiable physics. Machine learning is mentioned at the very top as a motivation, but there's nothing that makes this clear. And "physics" doesn't appear in that page at all. I think this is a case where the documentation makes a lot of assumptions about the reader and their knowledge.
|
Submitting author: @BoltzmannBrain (Alexander Lavin)
Repository: https://github.com/pasteurlabs/tesseract-core
Branch with paper.md (empty if default branch): joss
Version: v0.9.0
Editor: Pending
Reviewers: Pending
Managing EiC: Daniel S. Katz
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @BoltzmannBrain. Currently, there isn't a JOSS editor assigned to your paper.
@BoltzmannBrain 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: