Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 34 for variables (0.23 sec)

  1. ci/official/utilities/get_versions.sh

    # limitations under the License.
    # ==============================================================================
    # Variables containing version strings extracted from the canonical sources:
    # tensorflow/core/public/version.h and tools/pip_package/setup.py.
    #
    # These variables aren't available by default. Scripts must source this file
    # explicitly, *after* checking if update_version.py needs to be run for a
    Shell Script
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Jan 10 19:39:41 GMT 2024
    - 2.3K bytes
    - Viewed (0)
  2. tensorflow/c/checkpoint_reader.h

    // other languages.
    //
    // The class currently only interacts with single-slice (i.e., non-partitioned)
    // variables.
    class CheckpointReader {
     public:
      CheckpointReader(const string& filename, TF_Status* status);
    
      bool HasTensor(const string& name) const;
      const string DebugString() const;
    
      // Returns a map from variable names to their shapes.  Slices of a partitioned
      // tensor are combined into a single entry.
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Oct 12 08:49:52 GMT 2023
    - 3.1K bytes
    - Viewed (0)
  3. ci/official/bisect.sh

    # ==============================================================================
    # Run any CI script and env configuration to bisect a failing target in some
    # build configuration. You must set the following variables to control this
    # script:
    #
    #   TF_BISECT_GOOD: Last known good commit (e.g. commit from the last passing job)
    #   TF_BISECT_BAD: First bad commit (e.g. commit from the first failing job)
    Shell Script
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Thu Feb 01 03:21:19 GMT 2024
    - 1.8K bytes
    - Viewed (0)
  4. ci/official/requirements_updater/updater_config_repository.bzl

    '''
     Repository rule to set some environment variables.
     Can be set via build parameter "--repo_env=<VARIABLE_NAME>=<value>"
     e.g "--repo_env=REQUIREMENTS_FILE_NAME=requirements.in"
    
     List of variables:
     REQUIREMENTS_FILE_NAME
    '''
    
    def _updater_config_repository_impl(repository_ctx):
        repository_ctx.file("BUILD", "")
        requirements_file_name = repository_ctx.os.environ.get("REQUIREMENTS_FILE_NAME", "requirements.in")
        repository_ctx.file(
    Others
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Aug 31 18:17:57 GMT 2023
    - 718 bytes
    - Viewed (0)
  5. 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)
  6. ci/official/utilities/setup.sh

    # variables in it, OR may be left empty if the user has already exported the
    # relevant variables in their environment. Because of 'set -o allexport' above
    # (which is equivalent to "set -a"), every variable in the file is exported
    # for other files to use.
    #
    # Separately, if TFCI is set *and* there are also additional TFCI_ variables
    Shell Script
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Fri Jan 26 00:33:34 GMT 2024
    - 5.2K bytes
    - Viewed (1)
  7. SECURITY.md

    are working with. When loading untrusted checkpoints, the values of the traced
    variables from your model are also going to be untrusted. That means that if
    your code interacts with the filesystem, network, etc. and uses checkpointed
    variables as part of those interactions (ex: using a string variable to build a
    filesystem path), a maliciously created checkpoint might be able to change the
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Sun Oct 01 06:06:35 GMT 2023
    - 9.6K bytes
    - Viewed (0)
  8. ci/official/utilities/setup_docker.sh

    # Keep the existing "tf" container if it's already present.
    # The container is not cleaned up automatically! Remove it with:
    # docker rm tf
    if ! docker container inspect tf >/dev/null 2>&1 ; then
      # Pass all existing TFCI_ variables into the Docker container
      env_file=$(mktemp)
      env | grep ^TFCI_ > "$env_file"
      docker run $TFCI_DOCKER_ARGS --name tf -w "$TFCI_GIT_DIR" -itd --rm \
          -v "$TFCI_GIT_DIR:$TFCI_GIT_DIR" \
          --env-file "$env_file" \
    Shell Script
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Fri Jan 26 15:27:59 GMT 2024
    - 1.8K bytes
    - Viewed (0)
  9. ci/official/utilities/rename_and_verify_wheels.sh

    # limitations under the License.
    # ==============================================================================
    #
    # Usage: rename_and_verify_wheels.sh
    # This script is aware of TFCI_ variables, so it doesn't need any arguments.
    # Puts new wheel through auditwheel to rename and verify it, deletes the old
    # one, checks the filesize, and then ensures the new wheel is installable.
    set -euxo pipefail
    
    Shell Script
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Wed Mar 27 21:16:27 GMT 2024
    - 3.4K bytes
    - Viewed (0)
  10. tensorflow/c/eager/c_api_test.cc

                              remote_device) != device_names.end());
      }
    
      // Create a variable using `ctx_0`.
      // Read the variable using `ctx_1`. This read should succeed.
      // 1. Create a variable on `remote_device`, using `ctx_0`.
      TFE_TensorHandle* handle_0 =
          CreateVariable(ctx_0, 1.2, remote_device, /*variable_name=*/"var2");
    
      // 2. Wait for `var2` to be created and initialized on the worker.
    C++
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Aug 03 20:50:20 GMT 2023
    - 94.6K bytes
    - Viewed (1)
Back to top