Tobias Oberstein

> Well I was talking about a Pull request for the missing Custom Excite API. ok, understood. fwiw, if I find time, I'm going to expose it as well, added...

great, thanks for noticing and commenting! couple of comments back from my side: > But that function would need to be able to interpolate as the file not necessarily should...

here is more info about SigMF: * https://github.com/sigmf/SigMF * https://github.com/sigmf/SigMF fwiw, and here is what an AI says about SigMF - which sounds mostly cool/good/correct to me. Just that I...

one final thought: what about multi-channel IQ data? say I have 4 excitation ports defined in my openEMS model (and no, I haven't done that yet even though I am...

> IQ data? The FDTD method is a time-domain method. It has no concept of frequencies or complex numbers what so ever. Not sure I am following, isn't > It...

btw: as repo owner you should also be able to convert this whole issue in aggregate into a discussion preserving the contents above .. using one button click (top right...

> serializers are not negotiated in WAMP yes, that is true. however, WAMP transports may have negotiation - as does WebSocket for example. in code terms, both WAMP-WebSocket clients and...

writing above .. reminds me of "batched transports" ... which is a thing, and can bring quite some efficiencies. in particular on TLS. because there you want to shuffle multiple...

@konsultaner There is no negotiation in RawSocket by design. KISS;) The client must announce the one serializer it wants to talk, and the router accepts or denies. That's it. No...

> * But what serializer will wamp router choose? First from the client list that is supported by router? Or first one from the router list that is supported by...