Skip to content

[REVIEW]: Teaspoon: A Python Package for Topological Signal Processing #7243

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

Closed
editorialbot opened this issue Sep 18, 2024 · 72 comments
Closed
Assignees
Labels
accepted published Papers published in JOSS recommend-accept Papers recommended for acceptance in JOSS. review Track: 7 (CSISM) Computer science, Information Science, and Mathematics

Comments

@editorialbot
Copy link
Collaborator

editorialbot commented Sep 18, 2024

Submitting author: @lizliz (Elizabeth Munch)
Repository: https://github.com/TeaspoonTDA/teaspoon
Branch with paper.md (empty if default branch): joss-paper
Version: v1.5.23
Editor: @hugoledoux
Reviewers: @yossibokorbleile, @EduPH
Archive: 10.5281/zenodo.14989806

Status

status

Status badge code:

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

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

@yossibokorbleile & @EduPH, 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 @hugoledoux 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 @yossibokorbleile

📝 Checklist for @EduPH

@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

Software report:

github.com/AlDanial/cloc v 1.90  T=0.27 s (925.6 files/s, 286646.2 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
HTML                            91           5458            360          34440
Python                          60           3399           4221           7637
SVG                              4              1              1           4223
reStructuredText                48           1086            624           2410
Jupyter Notebook                12              0           7246           2085
CSS                              7            224             68           1019
JavaScript                      12            131            221            880
TeX                              2             67              1            652
YAML                             4             10             29            360
Markdown                         8            113              0            348
CSV                              1              0              0            300
TOML                             1              6              0             51
make                             1             14              9             35
-------------------------------------------------------------------------------
SUM:                           251          10509          12780          54440
-------------------------------------------------------------------------------

Commit count by author:

   119	Liz Munch
    62	danielle_barnes
    47	maxchumley
    43	EGR\myersau3
    25	Sarah Tymochko
    24	Firas Khasawneh
    23	Sunia Tanweer
    20	Melih Can Yesilli
    17	Audun Myers
    17	stanweer1
    14	barnesd8
     9	Martin Uray
     8	Elizabeth Munch
     6	Danielle Barnes
     5	Danielle
     4	Kayla Makela
     3	Jesse Berwald
     1	danielle
     1	firas khasawneh
     1	mcanyesilli

@editorialbot
Copy link
Collaborator Author

Paper file info:

📄 Wordcount for paper.md is 1747

✅ The paper includes a Statement of need section

@editorialbot
Copy link
Collaborator Author

License info:

🟡 License found: GNU General Public License v3.0 (Check here for OSI approval)

@editorialbot
Copy link
Collaborator Author

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

✅ OK DOIs

- 10.1051/0004-6361/201629272 is OK
- 10.1051/0004-6361/201322068 is OK
- 10.48550/ARXIV.2110.05266 is OK
- 10.1140/epjds/s13688-023-00379-5 is OK
- 10.1103/physreve.107.034303 is OK
- 10.1063/5.0102421 is OK
- 10.1137/22m1476848 is OK
- 10.48550/ARXIV.2312.02099 is OK
- 10.3934/fods.2024006 is OK
- 10.48550/ARXIV.2212.08295 is OK
- 10.1016/j.precisioneng.2023.05.005 is OK
- 10.1109/icmla.2019.00202 is OK
- 10.3934/fods.2022005 is OK
- 10.1007/s10208-022-09567-7 is OK
- 10.1007/s41468-021-00071-5 is OK
- 10.5281/zenodo.2533369 is OK
- 10.1140/epjds/s13688-017-0109-5 is OK
- 10.4310/HHA.2016.v18.n1.a21 is OK
- 10.48550/arxiv.2204.11080 is OK
- 10.18608/jla.2017.42.6 is OK
- 10.1016/j.physa.2016.06.028 is OK
- 10.1007/s11071-024-09289-1 is OK
- 10.1016/j.probengmech.2024.103634 is OK
- 10.1142/s0219498815500668 is OK
- 10.1109/cvprw59228.2023.00067 is OK
- 10.1109/TPAMI.2018.2885516 is OK
- 10.1109/CVPR.2015.7299106 is OK
- 10.1063/1.4919075 is OK
- 10.1007/s44007-024-00110-4 is OK
- 10.1115/1.4036814 is OK
- 10.1016/s0167-2789(97)00118-8 is OK

🟡 SKIP DOIs

- No DOI given, and none found for title: Gaps in Globular Cluster Streams: Pal 5 and the Ga...
- No DOI given, and none found for title: Galactic Dynamics: Second Edition
- No DOI given, and none found for title: Fidgit: An ungodly union of GitHub and Figshare
- No DOI given, and none found for title: When Hearts Beat as One – Cardiac Dynamics and Syn...
- No DOI given, and none found for title: Topological Time-Series Classification
- No DOI given, and none found for title: Topological Approaches for Quantifying the Shape o...
- No DOI given, and none found for title: GUDHI: Geometry Understanding in Higher Dimensions
- No DOI given, and none found for title: giotto-tda: A Topological Data Analysis Toolkit fo...
- No DOI given, and none found for title: Dionysus2
- No DOI given, and none found for title: Introduction to the R package TDA
- No DOI given, and none found for title: An Overview of the Topology ToolKit
- No DOI given, and none found for title: Computational Topology for Data Analysis
- No DOI given, and none found for title: Statistical Topological Data Analysis using Persis...
- No DOI given, and none found for title: Persistence Images: A Stable Vector Representation...
- No DOI given, and none found for title: Teaspoon: A comprehensive python package for topol...
- No DOI given, and none found for title: Algebraic Topology

❌ MISSING DOIs

- None

❌ INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

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

@yossibokorbleile
Copy link

yossibokorbleile commented Sep 18, 2024

@editorialbot generate my checklist

@editorialbot
Copy link
Collaborator Author

I'm sorry human, I don't understand that. You can see what commands I support by typing:

@editorialbot commands

@yossibokorbleile
Copy link

yossibokorbleile commented Sep 18, 2024

Review checklist for @yossibokorbleile

Conflict of interest

  • I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

General checks

  • Repository: Is the source code for this software available at the https://github.com/TeaspoonTDA/teaspoon?
  • License: Does the repository contain a plain-text LICENSE or COPYING file with the contents of an OSI approved software license?
  • Contribution and authorship: Has the submitting author (@lizliz) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
  • Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
  • Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
  • Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
  • Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

Functionality

  • Installation: Does installation proceed as outlined in the documentation?
  • Functionality: Have the functional claims of the software been confirmed?
  • Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

  • A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
  • Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
  • Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
  • Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
  • Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
  • Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

  • Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
  • A statement of need: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
  • State of the field: Do the authors describe how this software compares to other commonly-used packages?
  • Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
  • References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

@editorialbot
Copy link
Collaborator Author

Hello @EduPH, here are the things you can ask me to do:


# List all available commands
@editorialbot commands

# Get a list of all editors's GitHub handles
@editorialbot list editors

# Adds a checklist for the reviewer using this command
@editorialbot generate my checklist

# Set a value for branch
@editorialbot set joss-paper as branch

# Run checks and provide information on the repository and the paper file
@editorialbot check repository

# Check the references of the paper for missing DOIs
@editorialbot check references

# Generates the pdf paper
@editorialbot generate pdf

# Generates a LaTeX preprint file
@editorialbot generate preprint

# Get a link to the complete list of reviewers
@editorialbot list reviewers

@EduPH
Copy link

EduPH commented Sep 27, 2024

Review checklist for @EduPH

Conflict of interest

  • I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

General checks

  • Repository: Is the source code for this software available at the https://github.com/TeaspoonTDA/teaspoon?
  • License: Does the repository contain a plain-text LICENSE or COPYING file with the contents of an OSI approved software license?
  • Contribution and authorship: Has the submitting author (@lizliz) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
  • Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
  • Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
  • Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
  • Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

Functionality

  • Installation: Does installation proceed as outlined in the documentation?
  • Functionality: Have the functional claims of the software been confirmed?
  • Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

  • A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
  • Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
  • Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
  • Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
  • Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
  • Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

  • Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
  • A statement of need: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
  • State of the field: Do the authors describe how this software compares to other commonly-used packages?
  • Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
  • References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

@EduPH
Copy link

EduPH commented Oct 6, 2024

Hello @lizliz, thank you for such an excellent Python package. I am working on the review and added an issue in the repository about the needed version of the packages.

@yossibokorbleile
Copy link

Hey @lizliz

I agree with @EduPH that the package looks great! I have found some issues that are preventing me from verifying the functionality. I have created an issue on the repo.

@hugoledoux
Copy link

👋 @lizliz what is the status with respect to the issues that were raised 4w ago by the reviewers?

@lizliz
Copy link

lizliz commented Nov 25, 2024

Hi, my apologies. End of the semester plus holidays here meant I haven't taken care of this. Hoping to get it done the first week of Dec if not before. I appreciate your patience!

@yossibokorbleile
Copy link

I also still need to provide more information sorry. Have been travelling and teaching.

@lizliz
Copy link

lizliz commented Jan 8, 2025

Hello folks! I have returned to the land of the living!

I just took care of the requests from the reviewers (This issue which is now closed). Let me know what else I can do! And thanks again everyone for your time and patience.

@lizliz
Copy link

lizliz commented Jan 17, 2025

Hi @EduPH and @yossibokorbleile. I know I absolutely have no leg to stand on with this since I let it sit for a while, but is there anything else I can do for you for the review process? Thanks in advance! -Liz

@EduPH
Copy link

EduPH commented Jan 17, 2025

Hi @lizliz , thank you for following up! I’m currently at a conference this week, but this is one of my priorities for next week. I’ll get back to you soon. Thanks for your patience!

@yossibokorbleile
Copy link

Hey @lizliz
Sorry for the delay on my side, after raising the GitHub issue, I've had a lot of teaching/moving/travel. Hoping to get back to it last week of Jan/first week of Feb.

@hugoledoux
Copy link

okay, I'll bug you all in ~10 days (!) to see how it is going...

@EduPH
Copy link

EduPH commented Jan 24, 2025

Dear @lizliz, I have finished the review. Thank you for your nice work and the great contribution to the TDA community.

@hugoledoux, all done from my side.

@hugoledoux
Copy link

okay, I'll bug you all in ~10 days (!) to see how it is going...

@yossibokorbleile as promised, I am bugging you to see what is going one :)

@yossibokorbleile
Copy link

@hugoledoux
I'm getting back to it this week, I've pulled the latest commit, and am starting the tests again. If there are no issues I hope to have it tested in the next 2 weeks.

@yossibokorbleile
Copy link

Hi I have now finished my review. I opened another issue on the repo, but I don't think it should stop the review process. Overall the documentation is satisfactory, with maybe some places where extra examples would be beneficial.

@lizliz
Copy link

lizliz commented Feb 19, 2025

Thanks for the help, Yossi!!

The bugs appear to have been squashed (see here).

@hugoledoux what are the next steps?

@editorialbot
Copy link
Collaborator Author

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

@hugoledoux
Copy link

@editorialbot set 10.5281/zenodo.14989806 as archive

@editorialbot
Copy link
Collaborator Author

Done! archive is now 10.5281/zenodo.14989806

@hugoledoux
Copy link

@editorialbot set v1.5.23 as version

@editorialbot
Copy link
Collaborator Author

Done! version is now v1.5.23

@hugoledoux
Copy link

@editorialbot recommend-accept

@editorialbot
Copy link
Collaborator Author

Attempting dry run of processing paper acceptance...

@editorialbot
Copy link
Collaborator Author

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

✅ OK DOIs

- 10.1051/0004-6361/201629272 is OK
- 10.1051/0004-6361/201322068 is OK
- 10.48550/ARXIV.2110.05266 is OK
- 10.1140/epjds/s13688-023-00379-5 is OK
- 10.1103/physreve.107.034303 is OK
- 10.1063/5.0102421 is OK
- 10.1137/22m1476848 is OK
- 10.48550/ARXIV.2312.02099 is OK
- 10.3934/fods.2024006 is OK
- 10.48550/ARXIV.2212.08295 is OK
- 10.1016/j.precisioneng.2023.05.005 is OK
- 10.1109/icmla.2019.00202 is OK
- 10.3934/fods.2022005 is OK
- 10.1007/s10208-022-09567-7 is OK
- 10.1007/s41468-021-00071-5 is OK
- 10.5281/zenodo.2533369 is OK
- 10.1140/epjds/s13688-017-0109-5 is OK
- 10.4310/HHA.2016.v18.n1.a21 is OK
- 10.48550/arxiv.2204.11080 is OK
- 10.18608/jla.2017.42.6 is OK
- 10.1016/j.physa.2016.06.028 is OK
- 10.1007/s11071-024-09289-1 is OK
- 10.1016/j.probengmech.2024.103634 is OK
- 10.1142/s0219498815500668 is OK
- 10.1109/cvprw59228.2023.00067 is OK
- 10.1109/TPAMI.2018.2885516 is OK
- 10.1109/CVPR.2015.7299106 is OK
- 10.1063/1.4919075 is OK
- 10.1007/s44007-024-00110-4 is OK
- 10.1115/1.4036814 is OK
- 10.1016/s0167-2789(97)00118-8 is OK

