search

zqzqz / AVChecker

Code for Paper "A Systematic Framework to Identify Violations of Scenario-dependent Driving Rules in Autonomous Vehicle Software"
7 stars 2 forks source link

Apollo runtime environment and user interface #1

Open 853108389 opened 1 year ago

853108389 commented 1 year ago

Hello, I have two questions. First, do I need to set up an Apollo runtime environment for this work? Second, where can I get the user interface?

zqzqz commented 1 year ago

Hi @853108389. Basically there are three steps as described in the paper: compiling Apollo to LLVM IR, program analysis, SMT solving. The compiling step need Apollo Runtime (tested on 3.5), with instructions in https://github.com/zqzqz/AVChecker/tree/master/apollo_llvm_compile. The user interface is for SMT solving step, see https://github.com/zqzqz/AVChecker/tree/master/constraint_solver. For instance, we implemented many APIs to describe geometric relationship in https://github.com/zqzqz/AVChecker/blob/master/constraint_solver/av_solver/api.py.

853108389 commented 1 year ago

Thanks for your help. I have one more question. My understanding is that, in the code analysis step, AVchecker identifies code fragments in apollo about driving rules and then compiles these fragments. How much time and memory is needed for the whole compiling step? Can I reproduce AVChecker by using a server with a NVIDIA GeForce RTX 3070 GPU with 48GB RAM?

853108389 commented 1 year ago

Should I choose Apollo version 3.5 or 5.5?