|
@@ -93,7 +93,7 @@ After executing the above command, PaddleX will verify the dataset and count its
|
|
|
"dataset_path": "./dataset/fall_det",
|
|
"dataset_path": "./dataset/fall_det",
|
|
|
"show_type": "image",
|
|
"show_type": "image",
|
|
|
"dataset_type": "COCODetDataset"
|
|
"dataset_type": "COCODetDataset"
|
|
|
-}
|
|
|
|
|
|
|
+}
|
|
|
```
|
|
```
|
|
|
The above verification results indicate that the `check_pass` being `True` means the dataset format meets the requirements. Explanations for other indicators are as follows:
|
|
The above verification results indicate that the `check_pass` being `True` means the dataset format meets the requirements. Explanations for other indicators are as follows:
|
|
|
|
|
|
|
@@ -154,14 +154,14 @@ Each model in PaddleX provides a configuration file for model development, which
|
|
|
* `epochs_iters`: Number of training epochs;
|
|
* `epochs_iters`: Number of training epochs;
|
|
|
* `learning_rate`: Training learning rate;
|
|
* `learning_rate`: Training learning rate;
|
|
|
|
|
|
|
|
-For more hyperparameter introductions, refer to [PaddleX Hyperparameter Introduction](../module_usage/instructions/config_parameters_common_en.md).
|
|
|
|
|
|
|
+For more hyperparameter introductions, refer to [PaddleX General Model Configuration File Parameter Explanation](../module_usage/instructions/config_parameters_common_en.md).
|
|
|
|
|
|
|
|
**Note**:
|
|
**Note**:
|
|
|
- The above parameters can be set by appending command-line parameters, e.g., specifying the mode as model training: `-o Global.mode=train`; specifying the first two GPUs for training: `-o Global.device=gpu:0,1`; setting the number of training epochs to 10: `-o Train.epochs_iters=10`.
|
|
- The above parameters can be set by appending command-line parameters, e.g., specifying the mode as model training: `-o Global.mode=train`; specifying the first two GPUs for training: `-o Global.device=gpu:0,1`; setting the number of training epochs to 10: `-o Train.epochs_iters=10`.
|
|
|
- During model training, PaddleX automatically saves model weight files, with the default being `output`. To specify a save path, use the `-o Global.output` field in the configuration file.
|
|
- During model training, PaddleX automatically saves model weight files, with the default being `output`. To specify a save path, use the `-o Global.output` field in the configuration file.
|
|
|
- PaddleX shields you from the concepts of dynamic graph weights and static graph weights. During model training, both dynamic and static graph weights are produced, and static graph weights are selected by default for model inference.
|
|
- PaddleX shields you from the concepts of dynamic graph weights and static graph weights. During model training, both dynamic and static graph weights are produced, and static graph weights are selected by default for model inference.
|
|
|
|
|
|
|
|
-**Explanation of Training Outputs**:
|
|
|
|
|
|
|
+**Explanation of Training Outputs**:
|
|
|
|
|
|
|
|
After completing model training, all outputs are saved in the specified output directory (default is `./output/`), typically including the following:
|
|
After completing model training, all outputs are saved in the specified output directory (default is `./output/`), typically including the following:
|
|
|
|
|
|
|
@@ -250,7 +250,7 @@ for res in output:
|
|
|
```
|
|
```
|
|
|
For more parameters, please refer to [General Object Detection Pipeline Usage Tutorial](../pipeline_usage/tutorials/cv_pipelines/object_detection_en.md).
|
|
For more parameters, please refer to [General Object Detection Pipeline Usage Tutorial](../pipeline_usage/tutorials/cv_pipelines/object_detection_en.md).
|
|
|
|
|
|
|
|
-2. Additionally, PaddleX also offers service-oriented deployment methods, detailed as follows:
|
|
|
|
|
|
|
+2. Additionally, PaddleX offers three other deployment methods, detailed as follows:
|
|
|
|
|
|
|
|
* High-Performance Deployment: In actual production environments, many applications have stringent standards for deployment strategy performance metrics (especially response speed) to ensure efficient system operation and smooth user experience. To this end, PaddleX provides high-performance inference plugins aimed at deeply optimizing model inference and pre/post-processing for significant end-to-end process acceleration. For detailed high-performance deployment procedures, please refer to the [PaddleX High-Performance Deployment Guide](../pipeline_deploy/high_performance_deploy_en.md).
|
|
* High-Performance Deployment: In actual production environments, many applications have stringent standards for deployment strategy performance metrics (especially response speed) to ensure efficient system operation and smooth user experience. To this end, PaddleX provides high-performance inference plugins aimed at deeply optimizing model inference and pre/post-processing for significant end-to-end process acceleration. For detailed high-performance deployment procedures, please refer to the [PaddleX High-Performance Deployment Guide](../pipeline_deploy/high_performance_deploy_en.md).
|
|
|
* Service-Oriented Deployment: Service-oriented deployment is a common deployment form in actual production environments. By encapsulating inference functions as services, clients can access these services through network requests to obtain inference results. PaddleX supports users in achieving cost-effective service-oriented deployment of production lines. For detailed service-oriented deployment procedures, please refer to the [PaddleX Service-Oriented Deployment Guide](../pipeline_deploy/service_deploy_en.md).
|
|
* Service-Oriented Deployment: Service-oriented deployment is a common deployment form in actual production environments. By encapsulating inference functions as services, clients can access these services through network requests to obtain inference results. PaddleX supports users in achieving cost-effective service-oriented deployment of production lines. For detailed service-oriented deployment procedures, please refer to the [PaddleX Service-Oriented Deployment Guide](../pipeline_deploy/service_deploy_en.md).
|