test(lost_void): 覆盖寻路卡住判定与脱困策略 - #63
Open
pumpkinperson996 wants to merge 2 commits into
Open
Conversation
配套主仓 LostVoidMoveByDet 卡住判定重构(时间窗快照对比)与6阶段脱困: 快照配对纯逻辑、静止抖动约4秒判卡、正常靠近不误判、目标丢失重现不清零、 前进时长门槛、各阶段按键与方向、超上限返回执行超时、重开后重置 stuck_state。
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
为什么改
配套主仓 PR OneDragon-Anything/ZenlessZoneZero-OneDragon#2738（迷失之地寻路卡住判定重构 + 分阶段脱困），补对应测试。
改动要点
test_move_by_det_stuck.py：is_same_box_constellation纯逻辑（相同/抖动/位移/尺寸变化/数量变化/空列表）check_stuck时间窗判定：静止带抖动约 4 秒判卡、正常靠近（框变大+位移）不误判、目标丢失后原位重现不清零、无累计前进时长不判卡get_out_of_stuck阶段策略：0-3 阶段同侧两次再换侧（含横滑按键时长）、4 阶段后撤+平移、5 阶段转向绕行并翻转优先侧、脱困后清除跟踪目标、超上限返回执行超时LostVoidRunLevel.handle_find_target_fail重开成功后重建 stuck_state关联