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, Thanks For Developing The Amazing Tool! I Have A Question: I Deployed Trains-Server On Machine A And Started An Experiment On Machine B. Sometimes Machine A Will Reboot Automatically, So The Experiment On Machine B Will Be Killed. I Wonder If There Is

Hi, thanks for developing the amazing tool! I have a question:
I deployed trains-server on machine A and started an experiment on machine B. Sometimes machine A will reboot automatically, so the experiment on machine B will be killed. I wonder if there is a way to keep the experiment on the machine B when the machine A reboot

  
  
Posted 4 years ago
Votes Newest

Answers 6


Hi DelightfulRobin8 ,
Can you provide more info? Are you running the experiment on machine B using trains-agent or simply by running a python script? Also, can you share the logs from the experiment so we can try and understand the reason it was killed?

  
  
Posted 4 years ago

only running a python script with the code" Task.init"

  
  
Posted 4 years ago

And thanks for the kind compliments 🙂

  
  
Posted 4 years ago

Maybe next time it happen i will save the log and share 😂

  
  
Posted 4 years ago

i have clear the log 😓 . it seems like " ... Killed ..."

  
  
Posted 4 years ago

OK 🙂
Next time, instead of resetting the experiment, you can simply change the experiment name in the UI and Trains will create a new experiment entry in the UI when you run your experiment again.

  
  
Posted 4 years ago