- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 21 for fountain (0.22 sec)
-
ci/official/README.md
# of these env files. # # If you've clicked on a test result from our CI (via a dashboard or GitHub link), # click to "Invocation Details" and find BUILD_CONFIG, which will contain a TFCI # value in the "env_vars" list that you can choose to copy that environment. # Ex. 1: TFCI=py311,linux_x86_cuda,nightly_upload (nightly job) # Ex. 2: TFCI=py39,linux_x86,rbe (continuous job)
Plain Text - Registered: Tue Apr 23 12:39:09 GMT 2024 - Last Modified: Thu Feb 01 03:21:19 GMT 2024 - 8K bytes - Viewed (0) -
tensorflow/c/eager/immediate_execution_operation.h
ImmediateExecutionTensorHandle* input) = 0; virtual ImmediateExecutionContext* GetContext() const = 0; // Following two methods are used to support custom device. // Return true if the inputs contain custom device tensor handle. It means // that the argument need to be handled by a custom device. virtual bool HasCustomDeviceInput() const = 0; virtual const tensorflow::OpDef* OpDef() const = 0;
C - Registered: Tue Apr 23 12:39:09 GMT 2024 - Last Modified: Mon Sep 26 22:40:32 GMT 2022 - 3.6K bytes - Viewed (0) -
tensorflow/c/eager/c_api_unified_experimental.h
// type of eager and graph tensors. It is also the result of executing an // operation. typedef struct TF_AbstractTensor TF_AbstractTensor; // A TF_AbstractOp is the metadata we need to execute an operation. E.g. this // could contain the op type and other attributes. typedef struct TF_AbstractOp TF_AbstractOp; // Stores a function representation that can be used for execution or for // setting functional attributes of other composite ops e.g. control flow.
C - Registered: Tue Apr 23 12:39:09 GMT 2024 - Last Modified: Sun Oct 24 11:27:00 GMT 2021 - 7K bytes - Viewed (0) -
tensorflow/c/eager/c_api_experimental.h
// which is passed to the functions referenced in the TFE_CustomDevice struct // `device` (execute, delete_device, etc.). It can for example contain the // names of wrapped devices. // // There are currently no graph semantics implemented for registered custom // devices, so executing tf.functions which contain operations placed on the // custom devices will fail. // // `device_name` must not name an existing physical or custom device. It must
C - Registered: Tue Apr 23 12:39:09 GMT 2024 - Last Modified: Wed Feb 21 22:37:46 GMT 2024 - 39.5K bytes - Viewed (0) -
tensorflow/c/experimental/next_pluggable_device/c_api.h
TF_CAPI_EXPORT extern PJRT_Client* TF_GetPjRtCClient(const char* device_type, TF_Status* status); // Gets the `PJRT_Buffer*` stored in the tensor. The status will contain error // if the tensor does not have a `PjRtCApiBuffer`. TF_CAPI_EXPORT extern PJRT_Buffer* TF_GetPjRtCBuffer(TF_Tensor* c_tensor, TF_Status* status);
C - Registered: Tue Feb 27 12:39:08 GMT 2024 - Last Modified: Wed Dec 20 20:01:06 GMT 2023 - 7.2K bytes - Viewed (0) -
tensorflow/c/experimental/filesystem/plugins/gcs/gcs_filesystem.cc
TF_SetStatus(status, TF_INVALID_ARGUMENT, "GCS path doesn't contain a bucket name."); return; } *bucket = fname.substr(scheme_end + 1, bucket_end - scheme_end - 1); *object = fname.substr(bucket_end + 1); if (object->empty() && !object_empty_ok) { TF_SetStatus(status, TF_INVALID_ARGUMENT, "GCS path doesn't contain an object name."); } }
C++ - Registered: Tue Apr 23 12:39:09 GMT 2024 - Last Modified: Wed Aug 23 06:55:53 GMT 2023 - 46.9K bytes - Viewed (0) -
tensorflow/c/experimental/filesystem/filesystem_interface.h
/// `ReadOnlyMemoryRegion`) and one for all the operations a `Filesystem` /// implements. Each of them is in a 1-to-1 correspondence with the wrapper /// structures from the first section: these tables only contain function /// pointers that operate on the corresponding data. Thus, the first argument of /// each of these functions is a pointer to the paired struct and this argument
C - Registered: Tue Apr 23 12:39:09 GMT 2024 - Last Modified: Fri May 27 17:36:54 GMT 2022 - 53.1K bytes - Viewed (0) -
RELEASE.md
* Tensorflow code now produces 2 different pip packages: `tensorflow_core` containing all the code (in the future it will contain only the private implementation) and `tensorflow` which is a virtual pip package doing forwarding to `tensorflow_core` (and in the future will contain only the public API of tensorflow). We don't expect this to be breaking, unless you were importing directly from the implementation.
Plain Text - Registered: Tue Apr 23 12:39:09 GMT 2024 - Last Modified: Wed Apr 03 20:27:38 GMT 2024 - 727.4K bytes - Viewed (8) -
tensorflow/c/c_api_internal.h
TF_GUARDED_BY(mu); bool delete_requested TF_GUARDED_BY(mu); // set true by TF_DeleteGraph // Used to link graphs contained in TF_WhileParams to the parent graph that // will eventually contain the full while loop. TF_Graph* parent; TF_Output* parent_inputs; }; struct TF_OperationDescription { TF_OperationDescription(TF_Graph* g, const char* op_type,
C - Registered: Tue Apr 23 12:39:09 GMT 2024 - Last Modified: Sat May 13 00:49:12 GMT 2023 - 7.6K bytes - Viewed (0) -
tensorflow/c/experimental/filesystem/modular_filesystem_test.cc
const std::string translated_name = tensorflow::io::JoinPath(root_dir_, path); // We have already checked `GetParam().empty()` in // `ModularFileSystemTest()`. root_dir_ should contain `GetParam() + "://"` // if it isn't empty. return translated_name; } // Converts absolute paths to paths relative to root_dir_. StringPiece GetRelativePath(StringPiece absolute_path) {
C++ - Registered: Tue Apr 23 12:39:09 GMT 2024 - Last Modified: Fri May 27 20:25:58 GMT 2022 - 71K bytes - Viewed (0)