Weak coupling between usercode and the robot code is desirable as it reduces the security risk on thre brain and makes the understanding of the state of the brain more sensible. The Robot doesn't blow up when the usercode exits.
AS A person running robocon
I WANT a thin interface for the usercode to the robot libarry and the actual code avaiable over a network socket
SO THAT
DONE IS
Shepherd exposes the public methods of the robot object over a network socket
There is no tight coupling between shepherd and the robot object
Performance of R.see() is evaluated to ensure that it returning large matracies does not take significantly more time
If R.see() performance is anything more than 250ms worse an investigation into how to reduce the return payload is implemented.
NOTES:
This is something which could get very complicated and it would be good to keep this as simple as possible.
Weak coupling between usercode and the robot code is desirable as it reduces the security risk on thre brain and makes the understanding of the state of the brain more sensible. The Robot doesn't blow up when the usercode exits.
AS A person running robocon I WANT a thin interface for the usercode to the robot libarry and the actual code avaiable over a network socket SO THAT DONE IS
R.see()is evaluated to ensure that it returning large matracies does not take significantly more timeR.see()performance is anything more than 250ms worse an investigation into how to reduce the return payload is implemented.NOTES:
Alternatives prebuilt RPC is:
@shardros 's Personal opion is taht RPPy should be used.