Replies: 2 comments 2 replies
-
|
@riverma I cleaned up our brainstorm from yesterday. What do you think? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Adding @taddyb, @geosjim and @rileyhales to the brainstorm. Particularly interested in your thoughts on the data formats currently used in the |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This discussion is intended to outline the current thinking around
when and how to release RAPID v2.0.0, and to invite early
feedback.
RAPID v2 (https://github.com/c-h-david/rapid2) represents a substantial
redesign relative to RAPID v1 (https://github.com/c-h-david/rapid).
Although the scientific purpose is similar, the underlying architecture,
implementation language, and development philosophy have changed enough
to warrant a new repository and a deliberate release process.
Background
parallelism, targeting HPC environments.
Because of this shift, RAPID v2 should not be viewed as a drop-in
replacement for v1, but rather as a next-generation implementation with
overlapping goals.
At present:
This post aims to define a path toward a first stable public release.
Release Philosophy
and stabilize workflows:
v2.0.0-betav2.0.0-rc1,v2.0.0-rc2, ...The intent is to avoid prematurely freezing the software while still giving
users something concrete to test and comment on.
Community Feedback and Beta Testing
Before tagging v2.0.0, we would like to solicit feedback from a small
group of experienced RAPID users, focusing on real scientific use
cases rather than synthetic benchmarks.
Potential beta testers include collaborators from prior RAPID studies
Feedback from this group will help guide: - CLI stabilization - Workflow
clarity - Documentation priorities
Proposed Criteria for
v2.0.0-rc1The following items represent minimum readiness for a first release
candidate.
1. Minimal Scientific Capability
At minimum, RAPID v2 should be able to run end-to-end and produce scientifically meaningful output given:
Advanced capabilities (e.g., uncertainty quantification or data
assimilation) may exist in the codebase but are not required for
v2.0.0.
2. Codebase Stability
expected).
Potential CI improvements under consideration:
3. Sandbox
the released code.
4. Command-Line Interface (CLI)
--helpoutput--versionflagtqdmis candidate for this.5. Tutorial (Real Science Use Case)
This tutorial will serve as the primary reference example for new users.
6. Communication Channels
7. Website
The guiding principle is: > Incomplete but public is better than
complete but private. Minimum deliverable for this activity:
8. Versioning and Distribution
assumed here).
v2.0.0-rc1criteriaare met.
Next Steps
Feedback is very welcome, especially from users with prior RAPID
experience.
Beta Was this translation helpful? Give feedback.
All reactions