Will TensorFlow 2.0 support common Machine Learning libraries stated below?












0















With the exciting new features of TensorFlow 2.0, may I know if TensorFlow 2.0 will still support the common machine learning techniques as stated below?




  • Linear Regression

  • Logistic Regression

  • K-Means Clustering


  • K-Nearest Neighbors


  • Random Forest


  • Naive Bayes

  • Support Vector Machine


Thank you very much for your time and clarification in advance.










share|improve this question























  • There are some words about compatibility in the original announcement, but I don't think you'll get anything more specific before an actual release. tf.contrib as such will not exist, and subproject maintainers will be responsible for compatibility ("we will work with the respective owners on detailed migration plans", "we are looking for owners/maintainers for a number of projects currently in tf.contrib"). I'd assume everything officially supported now will be there, but no guarantees about tf.contrib.

    – jdehesa
    Nov 28 '18 at 11:29
















0















With the exciting new features of TensorFlow 2.0, may I know if TensorFlow 2.0 will still support the common machine learning techniques as stated below?




  • Linear Regression

  • Logistic Regression

  • K-Means Clustering


  • K-Nearest Neighbors


  • Random Forest


  • Naive Bayes

  • Support Vector Machine


Thank you very much for your time and clarification in advance.










share|improve this question























  • There are some words about compatibility in the original announcement, but I don't think you'll get anything more specific before an actual release. tf.contrib as such will not exist, and subproject maintainers will be responsible for compatibility ("we will work with the respective owners on detailed migration plans", "we are looking for owners/maintainers for a number of projects currently in tf.contrib"). I'd assume everything officially supported now will be there, but no guarantees about tf.contrib.

    – jdehesa
    Nov 28 '18 at 11:29














0












0








0








With the exciting new features of TensorFlow 2.0, may I know if TensorFlow 2.0 will still support the common machine learning techniques as stated below?




  • Linear Regression

  • Logistic Regression

  • K-Means Clustering


  • K-Nearest Neighbors


  • Random Forest


  • Naive Bayes

  • Support Vector Machine


Thank you very much for your time and clarification in advance.










share|improve this question














With the exciting new features of TensorFlow 2.0, may I know if TensorFlow 2.0 will still support the common machine learning techniques as stated below?




  • Linear Regression

  • Logistic Regression

  • K-Means Clustering


  • K-Nearest Neighbors


  • Random Forest


  • Naive Bayes

  • Support Vector Machine


Thank you very much for your time and clarification in advance.







tensorflow






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 27 '18 at 23:12









Admond LeeAdmond Lee

11




11













  • There are some words about compatibility in the original announcement, but I don't think you'll get anything more specific before an actual release. tf.contrib as such will not exist, and subproject maintainers will be responsible for compatibility ("we will work with the respective owners on detailed migration plans", "we are looking for owners/maintainers for a number of projects currently in tf.contrib"). I'd assume everything officially supported now will be there, but no guarantees about tf.contrib.

    – jdehesa
    Nov 28 '18 at 11:29



















  • There are some words about compatibility in the original announcement, but I don't think you'll get anything more specific before an actual release. tf.contrib as such will not exist, and subproject maintainers will be responsible for compatibility ("we will work with the respective owners on detailed migration plans", "we are looking for owners/maintainers for a number of projects currently in tf.contrib"). I'd assume everything officially supported now will be there, but no guarantees about tf.contrib.

    – jdehesa
    Nov 28 '18 at 11:29

















There are some words about compatibility in the original announcement, but I don't think you'll get anything more specific before an actual release. tf.contrib as such will not exist, and subproject maintainers will be responsible for compatibility ("we will work with the respective owners on detailed migration plans", "we are looking for owners/maintainers for a number of projects currently in tf.contrib"). I'd assume everything officially supported now will be there, but no guarantees about tf.contrib.

– jdehesa
Nov 28 '18 at 11:29





There are some words about compatibility in the original announcement, but I don't think you'll get anything more specific before an actual release. tf.contrib as such will not exist, and subproject maintainers will be responsible for compatibility ("we will work with the respective owners on detailed migration plans", "we are looking for owners/maintainers for a number of projects currently in tf.contrib"). I'd assume everything officially supported now will be there, but no guarantees about tf.contrib.

– jdehesa
Nov 28 '18 at 11:29












1 Answer
1






active

oldest

votes


















0














The models that you mention above will still definitely be supported in TensorFlow 2.0 as part of tf.estimator. If you are using a symbol in TensorFlow 1.x that is currently housed in tf.contrib, it will either be deprecated, transitioned to the tensorflow/addons repo, or moved into the core TF 2.0 API.



You can check out the RFCs below for more detailed changes:




  • TensorFlow Namespaces

  • Sunsetting tf.contrib

  • Move from tf.contrib to tensorflow/addons






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53509654%2fwill-tensorflow-2-0-support-common-machine-learning-libraries-stated-below%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The models that you mention above will still definitely be supported in TensorFlow 2.0 as part of tf.estimator. If you are using a symbol in TensorFlow 1.x that is currently housed in tf.contrib, it will either be deprecated, transitioned to the tensorflow/addons repo, or moved into the core TF 2.0 API.



    You can check out the RFCs below for more detailed changes:




    • TensorFlow Namespaces

    • Sunsetting tf.contrib

    • Move from tf.contrib to tensorflow/addons






    share|improve this answer




























      0














      The models that you mention above will still definitely be supported in TensorFlow 2.0 as part of tf.estimator. If you are using a symbol in TensorFlow 1.x that is currently housed in tf.contrib, it will either be deprecated, transitioned to the tensorflow/addons repo, or moved into the core TF 2.0 API.



      You can check out the RFCs below for more detailed changes:




      • TensorFlow Namespaces

      • Sunsetting tf.contrib

      • Move from tf.contrib to tensorflow/addons






      share|improve this answer


























        0












        0








        0







        The models that you mention above will still definitely be supported in TensorFlow 2.0 as part of tf.estimator. If you are using a symbol in TensorFlow 1.x that is currently housed in tf.contrib, it will either be deprecated, transitioned to the tensorflow/addons repo, or moved into the core TF 2.0 API.



        You can check out the RFCs below for more detailed changes:




        • TensorFlow Namespaces

        • Sunsetting tf.contrib

        • Move from tf.contrib to tensorflow/addons






        share|improve this answer













        The models that you mention above will still definitely be supported in TensorFlow 2.0 as part of tf.estimator. If you are using a symbol in TensorFlow 1.x that is currently housed in tf.contrib, it will either be deprecated, transitioned to the tensorflow/addons repo, or moved into the core TF 2.0 API.



        You can check out the RFCs below for more detailed changes:




        • TensorFlow Namespaces

        • Sunsetting tf.contrib

        • Move from tf.contrib to tensorflow/addons







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 11 at 19:47









        dynamicwebpaigedynamicwebpaige

        627




        627
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53509654%2fwill-tensorflow-2-0-support-common-machine-learning-libraries-stated-below%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Contact image not getting when fetch all contact list from iPhone by CNContact

            count number of partitions of a set with n elements into k subsets

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks