User Tools

Site Tools


newsletters:2024-02

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
newsletters:2024-02 [2024/02/29 17:45] – Resolve editor bug TODO adminnewsletters:2024-02 [2024/02/29 22:22] (current) osnr
Line 13: Line 13:
     * Integration with [[https://cuttle.xyz/@forresto/folk-computer-cuttle-xyz-FL0EJkXOEVCd|Cuttle]]: {{newsletters:image.webp?200}}     * Integration with [[https://cuttle.xyz/@forresto/folk-computer-cuttle-xyz-FL0EJkXOEVCd|Cuttle]]: {{newsletters:image.webp?200}}
  
-  * Andrés magazine article highlight+  * Andrés made a demo of a Folk-highlighted quote using an excerpt from [[ https://spikeartmagazine.com/articles/essay-emily-dickinson-apple-computer-house|this Spike magazine article about Folk]]. The program displays a letter-page-sized border and highlights the text of the quote on the printed-out article. To the right is a program that pulls out the highlighted text and projects it. This is a simple proof of concept, but you could imagine feeding these quotes into a spatial note-taking system on the table, or associating different kinds of data (definitions, related articles, comments on the same passage) to the highlights. 
 +      * {{newsletters:highlightquotedemo.jpg?500px}}
  
 (Omar: Both Forrest and Vedran's demos [and the receipt printer work from last year] indicate the potential importance of custom regions and accurate calibration, instead of the hard-coded 'half-size page' that we currently have. Ideally, it would be easy to make the program region follow the outline of the hex tile or the train or whatever else.) (Omar: Both Forrest and Vedran's demos [and the receipt printer work from last year] indicate the potential importance of custom regions and accurate calibration, instead of the hard-coded 'half-size page' that we currently have. Ideally, it would be easy to make the program region follow the outline of the hex tile or the train or whatever else.)
Line 22: Line 23:
  
 ==== Template matching ==== ==== Template matching ====
 +
 +Andrés: I've spent most of this month working on template matching (finding the location of an image in a larger image) to enable tracking custom game pieces in Folk. I wanted a basic demo where you can:
 +
 +  - capture a small, square image from the table, this is known as a template.
 +  - run a program that continuously searches for the template and highlight its location
 +
 +To that end, I wrapped a few programs into this "Image Slice Matcher" folder made from cardstock:
 +
 +{{newsletters:templatefoldercover.jpeg?300px}}
 +
 +{{newsletters:templatefolderinside.jpeg?400px}}
 +
 +When you open the folder, the left side includes two programs: on the full-size page is a program titled "slice" that will show if you've captured a template image, plus a program that pulls out to the side allowing you to trigger the template capture. Like so:
 +
 +{{newsletters:templatecapture.gif}}
 +
 +In a previous version, you had to manually take a photo of the table in order to recognize a template. Now the program reads the global camera image from Folk's main process. This allows the program that looks for and highlights matches to operate much faster and work continuously. Here it is searching for the cover of a small zine as I move it around the desk:
 +
 +{{newsletters:templatematcherdemo.gif}}
 +
 +Next month, I'll be extending this to track game pieces in a booklet of games I've been working on.
  
 ==== Parallel evaluator ==== ==== Parallel evaluator ====
Line 109: Line 131:
  
 Next steps here are to figure out the data structures/locking/atomics so that tests reliably pass, then do a run on a table with all the major components of the system (camera, AprilTags, GPU) and see how it performs compared to the old evaluator (that end-to-end test is really the only way to find out, I think) Next steps here are to figure out the data structures/locking/atomics so that tests reliably pass, then do a run on a table with all the major components of the system (camera, AprilTags, GPU) and see how it performs compared to the old evaluator (that end-to-end test is really the only way to find out, I think)
 +
 ==== RFID ==== ==== RFID ====
  
Line 159: Line 182:
   * New collaboration (still TBA) on deeper phone/laptop integration and knowledge management   * New collaboration (still TBA) on deeper phone/laptop integration and knowledge management
     * (Omar: I did some prototyping last weekend on localizing a phone using its camera + a tag on a laptop screen. I feel like you could do clever stuff with phone sensors and dead reckoning and smoothing to make this a nice experience even if tag tracking cuts out. Ideally you could just use a valid QR code, not even a specialized fiducial. Also thinking about Joy-Cons and Wii Remotes and how they do mouse-like pointing.)     * (Omar: I did some prototyping last weekend on localizing a phone using its camera + a tag on a laptop screen. I feel like you could do clever stuff with phone sensors and dead reckoning and smoothing to make this a nice experience even if tag tracking cuts out. Ideally you could just use a valid QR code, not even a specialized fiducial. Also thinking about Joy-Cons and Wii Remotes and how they do mouse-like pointing.)
 +  
 +  * Fine-tuning the template matching and using it to create small board-game interactions
  
   * Polishing Folk/CNC interface for use by other people at Hex House and in general   * Polishing Folk/CNC interface for use by other people at Hex House and in general
-    * USB stick install / Linux distro+    * USB stick install / Linux distro packaging, both Owen's demo and Folk more broadly (this will be a big deal for getting people up and running, I think)
     * Better Web UI     * Better Web UI
     * Finishing up the 3D/high-accuracy calibration work from late last year to actually do the machine preview in Folk     * Finishing up the 3D/high-accuracy calibration work from late last year to actually do the machine preview in Folk
Line 170: Line 195:
  
   * Parallel evaluator: continuing to work on locking and scheduling, goal is to do a table test after that to see how it performs   * Parallel evaluator: continuing to work on locking and scheduling, goal is to do a table test after that to see how it performs
 +
 ===== Links we've enjoyed ===== ===== Links we've enjoyed =====
  
Line 181: Line 207:
  
 ==== Andrés ==== ==== Andrés ====
 +
 +  * [[https://github.com/prathyvsh/Illustrated-Primers|Illustrated Primers
 + — Books that makes heavy use of visuals for scientific communication]]
 +  * [[https://alarmingdevelopment.org/?p=1708|"you should write an Onward! paper"]]
newsletters/2024-02.1709228737.txt.gz · Last modified: by admin

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki