Skip to content

Minimally viable examples, using the Rerun C++ SDK, for communicating with the Rerun team.

Notifications You must be signed in to change notification settings

ExpertOfNil/rerun_cpp_mve

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Minimally Viable Examples Using the Rerun SDK in C++

This is primarily used in communications with the Rerun team

Current Example:

  • SDK Version: 0.23.0
  • Viewer Version: 0.23.0
  • Description: The example workflow logs multiple images in rapid succession to a remote viewer. This results in a few logs getting through but then ceases, as though the connection is dropped.
  • Expected Results:
    • 50 iterations of image logging:
      • Image logged to mve/original
      • Image logged to mve/image1 (representing a permutation)
      • Image logged to mve/image2 (representing a permutation)
      • Image logged to mve/image along with pinhole and transform
    • Interspersed text logs
  • Actual Results:
    • All logs show up in a local viewer, but as little as 4 iterations of logs show up when a remote viewer is used.
  • Reference: Discord Question: Headless Logging

About

Minimally viable examples, using the Rerun C++ SDK, for communicating with the Rerun team.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published