Skip to content

Simjecture 0.5.4rc2 — research recovery and clear simulation outputs

Pre-release
Pre-release

Choose a tag to compare

View all tags
@tomzhu0225 tomzhu0225 released this 04 Oct 08:14
· 33 commits to main since this release
v0.5.4rc2
ec72091
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This preview fixes the compact-context error that prematurely stopped a research campaign and makes selected simulation files easier to interpret.

  • Research recovery: derived context, journal and routine report errors recover with visible diagnostics. Primary scientific-state validation and final-report publication remain required. Early stop causes and unused budget remain visible after expiry.
  • Simulation files: generated run outputs appear separately from copied or modified inputs. Command files and cross-run reports have shared-file labels. New runs record input hashes; older snapshots retain their provenance limits.
  • Monitoring and review: expose role-level cached/uncached usage and submission-to-result latency; defer unchanged healthy-job strategy reviews within a 15-minute bound while retaining shorter operational checks and evidence-triggered reviews.
  • Documentation: refresh the README, installer links, citation metadata and FLASH guidance, with a detailed campaign audit and rc2 acceptance record.

Install on Linux or WSL:

curl -fsSL https://github.com/tomzhu0225/simjecture/releases/download/v0.5.4rc2/install.sh | bash

Python-package users can install simjecture==0.5.4rc2 after the publishing workflow completes. 0.5.3 remains the latest stable release. Existing research files and application versions are preserved.

Validation: 1,196 Python tests passed with seven optional-runtime skips, including recovery and simulation-categorization browser tests. All 14 DSH/MCP checks, lint, JavaScript syntax, public schemas, strict documentation, recorded CLI demos, package/archive checks and a fresh installation without model credentials passed. GitHub CI also verifies the full source and real WarpX qualification before publication.

The linked recovery continuation reached its recorded deadline with no supervisor/director error. It recorded 27 successful diagnostic/pilot jobs and 14 failed attempts; the reconnection contribution remains unresolved. This is a harness repair, not a scientific completion or lower-cost claim.

See PR #11, the rc2 acceptance record, campaign audit and changelog.

Assets 5
Loading