I'm trying to run the perception module offline on my PC. In following the "how-to" guide there are two things that are unclear to me.
In any case, if I try to "play" any of the __record__ files contained in these folders (as described in step 9) I get error messages about the timestamps.
So, if I want to run perception offline, where can I find some data to feed the Apollo pipeline? I can play (using cyber_recorder) the file /apollo/docs/demo_guide/demo_3.5.record but that doesn't contain any video data and I need video data.
I suppose one of the difficulties is that I don't see how cyberRT tools would allow me to assemble my own __record__ file that I could use to feed the pipeline.
I can't access the apollo open(ish) dataset because to do that I would need to create an account with Baidu and I need to have a mobile phone in one of number of specific countries (most of Europe is not covered)
Any info please?
I'm going to partially answer my own questions:
As for getting data to feed the whole Apollo pipeline (including perception) I finally found that LG's open source simulator (LGSVL) is a good option for that. It can be run on another machine and the simulated sensor data sent via ethernet (assuming that you don't want to add too many high data rate sensors). That way you can see exactly what you're sending to Apollo.
@Autofoxsys did you get the link between LGSVL and Apollo working? How does your pipeline work? Do you manually drive around on LGSVL and create a .record file which you then play in apollo using cyber_recorder and simply view the planning and control output on dreamviewer? Or do you run things online with the control output from Apollo sent back to LGSVL?
Most helpful comment
I'm going to partially answer my own questions:
As for getting data to feed the whole Apollo pipeline (including perception) I finally found that LG's open source simulator (LGSVL) is a good option for that. It can be run on another machine and the simulated sensor data sent via ethernet (assuming that you don't want to add too many high data rate sensors). That way you can see exactly what you're sending to Apollo.