1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
|
/**
\page tutorial-read-write-NPZ-format Tutorial: NumPy NPY/NPZ file format for reading/writing large arrays of data
\tableofcontents
\section tutorial-read-write-NPZ-format-intro Introduction
\note
Please refer to the <a href="tutorial-npz.html">C++ tutorial</a> for an overview of the NPZ format and a quick usage
from a C++ point of view.
NumPy offers the possibility to save and read arrays of data in binary format. This is an alternative to the NumPy
<a href="https://numpy.org/doc/stable/reference/generated/numpy.savetxt.html">`numpy.savetxt`</a> function, which
allows the user to save 1D/2D arrays in plain text.
The NPY format, and the NPZ format which is a collection of NPY data zipped into a single file, offer the following
advantages:
- easy usage with <a href="https://numpy.org/doc/stable/reference/generated/numpy.savez.html">`numpy.savez`</a>
and <a href="https://numpy.org/doc/stable/reference/generated/numpy.load.html">`numpy.load`</a> for saving and reading
arrays of data,
- binary format contrary to using a plain text file, which reduces the file size,
- no data loss when saving, this can be problematic when dealing with floating-point numbers,
- easy access to the different saved variables since the returned loaded object is a dictionnary.
In contrary, the main disadvantages are:
- it is a non-human readable format,
- it is meant to be used with arrays of basic data type, hierarchical structures of data are not suitables for instance.
\note
You can refer to this Wikipedia page for an exhaustive comparison of
<a href="https://en.wikipedia.org/wiki/Comparison_of_data-serialization_formats">data-serialization formats</a>.
\n You can refer to the following page for a more thorough description of the
<a href="https://numpy.org/doc/stable/reference/generated/numpy.lib.format.html">NPY format</a>.
\section tutorial-read-write-NPZ-format-examples Examples
\subsection tutorial-read-write-NPZ-format-examples-quick Quick overview in Python
The following code snippet illustrates how to save 1-D vector, multi-dimensional array and append data to file.
\code{.py}
#! python3
# -*- coding: utf-8 -*-
import numpy as np
from tempfile import TemporaryFile
import matplotlib.pyplot as plt
def main():
# https://numpy.org/doc/stable/reference/generated/numpy.savez.html
outfile = TemporaryFile()
x_vec = np.arange(10)
sin_x = np.sin(x_vec)
np.savez(outfile, x=x_vec, y=sin_x)
_ = outfile.seek(0) # Only needed here to simulate closing & reopening file
npzfile = np.load(outfile)
print(f"npzfile.filesz: {npzfile.files}")
# append data to the file: https://stackoverflow.com/a/71183105
img = np.random.randint(low=0, high=256, size=(48, 64, 3), dtype=np.uint8)
print(f"img: {img.shape}")
data_dict = dict(npzfile)
data_dict["img"] = img
np.savez(outfile, **data_dict)
_ = outfile.seek(0) # Only needed here to simulate closing & reopening file
npzfile = np.load(outfile)
print(f"npzfile.filesz: {npzfile.files}")
plt.imshow(npzfile["img"])
plt.show()
if __name__ == '__main__':
main()
\endcode
\subsection tutorial-read-write-NPZ-format-examples-realsense Demo: read and display data from RealSense sensors
In this demo, we will first use visp-save-rs-dataset.cpp to save data on disk.
- save "[-s]" color "[-c]" infrared "[-i]" depth "[-d]" and pointcloud "[-p]" data on disk:
- \code{.sh} ./visp-save-rs-dataset -s -c -i -d -p \endcode
- use "[-e <pattern>]" to specify the filename pattern:
- \code{.sh} ./visp-save-rs-dataset -s -c -i -d -p -e %06d \endcode
- use "[-o <output folder>]" to specify the output folder, a folder with the current timestamp will be
automatically created inside it:
- \code{.sh} ./visp-save-rs-dataset -s -c -i -d -p -o output_dir \endcode
- use "[-C]" to save data on user click:
- \code{.sh} ./visp-save-rs-dataset -s -c -i -d -p -C \endcode
- use "[-f <fps>]" to specify the acquisition framerate:
- \code{.sh} ./visp-save-rs-dataset -s -c -i -d -p -f 60 \endcode
- use "[-depth-bin]" and "[-pcl-bin]" to force depth and pointcloud data to be saved in little-endian binary format:
- \code{.sh} ./visp-save-rs-dataset -s -c -i -d -p -depth-bin -pcl-bin \endcode
- use "[-pcl-npz]" to save pointcloud data in NumPy NPZ format (if this option is not passed and ViSP is not
built with the PCL third-party library as dependency, the NPZ format is used by default, unless the "[-depth-bin]"
and "[-pcl-bin]" options are passed):
- \code{.sh} ./visp-save-rs-dataset -s -c -i -d -p -pcl-npz \endcode
\note
Saving pointcloud data is very time consuming. If you need acquisition data to be as close as possible to the camera
framerate, you can save instead the depth data and compute the 3D pointcloud later using the stereo-camera parameters.
Then, you can use the PlotRGBIrDepthData.py Python script to display the data:
- \code{.sh} python3 PlotRGBIrDepthData.py -i <folder> \endcode
*/
|
