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
When executing a pipeline, the underlying interoperability framework typically need some configurations. In the case of dlite this would typically be where to search for entities, where to find plugins etc... Other interoperability frameworks will most likely have similar needs.
Since the strategies can be called either from oteapi-services or otelib, I think it make sense to add support for this in oteapi-core.
When using otelib, a natural place to provide such session-wide configurations may be via the get() method of the pipeline itself. Other possibilities could be via a dedicated session_configuration() method on the client or the pipeline.
The text was updated successfully, but these errors were encountered:
When executing a pipeline, the underlying interoperability framework typically need some configurations. In the case of dlite this would typically be where to search for entities, where to find plugins etc... Other interoperability frameworks will most likely have similar needs.
Since the strategies can be called either from oteapi-services or otelib, I think it make sense to add support for this in oteapi-core.
When using otelib, a natural place to provide such session-wide configurations may be via the get() method of the pipeline itself. Other possibilities could be via a dedicated
session_configuration()
method on the client or the pipeline.The text was updated successfully, but these errors were encountered: