Install issue (API, header file version inconsistency)

[QLI037]

Hello, I would like to request the official use of a consistent version of multiple dependencies to make sure that the API corresponds to the same version of many of the functions, header files, and APIs that I encountered during the installation process, including Hydra, Kimera-PGMO, and Khronos.

[QLI037]

@Schmluk

[Schmluk]

Hi @QLI037

Thanks for pointing out this issue! We're just in the process of rolling out a large update to Khronos, Hydra and the entire DSG ecosystem (yay!). While the Hydra parts are already live, we had to hold-off on Khronos to fix an extra bug we just found, we expect the release to be live in a few days. Many thanks for your patience!

[QLI037]

Thank you for your reply and look forward to the Khronos version fix and update！👍

[JoaoAlencar21]

Hi @QLI037

Thanks for pointing out this issue! We're just in the process of rolling out a large update to Khronos, Hydra and the entire DSG ecosystem (yay!). While the Hydra parts are already live, we had to hold-off on Khronos to fix an extra bug we just found, we expect the release to be live in a few days. Many thanks for your patience!

Hey, thats great news, is there a estimated date for that release?

[dvdmc]

Thanks for the update @Schmluk! Joining on the update waitlist :)

[QLI037]

Hello, I would like to ask about the specific time when the fix of Khronos will be completed ？ @Schmluk

[Schmluk]

Hi all,

Many thanks for your patience! This one specific issue turned out to be harder to track down than we anticipated, so we've opted for a partial release for now.

The plus sides:

• Khronos should build and run.
• We've included the open-set and real segmentation launch files that we wanted to release.
• The new Khronos should generally run better, be easier to use, and benefit from several updates to Hydra and the rest of the SPARK ecosystem.

The downside:

• The bug in change detection still remains, leading to reduced performance compared to the initial release. We've added a note to this effect and are working on a fix ASAP.

We hope that this allows you to use the multi-resolution and dynamic scene mapping capabilities of Khronos, as well as interfacing it with your data or building on top, while we work on fixing the last bit on the change detection side. Many thanks for your understanding!

[dvdmc]

Thanks a lot and sorry for the pressure! We will be working with the system and will let you know if any issues appear.

[Schmluk]

Thank you @dvdmc ! We apologize for the complications, please let us know if you find any other issues!

@dvdmc Looking forward to seeing what comes out of your work, let us know how it goes!