Merged
Conversation
Over version introduced in BVLC#1384 Highlights: * Interface change: column order is now determined by using a list of `OrderedDict` objects instead of `dict` objects, which obviates the need to pass around a tuple with the column orders. * The outputs are now named according to their names in the network protobuffer; e.g., if your top is named `loss`, then the corresponding column header will also be `loss`; we no longer rename it to, e.g., `TrainingLoss` or `TestLoss`. * Fixed the bug/feature of the first version where the initial learning rate was always NaN. * Add optional parameter to specify output table delimiter. It's still a comma by default. You can use Matlab code from [this gist](https://gist.github.com/drdan14/d8b45999c4a1cbf7ad85) to verify that your results are the same before and after the changes introduced in this pull request. That code assumes that your `top` names are `accuracy` and `loss`, but you can modify the code if that's not true.
f74c649 to
23d28fd
Compare
Member
|
Sounds improved all around. Thanks! |
shelhamer
added a commit
that referenced
this pull request
May 30, 2015
Python log parser improvements
|
I am using the log parser with this input: But this produces the following strange last values of 1.0 for the learning rates: Test
|
Contributor
Author
|
@drdan14 I am getting the following error when parsing a log without any test phase: Training logs with a test phase are parsed ok. |
Contributor
Author
|
@npit Please post a link to the training log that generates the error. And what is |
|
@drdan14 |
Contributor
Author
|
Thanks @dgolden1 ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Improvements to python log parser introduced in #1384
Master-based PR version of #1547
Highlights:
OrderedDictobjects instead ofdictobjects, which obviates the need to pass around a tuple with the column orders.loss, then the corresponding column header will also beloss; we no longer rename it to, e.g.,TrainingLossorTestLoss.You can use Matlab code from this gist to verify that your results are the same before and after the changes introduced in this pull request. That code assumes that your
topnames areaccuracyandloss, but you can modify the code if that's not true.