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
This seems redundant, not to mention error-prone when developing and maintaining.
With more and more custom pipelines emerging and people start thinking about pipeline organization more (e.g. #1758 ), it would be good to have pipeline registration in just one place.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Currently we have two pipeline registries:
https://github.com/PennyLaneAI/catalyst/blob/main/frontend/catalyst/pipelines.py: the frontend pipeline is used by default qjit program flow
https://github.com/PennyLaneAI/catalyst/blob/main/mlir/lib/Driver/Pipelines.cpp: the cpp pipeline is used by cli and things like having stage names in the pipeline being passed into the
pipeline
kwarg on qjit, e.g. in the oqd, mbqc, ppm pytests.This seems redundant, not to mention error-prone when developing and maintaining.
With more and more custom pipelines emerging and people start thinking about pipeline organization more (e.g. #1758 ), it would be good to have pipeline registration in just one place.
The text was updated successfully, but these errors were encountered: