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
Hey All. I'M Seeing A Strange Error When Trying To Run Hyperparameter Optimisation By Cloning A Base Training Task

Hey all. I'm seeing a strange error when trying to run hyperparameter optimisation by cloning a base training task
Action failed <500/0: tasks.clone/v1.0 (key 'nokia 2.4' must not contain '.')> (task=6eecc8fc55554a5f9f48ef7fad30a5de, new_task_name=logistic-regression-paths-and-sales-tfidf-device-model-0, new_task_parent=6eecc8fc55554a5f9f48ef7fad30a5de)I think this is due to the label map including some keys with a . in them. Why is this an issue?

  
  
Posted 3 years ago
Votes Newest

Answers 11


Verified, you are correct "." in label enumeration will break the clone .
I'll make sure this bug is passed to backend guys to fix. Thanks TenseOstrich47 !
meanwhile maybe "_" instead ? 😁

  
  
Posted 3 years ago

This is a suspicion only. It could be something else. In my case, there is no artifact or other config with a dict containing that key. Only the label map contains that key

  
  
Posted 3 years ago

I think this is due to the label map including some keys with a 

.

  in them.

Hi TenseOstrich47 what do you mean "label"

  
  
Posted 3 years ago

Hey Martin. By labels map, I'm referring to the labels map assigned to the model. The one you can view in the models tab // labels

  
  
Posted 3 years ago

Ohh, hmm, that is odd, there should not be a limit there. Let me check ....

  
  
Posted 3 years ago

using this method training_task.set_model_label_enumeration(label_map)

  
  
Posted 3 years ago

Hi TenseOstrich47
Thanks for following up!
Should be solved in the upcoming release (I think ETA is next week) 🙂

  
  
Posted 3 years ago

Yeah, it's not urgent. I will change the labels around to avoid this error 🙂 thanks for checking!

  
  
Posted 3 years ago

No worries, happy to help with the bug hunt 😄

  
  
Posted 3 years ago

My pleasure, and apologies 🙂

  
  
Posted 3 years ago

Any news on this bug?

  
  
Posted 3 years ago