newsletters:2024-06
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| newsletters:2024-06 [2024/06/30 14:15] – [Andrés] add multi colored stamp link admin | newsletters:2024-06 [2024/07/01 08:37] (current) – osnr | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== June 2024 newsletter | + | ====== June 2024 newsletter ====== |
| ===== What we've been up to ===== | ===== What we've been up to ===== | ||
| Line 60: | Line 60: | ||
| * Block out skew parameter of cam/proj intrinsics, can assume that it is always 0 (OpenCV does this so we copy them and assume it's OK) | * Block out skew parameter of cam/proj intrinsics, can assume that it is always 0 (OpenCV does this so we copy them and assume it's OK) | ||
| * Instead of averaging extrinsics (3D cam-> | * Instead of averaging extrinsics (3D cam-> | ||
| - | * [[https:// | + | * [[https:// |
| + | * Keeps a tiny bit of state (pose from prev frame) and finds the most likely pose for current frame using tag detection + prev state | ||
| + | * Can get stuck in weird poses but fixes itself if you cover & uncover tag, this is tolerable for now I think | ||
| + | * I really like that this is both pose estimation and ' | ||
| + | * Wonder if we could also teach it about the square tag instead of doing servoing for each point on its own, would that make it more robust | ||
| * Spent a while on performance micro-optimization, | * Spent a while on performance micro-optimization, | ||
| * Spent a while on making a separate correct-extrinsics step that you do at the end of calibration, | * Spent a while on making a separate correct-extrinsics step that you do at the end of calibration, | ||
| Line 81: | Line 85: | ||
| I've also made it almost fully backward-compatible with all existing code -- it now derives 2D projector-space region claims from the 3D calibration, | I've also made it almost fully backward-compatible with all existing code -- it now derives 2D projector-space region claims from the 3D calibration, | ||
| - | I'd like to get it to at least be on par with the existing 2D calibration in most cases before we merge it, and we're not there yet... | + | I'd like to get it to at least be on par with the existing 2D calibration in most cases before we merge it, and we're not there yet... |
| ---- | ---- | ||
| Line 180: | Line 184: | ||
| ===== What we'll be up to in July ===== | ===== What we'll be up to in July ===== | ||
| - | * **Our next [[https:// | + | * **Our next [[https:// |
| * Getting 3D calibration to work well on all systems, then merging it....... | * Getting 3D calibration to work well on all systems, then merging it....... | ||
| * Figuring out retraction and transaction behavior for parallel evaluator; testing it more | * Figuring out retraction and transaction behavior for parallel evaluator; testing it more | ||
| * Gadget iteration (need to fix swiveling, fix power issues, improve software) | * Gadget iteration (need to fix swiveling, fix power issues, improve software) | ||
| * Video support | * Video support | ||
| - | * Documentation (language reference, new kits and printable worksheets for setting up and learning the Folk language) | + | * Documentation (language reference, new kits and printable worksheets for setting up and learning the Folk language), open up GitHub repo |
newsletters/2024-06.1719756910.txt.gz · Last modified: by admin