[PRE REVIEW]: lintsampler: Easy random sampling via linear interpolation

[editorialbot]

Submitting author: !--author-handle-->@aneeshnaik<!--end-author-handle-- (Aneesh Naik) Repository: https://github.com/aneeshnaik/lintsampler Branch with paper.md (empty if default branch): Version: v0.3.0 Editor: !--editor-->@jbytecode<!--end-editor-- Reviewers: @matt-graham, @vankesteren Managing EiC: Chris Vernon

Status

Status badge code:

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

Author instructions

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

@aneeshnaik 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]

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]

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

OK DOIs

- 10.21105/joss.01864 is OK
- 10.21105/joss.05582 is OK
- 10.21105/joss.04113 is OK

MISSING DOIs

- No DOI given, and none found for title: Non-Uniform Random Variate Generation
- No DOI given, and none found for title: PyMC: Bayesian Stochastic Modelling in Python

INVALID DOIs

- None

[editorialbot]

Software report:

github.com/AlDanial/cloc v 1.90  T=0.05 s (1205.6 files/s, 173071.7 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Python                          27            895           1494           2357
Markdown                        15            276              0            591
Jupyter Notebook                 5              0           1862            284
YAML                             5             10              0            112
TeX                              1              9              0             62
TOML                             1              3              0             29
DOS Batch                        1              8              1             26
make                             1              4              7              9
-------------------------------------------------------------------------------
SUM:                            56           1205           3364           3470
-------------------------------------------------------------------------------

Commit count by author:

   181  Aneesh Naik
    40  michael-petersen
     6  Michael Petersen
     6  aneeshnaik

[editorialbot]

Paper file info:

📄 Wordcount for paper.md is 720

✅ The paper includes a Statement of need section

[editorialbot]

License info:

✅ License found: MIT License (Valid open source OSI approved license)

[editorialbot]

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

[crvernon]

@editorialbot invite @jbytecode as editor

:wave: @jbytecode - would you like to edit this one? I know you have several others going right now, so quite alright if not. Just let me know. Thanks!

[editorialbot]

Invitation to edit this submission sent!

[jbytecode]

@editorialbot assign me as editor

@crvernon - My lectures and final exams have just been done so I can handle one more submission for this time. Thank you for the invitation.

[editorialbot]

Assigned! @jbytecode is now the editor

[jbytecode]

@aneeshnaik - Hi, I am the handling editor of this submission. Thank you for sending you work to JOSS.

Do you have any suggestions for the potential reviewers? The manuscript and the code is on mainly Statistics and Python so you can search people that have experiences on these subjects using the search tool:

https://reviewers.joss.theoj.org/lookup

When you suggest potential reviewers, please do not use the @ character when you mention their GitHub handles just because we don't want to bother people.

Thank you in advance.

[aneeshnaik]

Hi @jbytecode, thanks for agreeing to serve as the editor!

Having searched the reviewer list you sent, here are some initial suggestions for suitable referees. I don't know any of them personally.

• matt-graham
• DanWaxman
• Edenhofer
• vankesteren
• larryshamalama

However, it seemed like there might well be many other suitable choices. Perhaps my co-author @michael-petersen might also have some suggestions?

[jbytecode]

👋👋👋 Dear @matt-graham and @vankesteren 👋👋👋

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]: lintsampler: Easy random sampling via linear interpolation

You can find more information at the top of this Github issue (LINK).

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!

[matt-graham]

Hi @jbytecode - yes I'd be happy to review this submission.

[jbytecode]

@editorialbot add @matt-graham as reviewer

@matt-graham Thank you for accepting our invitation.

[editorialbot]

@matt-graham added to the reviewers list!

[vankesteren]

Small question about the review process: was the scope/statement of need already checked by the editorial team before moving to the pre-review stage?

I have reservations about the statement of need, which would be elaborated in my review. If that is ok, I am happy to review!

[jbytecode]

@vankesteren - Scope check is always considered by our track editors. You can provide your thoughts and suggest corrections during the review process.

[jbytecode]

@editorialbot add @vankesteren as reviewer

[editorialbot]

@vankesteren added to the reviewers list!

[jbytecode]

@editorialbot start review

@matt-graham, @vankesteren, @aneeshnaik - I am starting the review in a separate thread, see you there.

[editorialbot]

OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/6906.