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

[Feature Request] Methods to be added to Graph API. #211

Open
1 of 9 tasks
bheijden opened this issue Sep 12, 2022 · 0 comments
Open
1 of 9 tasks

[Feature Request] Methods to be added to Graph API. #211

bheijden opened this issue Sep 12, 2022 · 0 comments
Labels
enhancement New feature or request user-friendly Measure to improve user-friendliness (e.g. via defensive programming, erorr checking, etc...)

Comments

@bheijden
Copy link
Member

bheijden commented Sep 12, 2022

🚀 Feature

  • Graph._remove_engine(): Should replace all engine node graphs with the agnostic object definition and remove the added engine.
  • Graph._agnostic_object(name="obj"): Should replace the engine node graph with the agnostic object definitions.
  • Add engine to EngineGraph & automatically connect tick if EngineNode is added.
  • Add legend to dag graphs.
  • Add engine: EngineSpec as argument object engine methods.
  • Check that arguments of EngineSpec.add_object() are the same for Engine.add_object().
  • Per default, use the straight line style as it is less cluttered. Make linestyle an argument to the gui render function.
  • Visualize all registered EngineStates after an Object has been substituted by its EngineGraph.

Pitch

A clear and concise description of what you want to happen.

Checklist

  • I have checked that there is no similar issue in the repo (required)
@bheijden bheijden added enhancement New feature or request user-friendly Measure to improve user-friendliness (e.g. via defensive programming, erorr checking, etc...) labels Sep 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request user-friendly Measure to improve user-friendliness (e.g. via defensive programming, erorr checking, etc...)
Projects
None yet
Development

No branches or pull requests

1 participant