🟡 SKIP DOIs

- No DOI given, and none found for title: Gaps in Globular Cluster Streams: Pal 5 and the Ga...
- No DOI given, and none found for title: Galactic Dynamics: Second Edition
- No DOI given, and none found for title: Fidgit: An ungodly union of GitHub and Figshare
- No DOI given, and none found for title: When Hearts Beat as One – Cardiac Dynamics and Syn...
- No DOI given, and none found for title: Topological Time-Series Classification
- No DOI given, and none found for title: Topological Approaches for Quantifying the Shape o...
- No DOI given, and none found for title: GUDHI: Geometry Understanding in Higher Dimensions
- No DOI given, and none found for title: giotto-tda: A Topological Data Analysis Toolkit fo...
- No DOI given, and none found for title: Dionysus2
- No DOI given, and none found for title: Introduction to the R package TDA
- No DOI given, and none found for title: An Overview of the Topology ToolKit
- No DOI given, and none found for title: Computational Topology for Data Analysis
- No DOI given, and none found for title: Statistical Topological Data Analysis using Persis...
- No DOI given, and none found for title: Persistence Images: A Stable Vector Representation...
- No DOI given, and none found for title: Teaspoon: A comprehensive python package for topol...
- No DOI given, and none found for title: Algebraic Topology

❌ MISSING DOIs

- None

❌ INVALID DOIs

- None

@hugoledoux
Copy link

@yossibokorbleile @EduPH thanks for your help, without our reviewers JOSS wouldn't exist!

@lizliz it's now accepted, but one final check needs to be done by one of the editor-in-chief, they might have some minor changes

@editorialbot
Copy link
Collaborator Author

👋 @openjournals/csism-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#6489, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

@editorialbot editorialbot added the recommend-accept Papers recommended for acceptance in JOSS. label Mar 11, 2025
@lizliz
Copy link

lizliz commented Mar 12, 2025

Thanks @hugoledoux ! This has been a lovely experience. I promise you're not rid of me yet, we have two more JOSS submissions coming down the pipe to send your way soon :D

Extra thanks to @yossibokorbleile and @EduPH for the helpful feedback!

@danielskatz
Copy link

As track editor, I will proofread this soon and let you know about any next steps on your part.

@danielskatz
Copy link

I've suggested a number of small changes in TeaspoonTDA/teaspoon#169 - please merge this, or let me know what you disagree with, then we can continue to publishing the work.

@lizliz
Copy link

lizliz commented Mar 13, 2025

Fabulous, thank you! I fixed a small typo and pulled it into the branch. Let me know what else you need.

@danielskatz
Copy link

@editorialbot recommend-accept

@editorialbot
Copy link
Collaborator Author

Attempting dry run of processing paper acceptance...

@editorialbot
Copy link
Collaborator Author

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

✅ OK DOIs

- 10.1051/0004-6361/201629272 is OK
- 10.1051/0004-6361/201322068 is OK
- 10.48550/ARXIV.2110.05266 is OK
- 10.1140/epjds/s13688-023-00379-5 is OK
- 10.1103/physreve.107.034303 is OK
- 10.1063/5.0102421 is OK
- 10.1137/22m1476848 is OK
- 10.48550/ARXIV.2312.02099 is OK
- 10.3934/fods.2024006 is OK
- 10.48550/ARXIV.2212.08295 is OK
- 10.1016/j.precisioneng.2023.05.005 is OK
- 10.1109/icmla.2019.00202 is OK
- 10.3934/fods.2022005 is OK
- 10.1007/s10208-022-09567-7 is OK
- 10.1007/s41468-021-00071-5 is OK
- 10.5281/zenodo.2533369 is OK
- 10.1140/epjds/s13688-017-0109-5 is OK
- 10.4310/HHA.2016.v18.n1.a21 is OK
- 10.48550/arxiv.2204.11080 is OK
- 10.18608/jla.2017.42.6 is OK
- 10.1016/j.physa.2016.06.028 is OK
- 10.1007/s11071-024-09289-1 is OK
- 10.1016/j.probengmech.2024.103634 is OK
- 10.1142/s0219498815500668 is OK
- 10.1109/cvprw59228.2023.00067 is OK
- 10.1109/TPAMI.2018.2885516 is OK
- 10.1109/CVPR.2015.7299106 is OK
- 10.1063/1.4919075 is OK
- 10.1007/s44007-024-00110-4 is OK
- 10.1115/1.4036814 is OK
- 10.1016/s0167-2789(97)00118-8 is OK

🟡 SKIP DOIs

- No DOI given, and none found for title: Gaps in Globular Cluster Streams: Pal 5 and the Ga...
- No DOI given, and none found for title: Galactic Dynamics: Second Edition
- No DOI given, and none found for title: Fidgit: An ungodly union of GitHub and Figshare
- No DOI given, and none found for title: When Hearts Beat as One – Cardiac Dynamics and Syn...
- No DOI given, and none found for title: Topological Time-Series Classification
- No DOI given, and none found for title: Topological Approaches for Quantifying the Shape o...
- No DOI given, and none found for title: GUDHI: Geometry Understanding in Higher Dimensions
- No DOI given, and none found for title: giotto-tda: A Topological Data Analysis Toolkit fo...
- No DOI given, and none found for title: Dionysus2
- No DOI given, and none found for title: Introduction to the R package TDA
- No DOI given, and none found for title: An Overview of the Topology ToolKit
- No DOI given, and none found for title: Computational Topology for Data Analysis
- No DOI given, and none found for title: Statistical Topological Data Analysis using Persis...
- No DOI given, and none found for title: Persistence Images: A Stable Vector Representation...
- No DOI given, and none found for title: Teaspoon: A comprehensive Python package for topol...
- No DOI given, and none found for title: Algebraic Topology

❌ MISSING DOIs

- None

❌ INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

👋 @openjournals/csism-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#6501, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

@danielskatz
Copy link

@editorialbot accept

@editorialbot
Copy link
Collaborator Author

Doing it live! Attempting automated processing of paper acceptance...

@editorialbot
Copy link
Collaborator Author

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

cff-version: "1.2.0"
authors:
- family-names: Khasawneh
  given-names: Firas A.
  orcid: "https://orcid.org/0000-0001-7817-7445"
- family-names: Munch
  given-names: Elizabeth
  orcid: "https://orcid.org/0000-0002-9459-9493"
- family-names: Barnes
  given-names: Danielle
- family-names: Chumley
  given-names: Max M.
  orcid: "https://orcid.org/0000-0002-5335-5409"
- family-names: Güzel
  given-names: İsmail
  orcid: "https://orcid.org/0000-0002-5888-7025"
- family-names: Myers
  given-names: Audun D.
  orcid: "https://orcid.org/0000-0001-6268-9227"
- family-names: Tanweer
  given-names: Sunia
  orcid: "https://orcid.org/0000-0002-7232-0973"
- family-names: Tymochko
  given-names: Sarah
  orcid: "https://orcid.org/0000-0002-4932-6373"
- family-names: Yesilli
  given-names: Melih
  orcid: "https://orcid.org/0000-0001-8224-7397"
contact:
- family-names: Munch
  given-names: Elizabeth
  orcid: "https://orcid.org/0000-0002-9459-9493"
doi: 10.5281/zenodo.14989806
message: If you use this software, please cite our article in the
  Journal of Open Source Software.
preferred-citation:
  authors:
  - family-names: Khasawneh
    given-names: Firas A.
    orcid: "https://orcid.org/0000-0001-7817-7445"
  - family-names: Munch
    given-names: Elizabeth
    orcid: "https://orcid.org/0000-0002-9459-9493"
  - family-names: Barnes
    given-names: Danielle
  - family-names: Chumley
    given-names: Max M.
    orcid: "https://orcid.org/0000-0002-5335-5409"
  - family-names: Güzel
    given-names: İsmail
    orcid: "https://orcid.org/0000-0002-5888-7025"
  - family-names: Myers
    given-names: Audun D.
    orcid: "https://orcid.org/0000-0001-6268-9227"
  - family-names: Tanweer
    given-names: Sunia
    orcid: "https://orcid.org/0000-0002-7232-0973"
  - family-names: Tymochko
    given-names: Sarah
    orcid: "https://orcid.org/0000-0002-4932-6373"
  - family-names: Yesilli
    given-names: Melih
    orcid: "https://orcid.org/0000-0001-8224-7397"
  date-published: 2025-03-14
  doi: 10.21105/joss.07243
  issn: 2475-9066
  issue: 107
  journal: Journal of Open Source Software
  publisher:
    name: Open Journals
  start: 7243
  title: "Teaspoon: A Python Package for Topological Signal Processing"
  type: article
  url: "https://joss.theoj.org/papers/10.21105/joss.07243"
  volume: 10
title: "Teaspoon: A Python Package for Topological Signal Processing"

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.

Find more information on .cff files here and here.

@editorialbot
Copy link
Collaborator Author

🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘

@editorialbot
Copy link
Collaborator Author

🦋🦋🦋 👉 Bluesky post for this paper 👈 🦋🦋🦋

@editorialbot
Copy link
Collaborator Author

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

  1. Check final PDF and Crossref metadata that was deposited 👉 Creating pull request for 10.21105.joss.07243 joss-papers#6502
  2. Wait five minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.07243
  3. If everything looks good, then close this review issue.
  4. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

@editorialbot editorialbot added accepted published Papers published in JOSS labels Mar 14, 2025
@danielskatz
Copy link

Congratulations to @lizliz (Elizabeth Munch) and co-authors on your JOSS publication!!

And thanks to @yossibokorbleile & @EduPH for reviewing, and to @hugoledoux for editing!
JOSS completely depends on volunteers and we couldn't do this work without you.

@editorialbot
Copy link
Collaborator Author

🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉

If you would like to include a link to your paper from your README use the following

code snippets

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.07243/status.svg)](https://doi.org/10.21105/joss.07243)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.07243">
  <img src="https://joss.theoj.org/papers/10.21105/joss.07243/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.07243/status.svg
   :target: https://doi.org/10.21105/joss.07243

This is how it will look in your documentation:

DOI

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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted published Papers published in JOSS recommend-accept Papers recommended for acceptance in JOSS. review Track: 7 (CSISM) Computer science, Information Science, and Mathematics
Projects
None yet
Development

No branches or pull requests

6 participants