Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Execution Flow #48

Closed
MathisFederico opened this issue Nov 21, 2021 · 3 comments · Fixed by #98
Closed

Execution Flow #48

MathisFederico opened this issue Nov 21, 2021 · 3 comments · Fixed by #98
Assignees
Labels
enhancement New feature or request

Comments

@MathisFederico
Copy link
Member

MathisFederico commented Nov 21, 2021

Executing a cell should trigger other cells depending of the graph.

  • Cells before should be run if they have not already or have been modified
  • Cells after should be run if the socket allows for it depending on socket flowtype (Socket flowtype #47)

This should be sequentially at first, in a depth-first or breadth-first manner (this could be a user choice for both before and after cells).

@MathisFederico
Copy link
Member Author

MathisFederico commented Nov 23, 2021

To be smart, we could use the recent GIL removing method to multi-thread independent branches.

As we have a graph, we can implement a scheduling like in this exam subject also present in wikipedia.

For scheduling, #52 might be a requirement.

@MathisFederico
Copy link
Member Author

More precisely, cells should have two buttons now:

  • ">" on left running everything before and the block, if possible only not launched and/or modified blocks.
  • "»" on right with the same behavior as ">" but also updating following cells in the graph

@MathisFederico
Copy link
Member Author

Having tests function for those two behaviors would be a very nice add !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants