-
Notifications
You must be signed in to change notification settings - Fork 0
Prequal 2025 #107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Prequal 2025 #107
Conversation
nathanaelren
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could consider rewrite lane_marker_detector.py to extend our generic hsv_filter.py, and moving to a more generic runType launch argument to enable customization beyond "yes prequal" and "no prequal" within the same launch argument. @viethungle-vt1401 lmk thoughts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If possible, I think it would be good to have this file re-written using the new HSV filter template to standardize all of our HSV filtering this year. Especially if we can have somebody who doesn't currently understand the CV pipeline help write this. @viethungle-vt1401 do you think this is reasonable? Or do you prefer to just prequal with this code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds like a good idea, though revamping prequal code is not the highest priority so I'm fine either way. I can rope someone to work on it while we are testing other stuff and/or before Crush prequal.
|
|
||
| ld = LaunchDescription() | ||
|
|
||
| ld.add_action(DeclareLaunchArgument( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@viethungle-vt1401 I think instead of having "prequal=Boolean", we could consider having "typeOfRun=string", and do "typeOfRun=prequal" etc., I think this might be a bit cleaner if we want to continue to use this schema for, e.g., comp run or something of the sort.
|
|
||
| ld = LaunchDescription() | ||
|
|
||
| ld.add_action(DeclareLaunchArgument( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment on cv.launch.py
| description='Enable or disable recording functionality', | ||
| )) | ||
|
|
||
| ld.add_action(DeclareLaunchArgument( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment on cv.launch.py
|
|
||
| ld.add_action(IncludeLaunchDescription( | ||
| PythonLaunchDescriptionSource(str(pkg_cv / 'launch' / 'cv.launch.py')), | ||
| launch_arguments=[ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We would need to do LaunchConfiguration('runType') == 'prequal' or something of the sort should we move in that direction, see comment on cv.launch.py. This change would also need to be reflected in the other relevant launch files (cv.launch.py, usb_camera_detectors.launch.py).
Draft PR for adjustments made to complete prequal.