You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/databox-online/data-box-edge-system-requirements.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,10 +118,10 @@ To understand and refine the performance of your solution, you could use:
118
118
- The compute metrics available in the Azure portal. Go to your Data Box Edge resource and then go to **Monitoring > Metrics**. Look at the **Edge compute - Memory usage** and **Edge compute - Percentage CPU** to understand the available resources and how are the resources getting consumed.
119
119
- The monitoring commands available via the PowerShell interface of the device such as:
120
120
121
-
-`dkr` stats to get a live stream of container(s) resource usage statistics. The command supports CPU, memory usage, memory limit, and network IO metrics.
122
-
-`dkr system df` to get information regarding the amount of disk space used.
123
-
-`dkr image [prune]` to clean up unused images and free up space.
124
-
-`dkr ps --size` to view the approximate size of a running container.
121
+
-`dkrdbe stats` to get a live stream of container(s) resource usage statistics. The command supports CPU, memory usage, memory limit, and network IO metrics.
122
+
-`dkrdbe system df` to get information regarding the amount of disk space used.
123
+
-`dkrdbe image prune` to clean up unused images and free up space.
124
+
-`dkrdbe ps --size` to view the approximate size of a running container.
125
125
126
126
For more information on the available commands, go to [Monitor and troubleshoot compute modules](data-box-edge-connect-powershell-interface.md#monitor-and-troubleshoot-compute-modules).
Copy file name to clipboardExpand all lines: articles/databox/data-box-disk-deploy-picked-up.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -153,8 +153,24 @@ If needed, you can contact Quantium Solution Support (Japanese language) at the
153
153
154
154
If you encounter any issues, kindly reach out to Data Box Operations Asia at [email protected]. Provide the job name in the subject header and the issue encountered.
155
155
156
-
3. Hand over to the courier.
156
+
3. Hand over to the courier.
157
157
158
+
### [In Self-Managed](#tab/in-selfmanaged)
159
+
160
+
If you are using Data Box Disk in Japan, Singapore, Korea, and West Europe and have selected the self-managed shipping option during order creation, follow these instructions.
161
+
162
+
1. Go to the **Overview** blade for your order in the Azure portal. Go through the instructions displayed when you select **Schedule pickup**. You should see an Authorization code that is used at the time of dropping off the order.
163
+
164
+
2. Send an email to the Azure Data Box Operations team using the following template when you are ready to return the device.
@@ -31,13 +31,13 @@ Each body frame contains a collection of body structs, a 2D body index map, and
31
31
32
32
## Access the collection of body structs
33
33
34
-
Multiple bodies might be detected in a single capture. You can query the number of bodies by calling the [k4abt_frame_get_num_bodies()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga29ab088b1a0d1a246bdb5542e21aa3c3.html#ga29ab088b1a0d1a246bdb5542e21aa3c3) function.
34
+
Multiple bodies might be detected in a single capture. You can query the number of bodies by calling the [k4abt_frame_get_num_bodies()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/1.x.x/group__btfunctions_ga29ab088b1a0d1a246bdb5542e21aa3c3.html#ga29ab088b1a0d1a246bdb5542e21aa3c3) function.
You use the [k4abt_frame_get_body_id()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga1d612404d133a279af847974e9359a92.html#ga1d612404d133a279af847974e9359a92) and [k4abt_frame_get_body_skeleton()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_gac7032ab06268253538556750775064fb.html#gac7032ab06268253538556750775064fb) functions to iterate through each body index to find the body ID and joint position/orientation information.
40
+
You use the [k4abt_frame_get_body_id()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/1.x.x/group__btfunctions_ga1d612404d133a279af847974e9359a92.html#ga1d612404d133a279af847974e9359a92) and [k4abt_frame_get_body_skeleton()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/1.x.x/group__btfunctions_gac7032ab06268253538556750775064fb.html#gac7032ab06268253538556750775064fb) functions to iterate through each body index to find the body ID and joint position/orientation information.
41
41
42
42
```C
43
43
for (size_t i = 0; i < num_bodies; i++)
@@ -50,7 +50,7 @@ for (size_t i = 0; i < num_bodies; i++)
50
50
51
51
## Access the body index map
52
52
53
-
You use the [k4abt_frame_get_body_index_map()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga0e4f2d0d7e330d444de7070fb1fee4f6.html#ga0e4f2d0d7e330d444de7070fb1fee4f6) function to access the body index map. Refer to [body index map](body-index-map.md) for detailed explanation of the body index map. Make sure to release the body index map when it is no longer needed.
53
+
You use the [k4abt_frame_get_body_index_map()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/1.x.x/group__btfunctions_ga0e4f2d0d7e330d444de7070fb1fee4f6.html#ga0e4f2d0d7e330d444de7070fb1fee4f6) function to access the body index map. Refer to [body index map](body-index-map.md) for detailed explanation of the body index map. Make sure to release the body index map when it is no longer needed.
The body tracker is an asynchronous API. The original capture may already have been released by the time the result is popped. Use the [k4abt_frame_get_capture()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_gad9eef11f6496bbfe997536c374217d9a.html#gad9eef11f6496bbfe997536c374217d9a) function to query the
63
+
The body tracker is an asynchronous API. The original capture may already have been released by the time the result is popped. Use the [k4abt_frame_get_capture()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/1.x.x/group__btfunctions_gad9eef11f6496bbfe997536c374217d9a.html#gad9eef11f6496bbfe997536c374217d9a) function to query the
64
64
input capture used to generate this body tracking result. The reference count for the k4a_capture_t is increased each time this function is called. Use [k4a_capture_release()](https://microsoft.github.io/Azure-Kinect-Sensor-SDK/master/group___functions_ga0ed6f74ec403c3eac1b8ef3afb32cee6.html#ga0ed6f74ec403c3eac1b8ef3afb32cee6) function when the capture is no longer needed.
Copy file name to clipboardExpand all lines: articles/kinect-dk/body-index-map.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ The body index map includes the instance segmentation map for each body in the d
17
17

18
18
19
19
>[!NOTE]
20
-
> The body index is different than the body id. You can query the body id from a given body index by calling API: [k4abt_frame_get_body_id()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga1d612404d133a279af847974e9359a92.html#ga1d612404d133a279af847974e9359a92).
20
+
> The body index is different than the body id. You can query the body id from a given body index by calling API: [k4abt_frame_get_body_id()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/1.x.x/group__btfunctions_ga1d612404d133a279af847974e9359a92.html#ga1d612404d133a279af847974e9359a92).
@@ -41,15 +42,22 @@ The `libk4abt<major>.<minor>` package contains the shared objects needed to run
41
42
42
43
The basic tutorials require the `libk4abt<major>.<minor>-dev` package. To install it, run
43
44
44
-
`sudo apt install libk4abt0.9-dev`
45
+
`sudo apt install libk4abt1.0-dev`
45
46
46
47
If the command succeeds, the SDK is ready for use.
47
48
48
49
> [!NOTE]
50
+
> When installing the SDK, remember the path you install to. For example, "C:\Program Files\Azure Kinect Body Tracking SDK 1.0.0". You will find the samples referenced in articles in this path.
49
51
> Body tracking samples are located in the [body-tracking-samples](https://github.com/microsoft/Azure-Kinect-Samples/tree/master/body-tracking-samples) folder in the Azure-Kinect-Samples repository. You will find the samples referenced in articles here.
50
52
51
53
## Change log
52
54
55
+
### v1.0.0
56
+
*[Feature] Add C# wrapper to the msi installer.
57
+
*[Bug Fix] Fix issue that the head rotation cannot be detected correctly: [Link](https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/997)
58
+
*[Bug Fix] Fix issue that the CPU usage goes up to 100% on Linux machine: [Link](https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/1007)
59
+
*[Samples] Add two samples to the sample repo. Sample 1 demonstrates how to transform body tracking results from the depth space to color space [Link](https://github.com/microsoft/Azure-Kinect-Samples/tree/master/body-tracking-samples/camera_space_transform_sample); sample 2 demonstrates how to detect floor plane [Link](https://github.com/microsoft/Azure-Kinect-Samples/tree/master/body-tracking-samples/floor_detector_sample)
60
+
53
61
### v0.9.5
54
62
*[Feature] C# support. C# wrapper is packed in the nuget package.
55
63
*[Feature] Multi-tracker support. Creating multiple trackers is allowed. Now user can create multiple trackers to track bodies from different Azure Kinect devices.
@@ -97,12 +105,6 @@ If the command succeeds, the SDK is ready for use.
97
105
*[API Change] Added `k4abt_frame_get_timestamp_usec()` function to simplify the steps for the users to query body frame timestamp.
98
106
* Further improved the body tracking algorithm accuracy and tracking reliability
99
107
100
-
### v0.3.0
101
-
102
-
*[Breaking Change] Added support for NVIDIA RTX GPUs by moving to CUDA 10.1 dependency
103
-
*[API Change] Provide the joint output in millimeters to be consistent with the Kinect for Windows v2 SDK
104
-
* Further improved the body tracking algorithm accuracy and reliability.
Copy file name to clipboardExpand all lines: articles/kinect-dk/body-sdk-setup.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,6 +52,10 @@ If everything is set up correctly, a window with a 3D point cloud and tracked bo
52
52
53
53

54
54
55
+
## Examples
56
+
57
+
You can find the examples about how to use the body tracking SDK [here](https://github.com/microsoft/Azure-Kinect-Samples/tree/master/body-tracking-samples).
# Quickstart: Build an Azure Kinect body tracking application
17
17
18
-
Getting started with the Body Tracking SDK? This quickstart will get you up and running with body tracking!
18
+
Getting started with the Body Tracking SDK? This quickstart will get you up and running with body tracking! You can find more examples in this [Azure-Kinect-Sample repo](https://github.com/microsoft/Azure-Kinect-Samples/tree/master/body-tracking-samples).
19
19
20
20
## Prerequisites
21
21
@@ -28,11 +28,11 @@ Getting started with the Body Tracking SDK? This quickstart will get you up and
@@ -116,7 +116,7 @@ if (pop_frame_result == K4A_WAIT_RESULT_SUCCEEDED)
116
116
117
117
## Access the body tracking result data
118
118
119
-
The body tracking results for each sensor capture are stored in a body frame [k4abt_frame_t](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/structk4abt__frame__t.html) structure. Each body frame contains three key components: a collection of body structs, a 2D body index map, and the input capture.
119
+
The body tracking results for each sensor capture are stored in a body frame [k4abt_frame_t](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/1.x.x/structk4abt__frame__t.html) structure. Each body frame contains three key components: a collection of body structs, a 2D body index map, and the input capture.
120
120
121
121
Your first body tracking application only accesses the number of detected bodies. Refer to [access data in body frame](access-data-body-frame.md) for detailed explanation of data in a body frame.
Copy file name to clipboardExpand all lines: articles/kinect-dk/get-body-tracking-results.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ case K4A_WAIT_RESULT_FAILED:
67
67
68
68
## Enqueue the capture and pop the results
69
69
70
-
The tracker internally maintains an input queue and an output queue to asynchronously process the Azure Kinect DK captures more efficiently. Use the [k4abt_tracker_enqueue_capture()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_ga093becd9bb4a63f5f4d56f58097a7b1e.html#ga093becd9bb4a63f5f4d56f58097a7b1e) function to add a new capture to the input queue. Use the [k4abt_tracker_pop_result()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/0.9.x/group__btfunctions_gaaf446fb1579cbbe0b6af824ee0a7458b.html#gaaf446fb1579cbbe0b6af824ee0a7458b) function o pop a result from the output queue. Use of the timeout value is dependent on the application and controls the queuing wait time.
70
+
The tracker internally maintains an input queue and an output queue to asynchronously process the Azure Kinect DK captures more efficiently. Use the [k4abt_tracker_enqueue_capture()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/1.x.x/group__btfunctions_ga093becd9bb4a63f5f4d56f58097a7b1e.html#ga093becd9bb4a63f5f4d56f58097a7b1e) function to add a new capture to the input queue. Use the [k4abt_tracker_pop_result()](https://microsoft.github.io/Azure-Kinect-Body-Tracking/release/1.x.x/group__btfunctions_gaaf446fb1579cbbe0b6af824ee0a7458b.html#gaaf446fb1579cbbe0b6af824ee0a7458b) function o pop a result from the output queue. Use of the timeout value is dependent on the application and controls the queuing wait time.
71
71
72
72
### Real-time processing
73
73
Use this pattern for single-threaded applications that need real-time results and can accommodate dropped frames. The `simple_3d_viewer` sample located in [GitHub Azure-Kinect-Samples](https://github.com/microsoft/Azure-Kinect-Samples) is an example of real-time processing.
0 commit comments