Skip to content

Intermediate Representation #20

Open
@sdesrozis

Description

@sdesrozis

We are currently thinking about a visual representation of building blocks composing an application : PyTorch objects, handlers, metrics, engines, etc. The idea is to provide a graphical helper to organise events and dataflow. In my knowledge, it is an original approach that could be complementary to our code generator (from templates).

To do this, the visual representation (from a graphical tool, in the spirit of PyFlow https://github.com/wonderworks-software/PyFlow) should be described in a specific representation used by a code generator. This representation could be similar to the intermediate representation (IR) used in compilation (e.g llvm, gcc). It helps optimisation, and code generation.

I wonder about merging our effort to have a unique representation. I mean

  • Templates -> IR -> code
  • Graphic Tool -> IR -> code

What do you think about that ?

Some insights

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions