First, I don't know where to set the env variables NUPLAN_DATA_ROOT NUPLAN_MAPS_ROOT NUPLAN_EXP_ROOT. If I set them in .env It will influence the env variables in python files. So I only can set absolute path in docker-compose to simulate it. Does it influence the docker image running in your sever?
Second, I have encountered the following error in the simulation, but I don't know how to solve it. I don't know where and how to set this env variable and it is not defaulting to a blank string.
Third, I wonder how to make sure the submission is valid and how much data I need to simulate? If I simulate my planner successfully in docker only using one db file, can I make sure that my submission is valid?
You can set this in your ~/.bashrc.
a. No it will not influence running in our servers. We do not use your simulation image. We only take your submission image
You can try exporting SCENARIO_FILTER_ID in nuplan-devkit/.env like so export SCENARIO_FILTER_ID=
If you can successfully run docker-compose then you should have a valid submission.
First, I don't know where to set the env variables NUPLAN_DATA_ROOT NUPLAN_MAPS_ROOT NUPLAN_EXP_ROOT. If I set them in .env It will influence the env variables in python files. So I only can set absolute path in docker-compose to simulate it. Does it influence the docker image running in your sever? Second, I have encountered the following error in the simulation, but I don't know how to solve it. I don't know where and how to set this env variable and it is not defaulting to a blank string.![sendpix0](https://github.com/motional/nuplan-devkit/assets/70321079/c6686eb6-9c06-4cd0-b964-063ef6c03615)
Third, I wonder how to make sure the submission is valid and how much data I need to simulate? If I simulate my planner successfully in docker only using one db file, can I make sure that my submission is valid?