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
I'M Experiencing Some Weird Behavior From The Automatic Logging Iterations. It Seem To Be Capped At The Number Of Batches Rather Than The Epochs. How Can I Control Which Variable The Logging Mechanism Tracks?

I'm experiencing some weird behavior from the automatic logging iterations. It seem to be capped at the number of batches rather than the epochs. How can I control which variable the logging mechanism tracks?

  
  
Posted 3 years ago
Votes Newest

Answers 6


Hi AgitatedDove14

Turns out my double loop caused some issues.

for e in range(num_epochs): for phase in ['train','valid']: for batch in dataloader:

  
  
Posted 3 years ago

LOL, no worries 🙂

  
  
Posted 3 years ago

Hi TrickyRaccoon92
If you are reporting to tensor-board, then "iteration" equals step. Is this the case?

  
  
Posted 3 years ago

I'm afraid I just had an improper indentation somewhere, no harms done. Thanks for the reply.

  
  
Posted 3 years ago

Interesting... TrickyRaccoon92 could it be the validation phase was creating a new Tensorboard file ?

  
  
Posted 3 years ago

Upon removing the phase loop the epoch was detected automatically again.

  
  
Posted 3 years ago
1K Views
6 Answers
3 years ago
one year ago
Tags