michigan-traffic-lab / Mcity-AV-Challenge

10 stars 2 forks source link

AV_data #2

Closed farabi1038 closed 5 months ago

farabi1038 commented 5 months ago

Format and evewrything is right but still the AV is not found. There is also a freezing terminal issue. I think it is due that AV is not found. Here is the output log :

next AV position: 49.09451108389534 89.47357407677919 current AV position: 49.09451108389534 89.47357407677919 next AV position: 48.782457279900555 89.45773533545434 current AV position: 48.782457279900555 89.45773533545434 next AV position: 48.47053130056942 89.44139193277806 iteration number 3 Terasim warmup timeout, resetting av status to 0. [5]+ Stopped bash /app/av_decision_making_module/main.sh root@62d22be1b433:/app# python3 /app/av_decision_making_module/visualization_tool.py 0%| | 0/671 [00:00<?, ?it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_1/fcd.xml 0%|▎ | 1/671 [00:00<01:44, 6.42it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_10/fcd.xml 0%|▌ | 2/671 [00:00<01:43, 6.46it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_100/fcd.xml 0%|▊ | 3/671 [00:00<01:44, 6.42it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_101/fcd.xml 1%|█▏ | 4/671 [00:00<01:48, 6.12it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_102/fcd.xml 1%|█▍ | 5/671 [00:00<01:41, 6.54it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_103/fcd.xml 1%|█▋ | 6/671 [00:00<01:37, 6.81it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_104/fcd.xml 1%|██ | 7/671 [00:01<01:39, 6.67it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_105/fcd.xml 1%|██▎ | 8/671 [00:01<01:44, 6.32it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_106/fcd.xml 1%|██▌ | 9/671 [00:01<01:43, 6.40it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_107/fcd.xml 1%|██▉ | 10/671 [00:01<01:43, 6.41it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_108/fcd.xml 2%|███▏ | 11/671 [00:01<01:42, 6.47it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_109/fcd.xml 2%|███▍ | 12/671 [00:01<01:37, 6.73it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_11/fcd.xml 2%|███▋ | 13/671 [00:02<01:59, 5.49it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_110/fcd.xml 2%|████ | 14/671 [00:02<01:46, 6.15it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_111/fcd.xml 2%|████▎ | 15/671 [00:02<01:41, 6.44it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_112/fcd.xml 2%|████▌ | 16/671 [00:02<01:43, 6.32it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_113/fcd.xml 3%|████▉ | 17/671 [00:02<01:37, 6.68it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_114/fcd.xml 3%|█████▏ | 18/671 [00:02<01:37, 6.70it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_115/fcd.xml 3%|█████▍ | 19/671 [00:02<01:32, 7.01it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_116/fcd.xml 3%|█████▊ | 20/671 [00:03<01:35, 6.84it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_117/fcd.xml 3%|██████ | 21/671 [00:03<01:31, 7.14it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_118/fcd.xml 3%|██████▎ | 22/671 [00:03<01:36, 6.70it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_119/fcd.xml 3%|██████▌ | 23/671 [00:03<01:32, 7.03it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_12/fcd.xml 4%|██████▉ | 24/671 [00:03<01:31, 7.09it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_120/fcd.xml 4%|███████▏ | 25/671 [00:03<01:33, 6.91it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_121/fcd.xml 4%|███████▍ | 26/671 [00:03<01:29, 7.20it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_122/fcd.xml 4%|███████▊ | 27/671 [00:04<01:34, 6.79it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_123/fcd.xml 4%|████████ | 28/671 [00:04<01:35, 6.71it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_124/fcd.xml 4%|████████▎ | 29/671 [00:04<01:38, 6.52it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_125/fcd.xml 4%|████████▋ | 30/671 [00:04<01:44, 6.14it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_126/fcd.xml 5%|████████▉ | 31/671 [00:04<01:48, 5.91it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_127/fcd.xml 5%|█████████▏ | 32/671 [00:04<01:40, 6.34it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_128/fcd.xml 5%|█████████▍ | 33/671 [00:05<01:41, 6.31it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_129/fcd.xml 5%|█████████▊ | 34/671 [00:05<01:35, 6.66it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_13/fcd.xml 5%|██████████ | 35/671 [00:05<01:31, 6.94it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_130/fcd.xml 5%|██████████▎ | 36/671 [00:05<01:36, 6.59it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_131/fcd.xml 6%|██████████▋ | 37/671 [00:05<01:32, 6.85it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_132/fcd.xml 6%|██████████▉ | 38/671 [00:05<01:32, 6.85it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_133/fcd.xml 6%|███████████▏ | 39/671 [00:05<01:28, 7.13it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_134/fcd.xml 6%|███████████▌ | 40/671 [00:06<01:33, 6.76it/s]No CAV trajectory in █████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▌ | 425/671 [01:12<01:22, 2.99it/s]No CAV trajectory in /app/output/trajectory_data/mcity_av_challenge_results/raw_data/0_482/fcd.xml 64%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▊ | 429/671 [01:16<03:24, 1.18it/s]/usr/local/lib/python3.10/dist-packages/matplotlib/animation.py:1741: UserWarning: Can not start iterating the frames for the initial draw. This can be caused by passing in a 0 length sequence for frames.

If you passed frames as a generator it may be exhausted due to a previous display or save. warnings.warn( 64%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████ | 430/671 [01:16<03:16, 1.22it/s]

zhuhj-tery commented 5 months ago

Have you observed any output videos? It appears that a considerable amount of time has passed prior to executing your AV algorithm. As a result, you may encounter numerous vacant trajectories because the Mcity testing environment has been operating in the background. Nevertheless, if your algorithm is functioning correctly, you should see videos that visually represent the trajectories of the AV.

farabi1038 commented 5 months ago

Hello, it does the same for even the base example that has come exactly as it is for the GitHub. Let me know if you need any further info.

farabi1038 commented 5 months ago

The issue is once by chance the av gets behind of the testing env, next time when there is any video generation problem, the code always try to generate those first and then go to the next . Intuitively, it should just generate video for the run I am running instead of for all the cases . I think in the visualization python file the following line is creating this issue :

traj_files = sorted( glob.glob( os.path.join(data_folder, "mcity_av_challenge_results/raw_data/**/fcd.xml") ) )

It might be a good idea to a run specific video generation. Correct me if I am wrong anywhere.

zhuhj-tery commented 5 months ago

I think your suggestion is good. We will add this option to the visualization script.

zhuhj-tery commented 5 months ago

I have added the function to visualize only one specific trajectory. Please feel free to do some tests.