-
Notifications
You must be signed in to change notification settings - Fork 186
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
tf 1.0 changes tf.pack -> tf.stack #8
Comments
@ahundt, I guess I will create a separate branch since tf 1.0 is not backwards compatible. |
the changes were quite minor |
I am getting following error after changing tf.stack when I am running fcn_32s_train.ipynb
|
I think that is a general problem with tf 1.0 |
You are correct, it was due to tf.zeros_initializer. |
Is tensorflow 1.0 backend available? I am using windows python3.5 tensorflow 1.0, and it always reports errors that I cannot fix myself. |
Thanks for the reply. I just find a way to use tensorflow upgrade tool to upgrade the folder |
Also I think if you use |
fcn_16s_checkpoint_path variable is not being used in the code.
I am using model_fcn8s_final.ckpt provided in dropbox.
saver.restore(sess, "C:/temp/model_fcn8s_final.ckpt")
What is the image size of this cat ?
I have this cat size as width = 144 and height = 85.
I am getting good segmentation of me.jpg and image size is 400x400.
I would like to whether segmentation depends on image size.
…On Sat, Mar 11, 2017 at 9:36 PM, zhaozj89 ***@***.***> wrote:
Also I think if you use fcn_8s_checkpoint_path =
'C:/TensorFlow/checkpoints/vgg_8.ckpt' instead of
``fcn_16s_checkpoint_path = 'C:/TensorFlow/checkpoints/vgg_16.ckpt', it
may produce better segmentation result. But I am not sure.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFye3To4b2Aulvg9VRT8Z4cnxW0gHoyYks5rk1oqgaJpZM4MACdU>
.
|
@vijtad can you please submit a pull request with your changes rather than including them in comments? That allows us to review and merge the code. Here are two documents that explain how: |
Hi @warmspringwinds, @vijtad, @ahundt, I took the liberty of submitting a PR that adds forward/backward compatibility for tf-1.0.x with version checks at all the fail points in the code based on the output of tf_upgrade_tool.py as suggested by @zhaozj89. Please have a look and consider merging. As I say in the PR though, I'm unsure if this type of forward/backward compatibility version checking is the best approach for future maintainability. E.g. it would probably break future applications of tf_upgrade_tool.py. In order to retain that option, maintaining separate branches might be better. In any case, I'll leave it up to you. |
Hi @barryridge Just tested for the tf_upgrade_tool.py and it worked like a charm. :) 👍 |
…ibility Fix for warmspringwinds#8: make forward/backward compatible with tf-1.0.x. # Conflicts: # tf_image_segmentation/utils/tf_records.py
@vijtad I refer your code and got an error below, any idea? I also found that you use
|
tf.pack should become tf.stack. There are a number of other changes that need to be applied for tf 1.0.
https://github.com/tensorflow/tensorflow/releases
The text was updated successfully, but these errors were encountered: