Skip to content

Commit 641f3ba

Browse files
authored
[1137] Example of tag descriptions (ecmwf#1212)
* exampels * more explanations
1 parent b452bd2 commit 641f3ba

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

config/default_config.yml

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -158,3 +158,25 @@ train_log_freq:
158158
terminal: 10
159159
metrics: 20
160160
checkpoint: 250
161+
162+
163+
# Tags for experiment tracking
164+
# These tags will be logged in MLFlow along with completed runs for train, eval, val
165+
# The tags are free-form, with the following rules:
166+
# - tags should be primitive types (strings, numbers, booleans). NO lists or dictionaries
167+
# - tags should not duplicate existing config entries.
168+
# - try to reuse existing tags where possible. MLFlow does not like having too many unique tags
169+
# - do not use long strings in values (less than 20 characters is a good rule of thumb, we may enforce this in the future)
170+
wgtags:
171+
# The name of the organization of the person running the experiment.
172+
# This may be autofilled in the future. Expected values are lowercase strings of
173+
# the organizations codenames in https://confluence.ecmwf.int/display/MAEL/Staff+Contact+List
174+
# e.g. "ecmwf", "cmcc", "metnor", "jsc", "escience"
175+
org: None
176+
# The name of the experiment. This is a distinctive codename for the experiment campaign being run.
177+
# This is expected to be the primary tag for comparing experiments in MLFlow.
178+
# Expected values are lowercase strings with no spaces, just underscores:
179+
# Examples: "rollout_ablation_grid"
180+
exp: None
181+
# *** Experiment-specific tags ***
182+
grid: None

0 commit comments

Comments
 (0)