Yeah one needs to distinguish between the optimal state sequence and the optimal state at a particular time. In other words, a joint posterior (state trajectory up to now given all measurements up to now) vs a marginal posterior (state right now given all measurements up to now). the KF only gives you a marginal posterior. they are not the same
Yeah we decided to integrate with Teams because I had that exact experience in the past. I was at a company that decided "we're using Teams". We weren't allowed to install alternatives like Discord or Slack.
Teams itself has some limitations that are easy to improve upon. They have no way of doing a huddle/pop-in-style room. They screw up the presence signaling in a way that discourages pop-ins: if you join a call with someone your and the other participants' status is set to busy/unavailable. From other peoples' perspective this isn't very inviting, and doesn't indicate that the conversation is public. Teams also limits who can share screens to only 1 person at a time.
Sorry to hear you stopped working on your tool. My cofounder and I are working on a similar product (teraphone.app). We're focusing specifically on making a discord-like product for microsoft shops. I agree it's partly a culture thing. There's also an awareness issue. A lot of people don't know that pop-in style communication tools exist, especially outside the tech industry.
Audio Weaver is a graphical tool for doing audio dsp. You use a drag-and-drop interface to configure your signal flow graph. When you "run" the system your graph is used to dynamically instantiate the necessary low level functions and compose them together. While the design is running you can do live tuning (changing gains, filter coefficients, delays, etc.). The low level functions have implementations on several architectures (PC, ARM Cortex-A and M, Tensilica HiFi 2 and 3, ADI SHARC, TI C66xx, plus a few more). This means that your signal flow graph is cross platform.
DISCLAIMER - I work for the company that makes Audio Weaver.
it has some nice features:
- follows .gitignore patterns
- optional file watcher to regenerate the snapshot when files are changed
- supports glob patterns for filter/exclude
- can report token usage
- can use a config yaml file if you have complicated filter/exclude patterns
i find myself using it all the time now. it's great with claude projects