mmod automatically determines the detector window's sizes by analyzing the dataset without considering the cropper rotation angle.
However if I set cropper rotation angle a high value, (e.g. cropper.set_max_rotation_degrees(90) ) dataset will dramatically change and previous "detector window's sizes" might not suffice. Do I miss something?
How can I handle highly rotated and cropped dataset?
Rather than setting a high value for cropper angle, should I manually rotate the dataset? (e.g. "imglab --rotate ..")
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
mmod automatically determines the detector window's sizes by analyzing the
dataset without considering the cropper rotation angle.
However if I set cropper rotation angle a high value, (e.g.
cropper.set_max_rotation_degrees(90) ) dataset will dramatically change and
previous "detector window's sizes" might not suffice. Do I miss something?
How can I handle highly rotated and cropped dataset?
Rather than setting a high value for cropper angle, should I manually
rotate the dataset? (e.g. "imglab --rotate ..")
mmod automatically determines the detector window's sizes by analyzing the dataset without considering the cropper rotation angle.
However if I set cropper rotation angle a high value, (e.g. cropper.set_max_rotation_degrees(90) ) dataset will dramatically change and previous "detector window's sizes" might not suffice. Do I miss something?
How can I handle highly rotated and cropped dataset?
Rather than setting a high value for cropper angle, should I manually rotate the dataset? (e.g. "imglab --rotate ..")
Yeah, that's all correct. There are lots of ways to do it, simplest is
probably what you suggested of using imglab to just prerotate by a big
value.
On Thu, May 27, 2021 at 4:16 AM John Puskin johnpuskin@users.sourceforge.net wrote: