New tool: Edit Coco Annotation#1889
Conversation
… tools/image_processing/yolo/test-data/Annotation_COCO_visualizer.json
…n to tools/image_processing/yolo/test-data/Edited_COCO_annotations_remove.json
…n to tools/image_processing/yolo/test-data/Edited_COCO_annotations_rename.json
|
Hi if you can add skip-version-check pls |
|
Tutur baba edit coco patch 1
|
For me It's fine |
| @@ -0,0 +1,208 @@ | |||
| <tool id="edit_coco_annotation" name="Edit COCO Annotation" version="1.0.0" profile="25.1"> | |||
There was a problem hiding this comment.
| <tool id="edit_coco_annotation" name="Edit COCO Annotation" version="1.0.0" profile="25.1"> | |
| <tool id="edit_coco_annotation" name="Edit COCO Annotation" version="@TOOL_VERSION@+galaxy@VERSION_SUFFIX@" profile="@PROFILE@"> |
Please use the above tokens
There was a problem hiding this comment.
Ok, but why?
If I use this method, I need to add the following block ?
<macros>
<token name="@TOOL_VERSION@">1.0.0</token>
<token name="@VERSION_SUFFIX@">0</token>
<token name="@PROFILE@">25.1</token>
</macros>
Doesn't that come down to the same thing in the end?
There was a problem hiding this comment.
Hi @SaimMomin12,
Should I also apply these changes to my new tool that was merged yesterday (so not yet available on Galaxy)?
#1892
There was a problem hiding this comment.
@TuturBaba maybe we did a mistake here. Are those coco tool in anyway related to YOLO?
We group Galaxy tools together into so called tool-suites. Those tools share functionality/parameters/requirements and are located in one folder.
That is why we usually have the same version number, same profile etc.
Co-authored-by: Saim Momin <64724322+SaimMomin12@users.noreply.github.com>
Co-authored-by: Saim Momin <64724322+SaimMomin12@users.noreply.github.com>
Features
Tests
Test 1: keep mode — keep track IDs 2, 4–6 and track ID 1 renamed to "Algae"
Test 2: remove mode — remove track ID 1 from frame 130 onwards
Test 3: rename mode — rename track ID 1 to "Algae" and track IDs 2–6 to "Crangon crangon"