feat(how-to-guides): add important temporal performance metrics

[takam5f2]

Description

I would like to add a new page that explains important temporal performance metrics. The page will consist of several lists of these metrics.

These metrics are particularly useful for evaluating Autoware in terms of temporal performance. Since Autoware is categorized as a real-time system, these metrics will provide valuable guidance in determining which aspects of Autoware to evaluate. Users will find these metrics helpful when attempting to integrate Autoware into their environment, including their computer, operating system, and middleware.

Defining task deadlines based on these metrics is crucial for executing Autoware as a real-time system.

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The Reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

[github-actions]

Documentation URL: https://autowarefoundation.github.io/autoware-documentation/pr-389/
Modified URLs:

• https://autowarefoundation.github.io/autoware-documentation/pr-389/how-to-guides/
• https://autowarefoundation.github.io/autoware-documentation/pr-389/how-to-guides/others/defining-temporal-performance-metrics/

[takam5f2]

@TakaHoribe

I expect it explains "how to measure the performance". But it actually explains just the concept of the metrics, no specific how-to.

Thank you for your feedback. I want to emphasize the metrics at the beginning because there are several ways to evaluate the metrics. If some users want to import Autoware to a platform other than ROS 2 and Linux, they have to choose another supported tool.
I added the same statement at eeac4f0.

Got it. Then it would be better to refer to it in the document.

Added the reason why temporal performance is used at 30bb7b5

[TakaHoribe]

@takam5f2 Looks nice!!

[takam5f2]

@mitsudome-r
I'm worried that the PR will not reviewed and will be left for a long time.
I understand that the PR picks up one of the minor topic like performance, which has difficulty of attracting attention from developers.
Do you have any idea to let the PR going toward merging?

[mitsudome-r]

if you want to emphasize the metrics, then I would suggest to change the document title to something like "Defining key temporal metrics for your system". Autoware can be customized, and key value could change depending on the setup. For example "AWOV-006" might not exist if people use Eagleye instead of NDT scan matcher.

Since the title says "Important temporal performance metrics on components", it seems like these are the metrics that reader should use. I think it would be better to emphasize the "policies" for choosing the topic as you mentioned in the document, and then provide the metrics table as an "example" if you launch the default autoware.launch.xml according to the tutorials

[takam5f2]

@mitsudome-r
Thank you for giving me feedback. I fixed the document as you suggested. Could you check it again? Best,

[mitsudome-r]

LGTM

[mitsudome-r]

Suggested change

	- [Important temporal performance metrics on components](others/important-temporal-performance-metrics.md)
	- [Important temporal performance metrics on components](others/defining-temporal-performance-metrics.md)

[mitsudome-r]

CI found a deadlink due to change in the file name. Please fix this, and I can merge this PR

[takam5f2]

Thank you for suggestion. It is fixed at 3d4c03c