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
In this equation, both $\text{StartTimestamp}$ and $\text{TimePartitionInterval}$ are configurable parameters to accommodate various production environments. The $\text{StartTimestamp}$ represents the starting time of the first time partition, while the $\text{TimePartitionInterval}$ defines the duration of each time partition. By default, the $\text{TimePartitionInterval}$ is set to one day.
48
+
In this equation, both $\text{StartTimestamp}$ and $\text{TimePartitionInterval}$ are configurable parameters to accommodate various production environments. The $\text{StartTimestamp}$ represents the starting time of the first time partition, while the $\text{TimePartitionInterval}$ defines the duration of each time partition. By default, the $\text{TimePartitionInterval}$ is set to seven day.
49
49
50
50
#### Schema Partitioning
51
51
Since the series partitioning algorithm evenly partitions the time series, each series partition corresponds to a schema partition. These schema partitions are then evenly allocated across the SchemaRegionGroups to achieve a balanced schema distribution.
2. Place the library-udf.jar file in the compressed file obtained in the directory `/ext/udf ` of all nodes in the IoTDB cluster
37
+
2. Place the `library-udf.jar` file in the compressed file obtained in the directory `/ext/udf ` of all nodes in the IoTDB cluster
38
38
3. In the SQL command line terminal (CLI) or visualization console (Workbench) SQL operation interface of IoTDB, execute the corresponding function registration statement as follows.
39
39
4. Batch registration: Two registration methods: registration script or SQL full statement
40
40
- Register Script
41
-
- Copy the registration script (register-UDF.sh or register-UDF.bat) from the compressed package to the `tools` directory of IoTDB as needed, and modify the parameters in the script (default is host=127.0.0.1, rpcPort=6667, user=root, pass=root);
41
+
- Copy the registration script (`register-UDF.sh` or `register-UDF.bat`) from the compressed package to the `tools` directory of IoTDB as needed, and modify the parameters in the script (default is host=127.0.0.1, rpcPort=6667, user=root, pass=root);
42
42
- Start IoTDB service, run registration script to batch register UDF
43
43
44
44
- All SQL statements
@@ -3934,26 +3934,86 @@ Output series:
3934
3934
3935
3935
Note: The input is $y=sin(2\pi t/4)+2sin(2\pi t/5)$ with a length of 20. Thus, the output is $y=2sin(2\pi t/5)$ after low-pass filtering.
3936
3936
3937
-
<!--
3938
3937
3939
-
Licensed to the Apache Software Foundation (ASF) under one
3940
-
or more contributor license agreements. See the NOTICE file
3941
-
distributed with this work for additional information
3942
-
regarding copyright ownership. The ASF licenses this file
3943
-
to you under the Apache License, Version 2.0 (the
3944
-
"License"); you may not use this file except in compliance
3945
-
with the License. You may obtain a copy of the License at
3946
-
3947
-
http://www.apache.org/licenses/LICENSE-2.0
3948
-
3949
-
Unless required by applicable law or agreed to in writing,
3950
-
software distributed under the License is distributed on an
3951
-
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
3952
-
KIND, either express or implied. See the License for the
3953
-
specific language governing permissions and limitations
This function achieves signal demodulation and envelope extraction by inputting a one-dimensional floating-point array and a user specified modulation frequency. The goal of demodulation is to extract the parts of interest from complex signals, making them easier to understand. For example, demodulation can be used to find the envelope of the signal, that is, the trend of amplitude changes.
3949
+
3950
+
**Name：** Envelope
3951
+
3952
+
**Input：** Only supports a single input sequence, with types INT32/INT64/FLOAT/DOUBLE
3953
+
3954
+
3955
+
**Parameters：**
3956
+
3957
+
+`frequency`: Frequency (optional, positive number. If this parameter is not filled in, the system will infer the frequency based on the time interval corresponding to the sequence).
3958
+
+`amplification`: Amplification factor (optional, positive integer. The output of the Time column is a set of positive integers and does not output decimals. When the frequency is less than 1, this parameter can be used to amplify the frequency to display normal results).
3959
+
3960
+
**Output：**
3961
+
+`Time`： The meaning of the value returned by this column is frequency rather than time. If the output format is time format (e.g. 1970-01-01T08:00: 19.000+08:00), please convert it to a timestamp value.
3962
+
3963
+
3964
+
+`Envelope(Path, 'frequency'='{frequency}')`：Output a single sequence of type DOUBLE, which is the result of envelope analysis.
3965
+
3966
+
**Note：** When the values of the demodulated original sequence are discontinuous, this function will treat it as continuous processing. It is recommended that the analyzed time series be a complete time series of values. It is also recommended to specify a start time and an end time.
Copy file name to clipboardExpand all lines: src/UserGuide/Master/User-Manual/Write-Delete-Data.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -185,11 +185,11 @@ In different scenarios, the IoTDB provides a variety of methods for importing da
185
185
186
186
### TsFile Batch Load
187
187
188
-
TsFile is the file format of time series used in IoTDB. You can directly import one or more TsFile files with time series into another running IoTDB instance through tools such as CLI. For details, see [Import-Export-Tool](../Tools-System/TsFile-Import-Export-Tool.md).
188
+
TsFile is the file format of time series used in IoTDB. You can directly import one or more TsFile files with time series into another running IoTDB instance through tools such as CLI. For details, see [Data Import](../Tools-System/Data-Import-Tool.md).
189
189
190
190
### CSV Batch Load
191
191
192
-
CSV stores table data in plain text. You can write multiple formatted data into a CSV file and import the data into the IoTDB in batches. Before importing data, you are advised to create the corresponding metadata in the IoTDB. Don't worry if you forget to create one, the IoTDB can automatically infer the data in the CSV to its corresponding data type, as long as you have a unique data type for each column. In addition to a single file, the tool supports importing multiple CSV files as folders and setting optimization parameters such as time precision. For details, see [Import-Export-Tool](../Tools-System/Data-Import-Export-Tool.md).
192
+
CSV stores table data in plain text. You can write multiple formatted data into a CSV file and import the data into the IoTDB in batches. Before importing data, you are advised to create the corresponding metadata in the IoTDB. Don't worry if you forget to create one, the IoTDB can automatically infer the data in the CSV to its corresponding data type, as long as you have a unique data type for each column. In addition to a single file, the tool supports importing multiple CSV files as folders and setting optimization parameters such as time precision. For details, see [Data Import](../Tools-System/Data-Import-Tool.md).
Copy file name to clipboardExpand all lines: src/UserGuide/V1.2.x/QuickStart/QuickStart.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Configuration files are located in the `conf` folder
51
51
* system config module (`iotdb-datanode.properties`)
52
52
* log config module (`logback.xml`).
53
53
54
-
For more information, please go to [Config](../stage/DataNode-Config-Manual.md).
54
+
For more information, please go to [Config](../Reference/DataNode-Config-Manual.md).
55
55
56
56
## Start
57
57
@@ -244,7 +244,7 @@ The server can be stopped using `ctrl-C` or by running the following script:
244
244
```
245
245
Note: In Linux, please add the `sudo` as far as possible, or else the stopping process may fail. <!-- TODO: Actually running things as `root` is considered a bad practice from security perspective. Is there a reson for requiring root? I don't think we're using any privileged ports or resources. -->
246
246
247
-
More explanations on running IoTDB in a clustered environment are available at [Cluster-Setup](../stage/Cluster/Cluster-Setup.md).
247
+
More explanations on running IoTDB in a clustered environment are available at [Cluster-Setup](../Deployment-and-Maintenance/Deployment-Guide_timecho.md).
In this equation, both $\text{StartTimestamp}$ and $\text{TimePartitionInterval}$ are configurable parameters to accommodate various production environments. The $\text{StartTimestamp}$ represents the starting time of the first time partition, while the $\text{TimePartitionInterval}$ defines the duration of each time partition. By default, the $\text{TimePartitionInterval}$ is set to one day.
48
+
In this equation, both $\text{StartTimestamp}$ and $\text{TimePartitionInterval}$ are configurable parameters to accommodate various production environments. The $\text{StartTimestamp}$ represents the starting time of the first time partition, while the $\text{TimePartitionInterval}$ defines the duration of each time partition. By default, the $\text{TimePartitionInterval}$ is set to seven day.
49
49
50
50
#### Schema Partitioning
51
51
Since the series partitioning algorithm evenly partitions the time series, each series partition corresponds to a schema partition. These schema partitions are then evenly allocated across the SchemaRegionGroups to achieve a balanced schema distribution.
2. Place the library-udf.jar file in the compressed file obtained in the directory `/ext/udf ` of all nodes in the IoTDB cluster
35
+
2. Place the `library-udf.jar` file in the compressed file obtained in the directory `/ext/udf ` of all nodes in the IoTDB cluster
36
36
3. In the SQL command line terminal (CLI) or visualization console (Workbench) SQL operation interface of IoTDB, execute the corresponding function registration statement as follows.
37
37
4. Batch registration: Two registration methods: registration script or SQL full statement
38
38
- Register Script
39
-
- Copy the registration script (register-UDF.sh or register-UDF.bat) from the compressed package to the `tools` directory of IoTDB as needed, and modify the parameters in the script (default is host=127.0.0.1, rpcPort=6667, user=root, pass=root);
39
+
- Copy the registration script (`register-UDF.sh` or `register-UDF.bat`) from the compressed package to the `tools` directory of IoTDB as needed, and modify the parameters in the script (default is host=127.0.0.1, rpcPort=6667, user=root, pass=root);
40
40
- Start IoTDB service, run registration script to batch register UDF
41
41
42
42
- All SQL statements
@@ -3933,26 +3933,86 @@ Output series:
3933
3933
3934
3934
Note: The input is $y=sin(2\pi t/4)+2sin(2\pi t/5)$ with a length of 20. Thus, the output is $y=2sin(2\pi t/5)$ after low-pass filtering.
3935
3935
3936
-
<!--
3937
3936
3938
-
Licensed to the Apache Software Foundation (ASF) under one
3939
-
or more contributor license agreements. See the NOTICE file
3940
-
distributed with this work for additional information
3941
-
regarding copyright ownership. The ASF licenses this file
3942
-
to you under the Apache License, Version 2.0 (the
3943
-
"License"); you may not use this file except in compliance
3944
-
with the License. You may obtain a copy of the License at
3945
-
3946
-
http://www.apache.org/licenses/LICENSE-2.0
3947
-
3948
-
Unless required by applicable law or agreed to in writing,
3949
-
software distributed under the License is distributed on an
3950
-
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
3951
-
KIND, either express or implied. See the License for the
3952
-
specific language governing permissions and limitations
This function achieves signal demodulation and envelope extraction by inputting a one-dimensional floating-point array and a user specified modulation frequency. The goal of demodulation is to extract the parts of interest from complex signals, making them easier to understand. For example, demodulation can be used to find the envelope of the signal, that is, the trend of amplitude changes.
3948
+
3949
+
**Name：** Envelope
3950
+
3951
+
**Input：** Only supports a single input sequence, with types INT32/INT64/FLOAT/DOUBLE
3952
+
3953
+
3954
+
**Parameters：**
3955
+
3956
+
+`frequency`: Frequency (optional, positive number. If this parameter is not filled in, the system will infer the frequency based on the time interval corresponding to the sequence).
3957
+
+`amplification`: Amplification factor (optional, positive integer. The output of the Time column is a set of positive integers and does not output decimals. When the frequency is less than 1, this parameter can be used to amplify the frequency to display normal results).
3958
+
3959
+
**Output：**
3960
+
+`Time`： The meaning of the value returned by this column is frequency rather than time. If the output format is time format (e.g. 1970-01-01T08:00: 19.000+08:00), please convert it to a timestamp value.
3961
+
3962
+
3963
+
+`Envelope(Path, 'frequency'='{frequency}')`：Output a single sequence of type DOUBLE, which is the result of envelope analysis.
3964
+
3965
+
**Note：** When the values of the demodulated original sequence are discontinuous, this function will treat it as continuous processing. It is recommended that the analyzed time series be a complete time series of values. It is also recommended to specify a start time and an end time.
0 commit comments