[REVIEW]: bifacial_radiance: a python package for modeling bifacial solar photovoltaic systems

[whedon]

Submitting author: @shirubana (Silvana Ayala Pelaez)
Repository: https:/NREL/bifacial_radiance/
Version: v0.3.3.1
Editor: @melissawm
Reviewers: @wholmgren, @dalonsoa, @usethedata
Archive: 10.5281/zenodo.3860350

Status

Status badge code:

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

Reviewers and authors:

Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)

Reviewer instructions & questions

@wholmgren ,@dalonsoa and @usethedata please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:

1. Make sure you're logged in to your GitHub account
2. Be sure to accept the invite at this URL: https:/openjournals/joss-reviews/invitations

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @melissawm know.

✨ Please try and complete your review in the next two weeks ✨

Review checklist for @wholmgren

Conflict of interest

• I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

• I confirm that I read and will adhere to the JOSS code of conduct.

General checks

• Repository: Is the source code for this software available at the repository url?
• License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
• Contribution and authorship: Has the submitting author (@shirubana) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?

Functionality

• Installation: Does installation proceed as outlined in the documentation?
• Functionality: Have the functional claims of the software been confirmed?
• Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
• Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
• Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
• Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
• Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

• Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• State of the field: Do the authors describe how this software compares to other commonly-used packages?
• Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
• References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

Review checklist for @dalonsoa

Conflict of interest

• I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

• I confirm that I read and will adhere to the JOSS code of conduct.

General checks

• Repository: Is the source code for this software available at the repository url?
• License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
• Contribution and authorship: Has the submitting author (@shirubana) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?

Functionality

• Installation: Does installation proceed as outlined in the documentation?
• Functionality: Have the functional claims of the software been confirmed?
• Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
• Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
• Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
• Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
• Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

• Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• State of the field: Do the authors describe how this software compares to other commonly-used packages?
• Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
• References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

Review checklist for @usethedata

Conflict of interest

• I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

• I confirm that I read and will adhere to the JOSS code of conduct.

General checks

• Repository: Is the source code for this software available at the repository url?
• License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
• Contribution and authorship: Has the submitting author (@shirubana) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?

Functionality

• Installation: Does installation proceed as outlined in the documentation?
• Functionality: Have the functional claims of the software been confirmed?
• Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
• Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
• Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
• Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
• Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

• Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• State of the field: Do the authors describe how this software compares to other commonly-used packages?
• Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
• References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

[whedon]

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @wholmgren, @dalonsoa it looks like you're currently assigned to review this paper 🎉.

⭐ Important ⭐

If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https:/openjournals/joss-reviews) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews 😿

To fix this do the following two things:

1. Set yourself as 'Not watching' https:/openjournals/joss-reviews:

2. You may also like to change your default settings for this watching repositories in your GitHub profile here: https:/settings/notifications

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

@whedon commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

👉 Check article proof 📄 👈

[dalonsoa]

Acceptance-blocker due to limited/incomplete installation instructions NREL/bifacial_radiance#190

[dalonsoa]

Not exactly an acceptance-blocker, but certainly desirable to understand how the software works NREL/bifacial_radiance#191

[dalonsoa]

Acceptance-blocker due to missing statement of need (or more specifically, intended audience) NREL/bifacial_radiance#192

[dalonsoa]

Not an acceptance blocker, but it will be useful for the authors to elaborate NREL/bifacial_radiance#193

[dalonsoa]

@melissawm It seems there’s a figure missing in the Software Paper. It is present in the repository and it appears when showing the markdown file of the paper in GitHub but it is not rendered when creating the PDF. I'm not sure of the reason for that.

[dalonsoa]

@melissawm The license of the software is BSD-3-Clause, clearly stated in the corresponding file, but in the DOI 10.11578/dc.20180530.16 it appears as BSD 2-clause "Simplified" License. I am not sure if it will necessary to consolidate the license in both places or, if not possible, to add a note somewhere indicating when the license was changed from one to the other. Or it it matters at all!

[melissawm]

@melissawm The license of the software is BSD-3-Clause, clearly stated in the corresponding file, but in the DOI 10.11578/dc.20180530.16 it appears as BSD 2-clause "Simplified" License. I am not sure if it will necessary to consolidate the license in both places or, if not possible, to add a note somewhere indicating when the license was changed from one to the other. Or it it matters at all!

I think it does matter, yes. Sorry for not catching this before. @shirubana could you clarify?

I'll check about the picture. Thanks!

[shirubana]

Well the DOI paper was published in 2017 when we started and it seems we changed the license to BSD-3 1 year ago, as per the github history of the file... @cdeline can you confirm if BSD-3 is what we will go on forever now and/or if we need to consolidate?

I think a simple solution would be to write a note of the switch on the documentation (maybe on the updates, package overview and/or contribution guidelines).

[cdeline]

Yes, we’re using a BSD-3 license for the software for now and forever more. Chris Deline National Renewable Energy Laboratory (303) 384-6359 From: Silvana Ayala <[email protected]> Sent: Thursday, November 7, 2019 2:05 PM To: openjournals/joss-reviews <[email protected]> Cc: Deline, Chris <[email protected]>; Mention <[email protected]> Subject: Re: [openjournals/joss-reviews] [REVIEW]: bifacial_radiance: a python package for modeling bifacial solar photovoltaic systems (#1865) Well the DOI paper was published in 2017 when we started and it seems we changed the license to BSD-3 1 year ago, as per the github history of the file... @cdeline<https:/cdeline> can you confirm if BSD-3 is what we will go on forever now and/or if we need to consolidate? I think a simple solution would be to write a note of the switch on the documentation (maybe on the updates, package overview and/or contribution guidelines). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#1865?email_source=notifications&email_token=AFRK2OA6BQYCBRYTK7UCXPDQSR7HZA5CNFSM4JJE6BX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDNZXKY#issuecomment-551263147>, or unsubscribe<https:/notifications/unsubscribe-auth/AFRK2OCVSMKMRJGHXQOH5U3QSR7HZANCNFSM4JJE6BXQ>.

[wholmgren]

@melissawm the COI policy states:

In addition, your recent (past year) association with the same organization of a submitter is a COI, for example, being employed at the same institution.

@shirubana was a graduate student at my organization, University of Arizona, from 2012- Dec 2018. So there is 1-2 month overlap over the past year. But, the COI policy also states as an example of when a waiver can be granted:

Or if you and a submitter are both employed by the same very large organization but in different units without any knowledge of each other.

We knew of each other but very rarely interacted. Different departments, siloed research programs.

I wouldn't have any problem providing an impartial review of this paper.

[wholmgren]

Also on the subject of the license, it includes this NREL specific language:

NOTICE: This software was developed at least in part by Alliance for Sustainable
Energy, LLC (“Alliance”) under Contract No. DE-AC36-08GO28308 with the U.S.
Department of Energy and the U.S. Government retains for itself and others acting
on its behalf a nonexclusive, paid-up, irrevocable worldwide license in the software
to reproduce, prepare derivative works, distribute copies to the public, perform
publicly and display publicly, and to permit others to do so.

Does this violate the requirement "Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?" My own opinion is "no" but seems like a question for the editors.

[danielskatz]

@wholmgren - the conflict you describe is weak enough that it can be waived, but thank you for making this possible issue transparent.

[melissawm]

Thank you all for your patience while I was checking this. As far as the change in licensing, a note in the documentation would be ok.

However, as far as the NOTICE mentioned above by @wholmgren , the best solution would be to remove it from the licence file (mantaining it a pure BSD 3 license) and adding this note somewhere in the project (for example, in the README).

@shirubana do you think this is feasible?

Please let me know if you have further questions or comments.

[shirubana]

@cdeline would this option of using the README instead of the License file to have the sponsoring/DOE acknowledgment work to satisfy NREL's legal stuff?

[cdeline]

Hi everybody! I'm investigating these two points with the legal team here at NREL, but for everyone's information, a LICENSE file wasn't added until v0.2.3 on 11/14/2018, and it was initiated as a BSD-3 license, and has remained the same since then. So, I believe the DOI entry is incorrect and should probably be updated - there are a couple of other inaccuracies there including that we were supported by the CEC.

[cdeline]

Hi all, i've been given approval by NREL legal to replace LICENSE.txt with a stock BSD-3 from the OSI webpage. I'm merging that in Master now.

[melissawm]

Thank you, @cdeline and @shirubana!

@wholmgren and @dalonsoa this means the review can resume as normal. If you have any further questions, don't hesitate to ask!

[danielskatz]

👋 @melissawm - I'm just checking in on the progress of this review

[dalonsoa]

I'm waiting for some changes to be made in this PR NREL/bifacial_radiance#199 before I can tick all the remaining boxes in the review. It seems that the PR is not passing all checks for now, so no sure what is the status of the review.

[shirubana]

sorry! I'll do this today. I hadn't realized that. ugh.

[shirubana]

@dalonsoa @danielskatz @wholmgren I have addressed all of issues and the PR comments now as well.

[dalonsoa]

I'll tick those things that have been solved... but the PR is still not passing 🤷‍♂ .

[shirubana]

ok now we're good :)

[shirubana]

@whedon generate pdf

[whedon]

👉 Check article proof 📄 👈

[shirubana]

I liked.... hmmm one of the titles disapeared.

[shirubana]

@whedon generate pdf

[whedon]

👉 Check article proof 📄 👈

[shirubana]

@whedon generate pdf

[whedon]

👉 Check article proof 📄 👈

[shirubana]

@kyleniemeyer ok I'm good , all references have DOI if they have them now.

[kyleniemeyer]

@whedon accept

[whedon]

Attempting dry run of processing paper acceptance...

[whedon]

Reference check summary:

OK DOIs

- 10.1109/JPHOTOV.2018.2819676 is OK
- 10.1109/JPHOTOV.2018.2877000 is OK
- 10.1109/JPHOTOV.2019.2892872 is OK
- 10.1109/JPHOTOV.2019.2924394 is OK
- 10.11578/dc.20180530.16 is OK
- 10.4229/EUPVSEC20192019-5DO.3.4 is OK
- 10.1002/pip.3259 is OK
- 10.5281/zenodo.1401378 is OK
- 10.1145/192161.192286 is OK
- 10.21105/joss.00884 is OK
- 10.1109/PVSC.2017.8366704 is OK
- 10.4229/35thEUPVSEC20182018-6CV.2.19 is OK
- 10.2172/1440404 is OK
- 10.1109/PVSC.2017.8366263 is OK

MISSING DOIs

- None

INVALID DOIs

- None

[whedon]

👋 @openjournals/joss-eics, this paper is ready to be accepted and published.

Check final proof 👉 openjournals/joss-papers#1474

If the paper PDF and Crossref deposit XML look good in openjournals/joss-papers#1474, then you can now move forward with accepting the submission by compiling again with the flag deposit=true e.g.

@whedon accept deposit=true

[kyleniemeyer]

@whedon accept deposit=true

[whedon]

Doing it live! Attempting automated processing of paper acceptance...

[whedon]

🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦

[whedon]

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

0. Check final PDF and Crossref metadata that was deposited 👉 Creating pull request for 10.21105.joss.01865 joss-papers#1475
1. Wait a couple of minutes to verify that the paper DOI resolves https://doi.org/10.21105/joss.01865
2. If everything looks good, then close this review issue.
3. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? notify your editorial technical team...

[kyleniemeyer]

Hey @arfon, this is now ready for the name fix, both in the paper footer and the citation on the landing page.

[kyleniemeyer]

Congrats @shirubana on your article's publication in JOSS!

Many thanks to @wholmgren, @dalonsoa, and @usethedata for reviewing this, and @melissawm for editing.

[melissawm]

Thank you all for working on this, especially @kyleniemeyer for taking over since I was unavailable. Congratulations @shirubana !

[shirubana]

thank you for this! everyone!!!! this is really great :)

[shirubana]

@arfon if you get a chance to update the last name on the footer and webpage --- to "Ayala Pelaez" instead of just Pelaez :) t

[arfon]

@arfon if you get a chance to update the last name on the footer and webpage --- to "Ayala Pelaez" instead of just Pelaez :) t

Sure thing. I can do that - I might not be able to get to this until tomorrow though sorry.

[arfon]

@shirubana - this should be updated now although the PDF may take a while to update as it's cached.

[whedon]

🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉

If you would like to include a link to your paper from your README use the following code snippets:

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.01865/status.svg)](https://doi.org/10.21105/joss.01865)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.01865">
  <img src="https://joss.theoj.org/papers/10.21105/joss.01865/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.01865/status.svg
   :target: https://doi.org/10.21105/joss.01865

This is how it will look in your documentation:

We need your help!

Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:

• Volunteering to review for us sometime in the future. You can add your name to the reviewer list here: https://joss.theoj.org/reviewer-signup.html
• Making a small donation to support our running costs here: https://numfocus.org/donate-to-joss