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

Reproducing figure in JOSS paper #34

Closed
matt-graham opened this issue May 22, 2024 · 5 comments
Closed

Reproducing figure in JOSS paper #34

matt-graham opened this issue May 22, 2024 · 5 comments
Labels
documentation Improvements or additions to documentation

Comments

@matt-graham
Copy link
Contributor

Raising as part of JOSS review openjournals/joss-reviews/issues/6713

It would be nice if code was provided (even better if it was in the paper as an example usage) for reproducing the plot / table shown in Figure 1 in the paper, along with some description of the data used to produce it and how to access.

@tupui
Copy link
Member

tupui commented May 22, 2024

I would not do that in the paper. APIs tend to change and I would not want people to copy past something from a paper that we cannot easily update.

The figure was more of showcase not meant to be analysed by the reader, since the paper is less about the method and more about the code. i.e. we managed to make something pretty which is meaningful.

But if you really want, we can add a description.

Otherwise I would close this issue in favour #31 where you ask for an example in the doc itself, which we can run in the CI and update as we go.

@tupui tupui added the documentation Improvements or additions to documentation label May 22, 2024
@matt-graham
Copy link
Contributor Author

In terms of APIs changing - while a good point, there are ways that could be dealt with, for example specifying the version of the package used if providing code in the paper or providing a permalink to a script in the repository at a specific commit. The reviewer checklist asks us to confirm that 'If the paper contains original results, results are entirely reproducible by reviewers' which at the moment I judged not to be the case, hence this issue.

I would say some form of description of what the figure is showing and the provenance of the data being visualized is a minimum requirement for the figure to be useful to a reader. At the moment from the current paper alone I struggled to understand what the figure was showing. Alternatively there is no requirement to include any figures so it could be removed, but I do think having an example output to help the reader understand what the package can do is helpful.

@tupui
Copy link
Member

tupui commented May 24, 2024

there are ways that could be dealt with, for example specifying the version of the package used if providing code in the paper or providing a permalink to a script in the repository at a specific commit.

I disagree here. We have exactly this issue with SciPy and even with proper referencing of the version, people still complain and raise issues.

We will add a description of the figure itself so it can be understood better. If after that it's still too complicated, then we will just remove it since again it's not a paper about the science behind and should just be a one pager.

@tupui
Copy link
Member

tupui commented May 30, 2024

@matt-graham I added an executable notebook in the doc, see #23

Screenshot 2024-05-30 at 11 31 01 Screenshot 2024-05-30 at 11 31 12

@tupui tupui closed this as completed May 30, 2024
@matt-graham
Copy link
Contributor Author

Thanks this looks great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants