Closed AlicanAKCA closed 9 months ago
When you create an Experiment()
, can you add the parameter auto_output_logging="simple"
like:
experiment = Experiment(
api_key="xxxx",
project_name=project_name,
workspace="segmentations",
auto_output_logging="simple"
)
and report back if that works?
Firstly, thank you for your interest. I just tried but the logs and graphs are the same as before.
It looks like the YOLO example will create the comet_ml Experiment automatically, so you don't need to make an Experiment. I suspect that you are creating two experiments, and the metrics are going to the second one.
I do not think that the code creates another Experiment on its own in the background. GPU utilization metrics were plotted. These screenshots have been taken from another Experiment that also had been run with 2 GPUs:
What happens if you run the following version:
%env COMET_API_KEY= xxxx
import comet_ml
from comet_ml import Experiment
comet_ml.init()
from ultralytics import YOLO
MODEL_PATH = "yolov8l-seg.yaml"
model = YOLO(MODEL_PATH)
experiment_name = 'nodule-seg_LARGE_v1.0'
project_name = '2SEGMENT'
model.train(data="/kaggle/working/dataset/data.yaml", imgsz = 720, optimizer= 'AdamW',lr0= 0.0001, batch=16,
name=experiment_name,mask_ratio= 1,
save_period=4, single_cls = True, device = [0,1] ,epochs=40, dfl = 1.0)
Does it create a Comet experiment?
Yes, it does. But it located in the "General" tab. Also, experiment name is set to comparative_lepton_7102. Lastly, the loggings were sent into this experiment. So, I think it sent the loggings into another experiment that is automatically created by comet.
This page of documentation might be useful to you as it shows how to set experiment name and other items: https://docs.ultralytics.com/yolov5/tutorials/comet_logging_integration/
Describe the Bug
Experiment is not being shown if I run the code using 2 GPUs. The log is stucked at the begining of the training. The graphs' metrics aren't sent into comet also.
Expected behavior
A clear and concise description of what you expected to happen.
Where is the issue?
To Reproduce
Steps to reproduce the behavior:
Stack Trace
If possible please include the full stack trace of your issue here
Code in the notebook:
Screenshots