Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UpgradeNetAsNeeded should refuse to process nets with mixed versions #3381

Closed
seanbell opened this issue Nov 24, 2015 · 0 comments
Closed

UpgradeNetAsNeeded should refuse to process nets with mixed versions #3381

seanbell opened this issue Nov 24, 2015 · 0 comments

Comments

@seanbell
Copy link

The upgrade code (UpgradeNetAsNeeded) should refuse to process a net that has a mix of layer versions (some from the old format layers, and some from the new format layer), and give a message explaining the problem and how to manually fix it. Otherwise, you end up with some layers being silently deleted (e.g. #3375).

I thought this was already an issue, but I couldn't find it.

zouxiaochuan pushed a commit to zouxiaochuan/caffe that referenced this issue Mar 17, 2016
die loudly if a net definition (prototxt) mixes proto formats by
defining both `layer` and `layers` fields instead of complaining but
discarding and continuing.

fix BVLC#3381
SvenTwo pushed a commit to SvenTwo/caffe that referenced this issue Apr 6, 2016
die loudly if a net definition (prototxt) mixes proto formats by
defining both `layer` and `layers` fields instead of complaining but
discarding and continuing.

fix BVLC#3381
fxbit pushed a commit to Yodigram/caffe that referenced this issue Sep 1, 2016
die loudly if a net definition (prototxt) mixes proto formats by
defining both `layer` and `layers` fields instead of complaining but
discarding and continuing.

fix BVLC#3381
zouxiaochuan pushed a commit to zouxiaochuan/caffe that referenced this issue Oct 24, 2016
die loudly if a net definition (prototxt) mixes proto formats by
defining both `layer` and `layers` fields instead of complaining but
discarding and continuing.

fix BVLC#3381
zouxiaochuan pushed a commit to zouxiaochuan/caffe that referenced this issue Oct 24, 2016
die loudly if a net definition (prototxt) mixes proto formats by
defining both `layer` and `layers` fields instead of complaining but
discarding and continuing.

fix BVLC#3381
zouxiaochuan pushed a commit to zouxiaochuan/caffe that referenced this issue Feb 15, 2017
die loudly if a net definition (prototxt) mixes proto formats by
defining both `layer` and `layers` fields instead of complaining but
discarding and continuing.

fix BVLC#3381
zouxiaochuan pushed a commit to zouxiaochuan/caffe that referenced this issue Feb 15, 2017
die loudly if a net definition (prototxt) mixes proto formats by
defining both `layer` and `layers` fields instead of complaining but
discarding and continuing.

fix BVLC#3381
zouxiaochuan pushed a commit to zouxiaochuan/caffe that referenced this issue Feb 15, 2017
die loudly if a net definition (prototxt) mixes proto formats by
defining both `layer` and `layers` fields instead of complaining but
discarding and continuing.

fix BVLC#3381
zouxiaochuan pushed a commit to zouxiaochuan/caffe that referenced this issue Feb 15, 2017
die loudly if a net definition (prototxt) mixes proto formats by
defining both `layer` and `layers` fields instead of complaining but
discarding and continuing.

fix BVLC#3381
acmiyaguchi pushed a commit to acmiyaguchi/caffe that referenced this issue Nov 13, 2017
die loudly if a net definition (prototxt) mixes proto formats by
defining both `layer` and `layers` fields instead of complaining but
discarding and continuing.

fix BVLC#3381
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant