This checklist should be completed after setting up the modernized development environment.
-
Install R (if not already installed)
# macOS brew install r # Ubuntu/Debian sudo apt-get install r-base r-base-dev
-
Run R setup script
./setup_r.sh
Expected: ggplot2 and mgcv packages installed successfully
-
Install Python dependencies with uv
# Install uv if needed curl -LsSf https://astral.sh/uv/install.sh | sh # Install dependencies uv pip install -r requirements.txt
Expected: All packages install without errors
-
Verify R integration
python -c "import rpy2.robjects as ro; ro.r('library(ggplot2)'); print('R integration works!')"Expected: No errors, prints "R integration works!"
-
Run tests
make testExpected: All tests pass
-
Quick render test (without notebook execution)
make qrender
Expected: Generates web/index.html from existing Examples.ipynb
-
Full build test (with notebook execution)
make render
Expected:
- Executes notebook successfully
- Generates all plot images in web/img/plots/
- Creates web/index.html
- No errors from any plotting library
- Verify plotly plots render without authentication
- Check that Kaleido is used for static image export (not Orca)
- Ensure all plotly examples in notebook still work
- Verify altair plots render to PNG
- Confirm altair-saver is not needed (using native rendering)
- Check selenium/geckodriver works for image export
- Verify all ggplot-style plots render correctly
- Check for any deprecation warnings
- Verify regression line plots work
- Check confidence interval calculations
- Verify %%R magic commands work
- Check data passing between Python and R
- Ensure all R ggplot2 examples render
- Verify geckodriver compatibility
- Check headless browser operations
- Test with xvfb if on Linux
- GitHub Actions workflow
- Push to a test branch
- Verify all workflow steps complete
- Check Netlify preview deploy works
- Merge to master and verify production deploy
- Note build time for comparison (old vs new)
- Check generated image file sizes
- Verify web/index.html loads correctly in browser
If critical issues are found:
- Keep Travis CI config (.travis.yml) until GitHub Actions is confirmed working
- Document any notebook cells that fail with new library versions
- Consider pinning problematic packages to older versions temporarily