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
Any Specific Reason For Modelling Experiments As Separate Tasks Rather Than A Single Entity With Multiple Runs?

Any specific reason for modelling experiments as separate tasks rather than a single entity with multiple runs?

  
  
Posted 2 years ago
Votes Newest

Answers 3


Yeah was planning to use nested projects for that

  
  
Posted 2 years ago

Yes, experiments are standalone as they do not have to have any connecting thread.
When would you say a new "run" vs a new "experiment" ? when you change a parameter ? change data ? change code ?
If you want to "bucket them" use projects 🙂 it is probably the easiest now that we have support for nested projects.

  
  
Posted 2 years ago

tested=nested 🙂

  
  
Posted 2 years ago
495 Views
3 Answers
2 years ago
one year ago
Tags