Another update on the migration of Synavis: Would it not be nice to have the choice of backends? This is particularly useful for users who want to run Synavis in different circumstances, such as more data-centric, and focussed on using Unreal Engine as a virtual world backend in which real measurements are embedded. I showcase this in my virtual world coupling publication in In Silico Plants, where we focus on photosynthetic measurements. For that purpose it was always a little awkward to use WebRTC as backend for something which ultimately uses a simulation data coupling for both directions. In this case, it might be more straight forward to rather make use of something that is also developed for the concurrent run of two endpoints, but more focussed on bulk data transfer: ADIOS!
This is not everything that will happen until the migration is complete. We also have to take a deepdive into substrate! Substrate is a cornerstone of the migration which I will also make a video about... I have no idea how compatible all the presently used concepts are to Substrate, but we will find out!
Looking Forward
I will keep you updated! This will be highlighted in more detail in the future. As we have more people interested in Synavis, I will do a more concentrated effort to make it more user friendly.