Diogo Vieira

> Right. We had this limitation from other approaches already for example when we used the opencv stereo camera calibration. Most of these methods use chessboards as patterns, and these...

Hi @miguelriemoliveira! Since I haven't worked on this for the past few weeks, I'm now checking that these methods work properly before running batch calibrations, starting with the OpenCV method...

Hi @miguelriemoliveira! That makes sense, thanks! In that case, all the OpenCV methods work properly and return OK results in the calibration of the real `riwmpbot`. I'm now debugging the...

Hello @miguelriemoliveira and @manuelgitgomes! I was running batch executions of the real `riwmpbot` calibrations using the 5 OpenCV methods and I noticed something about the `process_results` script. This script assumes...

A small correction to my previous comment is that it does not, in fact, need to have a row with the name "Averages" since we can specify the name of...

I got it to work by adding the flag: https://github.com/lardemua/atom/blob/f25c302efde9598f5e753f9c49d3e287129197bb/atom_batch_execution/scripts/process_results#L58-L59 And I changed the instances of `'Collection #'` in the code with this argument. This effectively works, but maybe some...

Thank you @miguelriemoliveira! In the meantime I realized that these results aren't representative of the actual errors, since the reprojection error for the real case of the `riwmpbot_real` system isn't...

I agree, I think this is okay like this. Alternatively (though it sounds a bit "janky"), we could have an optional argument to change the "average row name"? That way...

Yes, thank you!

Awesome! So now we can calibrate the real zau system with the T265 right? I don't remember, did we converge on a solution to connecting the TF tree?