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
And An Explicit Question: When Using

and an explicit question:
When using Task.get_tasks how do I filter by specific parameters? For example I have a script that accepts as a command line argument the argument model_name and let's say its set to gpt-3 one time and gpt-neo another time. I want to fetch the experiment that the Args/model_name == "gpt-3" how do I do that? I went over the https://github.com/allegroai/clearml/blob/aba130eb1f0ddfb147185ffbf41c4d13781bbdd8/clearml/backend_api/services/v2_9/tasks.py#L5781 (the Task.get_tasks docs sent me there) but I couldn't figure out how to filter by parameters

  
  
Posted 3 years ago
Votes Newest

Answers 9


It basically allows you to sneak in custom request fields even if they don't currently match the schema used by the SDK for communication with the server 🙂

  
  
Posted 3 years ago

Wait until I get my breath back

  
  
Posted 3 years ago

if I set it to 24 does it explode?

  
  
Posted 3 years ago

now I'm curious what is the effect of _allow_extra_fields_

  
  
Posted 3 years ago

WackyRabbit7 I have a development backdoor for you 🙂 - but keep it between us 😄
Use this:
task_filter = {"hyperparams.Args.model_name.value": "gpt-3", "_allow_extra_fields_": True}We'll make sure this override will be the default in future versions

  
  
Posted 3 years ago

💪

  
  
Posted 3 years ago

let me see if I can find something

  
  
Posted 3 years ago

Oh, sorry, we don't seem to support it right now in the SDK side

  
  
Posted 3 years ago

Well, the interface there is still not very tight (still relies on internal server schema, mostly) - we plan to design a better query interface soon.
Meanwhile, what you're after can be done using:
task_filter = {"hyperparams.Args.model_name.value": "gpt-3"}

  
  
Posted 3 years ago
955 Views
9 Answers
3 years ago
one year ago
Tags