This is a bit of a "temporary" solution, used while the modeling and intertypes are still being fleshed out. Eventually I think that we will want the interface to every type of model including decapodes, to be from the same place. For now though, I've created ACSets for StockFlow and RegNets that hold all of the information needed to create an MTK model. JSON AMR models get parsed in to these ACSets, which are then turned in to MTK models. This is kind of like what I'm anticipation will happen for every type of model in the future, i.e. JSON -> ACSet -> MTK. The way this is implemented will probably change in the future, but this gets it working for now.
This addresses issues https://github.com/DARPA-ASKEM/sciml-service/issues/120 and https://github.com/DARPA-ASKEM/sciml-service/issues/118.
This is a bit of a "temporary" solution, used while the modeling and intertypes are still being fleshed out. Eventually I think that we will want the interface to every type of model including decapodes, to be from the same place. For now though, I've created ACSets for StockFlow and RegNets that hold all of the information needed to create an MTK model. JSON AMR models get parsed in to these ACSets, which are then turned in to MTK models. This is kind of like what I'm anticipation will happen for every type of model in the future, i.e. JSON -> ACSet -> MTK. The way this is implemented will probably change in the future, but this gets it working for now.