Hello all,
when testing my MotionPlanner.py, I get the following error message for the mentioned scenario:
AssertionError: <Trajectory/state_list>: all states must have the same attributes. Attributes of first state: [‘position’, ‘orientation’, ‘velocity’, ‘steering_angle’, ‘acceleration’, ‘time_step’].
This is actually the only file so far where I get an error message. Does somebody have an idea what could be wrong here?
Thank you so much in advance!
Regards
Hi,
other students have reported the same. you may skip this scenario before it is fixed.
thanks for the feedback!
Sorry to revive an old thread. But for the 2020a data all the Zambia scenarios are throwing the same error. Since this was over two years ago, has a fix been published?
Basically throughout the code, such as in PrimitiveState, the ‘acceleration’ attribute is always dropped.
I can trick the code to run by adding if hasattr(self.state_initial, 'acceleration'): del self.state_initial.acceleration in SearchBaseClass.__init__, just like what’s done with the attributes ‘yaw_rate’ and ‘slip_angle’. Not sure if that’s valid though.
Output of batch script:
============================== Exception occurred ==============================
- ZAM_Tjunction-1_100_T-1
- ZAM_Tjunction-1_43_T-1
- ZAM_Tjunction-1_44_T-1
- ZAM_Tjunction-1_45_T-1
- ZAM_Tjunction-1_46_T-1
- ZAM_Tjunction-1_47_T-1
- ZAM_Tjunction-1_48_T-1
- ZAM_Tjunction-1_49_T-1
- ZAM_Tjunction-1_50_T-1
- ZAM_Tjunction-1_51_T-1
- ZAM_Tjunction-1_52_T-1
- ZAM_Tjunction-1_53_T-1
- ZAM_Tjunction-1_54_T-1
- ZAM_Tjunction-1_55_T-1
- ZAM_Tjunction-1_56_T-1
- ZAM_Tjunction-1_57_T-1
- ZAM_Tjunction-1_58_T-1
- ZAM_Tjunction-1_59_T-1
- ZAM_Tjunction-1_60_T-1
- ZAM_Tjunction-1_61_T-1
- ZAM_Tjunction-1_62_T-1
- ZAM_Tjunction-1_63_T-1
- ZAM_Tjunction-1_64_T-1
- ZAM_Tjunction-1_65_T-1
- ZAM_Tjunction-1_66_T-1
- ZAM_Tjunction-1_67_T-1
- ZAM_Tjunction-1_68_T-1
- ZAM_Tjunction-1_69_T-1
- ZAM_Tjunction-1_70_T-1
- ZAM_Tjunction-1_71_T-1
- ZAM_Tjunction-1_72_T-1
- ZAM_Tjunction-1_73_T-1
- ZAM_Tjunction-1_74_T-1
- ZAM_Tjunction-1_75_T-1
- ZAM_Tjunction-1_76_T-1
- ZAM_Tjunction-1_77_T-1
- ZAM_Tjunction-1_78_T-1
- ZAM_Tjunction-1_79_T-1
- ZAM_Tjunction-1_80_T-1
- ZAM_Tjunction-1_81_T-1
- ZAM_Tjunction-1_82_T-1
- ZAM_Tjunction-1_83_T-1
- ZAM_Tjunction-1_84_T-1
- ZAM_Tjunction-1_85_T-1
- ZAM_Tjunction-1_86_T-1
- ZAM_Tjunction-1_87_T-1
- ZAM_Tjunction-1_88_T-1
- ZAM_Tjunction-1_89_T-1
- ZAM_Tjunction-1_90_T-1
- ZAM_Tjunction-1_91_T-1
- ZAM_Tjunction-1_92_T-1
- ZAM_Tjunction-1_93_T-1
- ZAM_Tjunction-1_94_T-1
- ZAM_Tjunction-1_95_T-1
- ZAM_Tjunction-1_96_T-1
- ZAM_Tjunction-1_97_T-1
- ZAM_Tjunction-1_98_T-1
- ZAM_Tjunction-1_99_T-1
Hi, different planning problems might give you initial states with different components. The current solution format require that all states in the trajectory possess the same attributes. You can fill the states output from your planner with 0 for those extra attributes in the initial state if it does not affect the validity of your solution (this depends on which vehicle model you use).