search

iut-ibk / DynaMind-ToolBox

DynaMind-ToolBox
www.dance4water.org
GNU General Public License v2.0
9 stars 6 forks source link

Groups with just an outport #216

Closed christianurich closed 11 years ago

christianurich commented 11 years ago

I just tried to organise my simulations and wanted to create a group for data import. Is it possible to create a group with just an outport?

zacharias2k commented 11 years ago

Yes, but not with a loop group.

Von Samsung Mobile gesendet

-------- Ursprüngliche Nachricht -------- Von: Christian Urich notifications@github.com Datum: 03.09.2013 4:52 (GMT+01:00) An: iut-ibk/DynaMind-ToolBox DynaMind-ToolBox@noreply.github.com Cc: zacharias2k m.sengthaler@gmail.com Betreff: [DynaMind-ToolBox] Groups with just an outport (#216)

I just tried to organise my simulations and wanted to create a group for data import. Is it possible to create a group with just an outport?

— Reply to this email directly or view it on GitHub.

zacharias2k commented 11 years ago

To be more precise: i plan to create a "plain" container, really just to en-group modules, organize simulations as you said - will implement that soon.

christianurich commented 11 years ago

why not just use the loop group? Would even have the advantage that if I decided to execute the "plain" container several times I simple increase the counter.

zacharias2k commented 11 years ago

Because it makes no sense e.g. to have a out-port-only-loop. The container can be much more lightweight, reducing code complexity and branching - as there is no data back-feeding and thus no expensive computation necessary. Plus it can be auto generated (e.g. out of a sim file - automatic in/out port creation) - a loop group would have ambiguous connections etc.

christianurich commented 11 years ago

I just suggest it because it is probably implemented in 15 min and would help heaps in the model development. Whereas creating a whole other group takes time that we don't have at the moment since there are far more important things to do.

Branching should anyway just happen when the data stream is actually forked even when using loop groups. And I can't imagine that we gain a lot out of reducing the "complexity" of the data stream checking since it's not like we use this a million times during a simulation.

I don't get the second point at all.

zacharias2k commented 11 years ago

A simple container group wouldn't take much time. But anyway, i got the time, i will implement it soon.

Branching as term of computer science, not Dynamind-System-Branching. Code complexity, not execution complexity, and least of all stream checking. The second point is a suggested feature for auto generated module-links.

christianurich commented 11 years ago

as said before the focus should be set on the import things like view, links and finally the db. So I'll close this until and we come back if it is needed later.