[PRE REVIEW]: pyclustering

[whedon]

Submitting author: @annoviko (Andrei Novikov)
Repository: https://github.com/annoviko/pyclustering
Version: 0.8.2
Editor: @poulson
Reviewers: @adavidzh

Author instructions

Thanks for submitting your paper to JOSS @annoviko. The JOSS editor Pending, will work with you on this issue to find a reviewer for your submission before creating the main review issue.

@annoviko if you have any suggestions for potential reviewers then please mention them here in this thread. In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission.

Editor instructions

The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:

@whedon commands

[whedon]

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@whedon commands

What happens now?

This submission is currently in a pre-review state which means we are waiting for an editor to be assigned and for them to find some reviewers for your submission. This may take anything between a few hours to a couple of weeks. Thanks for your patience 😸

You can help the editor by looking at this list of potential reviewers to identify individuals who might be able to review your submission (please start at the bottom of the list). Also, feel free to suggest individuals who are not on this list by mentioning their GitHub handles here.

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[arfon]

👋 @poulson - would you be willing to edit this submission for JOSS?

[whedon]

PDF failed to compile for issue #1195 with the following error:

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 15 0 15 0 0 184 0 --:--:-- --:--:-- --:--:-- 185
sh: 0: getcwd() failed: No such file or directory
sh: 0: getcwd() failed: No such file or directory
sh: 0: getcwd() failed: No such file or directory
pandoc: 10.21105.joss.01195.pdf: openBinaryFile: does not exist (No such file or directory)
Looks like we failed to compile the PDF

[arfon]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

👉 Check article proof 📄 👈

[annoviko]

Hello, @arfon,
I have checked the list and found out that adavidzh, dvysardana, pragyansmita are suitable persons for review in line with the description (C/C++, Python, Cluster Analysis, Data Mining).

The article devoted to 0.8.2 version that is on stable release branch '0.8.2.rel' (link: https://github.com/annoviko/pyclustering/tree/0.8.2.rel). DOI is already assigned for this release (link: https://zenodo.org/record/1491324#.XEgztVUzaUk) and it can be used by JOSS if it does not contradict the rules. Master branch already contains changes related to the new version of the library.

[arfon]

I have checked the list and found out that adavidzh, dvysardana, pragyansmita are suitable persons for review in line with the description (C/C++, Python, Cluster Analysis, Data Mining).

Thanks @annoviko. Before we decide upon reviewers, we need to have an editor assigned - this shouldn't take more than a week.

The article devoted to 0.8.2 version that is on stable release branch '0.8.2.rel' (link: https://github.com/annoviko/pyclustering/tree/0.8.2.rel). DOI is already assigned for this release (link: https://zenodo.org/record/1491324#.XEgztVUzaUk) and it can be used by JOSS if it does not contradict the rules. Master branch already contains changes related to the new version of the library.

Is the paper (#1195 (comment)) above not correct then? We can ask @whedon to compile a paper from a different branch in your repository.

Also, regarding the DOI & archive you already have - this might be OK, if your code is modified because of the review here we would ask you to make a new archive before publication.

[annoviko]

@arfon, thanks for the clarification. The paper is totally correct, no need to rebuild it, I have just provided some extra information about the repository.

[danielskatz]

👋 @arfon - is this ready to go to an editor in your opinion? If so, can you suggest one? If not, what else do you think is needed?

[arfon]

If so, can you suggest one?

Many of our editors are pretty loaded right now. Perhaps @poulson could take this one?

[danielskatz]

👋 @poulson - Are you able to edit this submission?

[danielskatz]

👋 @poulson - ping... Are you able to edit this submission?

[poulson]

@arfon @danielskatz Yes, I would be happy to edit this submission and apologize, none of my pings had been going through. I promise I was not actively ignoring this!

[poulson]

@lmcinnes Would you be able to review this submission?

[poulson]

@adavidzh Would you be able to review this submission?

[adavidzh]

@adavidzh Would you be able to review this submission?

I just looked through the different materials and can do.

[danielskatz]

@whedon assign @poulson as editor

by the way @poulson - you can perform this command too...

[whedon]

OK, the editor is @poulson

[poulson]

@whedon assign @adavidzh as reviewer

[whedon]

OK, the reviewer is @adavidzh

[poulson]

@whedon commands

[whedon]

Here are some things you can ask me to do:

# List all of Whedon's capabilities
@whedon commands

# Assign a GitHub user as the sole reviewer of this submission
@whedon assign @username as reviewer

# Add a GitHub user to the reviewers of this submission
@whedon add @username as reviewer

# Remove a GitHub user from the reviewers of this submission
@whedon remove @username as reviewer

# List of editor GitHub usernames
@whedon list editors

# List of reviewers together with programming language preferences and domain expertise
@whedon list reviewers

# Change editorial assignment
@whedon assign @username as editor

# Set the software archive DOI at the top of the issue e.g.
@whedon set 10.0000/zenodo.00000 as archive

# Set the software version at the top of the issue e.g.
@whedon set v1.0.1 as version

# Open the review issue
@whedon start review

EDITORIAL TASKS

# Compile the paper
@whedon generate pdf

# Ask Whedon to accept the paper and deposit with Crossref
@whedon accept

# Ask Whedon to check the references for missing DOIs
@whedon check references

[poulson]

@whedon start review

[whedon]

OK, I've started the review over in #1230. Feel free to close this issue now!