TL;DR: visibility and control for all connections (marketplace apps, 4th parties) to your 3rd party SaaS platforms. See which connections are active as well as when and how much they transmit. Transparent token splitting to force connections through the proxy as well as instant token revocation and ACLs.
We are currently building this and would appreciate your feedback!
This is nice to hear about. Can you tell me more about how your live results matched or diverged from your backtesting?
Did you list the returns of the commodities as a comparison, or are you trading those futures as well in the mix? (I know you only talked about ES/MES)
>but I’m more so pushing back on the added cost and complexity of human elements NOT required by the built environment
Am I understanding you correctly that you would want something that still had cameras at head height, but simply didn't have the head form factor? And perhaps had 4 arms for some tasks that it would benefit from instead of being limited to two arms?
If so, how many environments are you going to build robots for? And how does your total overall build cost increase with each different model you build?
Doesn't matter if it's simper in the end-design if getting there ends up costing you as much as it would to build a general purpose design in the first place.
Knowing starting battery temperature would go a long way to interpreting the results here. You could assume they all started the same, but it would be nice to know for sure.
Nowhere do they describe initial starting conditions for the batteries / vehicles besides saying 10% SOC at start.
TL;DR: visibility and control for all connections (marketplace apps, 4th parties) to your 3rd party SaaS platforms. See which connections are active as well as when and how much they transmit. Transparent token splitting to force connections through the proxy as well as instant token revocation and ACLs.
We are currently building this and would appreciate your feedback!