You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now labels live in CSV file which gets updated with new labels and continually updated and renamed/modified every time a label correction run is done (fix_labels.py).
Perhaps a database would be better suited to this over time?
Just update the rows indexed by image_id (which is a UUID) with new values each time there's a major labelling change?
The text was updated successfully, but these errors were encountered:
mrdbourke
added
labelling
Data labelling issue relating to the annotation or improvement of a dataset.
database
Issues to do with Nutrify's database(s)
labels
Jan 12, 2023
On Thu, 12 Jan 2023, 5:09 pm Daniel Bourke, ***@***.***> wrote:
Right now labels live in CSV file which gets updated with new labels and
continually updated and renamed/modified every time a label correction run
is done (fix_labels.py).
Perhaps a database would be better suited to this over time?
Just update the rows indexed by image_id (which is a UUID) with new
values each time there's a major labelling change?
—
Reply to this email directly, view it on GitHub
<#51>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMGDQM536S3Q4IQFLLMT2V3WR57YFANCNFSM6AAAAAATYZEALU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Right now labels live in CSV file which gets updated with new labels and continually updated and renamed/modified every time a label correction run is done (
fix_labels.py
).Perhaps a database would be better suited to this over time?
Just update the rows indexed by
image_id
(which is a UUID) with new values each time there's a major labelling change?The text was updated successfully, but these errors were encountered: