Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for Freddy (0.2 sec)

  1. tensorflow/c/eager/c_api.h

    //
    // If async execution is enabled, the call may simply enqueue the execution
    // and return "non-ready" handles in `retvals`. Note that any handles contained
    // in 'op' should not be mutated till the kernel execution actually finishes.
    //
    // For sync execution, if any of the inputs to `op` are not ready, this call
    // will block till they become ready and then return when the kernel execution
    // is done.
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Apr 27 21:07:00 GMT 2023
    - 22.8K bytes
    - Viewed (1)
  2. tensorflow/c/eager/c_api_remote_test_util.h

    // Run a function containing a MatMul op and check its output.
    // If heavy_load_on_streaming_rpc is true, send some rpc requests before the one
    // which creates a remote input, to simulate a scenario that the remote input
    // is not ready when we start running an op or a function.
    void TestRemoteExecuteSilentCopies(bool async, bool remote, bool func,
                                       bool heavy_load_on_streaming_rpc,
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Fri Dec 11 22:56:03 GMT 2020
    - 1.4K bytes
    - Viewed (0)
  3. tensorflow/c/eager/c_api_remote_function_test.cc

                                        /*remote_func_outputs=*/true);
    }
    TEST(CAPI, RemoteExecuteSilentCopiesLocalAsyncFuncOrdering) {
      // A remote input may be not ready when we start running a function. Test that
      // the function execution should wait until the remote input is ready.
      TestRemoteExecuteSilentCopiesFunc(/*async=*/true, /*remote=*/false,
                                        /*heavy_load_on_streaming_rpc=*/true);
    }
    C++
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Fri Dec 11 22:56:03 GMT 2020
    - 3.6K bytes
    - Viewed (0)
  4. CONTRIBUTING.md

    TensorFlow team members will be assigned to review your pull requests. Once the
    pull requests are approved and pass continuous integration checks, a TensorFlow
    team member will apply `ready to pull` label to your change. This means we are
    working on getting your pull request submitted to our internal repository. After
    the change has been submitted internally, your pull request will be merged
    automatically on GitHub.
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Mar 21 11:45:51 GMT 2024
    - 15.6K bytes
    - Viewed (0)
  5. ci/official/requirements_updater/requirements.in

    # TODO(b/304751256): Adjust the numpy pin to a single version, when ready
    numpy ~= 1.23.5 ; python_version <= "3.11"
    numpy ~= 1.26.0 ; python_version >= "3.12"
    wheel ~= 0.41.2
    h5py >= 3.10.0
    lit ~= 17.0.2
    opt_einsum == 3.3.0
    astunparse == 1.6.3
    dill == 0.3.7
    astor == 0.7.1
    typing_extensions == 4.8.0
    gast == 0.4.0
    termcolor == 2.3.0
    wrapt == 1.16.0
    tblib == 2.0.0
    
    # Install tensorboard, and keras
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Feb 15 07:17:18 GMT 2024
    - 806 bytes
    - Viewed (0)
  6. RELEASE.md

    OverLordGoldDragon, Owen Lyke, Patrick Hemmer, Paul Andrey, Peng Sun,
    periannath, Phil Pearl, Prashant Dandriyal, Prashant Kumar, Rahul Huilgol, Rajan
    Singh, Rajeshwar Reddy T, rangjiaheng, Rishit Dagli, Rohan Reddy, rpalakkal,
    rposts, Ruan Kunliang, Rushabh Vasani, Ryohei Ikegami, Semun Lee, Seo-Inyoung,
    Sergey Mironov, Sharada Shiddibhavi, ShengYang1, Shraiysh Vaishay, Shunya Ueta,
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Mon Apr 29 19:17:57 GMT 2024
    - 727.7K bytes
    - Viewed (8)
Back to top