Skip to content
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]: Dyad: a binary-star dynamics and statistics package for Python #7885

Open
editorialbot opened this issue Mar 7, 2025 · 6 comments
Labels
pre-review TeX Track: 1 (AASS) Astronomy, Astrophysics, and Space Sciences

Comments

@editorialbot
Copy link
Collaborator

Submitting author: @AmeryGration (Amery Gration)
Repository: https://github.com/AmeryGration/dyad
Branch with paper.md (empty if default branch): joss_paper
Version: 0.0.0
Editor: Pending
Reviewers: Pending
Managing EiC: Warrick Ball

Status

status

Status badge code:

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

Author instructions

Thanks for submitting your paper to JOSS @AmeryGration. Currently, there isn't a JOSS editor assigned to your paper.

@AmeryGration 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:

@editorialbot commands
@editorialbot editorialbot added pre-review Track: 1 (AASS) Astronomy, Astrophysics, and Space Sciences labels Mar 7, 2025
@editorialbot
Copy link
Collaborator Author

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:

@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.98  T=0.01 s (521.3 files/s, 42356.2 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
TeX                              1             20              0            210
Markdown                         2              6              0             65
YAML                             1              1              4             19
-------------------------------------------------------------------------------
SUM:                             4             27              4            294
-------------------------------------------------------------------------------

Commit count by author:

    56	AmeryGration
    23	Amery Gration

@editorialbot
Copy link
Collaborator Author

@editorialbot
Copy link
Collaborator Author

Paper file info:

📄 Wordcount for paper.md is 450

✅ The paper includes a Statement of need section

@editorialbot
Copy link
Collaborator Author

License info:

🔴 Failed to discover a valid open source license

@warrickball
Copy link

warrickball commented Mar 7, 2025

Hi @AmeryGration, thanks for your submission! All the suitable JOSS editors are currently working at capacity so I'm going to "waitlist" this review until an editor with the relevant expertise is available to take it on. Thanks for your patience!

For other editors, the pipelines look like they're being thrown off by the joss_paper branch only containing the JOSS manuscript and not any of the main code. I haven't seen this before so will follow up but it isn't fundamentally a problem. I ran cloc manually and the results were:

github.com/AlDanial/cloc v 2.02  T=0.43 s (527.9 files/s, 197657.8 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
HTML                            99          17100            694          46421
Python                          32           2898           5850           7359
JavaScript                      13            181            271           1126
CSS                              7            204             70            937
reStructuredText                65            334            397            291
DOS Batch                        1              8              1             26
Markdown                         2              7              0             22
Text                             3              0              0             12
SVG                              2              0              0              9
make                             1              4              7              9
-------------------------------------------------------------------------------
SUM:                           225          20736           7290          56212
-------------------------------------------------------------------------------

but I have comments for the author below.

In the meantime @AmeryGration, there are a few details we can iron out.

  1. The paper looks like it's failing to build on account of a tab in YAML header. If you fix that you can try running the pipeline again here by posting a comment starting with @editorialbot generate pdf.

  2. Don't worry about the automatic check failing to find the license. I can see the GPL v3 licence in the COPYING file.

  3. It looks like you've bundled the built HTML docs in the repo, which I'd disadvise mostly to avoid repo churn and the potential to not update them. You may want to rather host the built docs on e.g. GitHub pages, but either way I'd suggest remove everything under docs/build from the repo and let users know they can rebuild them with Sphinx.

  4. It looks like some temporary files have also made their way into the repo and should be removed. I found at least

    ./dyad/constants/#__init__.py#
    ./dyad/stats/data/log_period/#sample_pdf.py#
    ./dyad/stats/data/period/#sample_pdf.py#
    
  5. The largest Python source file is dyad/stats/_distn_infrastructure.py, which looks like it overlaps a lot with the same file in the scipy.stats module. Can you explain a bit more what's going on here? I haven't looked in too much detail but if it's the infrastructure for constructing your own statistical distributions with the SciPy API, why not just use the SciPy implementation? I note the commit message says

    Local versions of scipy.stats._distn_infrastructure.py and scipy.stats.distr_params created to allow automatic generation of docstrings

    but duplicating so much source doesn't feel like the best solution. (I'm happy to help work out a better one. I've subclassed SciPy stats classes before but I don't remember offhand what we did—if anything—about API docs, if that's the issue.)

    (For editors wondering about scope, cloc reports 3625 lines of code in _distribution_infrastructure.py, so there still appears to be ~3800 other lines of code in the repo.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pre-review TeX Track: 1 (AASS) Astronomy, Astrophysics, and Space Sciences
Projects
None yet
Development

No branches or pull requests

2 participants