Differences

This shows you the differences between two versions of the page.

--- newsletters:2026-04 [2026/05/05 19:31] – [Communal table (folk-convivial) / JMGO N1 Ultra setup] osnr
+++ newsletters:2026-04 [2026/05/05 20:08] (current) – [NaN handling] osnr
@@ Line 1: / Line 1: @@
 ====== April 2026 newsletter ======
@@ Line 47: / Line 46: @@
 Given this stereo camera, how can we add crop support to the UI and ultimately calibrate and use both 'eyes' to do better pose estimation?
+=== Easier camera config ===
+Added a setting on /camera that lets you set the exposure (and auto-exposure mode) live right there. Also now iframe /camera on the calibration page, so we have just that one uniform UI for camera config (including any future settings we might want to add), rather than /calibrate having its own one-off exposure slider.
 === Camera crop ===
@@ Line 55: / Line 60: @@
 (We use this to pick just the left eye for now out of a stereo side-by-side ELP image, but eventually want to use this to create two virtual cameras, one from each eye, to co-calibrate.)
-=== Easier camera config ===
-Added a setting on /camera that lets you set the exposure (and auto-exposure mode) live right there. Also now iframe /camera on the calibration page, so we have just that one uniform UI for camera config (including any future settings we might want to add), rather than /calibrate having its own one-off exposure slider.
@@ Line 67: / Line 67: @@
 Now when you boot Folk on a PC with two displays, we can draw to both, but it's still the same stuff drawn to both. In order to have a properly multi-display Folk system, we need to change a lot of the draw statements to be scoped to a specific display, which may be a breaking API change.
+==== Ideas for fixing pose estimation errors ====
+Some systems have [[https://github.com/AprilRobotics/apriltag/issues/71|pose estimation problems]] while we rely on monocular vision. One solution is to use a stereo camera to remove ambiguity; another is to account for the table plane in some way to narrow down candidates.
+Here is a simple proposal:
+{{newsletters:screenshot-2026-04-24-at-5.10.07-pm.png?400px}}
 ==== New studio setup ====
-Last month, we started [[newsletters/2026-03#moving-into-the-new-studio|moving ]]out of Hex House and into a new studio space in Williamsburg. We continued that process this month and finalized a lot of the layout (although we don't necessarily have final mounting situation and tables/storage yet).
+Last month, we started [[newsletters/2026-03#moving-into-the-new-studio|moving]] out of Hex House and into a new studio space in Williamsburg. We continued that process this month and finalized a lot of the layout (although we don't necessarily have final mounting situation and tables/storage yet).
 === L-shaped dedicated area for Folk ===
@@ Line 81: / Line 90: @@
 Was trying the Logitech Brio 4K on one side and NexiGo on the other side at first. Horrible issues with USB3; ultimately gave up on the Brio 4K for now.
+{{newsletters:img_4149.mp4?250px}}
 {{.:pasted:20260504-222528.png?350px}}
-(I think it's the SAM2 demo that's running/rerunning all the time and really pushing the Nvidia drivers.)
+(I think it might be the SAM2 demo I have on the table that's running/rerunning all the time and really pushing the Nvidia drivers and causing deadlock.)
 === Communal table (folk-convivial) / JMGO N1 Ultra setup ===
@@ Line 136: / Line 148: @@
 {{newsletters:screenshot-2026-04-29-at-6.04.12-pm.png?500px}}
+Now capping the number of optimization iterations and throwing an error when NaN appears in any parameter. Still need to report to frontend UI.
 === Inline live preview on /calibrate ===