Open MaximilianV opened 5 years ago
fa3aef846efc49c1ca1e337e175bc521efb2ace4 removed the Problem Definition
from resource activities. Now only the Method
can be selected, which is called Recipe
in Rembrandt.
In 52642e2b83e88d52b0b11c1c7ee21bcfc3b71fae, the hard-coded mock url was removed and replaced by a resource api helper. The api helper accesses the same config file as the gryphon front-end.
c0a0ab4217b5c3288d0aacf796ff5c89adadb48f partly solves the third problem. Now the resource task validator relies on information coming directly from Rembrandt (including the inputs and outputs of a optimization method/recipe). But still, gryphon requires explicit modeling of input and output data objects, even though they don't have any effect at deployment time.
So far, there are some flaws, imperfections or logical issues on the
resource/dev
branch, that need to be solved before merging:Problem Definition
andOptimization Method
. But those have to be selected in the Gryphon modeler.public_src
, notserver_src
.)