Skip to content

Conversation

@Samuel-amap
Copy link
Collaborator

Alternate (and possibly more promising, or could with more changes lead to a more promising) approach to multitimestep : a softdependencynode computes its timestep-mapped outputs directly into its status. This meshes better with the current mapping implementation, and avoids other redundancies. More discussions to come.

…mesteps handled, but bad meshing with refvalue/refvectors cause overwrites if we use multiscale mappings, and unexplored issues if we avoid them. Also, many-node to many-node issues if multiscale mapping. Some TODO comments, structs, commented out code and notes are outdated. More exploration and cleanup required, but current state is much more interesting than the previous commit.
…imestep-mapped variables from their source, to avoid overwriting source (inputs to non-default-timestep models are changed by the accumulation function so can't be a simple Ref to source)
…eModels, which should enable better meshing with current mapping structures. More work needed
…tigate. More tests to implement, and other tests to fix, etc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants