About custom datasets and num_pred_height in config #38

When I try to use my own dataset to connect to vidar debugging, point_cloud_range = [-70, -150, -10.0, 70, 150, 10.0], num_pred_height = 16, but there are always some idx data whose loss in the first frame and the second frame is 0. The reason is that when generating cur_origin_points and cur_gt_points, the height of z exceeds num_pred_height, resulting in cur_valid_mask being all false when calculating loss, and subsequent dense.loss is all 0

I would like to know if the range of num_pred_height and point_cloud_range is related to this?
I would like to ask if the author has ever encountered such a situation?