Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Please include a summary of the change and which issue is fixed or implemented. Please also include relevant motivation and context (e.g. links, docs, tickets etc.).
List any dependencies that are required for this change.
Related to this issue #311.
I debugged by outputting the contents of epoch here https://github.com/roboflow/roboflow-python/blob/main/roboflow/core/version.py#L414
Somehow for the last epoch , we do not find the "loss" values . (It shows up in UI though, but somehow not in this dict).
Here is the output from my debugging. Please refer the last epoch 167
So, I am proposing defensive coding and adding the "loss" only if those keys exist in the dictionary.
https://app.roboflow.com/test-4h9f7/test2-forest-fire-detection/6
Type of change
Please delete options that are not relevant.
Related to this issue TRAINING: Errors after executing version.train() due to "KeyError: 'box_loss'" #311.
How has this change been tested, please provide a testcase or example of how you tested the change?
From the UI, Created a new project, new version with sample dataset, created version.
I then modified the code (as in the PR) in my virtual environment and tested it.
PS/ Side Note : There is one more bug in the code where we get error https://github.com/roboflow/roboflow-python/blob/main/roboflow/core/version.py#L450 . But we can probably take it as a separate PR.
Opened a new issue for tracking that.
Any specific deployment considerations
For example, documentation changes, usability, usage/costs, secrets, etc.
Docs