You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 80a8070
Browse filesBrowse the repository at this point in the historyBrowse files
- Either set `COMET_API_KEY` in the environment, or
223
+
- Pass an explicit `comet_api_key` in the logger config.
224
+
225
+
3) Configure logging in your training setup.
226
+
227
+
```python
228
+
from megatron.bridge.training.config import LoggerConfig
229
+
230
+
cfg.logger = LoggerConfig(
231
+
tensorboard_dir="./runs/tensorboard",
232
+
comet_project="my_project",
233
+
comet_experiment_name="llama32_1b_pretrain_run",
234
+
comet_workspace="my_workspace", # optional
235
+
comet_tags=["pretrain", "llama32"], # optional
236
+
)
237
+
```
238
+
239
+
```{note}
240
+
Comet ML is initialized lazily on the last rank when `comet_project` is set and `comet_experiment_name` is non-empty.
241
+
```
242
+
243
+
#### Comet ML Configuration with NeMo Run Launching
244
+
245
+
For users launching training scripts with NeMo Run, Comet ML can be optionally configured using the {py:class}`bridge.recipes.run_plugins.CometPlugin`.
246
+
247
+
The plugin automatically forwards the `COMET_API_KEY` and by default injects CLI overrides for the following logger parameters:
248
+
249
+
-`logger.comet_project`
250
+
-`logger.comet_workspace`
251
+
-`logger.comet_experiment_name`
252
+
253
+
200
254
#### Progress Log
201
255
202
256
When `logger.log_progress` is enabled, the framework generates a `progress.txt` file in the checkpoint save directory.
0 commit comments