Generating .locs Files for Custom DevKit Configurations
This page is relevant only if you have created a DevKit cap of your own configuration.
Customers may wish to create their own DevKit cap layouts, and each unique configuration requires a corresponding locations (.locs) file so that the Kernel Flow UI and data pipelines correctly represent the sensor geometry. Until automated tools are released, Kernel provides a supported workflow for generating accurate .locs files for any custom cap.
To request new .locs files:
- Capture a video of your custom cap according to the instructions below.
- Submit the video to Kernel Support . Our team will generate updated .locs files based on your recording and upload them directly to your device.
This workflow ensures your custom cap is fully recognized by the system and that all channel positions remain accurate for data collection and analysis. Tools for independently creating and editing .locs files will be available in a future release.
Capturing a video of your DevKit
1. Mount AprilTags to the DevKit
Affix several printed AprilTags to the outer surface of the DevKit.
- Precise placement is not critical—they simply provide stable visual anchors for reconstruction.
- Tags may be mounted on small cardboard squares using double-sided tape or similar adhesive.
- Ensure that multiple tags remain visible from all directions during video capture.
2. Fit the DevKit onto a Mannequin or Model
The cap should be placed on either:
- A human wearing the DevKit, seated and able to remain still while you orbit around them.
- A 3D-printed mannequin head (recommended for consistency). A printable mannequin file is provided.
If using a human subject, they may cover their face with their hands if desired. Ensure the cap sits naturally and snugly on the head form.
3. Record the Video
If using a smartphone, record in 1080p or 4K at 60 FPS when possible.
Shoot in landscape orientation.
Ensure bright, diffuse lighting. Avoid glare on AprilTags and avoid strong shadows.
Use a plain, uncluttered background whenever possible.
- Perform a 360 degree scan.
- Perform a full 360° orbit around the headset. Complete multiple orbits with minor variations in camera elevation on each pass—slightly above, level with, and slightly below the horizontal plane of the tags. This provides richer geometric information and reduces blind spots.