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
Hi! Please, Could Anyone Explain This Sort Of Behaviour? First, We Save A Model Checkpoint During Training (Both In

Hi! Please, could anyone explain this sort of behaviour?

First, we save a model checkpoint during training (both in .pth and .onnx format)
` output_model_pth = OutputModel(task='task_name', name='running_best_pth')
output_model_pth.update_weights('/path/to/model.pth', upload_uri='some_aws_uri',
target_filename='running_best.pth')

output_model_onnx = OutputModel(task='task_name', name='running_best_onnx')
output_model_pth.update_weights('/path/to/model.onnx', upload_uri='some_aws_uri',
target_filename='running_best.onnx') Then, we try to use running_best_pth as a starting point for another experiment input_model = InputModel(project='our_project', name='running_best_pth')
print(input_model.name) It returns running_best_onnx Why onnx when it should be pth ` ?

btw, in web ui there are 2 distinct models with correct names and file addresses

  
  
Posted one year ago
Votes Newest

Answers 9


Hi MelancholyElk85 ,
What happens when you try:
input_model = InputModel(project='our_project', name='^running_best_pth$') print(input_model.name)

  
  
Posted one year ago

SuccessfulKoala55 It gives the correct name, that is running_best_pth !

  
  
Posted one year ago

I think that's a bug in the interface - the query field itself is a regex field, but the name argument does not mention that

  
  
Posted one year ago

WDYT?

  
  
Posted one year ago

😄

  
  
Posted one year ago

We can either fix the documentation, or make sure we wrap this text accordingly inside the call

  
  
Posted one year ago

Sounds good, I'll fix the implementation 🙂

  
  
Posted one year ago

Thank you

  
  
Posted one year ago

I think it would be intuitive to have an exact name or introduce another parameter that regulates whether name is regex

And when it is a regex, it can return all matched models (e.g. as list) rather than only the last one

  
  
Posted one year ago
665 Views
9 Answers
one year ago
one year ago
Tags