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, Another Question. I Tried To Not

Hi, another question.
I tried to not auto_connect_arg_parser but in that case I need to do the Task.init before I'm parsing the arguments. I don't want that as I'm passing the project name & task name using the arguments.
So my question is how can I modify the arguments in trains server after they were set? and how can I define from my agent the information such as the "script path" and "working directory"?
Thanks

  
  
Posted 3 years ago
Votes Newest

Answers 8


I've solved the first part by importing trains after parsing the arguments. Still not sure about the second part of my question.

  
  
Posted 3 years ago

BTW: 0.14.3 solved the issue you are referring to, so you can import trains before / parsing the args without an issue. Regrading passing project/name as parameters. A few thoughts: (1) you can always rename / move projects from the UI (2) If you are running it with trains-agent there is no meaning to these arguments, as by definition the Task was already created... Maybe we should give an option to exclude a few arguments from argparser, I think this topic came up a few times... What do you think?

  
  
Posted 3 years ago

PompousBeetle71 so basically exclude parameters that are considered "local" only, so that other people will not accidentally use them?

  
  
Posted 3 years ago

AgitatedDove14 yes, exactly.

  
  
Posted 3 years ago

awesome 🙂

  
  
Posted 3 years ago

PompousBeetle71 cool, next RC will have the argparse exclusion feature :)

  
  
Posted 3 years ago

Hi PompousBeetle71 , what exactly is the scenario / problem we are trying to solve ?

  
  
Posted 3 years ago

AgitatedDove14
I think exclusion of arguments from the arg praser is a good idea.
Regarding the other parameters such as the working directory and script path. I just want to automate it as when running the script from my local machine for the "template" of the experiment it gets values that won't work when running in the worker. I just thought it can be automated from the code.

  
  
Posted 3 years ago
633 Views
8 Answers
3 years ago
one year ago
Tags
Similar posts