Skip to content

TensorFlowEstimator initialization info is missing #4932

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

Closed
vslynko opened this issue Mar 11, 2020 — with docs.microsoft.com · 1 comment · Fixed by #4941
Closed

TensorFlowEstimator initialization info is missing #4932

vslynko opened this issue Mar 11, 2020 — with docs.microsoft.com · 1 comment · Fixed by #4941
Labels
documentation Related to documentation of ML.NET P3 Doc bugs, questions, minor issues, etc.

Comments

Copy link

vslynko commented Mar 11, 2020

TensorFlowEstimator is not static and has no public constructors. Therefore the link to the documentation on how to initialize TensorFlowEstimator is essential.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@vslynko vslynko changed the title Initialization info is missing TensorFlowEstimator initialization info is missing Mar 11, 2020
@najeeb-kazmi
Copy link
Member

Hi @vslynko - thanks for reporting this. TensorFlowEstimator can only be initialized through the MLContext API entry point. Usage samples are available here.

You're right, this should be mentioned on the doc page for the estimator itself, in the see also section, just like other estimators. I'll mark this as a docs issue and put it on our backlog of work items.

@najeeb-kazmi najeeb-kazmi added documentation Related to documentation of ML.NET P3 Doc bugs, questions, minor issues, etc. labels Mar 11, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Mar 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Related to documentation of ML.NET P3 Doc bugs, questions, minor issues, etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants