When customizing the save path, modify the "save_details" location #1092
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the local model path is used, such as /mnt/public/xxxx, and the results_path_template is not specified, the path for saving the results will be extremely long and the directory will be difficult to read.
Now, we can specify the results_path_template so that the files will be saved in the corresponding path. However, if save_details is specified, the details will still be saved in the original path, which is not convenient for reading the parquet corresponding to the details. Therefore, I change that under the condition that the user specifies the saving path, the details can also be placed in the corresponding directory.