[amadeuszsz]

Description

Pins the ptv3 model bundle to v0.1.1, which the node requires as of autowarefoundation/autoware_universe#13300.

The version goes from v4.0 to v0.1.1 on purpose. We now use the same version numbers as in our internal model releases. The version is also stored in the ONNX metadata (v0.1.1 in this case), so it is printed in the logs when TensorRT loads the ONNX files automatically. Tagging it as v5.0 would be confusing. I believe moving the version back once for this model is not a big deal.

Related PRs

• universe: feat(autoware_ptv3): support multisweep densification with time-lag features autoware_universe#13300
• data: AutowareFoundation/ptv3 PR #1 (tag v0.1.1)

[github-actions]

Thank you for contributing to the Autoware project!

🚧 If your pull request is in progress, switch it to draft mode.

Please ensure:

• You've checked our contribution guidelines.
• Your PR follows our pull request guidelines.
• All required CI checks pass before marking the PR ready for review.

[xmfcx]

Thanks. I checked that the v0.1.1 tag exists on Hugging Face and has the same file names as v4.0, so the node finds the files at the same paths.

The version going back from v4.0 to v0.1.1 is fine with me. Could you add a short comment above the line, like the ones for diffusion_planner and tensorrt_vad? Without it, a later reader may take v0.1.1 for a typo and "fix" it. For example:

    # ptv3 uses the version numbers of the internal model releases, so v0.1.1 is newer than v4.0.
    - { repo: ptv3, revision: v0.1.1 }

This is optional. I approve as it is.