slibkind

Thanks for the feedback @rejuvyesh! This turned out to point to a bigger problem regarding extra allocations when composing systems, which has been fixed in PR #91. With the small...

One of the reasons that `dynamics` and `readout` have their type signatures restricted is that in order to compute the composite dynamics (e.g. the dynamics of two machines wired together),...

Neat! Thanks for sharing. [PR #89](https://github.com/AlgebraicJulia/AlgebraicDynamics.jl/pull/89) adds the functionality for evaluating the dynamics of a system with batch initial conditions and inputs, although so far only for systems composed using...

This is a great example @slwu89! To answer your questions about `oapply` and `induced_dynamics`. In both examples there are two things to keep track of: the states before the composition...

> I can replicate this "read only" idea with the existing resource sharers by simply saying the effect of these ports on their junctions is zero. I'll do this for...

Oh! I didn't understand that the state is entirely in the junctions. That would be a big difference between RSMs and the proposed algebra on UWDs with two ports. I...

We have not! This is a bit tangential, but one thing I was wondering about that is the morphisms of the operad can be specified by a $\mathcal C$-set where...

Unfortunately, there aren't (as of yet) any examples using the `@program` macro in AlgebraicDynamics

Great point! I added some documentation in PR #115. Do you think that clarifies the useage of `portmap`?

When adding labels for ResourceSharers improve interoperation between AlgebraicPetri and AlgebraicDynamics by ensuring that the labels on LabelledPetriNets are preserved