-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Roboflow data formats #1044
Conversation
frame_filename = parsed_record.get("image/filename", None).numpy().decode("utf-8") | ||
frame_height = tf.cast(parsed_record.get("image/height", 0), tf.int64).numpy().item() | ||
frame_width = tf.cast(parsed_record.get("image/width", 0), tf.int64).numpy().item() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need these change except frame_id
? If parsed_record.get("image/filename", None) => None
, None.numpy()
is impossible. This type of error can be confusing than raising KeyError
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, I have thought about it, but tf_detection_api
is used to contain them. Only the frame_id
is not included in Roboflow TFRecord format. Is it better to update others under consideration of KeyError
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that it is better to leave it to raise KeyError
in this case because it is genuinely KeyError
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Summary
How to test
Checklist
License
Feel free to contact the maintainers if that's a concern.