dev date change and better 0.2 release notes

Author: maureeungaro

.github/workflows/dev_release.yml

@@ -16,7 +16,7 @@ jobs:
   dev-release:
     runs-on: ubuntu-latest
     env:
-      DEVMD_SINCE: "2026-04-29"   # optional fixed start date
+      DEVMD_SINCE: "2026-05-21"   # optional fixed start date
       TAG_NAME: "dev"             # reuse the same tag each night
       RELEASE_TITLE: "Dev Nightly"
     steps:

.github/workflows/update-binder.yml

@@ -18,7 +18,7 @@ fi
 echo "[devmd] branch = $BRANCH"
 
 # --- Time window (optional) ---
-SINCE="2026-04-29" # Manually set the start date for commits
+SINCE="2026-05-21" # Manually set the start date for commits
 
 UNTIL="${DEVMD_UNTIL:-}"   # e.g. 2025-09-01
 FLAGS=""

ci/update-devmd.sh

@@ -1,44 +1,51 @@
-This version features:
+This version includes:
 
 - Support for the LUND generator format
 - Installed environment setup scripts for easier GEMC usage
-- Installed analyzer scripts
+- Python analyzer
 - Additional examples
 - Jupyter support
 - Various bug fixes and improvements
 
-# Release notes
+<br/>
+
+## Release notes
 
 - Cleaned up registry container names and improved the CI summary
 - Added a more robust algorithm to determine the GEMC version from the GitHub tag
 - Updated Assimp to 6.0.5
-- Examples added:
+- Added examples:
     - Simple_Flux
     - Materials
     - PyVista
     - Cherenkov
 
-## New Developments
+<br/>
+
+## New developments
 
 - Support for the LUND generator format through the generator factory. Events are distributed over Geant4 threads.
-- Installed the Python analyzer package alongside GEMC
-- Jupyter support for the examples
+- Installed the Python analyzer package alongside GEMC.
+- Added Jupyter support for the examples and quickstart.
 - Added installed `gemc.sh` and `gemc.csh` environment setup scripts so users
   can source one file to configure `PATH`, library paths, and `PYTHONPATH`.
   The scripts add both the installed `bin` and `api` directories to `PATH`,
   since the `api` directory includes executables.
-- Added vtk export to the API (needs additional pyvista module `pip install "pyvista[jupyter]"`)
-
+- Added VTK export to the API. This requires the optional PyVista Jupyter extras:
+  `pip install "pyvista[jupyter]"`.
+- Included various bug fixes and improvements.
 
-# Addressed Issues
+<br/>
 
+## Addressed issues
 
 - [Issue #87](https://github.com/gemc/src/issues/87): Support the LUND generator format
 - [Issue #83](https://github.com/gemc/src/issues/83): Install environment setup scripts
 - [Issue #82](https://github.com/gemc/src/issues/82): Add analyzer scripts
 - [Issue #81](https://github.com/gemc/src/issues/81): Fix Cherenkov bug and add example (thanks to Zhiwen)
 - [Issue #79](https://github.com/gemc/src/issues/79): Add Jupyter support
 
+<br/>
 
 ## Supported platforms
 
@@ -51,15 +58,15 @@ Both x86_64 and ARM64 platforms are supported.
 - Debian: 13
 - Arch Linux: latest
 
-
+<br/>
 
 ## Dependencies
 
 - Geant4: 11.4.1 or higher
 - CLHEP: 2.4.6.0 or higher
 - Xerces-C: 3.2 or higher
 
-
+<br/>
 
 ## Detailed list of changes and fixes
 
@@ -71,33 +78,32 @@ Both x86_64 and ARM64 platforms are supported.
 - Fixed CI tests not exiting after failures
 - Fixed the Python API not resetting ASCII files for new variations
 - Fixed `g4view` option help
-- Added screenshot bool and function in `GRunAction::EndOfRunAction`
-- Added cloud style for volumes (0=wireframe, 1=solid, 2=cloud)
+- Added a screenshot boolean and function in `GRunAction::EndOfRunAction`
+- Added cloud style for volumes (`0=wireframe`, `1=solid`, `2=cloud`)
 - YAML files are more consistent across examples
 - Installed the Python analyzer package alongside GEMC, matching the existing installed API layout.
 - Added installed `gemc.sh` and `gemc.csh` environment setup scripts that configure
   `PATH`, library paths, and `PYTHONPATH`, including the installed `api` directory
   on `PATH`
 - Cleaned up Meson test behavior by fixing duplicate test names and making
   ROOT-dependent tests conditional on ROOT availability
-- Using $SIM_HOME instead of $GEMC for installation paths
-- Pre-load streamer plugins before Geant4 creates worker threads
-- gemc.cc preloads only whatever streamers are actually configured.
-- Temporarely protecting, on linux, explicit G4VisExecutive teardown. This is a possible
+- Used `$SIM_HOME` instead of `$GEMC` for installation paths
+- Preloaded streamer plugins before Geant4 creates worker threads
+- `gemc.cc` preloads only the streamers that are configured.
+- Temporarily protected explicit `G4VisExecutive` teardown on Linux. This is a possible
   Geant4 bug: a double-free in a process-wide G4Colour map during static destruction
-- Added workournd for Undefined sanitizer on Linux by using `LD_PRELOAD`
-- Common version of libraries and os/version for deployment and sanitizer workflows
-- More consistent ci workflow job names
-- Added LUND input format through gmanager
-- Distributing LUND events along with gparticles event to Geant4 threads
+- Added a workaround for UndefinedBehaviorSanitizer on Linux by using `LD_PRELOAD`
+- Used common library and OS/version definitions for deployment and sanitizer workflows
+- Made CI workflow job names more consistent
+- Added the LUND input format through `gmanager`
+- Distributed LUND events and `gparticles` events to Geant4 threads
 - Added VTK capabilities: examples now display the interactive view
-- Added vertex information to true and digitized infos
-- Fixed a missing closing brace in the JSON format 
-- Adjusted system_template to provide simpler geometry and methane target material
-- Adjusted simple_flux target material to G4_lH2
-- Added handling of style=2 in pyvista: using cloud
-- Fixed wireframe rendering in pyvista
-- Better pyvista example
-- Added g4light option to g4camera to set the light direction
+- Added vertex information to true and digitized data
+- Fixed a missing closing brace in the JSON format
+- Adjusted `system_template` to provide simpler geometry and methane target material
+- Adjusted `simple_flux` target material to `G4_lH2`
+- Added handling of `style=2` in PyVista by using cloud rendering
+- Fixed wireframe rendering in PyVista
+- Improved the PyVista example
+- Added the `g4light` option to `g4camera` to set the light direction
 - Fixed not assigning optical properties to materials when they were set to zero
-- Various code cleanups