Skip to content

Conversation

@maxwang7
Copy link

I went through the pet detector tutorial and made some fixes that got the training portion running. I haven't figured out how to get the evaluation code (there's an open issue for pycocotools) or the ipython notebook running. I don't have context on whether the fixes I made here were the correct ones, but they did get the program to the point where it was working for me.

I hope this contribution helps improve the quality of the tutorials in the future, thank you for maintaining this project!

These parameters seem to work reasonably well, though I sometimes receive `UnavailableError: Stream removed` errors
@tensorflow-jenkins
Copy link
Collaborator

Can one of the admins verify this patch?

@googlebot
Copy link

Thanks for your pull request. t looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers
  • Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
  • The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
  • The email used to register you as an authorized contributor must also be attached to your GitHub account.

@jlertle
Copy link

jlertle commented Mar 17, 2018

@maxwang7 do you happen to have a link for open issue with pycocotools regard the evaluation issues? Would love to track it as I can't seem to get coco_mask_metrics working.

@maxwang7 maxwang7 requested review from a team and pkulzc as code owners May 14, 2018 22:31
@pkulzc
Copy link
Contributor

pkulzc commented May 14, 2018

Sorry I didn't get your purpose of this pull request.

  1. Some of you files are outdated
  2. It includes issues already fixed(BackupHandler)
  3. It contains your personal gs address or other paths.

Do you simply want to keep this PR as a reference? In that case you should make your own branch instead of sending a PR.

Currently running on CMLE is not working due to tf runtime issue (temporary way is to use my gcp-1.2-ready branch) but running locally do not require any fixes.

@qlzh727 qlzh727 removed the request for review from a team June 25, 2018 16:37
@saberkun saberkun closed this Nov 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants