Data Layout and Flow

[SomeoneInParticular]

This discussion is mainly a place for use to, well, discuss how data should be managed by CART, and the class structure to accomplish that. Feel free to chime in and suggest any ideas, or provide feedback on existing ones!

[SomeoneInParticular]

I'll start: first suggestion is to formalize the data flow. I believe we discussed something like the following (which matches how Slicer itself manages modules):

Where, in our case, the [GUI] element is managed by our CARTWidget, and we don't have a [CLI] element yet.

[SomeoneInParticular]

Dot file used, if you would like to tinker with it: dataflow.dot.txt

[SomeoneInParticular]

@AcastaPaloma @Ivan-E-Johnson when you get the chance, please review this and confirm its validity (or correct/suggest alternatives)

[AcastaPaloma]

Yeah this makes sense;
Task is what the user is doing this session with CART;
Data Units are what the user is iterating through;
Data Manager deals with loading the resources;