Skip to content

Testing bmd package #12

@Zhenglei-BCS

Description

@Zhenglei-BCS

I am trying to add more documentation to bmd while testing and validating the package.

bmd pull request

Suggestions for Improvement

Documentation Improvements

  1. Comprehensive Vignettes:

    • Create step-by-step tutorials for common workflows
    • Include real-world examples for different response types
    • Provide guidance on model selection and interpretation
  2. Function Documentation:

    • Add more detailed examples to each function's documentation
    • Clarify parameter choices and their implications
    • Include references to statistical literature for advanced methods
  3. Theoretical Background:

    • Add more documentation explaining the statistical theory behind different BMD definitions
    • Explain when to use different confidence interval methods
    • Provide guidance on interpreting results

Code Structure and Functionality

  1. Code Organization:

    • Refactor code to improve consistency in function naming and parameter order
    • Group related functions into coherent files rather than having one function per file
    • Implement S3 methods consistently across all object types
  2. Error Handling:

    • Improve error messages to be more informative and actionable
    • Add input validation for major functions
    • Implement warning messages for potentially problematic parameter combinations
  3. Performance Optimization:

    • Optimize computationally intensive functions (especially bootstrapping)
    • Implement parallel processing options for bootstrap procedures
    • Consider using Rcpp for performance-critical calculations

New Features

  1. Expanded Model Types:

    • Add support for hormetic/non-monotonic dose-response models
    • Implement Bayesian dose-response models (brms ?)
    • Add time-to-event models for survival data
  2. Model Diagnostics:

    • Add comprehensive model diagnostic functions
    • Implement goodness-of-fit tests specific to dose-response models
    • Add residual analysis tools for different response types
  3. Export Capabilities:

    • Add functions to export results in formats compatible with regulatory submissions (maybe for drcHelper)
  4. Other thoughts

    • Develop interfaces to toxicological databases

Technical Improvements

  1. Testing Framework:

    • Implement comprehensive unit tests for all functions
    • Add integration tests for common workflows
    • Create benchmark tests for performance-critical functions
  2. Documentation Generation:

    • Use roxygen2 consistently for all documentation
    • Include mathematical formulas in documentation using LaTeX
    • Generate a package website using pkgdown

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions