Paper: Statement of need

[sscivier]

Issue raised as part of the JOSS review: openjournals/joss-reviews#9408.

One of the items on my review checklist for the paper is:

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?

The Statement of Need is present, well-written, and mostly complete. It clearly communicates the problems addressed by the software, highlights gaps in existing software, and helps position floatCSEP relative to existing efforts.

However, my impression is that the target audience is more implied than specified. I believe the section would benefit from a brief, explicit statement of target audiences and users.

Additionally, the final sentence of the statement ("The solution should manage...") may benefit from specifying that floatCSEP is designed to address these requirements, and briefly highlighting how it overcomes previous issues. This would help explicitly situate floatCSEP among existing software.

These are minor comments, and I'm happy for the authors to address them in whichever manner they consider best.

EDIT:

I additionally noticed a double citation (pandoc syntax and manual text side-by-side):

"...@mizrahi2024developing Mizrahi et al. (2024),..."

[pabloitu]

I addressed the reviews with #95. These two lines were changed and expanded:

This lack highlights the need for comprehensive software that provides Testing Center capabilities while remaining decoupled from specific hosting hardware.
The solution should manage the entire experiment lifecycle, from model integration and initial deployment, to the incremental updating of input data, forecasts, results, and reports as new observations become available.

with the following information:

That is, additional software is required that provides Testing Center capabilities while remaining decoupled from specific hosting hardware.
To meet this need, we developed floatCSEP, which manages the entire experiment lifecycle, from model integration and initial deployment to the incremental updating of input data, forecasts, results, and reports as new observations become available.
It is intended for earthquake forecast model developers, institutions that run CSEP-style forecasting experiments, and the broader statistical seismology community.

The reference typo was addressed in the floatcsep_joss manuscript branch with commit c89fec8

[sscivier]

@pabloitu -- Thanks for addressing the comments! I'll be happy to tick off that item on my review checklist once the PR #95 is merged.

[pabloitu]

Closed with #95