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
When Using

when using trains-server is there any limitation for the debug images in Metrics & Logs ? This small script show the behavior, the iteration kept is only the last one, it "forget" all the previous iteration reports. Did I do something wrong to make this behavior ? I use a localhost trains-server with docker.

  
  
Posted 4 years ago
Votes Newest

Answers 16


Hi SteadyFox10 ,
Sounds like a strange bug related to replacing / (to avoid nesting folders when uploading these files) - we'll take a look and let you know...
And thanks for reporting this :)

  
  
Posted 4 years ago

I'm in a process to setup a trains stack for my projects and so far it work great thank for this awesome work.

  
  
Posted 4 years ago

SteadyFox10 could you try replacing the slash in the image name?

  
  
Posted 4 years ago

Any reason for / to not work?

  
  
Posted 4 years ago

Oh it works with an _ .

  
  
Posted 4 years ago

Thanks!

  
  
Posted 4 years ago

SuccessfulKoala55 Also I see that the images name are not ordered naturaly it's display like this image_name_1 , image_name_10 , image_name_2 , and so on, is it possible to have a natural order to see image_name_1 , image_name_2 , etc... ?

  
  
Posted 4 years ago

Since the image names are strings, the ordering is lexicographical

  
  
Posted 4 years ago

It is in lexicographical ordering as you said.

  
  
Posted 4 years ago

Is this screenshot better?

  
  
Posted 4 years ago

Hi SteadyFox10 the way it works is that Trains limits the debug image history by reusing the same files names, so the UI will only present the iterations where the debug images are relevant for. With your sample code it looks like it exposes a bug , the generated link should contain iteration number, it does not and so it overwrites the debug images every iteration. Here is the image link: https://demofiles.trains.allegro.ai/Test/test_images.6ed32a2b5a094f2da47e6967bba1ebd0/metrics/Test/test.slash.10/Test_test.slash.jpeg as you can see there is no iteration number

  
  
Posted 4 years ago

Ok thanks

  
  
Posted 4 years ago

Just FYI, you can set the number of the debug images history (after which the names are reused) in the configuration file (see https://github.com/allegroai/trains/blob/4bb17ca42081aaf27fabcd21c6a42e32313fb80e/docs/trains.conf#L32 )

  
  
Posted 4 years ago

Can you share the link to de demo app or a full screenshot? I see lexicographical order in your attached image

  
  
Posted 4 years ago

ok I'll go check

  
  
Posted 4 years ago

I made the experiment on the allegroai demo server and it's the same https://demoapp.trains.allegro.ai/projects/fcf3f3fb1013434eb2001870990e5e94/experiments/6ed32a2b5a094f2da47e6967bba1ebd0/output/debugImages . I really think it's a technical limitation to not display all the image am I right ?

  
  
Posted 4 years ago
748 Views
16 Answers
4 years ago
one year ago
Tags