Yup, I see. My apologies for not catching that before posting 🙂
They inherit from one another, so it does make sense. Also the add_tags is on the "main" Task and not the backend parent
Oh btw the set_system_tags we talked about previously to auto-archive by adding the archived tag is throwing me an error.
for t in top_exp: t.set_tags(t.get_tags() + ["trial"]) t.set_system_tags(t.get_system_tags() + ["archived"])With error: ValueError: Task object can only be updated if created or in_progress
I think its because the _edit call happens after the set_task_property call?
BTW: the new documentation should contain a full search over the docstring
LudicrousParrot69 there is already
Task.add_tags
https://github.com/allegroai/clearml/blob/2d561bf4b3598b61525511a1a5f72a9dba74953e/clearml/task.py#L964
How odd, its not in my task.py file!
Let me check…
Ah. The code inspector is jumping to backend_interface.task.py, not clearml.task.py, how embarrassing for me!
Just fixed, will be merged later, basically some field you are not supposed to change post execution (but system tags should be exempt from that). The SDK checks before the backend does, so you get a nice error 🙂 anyhow the backend will obviously allow it
Notice that if you pass string it will split it based on spaces
Ah fantastic, Ill use that over IDEs suggestions from now on 🙂