issue-tracking
issue-tracking copied to clipboard
Cannot log hyperparameter if it looks like a number in scientific notation
Where is the issue?
- [x] Comet Python SDK
- [x] Comet UI
- [ ] Third Party Integrations (Huggingface, TensorboardX, Pytorch Lighting etc)
To Reproduce
Steps to reproduce the behavior:
-
api_exp.log_parameters({'hash': '80e5005'})
- Experiments > 'hash' filled is blank for this experiment, other hashes work
- If I get the experiment via
comet_ml.API(...).get(...)
, then theexp.get_parameters_summary("hash")
is[]
.
Screenshots or GIFs
Link to Comet Project/Experiment
https://www.comet.ml/mscham/normal/view/aeJxyfMF2731Kme0gAn0i2oqb/experiments
Additional context
I have reported the same bug before ( in the slack at the time ), but then full number strings "123456"
were the problem.
Thanks for reporting @mova.
Would you be able to link me to the experiment with the issue? I can't seem to find it in your project page.
Oh, sorry, I accidentally archived it. https://www.comet.ml/mscham/normal/932caccd927a4073b60a27aaa356b346 or: https://www.comet.ml/mscham/normal/10a59adb6b7a4fbdbdf4d0e9d9e1164f
Thank you @mova! I was able to reproduce the issue. Let me check with our team to see what might be happening. I will update you here when we have a resolution.
@mova Would it be possible to increase the character length of your hash strings so that they do not look like scientific notation? This could be a quick way to unblock you with the issue
Hey,
if I'm understanding correctly that would only make it less likely to happen, since 80098765347887667e5005786546
is still valid python. If possible, the datatype of parameters/metrics could be recorded to exclude such errors in the future.
For my personal project, i have changed the way the hash is calculated to avoid the issue for now.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.