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
Sometimes when tagging new labels that were not thought of when the project was initialized are needed. Essentially, it would be nice to be able to add classes to the config.ini and have the pascal_label_map update automatically with the new labels.
@yashpande provided this code
The code to make a new label map file:
with open(config_file["label_map_path"], "w") as map_file:
for index, name in enumerate(config_file["classes"].split(","), 1):
map_file.write("item {{\n id: {}\n name: '{}'\n}}".format(index, name))
The easiest way is probably just to manually fill in the variables config_file["label_map_path"] and config_file["classes"] then run it as an independent script.
You might want to add an issue about just having that code run each time training kicks off.
The text was updated successfully, but these errors were encountered:
@olgaliak The best place for this would likely be in convert_tf_record.py in line 73. Since config_file["classes"] is already a parameter (tag_names) you would simply also have to send the config_file["label_map_path"] parameter as label_map_path and then you could use the code:
Sometimes when tagging new labels that were not thought of when the project was initialized are needed. Essentially, it would be nice to be able to add classes to the config.ini and have the pascal_label_map update automatically with the new labels.
@yashpande provided this code
The code to make a new label map file:
The easiest way is probably just to manually fill in the variables
config_file["label_map_path"]
andconfig_file["classes"]
then run it as an independent script.You might want to add an issue about just having that code run each time training kicks off.
The text was updated successfully, but these errors were encountered: