Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Hi All

Hi all 👋 ! I'm creating a pipeline from tasks with clearml-task (and with PipelineController).
I execute the tasks remotely on an open-source server I set up. Everything run perfectly, but I can't access the pipeline in the "pipelines" in the UI, but I get the link to the pipeline in the consol of the PipelineController task.
I wonder if I'm missing something, do I need to add a parameter to make it appear in the pipelines ? 🤔

Posted 5 months ago
Votes Newest

Answers 5

Hi @<1523701205467926528:profile|AgitatedDove14> , yes the pipeline is created via the clearml-task CLI. I find it less constraining to launch a pipeline via the CLI. I'm opening a GitHub issue right now, hoping it will be fixed soon. Thank you for your answer 😁

Posted 5 months ago

Thank you! 🤩

Posted 5 months ago

Hi @<1546303293918023680:profile|MiniatureRobin9> , can you please add the full log of the run? Also, do you have some code that reproduces this?

Posted 5 months ago

Hi @<1523701070390366208:profile|CostlyOstrich36> , you can reproduce it with the pipeline of the iris dataset from the github None
I have a gitlab repo, I run this command to run this pipeline :
clearml-task --project test-iris --name pipeline-iris --repo ***.git --script pipeline/pipeline_from tasks.py --queue services --requirements requirements.txt --task-type controller --branch main
My agent is setup as a docker.
Here are the logs :

Posted 5 months ago

Hi @<1546303293918023680:profile|MiniatureRobin9> could it be the pipeline logic is created via the clrarml-task CLI? If this is the case, I think this is an edge case we should fix. Basically it creates a Task instead of pipeline, which in.essence only effects the UI. To solve it, just run the pipeline locally, notice that by default when you start it, it will actually stop the local run and relaunch itself on an agent.
Also, could you open a GitHub issue so we add a flag for it?

Posted 5 months ago
5 Answers
5 months ago
5 months ago
Similar posts