Closed vlaskine closed 10 years ago
does this mean I should avoid updating on the segways, lest I break our lab demo?
i don't know why it stopped working: i cannot localize the problem yet
e.g. if i run on my machine:
cat VelodyneLaser12779* | velodyne-to-csv -q --fields=t,x,y,z,block,id,intensity | points-to-partitions --fields=,x,y,z,block
a few lines in every block are garbled
i am trying to localize the issue (which looks bizarre and may be because of some changes in tbb) and understand whether it is due the recent changes in csv::stream
if you plan to show any demos, i would suggest you re-run them beforehand
i don't know when i manage to fix it, since we have a milestone in march with a knife at our throats
fixed by untieing std::cin from std::cout in static space
since std::cout is not flushed anymore every time std::cin is called, it may potentially cause problems in a number of places (nothing i can think about, but please watch and report mishaps like: last lines of a file are not processed or application hands on exit)
something tbb-related: although write_filter type is set to serial_in_order, it seems to output garbled data; e.g. try it on a stream of velodyne data