Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for initialize (0.19 sec)

  1. WORKSPACE

    # buildifier: disable=load-on-top
    
    workspace(name = "org_tensorflow")
    
    # buildifier: disable=load-on-top
    
    # We must initialize hermetic python first.
    load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
    
    http_archive(
        name = "bazel_skylib",
        sha256 = "74d544d96f4a5bb630d465ca8bbcfe231e3594e5aae57e1edbf17a6eb3ca2506",
        urls = [
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Fri Apr 05 22:27:48 GMT 2024
    - 3K bytes
    - Viewed (2)
  2. tensorflow/c/eager/parallel_device/BUILD

    package(
        # copybara:uncomment default_applicable_licenses = ["//tensorflow:license"],
        licenses = ["notice"],
    )
    
    # Currently pybind extension shared objects must use only C API headers since
    # the C API has static initializers duplicated in the Python bindings. So we
    # need a second rule that omits .cc files, in
    # tensorflow/python:_pywrap_parallel_device.
    filegroup(
        name = "lib_headers",
        srcs = ["parallel_device_lib.h"],
    )
    
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Mon Apr 01 20:19:06 GMT 2024
    - 4.8K bytes
    - Viewed (0)
  3. RELEASE.md

    *   `tf.all_variables`, `tf.VARIABLES` and `tf.initialize_all_variables` renamed
        to `tf.global_variables`, `tf.GLOBAL_VARIABLES` and
        `tf.global_variables_initializer` respectively.
    *   `tf.zeros_initializer()` and `tf.ones_initializer()` now return a callable
        that must be called with initializer arguments, in your code replace
        `tf.zeros_initializer` with `tf.zeros_initializer()`
    
    ## Bug Fixes and Other Changes
    
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Mon Apr 29 19:17:57 GMT 2024
    - 727.7K bytes
    - Viewed (8)
  4. ci/official/README.md

    is a brief explanation of how they tie together:
    
    1.  `envs/*` are lists of variables made with bash syntax. A user must set a
        `TFCI` env param pointing to a list of `env` files.
    2.  `utilities/setup.sh`, initialized by all top-level scripts, reads and sets
        values from those `TFCI` paths.
        -   `set -a` / `set -o allexport` exports the variables from `env` files so
            all scripts can use them.
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Thu Feb 01 03:21:19 GMT 2024
    - 8K bytes
    - Viewed (0)
Back to top