Interval Parameters as options for to compute Ratio Parameter Calculations

[Gero1999]

Issue

Closes #1135

Description

Interval/partial parameters (e.g. AUCINT_0-20, AUMCINT_0-30) can now be selected as Test or Reference parameters in the Ratio Calculations table.

Key changes:

1. Wiring: int_parameters reactive from NCA settings is passed into ratios_table_server so the ratio module can read the current interval definitions.

2. UI dropdown: .build_interval_param_options() constructs range-suffixed entries from the int_parameters table (e.g. AUCINT_0-20), filtering out incomplete rows. These are merged into ratio_param_options() alongside the existing main-interval parameters.

3. Ratio computation: parse_interval_parameter() detects range-suffixed parameters and extracts the base PPTESTCD + start/end values. .filter_interval_results() pre-filters res$result to only the matching interval rows before calculate_ratios() runs. Uses start_dose/end_dose (dose-relative times) since int_parameters defines intervals relative to dose time. Non-interval parameters are unaffected.

Definition of Done

• Interval parameters from int_parameters() appear in the ratio Test/Ref Parameter dropdowns with range suffix (e.g. AUCINT_0-20)
• Dropdown updates reactively when int_parameters() changes
• calculate_ratio_app() correctly parses range-suffixed parameters and filters by start/end
• Existing ratio calculations for non-interval parameters are unaffected
• Unit tests cover interval parameter ratio scenarios
• Ratio calculations produce correct results for interval parameters (manual app verification)

How to test

1. Upload a dataset and configure interval/partial parameters in NCA > Settings (e.g. AUCINT with start=0, end=20).
2. Open the Ratio Calculations accordion — the interval parameters should appear in the Test/Ref Parameter dropdowns as AUCINT_0-20.
3. Add a ratio row using an interval parameter and run NCA — verify the ratio is computed correctly.
4. Change the interval definitions in Settings — verify the dropdown updates.
5. Verify existing (non-interval) ratio calculations still work as before.

Contributor checklist

• Code passes lintr checks
• Code passes all unit tests
• New logic covered by unit tests
• New logic is documented
• App or package changes are reflected in NEWS
• Package version is incremented
• R script works with the new implementation (if applicable)
• Settings upload works with the new implementation (if applicable)
• If any .scss change was done, run data-raw/compile_css.R

Notes to reviewer

• R is not available in the dev container, so devtools::document(), lintr::lint_package(), and devtools::test() could not be run locally. CI will validate these.
• The range suffix format (PARAM_start-end) follows the same convention already used in descriptive_statistics.R, nca_results.R, and parameter_plots.R.
• parse_interval_parameter() supports decimal start/end values (e.g. AUCINT_0.5-12.5).

[js3110]

Worked well for me :)

[Gero1999]

While reviewing myself I realized that doing a ratio of two interval parameters (e.g, AUCINT_0-20, AUCINT_0-30) was not working as expected (PKNCA run produced a warning: Ratio MRAUCINT_0-20 not computed.No comparable groups found between RefGroups (PARAM: DrugA)and TestGroups ((all other levels))).

Now it should be fixed