This issue is much simpler. We should prepare sets of JSONs for GE for the models they have been working with to assist them in making the transition from using GrFN2 + ExprTree JSONs to using GrFN3 JSON.
Note: all references in this issue are for the grfn2gromet branch. I'm not sure whether the references are correct on master.
Tasks
Prepare the following three JSON objects for any model of interest to GE:
model_name--GrFN.json
model_name--GrFN3.json
model_name--expr-trees.json
Helpful tips
The code for transforming lambda expressions into expr-trees exists both as a standalone script and as a function in automates/model_assembly/networks.py. The same core library is used and the calls are done for each expression function in GrFN whether we are talking 2.0 or 3.0.
The script where the expr-trees are formed is located at: scripts/model_assembly/expression_walker.py
The method in GrFN3 generation that performs the same function for each ExpressionFuncNode is located at: automates/model_assembly/networks.py::BaseFuncNode::expression_to_expr_nodes()
If necessary, it should be possible to use the second function to generate the information needed to form the expr-tree JSON during GrFN3 translation. I'm not sure if that will make things easier, but I wanted you both to know about that as an option.
Overview
This issue is much simpler. We should prepare sets of JSONs for GE for the models they have been working with to assist them in making the transition from using GrFN2 + ExprTree JSONs to using GrFN3 JSON.
Note: all references in this issue are for the
grfn2gromet
branch. I'm not sure whether the references are correct onmaster
.Tasks
model_name--GrFN.json
model_name--GrFN3.json
model_name--expr-trees.json
Helpful tips
The code for transforming lambda expressions into expr-trees exists both as a standalone script and as a function in
automates/model_assembly/networks.py
. The same core library is used and the calls are done for each expression function in GrFN whether we are talking 2.0 or 3.0.scripts/model_assembly/expression_walker.py
automates/model_assembly/networks.py::BaseFuncNode::expression_to_expr_nodes()
If necessary, it should be possible to use the second function to generate the information needed to form the expr-tree JSON during GrFN3 translation. I'm not sure if that will make things easier, but I wanted you both to know about that as an option.