Feature/time to collision condition

[yamacir-kit]

Description

Please check examples and comment out this sentence. Minimal example is here and detailed example is here

Abstract

[Required] This section is required, keep it short, clear and to the point.
Delete this sentence and explain this pull request shortly.

Background

[Optional] If there is no background information that needs explanation (e.g., just a typo correction, etc.), you can skip this section.
Delete this sentence and explain the circumstances that led to this pull request being sent.

Details

[Optional] If there are only differences whose effects are so obvious that no explanation is needed, or if there are no differences in the code (e.g., documentation additions), you can skip this section.
Delete this sentence and describe this pull request.
For example, it is desirable to describe the specifications of added functions, and detailed explanations of bugs that have been fixed.

References

[Optional] If the referenced material does not exist, you can skip this section.
Describe any standards, algorithms, books, articles, etc. that you referenced when creating the pull request. If there is any novelty, mention it.

Destructive Changes

[Optional] If no destructive change exists, you can skip this section.
Include a description of the changes and a migration guide and send the pull request with a bump major label. (Example : #1139)
Otherwise, skip the "Destructive Changes" section and make sure this pull request is labeled bump minor or bump patch.

Known Limitations

[Optional] If there are no known limitations that you can think of, you can skip this section. If there are any limitations on the features or fixes added by this pull request, delete this sentence and clearly describe them.
For example, the lane matching algorithm currently (1/25/2024) employed is unable to match Entity that is heavily tilted with respect to the lane, and it is difficult to throw an exception.
If the developer is aware of the existence of such problems or limitations, describe them in detail. The problems or limitation should be listed as an Issue on GitHub and a link to it should be provided in this section.

[github-actions]

Checklist for reviewers ☑️

All references to "You" in the following text refer to the code reviewer.

• Is this pull request written in a way that is easy to read from a third-party perspective?
• Is there sufficient information (background, purpose, specification, algorithm description, list of disruptive changes, and migration guide) in the description of this pull request?
• If this pull request contains a destructive change, does this pull request contain the migration guide?
• Labels of this pull request are valid?
• All unit tests/integration tests are included in this pull request? If you think adding test cases is unnecessary, please describe why and cross out this line.
• The documentation for this pull request is enough? If you think adding documents for this pull request is unnecessary, please describe why and cross out this line.