You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current DAG implementation is utterly unoptimized and thus leads to long runtime for calculation of methods such as depth. This must be optimized to reduce the runtime.
Tips
Max depth should be stored after each operation that is applied to the DAG to avoid recomputation with get_depth calls. This should become an attribute.
Ideally, this should be rewritten in a more performant library or even language and be binded to python for the UI.
The text was updated successfully, but these errors were encountered:
Optimization of DAG module
Description
The current DAG implementation is utterly unoptimized and thus leads to long runtime for calculation of methods such as depth. This must be optimized to reduce the runtime.
Tips
get_depth
calls. This should become an attribute.The text was updated successfully, but these errors were encountered: