- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for NORMALIZED (0.09 sec)
-
src/cmd/internal/obj/s390x/asmz.go
const ( op_A uint32 = 0x5A00 // FORMAT_RX1 ADD (32) op_AD uint32 = 0x6A00 // FORMAT_RX1 ADD NORMALIZED (long HFP) op_ADB uint32 = 0xED1A // FORMAT_RXE ADD (long BFP) op_ADBR uint32 = 0xB31A // FORMAT_RRE ADD (long BFP) op_ADR uint32 = 0x2A00 // FORMAT_RR ADD NORMALIZED (long HFP) op_ADTR uint32 = 0xB3D2 // FORMAT_RRF1 ADD (long DFP)
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Apr 16 17:46:09 UTC 2024 - 176.7K bytes - Viewed (0) -
tensorflow/compiler/mlir/lite/ir/tfl_ops.td
Pure]> { let summary = "Local Response Normalization."; let description = [{ The 4-D `input` tensor is treated as a 3-D array of 1-D vectors (along the last dimension), and each vector is normalized independently. Within a given vector, each component is divided by the weighted, squared sum of inputs within `depth_radius`. In detail, sqr_sum[a, b, c, d] =
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Thu Jun 06 19:09:08 UTC 2024 - 186K bytes - Viewed (0) -
samples/addons/grafana.yaml
utilization under steady load.\n\n- **vCPU / 1k rps:** shows vCPU utilization by the main Istio components normalized by 1000 requests/second. When idle or low traffic, this chart will be blank. The curve for istio-proxy refers to the services sidecars only.\n- **vCPU:** vCPU utilization by Istio components, not normalized.\n- **Memory:** memory footprint for the components. Telemetry and policy are normalized by 1k rps, and no data is shown when there is no traffic. For ingress and istio-proxy, the data...
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Jun 12 20:46:28 UTC 2024 - 242.3K bytes - Viewed (0) -
cmd/site-replication.go
// use the normalized form of the entityName (which will be an LDAP DN). userType := IAMUserType(mapping.UserType) isGroup := mapping.IsGroup entityName := mapping.UserOrGroup if globalIAMSys.GetUsersSysType() == LDAPUsersSysType && userType == stsUser { // Validate that the user or group exists in LDAP and use the normalized // form of the entityName (which will be an LDAP DN).
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Fri May 24 23:05:23 UTC 2024 - 184.3K bytes - Viewed (0)