Joss-reviews: [PRE REVIEW]: PyCM: Multi class confusion matrix library in python

[whedon]

Submitting author: @sepandhaghighi (Sepand Haghighi)
Repository: https://github.com/sepandhaghighi/pycm
Version: v0.8.1
Editor: @arokem
Reviewers: @NickleDave

Author instructions

Thanks for submitting your paper to JOSS @sepandhaghighi. The JOSS editor (shown at the top of this issue) will work with you on this issue to find a reviewer for your submission before creating the main review issue.

@sepandhaghighi 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. I'm here to help you with some common editorial tasks. @arokem it looks like you're currently assigned as the editor for this paper :tada:

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

@whedon commands

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

PDF failed to compile for issue #708 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 13 0 13 0 0 91 0 --:--:-- --:--:-- --:--:-- 92
pandoc-citeproc: reference Goodman1963 not found
Error producing PDF.
! Undefined control sequence.
l.291 Combination of (\upchi

Looks like we failed to compile the PDF

[arfon]

👋@arokem - the submitting author suggested you as the editor.

[sepandhaghighi]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

PDF failed to compile for issue #708 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 13 0 13 0 0 163 0 --:--:-- --:--:-- --:--:-- 164
Error producing PDF.
! Undefined control sequence.
l.290 Combination of (\upchi

Looks like we failed to compile the PDF

[sepandhaghighi]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

--> Check article proof :page_facing_up: <--

[sepandhaghighi]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

--> Check article proof :page_facing_up: <--

[sepandhaghighi]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

--> Check article proof :page_facing_up: <--

[sepandhaghighi]

Hi @arfon

Could you please tell me what is the problem of image in paper.md ?

Thanks ;-)

[arfon]

Could you please tell me what is the problem of image in paper.md ?

I don't know sorry. I think there must be something strange with the figure - if I swap your figure out for another image the size is normal.

Can you try regenerating the figure?

[sepandhaghighi]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

--> Check article proof :page_facing_up: <--

[sepandhaghighi]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

--> Check article proof :page_facing_up: <--

[sepandhaghighi]

@arfon
Oh fixed, after I changed size of the image to 600*662 in .png format.
But another question is about the image location??!!!

[sepandhaghighi]

I suggest @nhejazi for review.

[arfon]

Oh fixed, after I changed size of the image to 600*662 in .png format.

Great thanks.

But another question is about the image location??!!!

I think this is just the LaTeX engine being weird (image placement in LaTeX is notoriously peculiar) because the paper is very short. I suggest we fix this when we've been through review.

[arokem]

@whedon assign @arokem as editor

[whedon]

OK, the editor is @arokem

[arokem]

👋 Hey @rasbt: would you be willing to review this article for JOSS?

[rasbt]

Hi @arokem. Generally, I would be happy to do the review, but I am currently already involved in the mlpack review at JOSS, which will probably take a few weeks. As alternative reviewer with substantial expertise in that area, I would suggest @rhiever @NickleDave @jmschrei @jmwoloso

[NickleDave]

Thanks @rasbt . Hi @arokem, I would be willing to act as a reviewer.

[jmwoloso]

Very cool project @sepandhaghighi Happy to help as well with anything @rasbt @arokem

[arokem]

@NickleDave : thanks!

[arokem]

@whedon assign @NickleDave as reviewer

[whedon]

OK, the reviewer is @NickleDave

[arokem]

@jmwoloso : thanks for offering! I will keep this in mind as we make progress here, in case a second opinion is needed.

[arokem]

@whedon start review magic-word=bananas

[whedon]

OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/729. Feel free to close this issue now!

[arokem]

@NickleDave : please head over to #729 for the review