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
Answered
Hello. I Have A Question Regarding Pipeline Parameters. Is It Possible To Reference Pipeline Parameters In Other Fields Of The

Hello. I have a question regarding pipeline parameters. Is it possible to reference pipeline parameters in other fields of the https://clear.ml/docs/latest/docs/references/sdk/automation_controller_pipelinecontroller#add_function_step ?

I know it can be done for function_kwargs as per the example here: https://clear.ml/docs/latest/docs/guides/pipeline/pipeline_functions

But what about if I want to parameterize the function step execution_queue or docker_args for example?

  
  
Posted one year ago
Votes Newest

Answers 5


Hi DangerousDragonfly8 ! At the moment, this is not possible, but we do have it in plan (we had some prior requests for this feature)

  
  
Posted one year ago

Thank you for the reply SmugDolphin23

Is there any possible workaround at the moment?

  
  
Posted one year ago

DangerousDragonfly8 I'm pretty sure you can use pre_execute_callback or post_execute_callback for this. you get the PipelineController in the callback and the Node . Then you can modify the next step/node. Note that you might need to access the Task object directly to change the execution_queue and docker_args . You can get it from node.job.task https://clear.ml/docs/latest/docs/references/sdk/automation_controller_pipelinecontroller#add_function_step

  
  
Posted one year ago

Thank you SmugDolphin23 I'll try it out.

  
  
Posted one year ago

Hi SmugDolphin23 . I have tried to access node.job with a pre_execute_callback but the node object does not have the job attribute set as you can see above.

  
  
Posted one year ago
1K Views
5 Answers
one year ago
one year ago
Tags