This repository was archived by the owner on Oct 1, 2026. It is now read-only.
Repository navigation
Establish scientific model library and developer workflow - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scientific model library and developer workflow
R01 of the ecosystem delivery map. Establish PottsModels as the owner of
complete model factories and tutorials, using public Potts APIs rather than a
second executor. The companion Potts PR removes the displaced full examples.
Included
scientific references, and documented modeling assumptions.
explicit developer/test/documentation environments.
dependencies or requiring Potts/Core to depend on PottsModels.
Local validation
channel assertions passed.
Hosted CI is a separate required validation of this PR and has not been inferred
from those local results. The persistent-task Aqua check has a documented
exclusion because its fresh environment cannot resolve unregistered developed
dependencies; ordinary environment loading and precompilation were exercised.
Scope
These factories demonstrate bounded sequential-CPU models, not calibrated paper
reproductions or newly established GPU guarantees. The OpenVT-inspired example
does not establish a growing contact-inhibited tissue law. Broader models,
authoring features, and device combinations remain later work in the chain.