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
For NimbusML we have a "ManifestGenerator" that creates the EntryPoint manifest.json from a given set of ML.NET assemblies. Currently we implement this the same way it is implemented in TestEntryPoints.cs, but ConsoleEnvironment has been made internal, and ML.Context doesn't have a ComponentCatalog. What are ways I could get access to a ComponentCatalog and use JsonManifestUtils to build a new manifest.json?
Probably more importantly is figuring out how to load the assemblies in NimbusML's bridge to ML.NET now that the items in the ComponentCatalog have been internalized:
For NimbusML we have a "ManifestGenerator" that creates the EntryPoint manifest.json from a given set of ML.NET assemblies. Currently we implement this the same way it is implemented in TestEntryPoints.cs, but ConsoleEnvironment has been made internal, and ML.Context doesn't have a ComponentCatalog. What are ways I could get access to a ComponentCatalog and use JsonManifestUtils to build a new manifest.json?
@Ivanidzo4ka @yaeldekel @ganik
The text was updated successfully, but these errors were encountered: