[REVIEW]: ProMCDA: A Python package for Probabilistic Multi-Criteria Decision Analysis #6190

editorialbot · 2024-01-08T21:30:10Z

Submitting author: @Flaminietta (Flaminia Catalli)
Repository: https://github.com/wetransform-os/ProMCDA
Branch with paper.md (empty if default branch): main
Version: v1.1.0
Editor: @galessiorob
Reviewers: @limengbinggz, @B3J4y, @paulrougieux
Archive: 10.5281/zenodo.13694286

Status

Status badge code:

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

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

@limengbinggz & @B3J4y, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review.
First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

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

✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨

Checklists

📝 Checklist for @limengbinggz

📝 Checklist for @B3J4y

📝 Checklist for @paulrougieux

The text was updated successfully, but these errors were encountered:

editorialbot · 2024-01-08T21:30:13Z

Hello humans, 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 · 2024-01-08T21:30:14Z

Software report:

github.com/AlDanial/cloc v 1.88  T=0.05 s (541.8 files/s, 87446.0 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Python                          18            493            306           2030
HTML                             1             84              5            620
Markdown                         2             75              0            256
TeX                              1             16              0            220
YAML                             3              8              2             58
JSON                             1              4              0             19
-------------------------------------------------------------------------------
SUM:                            26            680            313           3203
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

editorialbot · 2024-01-08T21:30:15Z

Wordcount for paper.md is 1415

editorialbot · 2024-01-08T21:30:16Z

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

OK DOIs

- 10.1007/s10669-020-09784-x is OK
- 10.1016/j.envsoft.2021.105208 is OK
- 10.1016/S0377-2217(97)00163-X is OK
- 10.1016/j.dss.2022.113848 is OK
- 10.21105/joss.04567 is OK
- 10.1016/j.envsoft.2020.104890 is OK
- 10.1016/j.omega.2017.04.007 is OK
- 10.1007/978-1-4757-2500-1_2 is OK
- 10.1007/0-387-31099-1_2 is OK
- 10.1007/s11205-017-1832-9 is OK
- 10.1016/j.ecolind.2018.06.009 is OK
- 10.1016/j.ecolind.2019.105731 is OK
- 10.1016/j.ijggc.2016.08.023 is OK
- 10.1007/978-1-4939-3094-4_12 is OK
- 10.1016/j.ecolind.2014.05.014 is OK

MISSING DOIs

- None

INVALID DOIs

- None

editorialbot · 2024-01-08T21:31:17Z

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

galessiorob · 2024-01-08T21:31:43Z

🚀 @limengbinggz, @B3J4y thank you so much for volunteering to review this paper! Please comment @editorialbot generate my checklist and start your review at your earliest convenience. Let me know if you have any questions.

galessiorob · 2024-01-08T21:34:41Z

👋 Hi @paulrougieux! @Flaminietta suggested you'd be a good reviewer for this paper - do you have the bandwidth to help us out? Thanks!

B3J4y · 2024-01-09T05:57:56Z

Review checklist for @B3J4y

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 https://github.com/wetransform-os/ProMCDA?
License: Does the repository contain a plain-text LICENSE or COPYING file with the contents of an OSI approved software license?
Contribution and authorship: Has the submitting author (@Flaminietta) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

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: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
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?

B3J4y · 2024-01-09T06:30:35Z

Opened Issue:

JOSS Paper: The Tables are Partially Visible wetransform-os/ProMCDA#18

paulrougieux · 2024-01-09T07:11:07Z

I accept this review.

👋 Hi @paulrougieux! @Flaminietta suggested you'd be a good reviewer for this paper - do you have the bandwidth to help us out? Thanks!

Dear @galessiorob I can do the review within a bit more than 2 weeks.

Flaminietta · 2024-01-09T09:15:26Z

@editorialbot generate preprint

editorialbot · 2024-01-09T09:16:00Z

📄 Preprint file created: Find it here in the Artifacts list 📄

Flaminietta · 2024-01-09T09:44:45Z

@editorialbot generate preprint

editorialbot · 2024-01-09T09:45:12Z

📄 Preprint file created: Find it here in the Artifacts list 📄

Flaminietta · 2024-01-09T11:21:58Z

@editorialbot generate preprint

editorialbot · 2024-01-09T11:22:26Z

📄 Preprint file created: Find it here in the Artifacts list 📄

limengbinggz · 2024-01-09T19:27:00Z

Review checklist for @limengbinggz

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 https://github.com/wetransform-os/ProMCDA?
License: Does the repository contain a plain-text LICENSE or COPYING file with the contents of an OSI approved software license?
Contribution and authorship: Has the submitting author (@Flaminietta) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

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: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
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?

galessiorob · 2024-01-15T18:35:13Z

👋 Hi everyone! Checking in to see if anyone has questions on the review process or the paper itself, thanks!

B3J4y · 2024-01-18T06:08:58Z

Hi, thank you for checking in. I have no questions from my side so far.

B3J4y · 2024-01-18T09:24:05Z

Could not run the example wetransform-os/ProMCDA#19

paulrougieux · 2024-01-31T13:47:01Z

@editorialbot generate my checklist

editorialbot · 2024-01-31T13:47:02Z

@paulrougieux I can't do that because you are not a reviewer

mspada · 2024-12-20T17:58:01Z

@editorialbot generate pdf

editorialbot · 2024-12-20T17:59:32Z

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

mspada · 2024-12-20T18:10:08Z

@samhforbes, @arfon,
I removed the IDs and the editorialbot is able to generate the pdf correctly.
Could you please check if now the acceptance works?
Thank you!

mspada · 2025-01-14T11:11:06Z

Dear @samhforbes and @arfon,
first of all, Happy New Year!
We are just checking the status of the paper, since we corrected the IDs issue and it should work out now (we hope).
Could you please check?

Thanks and Best,
Matteo and Flaminia

samhforbes · 2025-01-14T11:46:01Z

Sorry I missed that. Let me try

samhforbes · 2025-01-14T11:46:21Z

@editorialbot recommend-accept

editorialbot · 2025-01-14T11:46:24Z

Attempting dry run of processing paper acceptance...

editorialbot · 2025-01-14T11:46:46Z

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

✅ OK DOIs

- 10.1007/s10669-020-09784-x is OK
- 10.48550/arXiv.2404.06370 is OK
- 10.1016/j.envsoft.2021.105208 is OK
- 10.1016/S0377-2217(97)00163-X is OK
- 10.1016/j.dss.2022.113848 is OK
- 10.1016/j.softx.2023.101368 is OK
- 10.21105/joss.04567 is OK
- 10.1016/j.envsoft.2020.104890 is OK
- 10.1016/j.omega.2017.04.007 is OK
- 10.1007/978-1-4757-2500-1_2 is OK
- 10.1007/0-387-31099-1_2 is OK
- 10.1007/s11205-017-1832-9 is OK
- 10.1016/j.ecolind.2018.06.009 is OK
- 10.1016/j.ecolind.2019.105731 is OK
- 10.1016/j.ijggc.2016.08.023 is OK
- 10.1007/978-1-4939-3094-4_12 is OK
- 10.1016/j.ecolind.2014.05.014 is OK

🟡 SKIP DOIs

- No DOI given, and none found for title: The global competitiveness report 2018

❌ MISSING DOIs

- None

❌ INVALID DOIs

- None

editorialbot · 2025-01-14T11:48:10Z

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

Check final proof 👉📄 Download article

If the paper PDF and the deposit XML files look good in openjournals/joss-papers#6335, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

mspada · 2025-01-14T12:35:26Z

@editorialbot accept

editorialbot · 2025-01-14T12:35:29Z

I'm sorry @mspada, I'm afraid I can't do that. That's something only eics are allowed to do.

mspada · 2025-01-14T12:37:24Z

@samhforbes I checked the pdf and the repository and all look fine to me.

samhforbes · 2025-01-14T16:43:20Z

Hi @mspada just a couple of things to fix I can see in references:

Bouyssou et al capitalisation should probably be: Problem formulation and structuring: The decision aiding process. In Evaluation and Decision Models with Multiple Criteria: Stepping Stones for the Analyst
Greco et al capitalisation should be: On the methodological framework of composite indices: A review of the issues of weighting, aggregation, and robustness. Social Indicators Research
Typo in Pereira et al: Journal should be arXiv
Roy should be Decision aiding: Major actors and the role of models
Likewise Stewart and Durbach should be uncertainties rather than Uncertainties

mspada · 2025-01-15T19:51:18Z

@editorialbot generate pdf

editorialbot · 2025-01-15T19:52:55Z

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

mspada · 2025-01-15T19:55:00Z

@samhforbes thanks for the feedback on the references. I just corrected them

samhforbes · 2025-01-16T13:44:36Z

@editorialbot accept

editorialbot · 2025-01-16T13:44:39Z

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

editorialbot · 2025-01-16T13:51:47Z

Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository.

If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file.

You can copy the contents for your CITATION.cff file here:

CITATION.cff

cff-version: "1.2.0"
authors:
- family-names: Catalli
  given-names: Flaminia
  orcid: "https://orcid.org/0000-0003-0515-5282"
- family-names: Spada
  given-names: Matteo
  orcid: "https://orcid.org/0000-0001-9265-9491"
doi: 10.5281/zenodo.13694286
message: If you use this software, please cite our article in the
  Journal of Open Source Software.
preferred-citation:
  authors:
  - family-names: Catalli
    given-names: Flaminia
    orcid: "https://orcid.org/0000-0003-0515-5282"
  - family-names: Spada
    given-names: Matteo
    orcid: "https://orcid.org/0000-0001-9265-9491"
  date-published: 2025-01-16
  doi: 10.21105/joss.06190
  issn: 2475-9066
  issue: 105
  journal: Journal of Open Source Software
  publisher:
    name: Open Journals
  start: 6190
  title: "ProMCDA: A Python package for Probabilistic Multi-Criteria
    Decision Analysis"
  type: article
  url: "https://joss.theoj.org/papers/10.21105/joss.06190"
  volume: 10
title: "ProMCDA: A Python package for Probabilistic Multi-Criteria
  Decision Analysis"

If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation.

Find more information on .cff files here and here.

editorialbot · 2025-01-16T13:51:52Z

🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘

editorialbot · 2025-01-16T13:51:53Z

🦋🦋🦋 👉 Bluesky post for this paper 👈 🦋🦋🦋

editorialbot · 2025-01-16T13:51:54Z

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

Here's what you must now do:

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

Any issues? Notify your editorial technical team...

samhforbes · 2025-01-16T13:56:25Z

@Flaminietta and @mspada congrats on your publication!
Thanks to @limengbinggz, @B3J4y, @paulrougieux for reviewing, and of course @galessiorob for editing!

editorialbot · 2025-01-16T13:56:28Z

🎉🎉🎉 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.06190/status.svg)](https://doi.org/10.21105/joss.06190)

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

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

This is how it will look in your documentation:

We need your help!

The 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://reviewers.joss.theoj.org/join
Making a small donation to support our running costs here: https://numfocus.org/donate-to-open-journals

mspada · 2025-01-19T16:32:54Z

Thank you for the acceptance and the work and support @samhforbes and @galessiorob!
I'd like also to thank you @limengbinggz @B3J4y and @paulrougieux for the reviews, which help us improving both the manuscript and the code!

Flaminietta · 2025-01-19T19:23:58Z

Dear all, I can only echo what Matteo said, thank you for your work! Best, Flaminia

…

On 19. Jan 2025, at 17:33, Matteo Spada ***@***.***> wrote: Thank you for the acceptance and the work and support @samhforbes and @galessiorob! I'd like also to thank you @limengbinggz @B3J4y and @paulrougieux for the reviews, which help us improving both the manuscript and the code! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

editorialbot added HTML Python review TeX Track: 4 (SBCS) Social, Behavioral, and Cognitive Sciences labels Jan 8, 2024

editorialbot assigned galessiorob Jan 8, 2024

editorialbot mentioned this issue Jan 8, 2024

[PRE REVIEW]: ProMCDA: A Python package for Probabilistic Multi-Criteria Decision Analysis #6137

Closed

paulrougieux mentioned this issue Jan 31, 2024

Paper: add plots to illustrate some of the package's functionality wetransform-os/ProMCDA#23

Closed

editorialbot added the recommend-accept Papers recommended for acceptance in JOSS. label Jan 14, 2025

editorialbot added accepted published Papers published in JOSS labels Jan 16, 2025

samhforbes closed this as completed Jan 16, 2025

[REVIEW]: ProMCDA: A Python package for Probabilistic Multi-Criteria Decision Analysis #6190

[REVIEW]: ProMCDA: A Python package for Probabilistic Multi-Criteria Decision Analysis #6190

Comments

editorialbot commented Jan 8, 2024 • edited by galessiorob Loading

Status

Reviewer instructions & questions

Checklists

editorialbot commented Jan 8, 2024

editorialbot commented Jan 8, 2024

editorialbot commented Jan 8, 2024

editorialbot commented Jan 8, 2024

editorialbot commented Jan 8, 2024

galessiorob commented Jan 8, 2024

galessiorob commented Jan 8, 2024

B3J4y commented Jan 9, 2024 • edited Loading

Review checklist for @B3J4y

Conflict of interest

Code of Conduct

General checks

Functionality

Documentation

Software paper

B3J4y commented Jan 9, 2024 • edited Loading

paulrougieux commented Jan 9, 2024

Flaminietta commented Jan 9, 2024

editorialbot commented Jan 9, 2024

Flaminietta commented Jan 9, 2024

editorialbot commented Jan 9, 2024

Flaminietta commented Jan 9, 2024

editorialbot commented Jan 9, 2024

limengbinggz commented Jan 9, 2024 • edited Loading

Review checklist for @limengbinggz

Conflict of interest

Code of Conduct

General checks

Functionality

Documentation

Software paper

galessiorob commented Jan 15, 2024

B3J4y commented Jan 18, 2024

B3J4y commented Jan 18, 2024 • edited Loading

paulrougieux commented Jan 31, 2024

editorialbot commented Jan 31, 2024

mspada commented Dec 20, 2024

editorialbot commented Dec 20, 2024

mspada commented Dec 20, 2024 • edited Loading

mspada commented Jan 14, 2025

samhforbes commented Jan 14, 2025

samhforbes commented Jan 14, 2025

editorialbot commented Jan 14, 2025

editorialbot commented Jan 14, 2025

editorialbot commented Jan 14, 2025

mspada commented Jan 14, 2025

editorialbot commented Jan 14, 2025

mspada commented Jan 14, 2025

samhforbes commented Jan 14, 2025

mspada commented Jan 15, 2025

editorialbot commented Jan 15, 2025

mspada commented Jan 15, 2025

samhforbes commented Jan 16, 2025

editorialbot commented Jan 16, 2025

editorialbot commented Jan 16, 2025

editorialbot commented Jan 16, 2025

editorialbot commented Jan 16, 2025

editorialbot commented Jan 16, 2025

samhforbes commented Jan 16, 2025

editorialbot commented Jan 16, 2025

mspada commented Jan 19, 2025 • edited Loading

Flaminietta commented Jan 19, 2025 via email

editorialbot commented Jan 8, 2024 •

edited by galessiorob

Loading

B3J4y commented Jan 9, 2024 •

edited

Loading

B3J4y commented Jan 9, 2024 •

edited

Loading

limengbinggz commented Jan 9, 2024 •

edited

Loading

B3J4y commented Jan 18, 2024 •

edited

Loading

mspada commented Dec 20, 2024 •

edited

Loading

mspada commented Jan 19, 2025 •

edited

Loading