Kristoffer Eide

This is caused by two threads interacting with the same data source simultaneously: - libcosim inserts data (fast) - the server extracts data (slow) For each cycle of the trend...

> I am not sure it is connected, but I have observed (after I have reported the issue above) that the RTF jumps to very small values every now and...

``` panic: runtime error: index out of range goroutine 51 [running]: cse-server-go/cse.removeAllFromTrend(0xc00014a050, 0xc000438080, 0x81ff71, 0x1, 0x0, 0x0, 0xc000431d48) D:/JenkinsOSP/workspace/on-platform_cse-server-go_v0.5.0/src/cse-server-go/cse/trending.go:82 +0x383 cse-server-go/cse.executeCommand(0xc000004040, 0x2, 0x2, 0xc00014a050, 0xc000438080, 0xc000d941d0, 0xb, 0x0, 0x0, 0x0,...

Is the idea is to also use cse-client when running the server on a different port? If so, some changes will also be required in cse-client, as its websocket connection...

I think this relates to connections, as a special case of unit conversion. IE connecting two variables where one gives a value in `%`, and the other expects the value...

For clarification; In a C++ software project using the cse-core C++ API (such as `cse-consumer`) it is fully possible to create your own observer and add it to the execution....

> Are there other examples of cases where this would be useful? Not that I know of. > It kind of sounds like we have a bug in our existing...