chore: Add validation of parameters

[mhovd]

Ensures that the parameter ranges are valid prior to initialization

[Copilot]

Pull Request Overview

This PR adds validation for parameter bounds before sampling and renames accessor methods in the Prior enum.

• Renamed get_points → points and get_seed → seed, with updated doc comments
• Added a loop in sample_space to validate that each parameter’s bounds are finite, properly ordered, and non-zero

Comments suppressed due to low confidence (1)

src/routines/initialization/mod.rs:68

• These new validation branches lack unit tests. Consider adding tests that exercise infinite bounds, reversed bounds, and zero‐range parameters to ensure each bail condition behaves as expected.

for param in settings.parameters().iter() {

[github-actions]

Bencher Report

Branch	parameter-validation
Testbed	orion

Click to view all benchmark results

Benchmark	Latency	Benchmark Result seconds (s) (Result Δ%)	Upper Boundary seconds (s) (Limit %)
bimodal_ke_fit	📈 view plot 🚷 view threshold	9.71 s (-40.47%) Baseline: 16.31 s	26.62 s (36.46%)

🐰 View full continuous benchmarking report in Bencher

[Copilot]

Pull Request Overview

This PR adds validation to ensure that parameter ranges are valid prior to initialization, preventing infinite bounds and invalid orderings. In addition, the PR refactors getter method names from get_points/get_seed to more idiomatic points/seed, while incorporating inline documentation for clarity.

Comments suppressed due to low confidence (1)

src/routines/initialization/mod.rs:68

• Consider adding unit tests for the new parameter validation logic to ensure that the bail! calls are triggered as expected for infinite bounds and invalid ranges.

for param in settings.parameters().iter() {