Hvass-Labs / TensorFlow-Tutorials

TensorFlow Tutorials with YouTube Videos
MIT License
9.28k stars 4.19k forks source link

issue when implementing image caption model #125

Closed John-p-v1999 closed 3 years ago

John-p-v1999 commented 3 years ago

I trained the model, following your instructions. But for some reason, the model produces the same caption for different images. It is as if it is ignoring the initial state supplied to the GRU layer. Can you please help me out

John-p-v1999 commented 3 years ago

actually, the model gives the same caption for every image. Elaborating on my intuition that the model is "ignoring" the initial sate. When I give start_word as another word(instead of 'sos'), different captions are generated. In fact generate captions works fine, the problem is it does not generate according to images. on the contrary caption generation of caption only depends on start word

Hvass-Labs commented 3 years ago

I can see this is your first issue on github so I am going to be extremely nice. You cannot expect anyone to help you with a question like this. Look at the date when the tutorial was made - it was YEARS ago! You cannot expect me to remember the details anymore. So I would have to spend hours investigating this problem, and in the end my experience has always been, that it is the user who made problems, so I wasted my time trying to solve non-existent problems. You are coming across as very inconsiderate and selfish when you are posting a question like this. In the future when you post a question on github, stackoverflow, or somewhere else, you need to be very specific about exactly what you have done to the code and data, how you run it, and what the result is. And I would also recommend that you write proper English and capitalize and punctuate your sentences properly. You can't even put a tiny bit of effort into writing a legible question with proper syntax that makes it easy for me to read and maybe answer it, but you expect me to spend hours solving your problems. It really ticks me off when people are being so selfish and inconsiderate.

John-p-v1999 commented 3 years ago

Pardon my inexperience.

https://api.accredible.com/v1/frontend/credential_website_embed_image/badge/22999930

On Mon, Oct 26, 2020, 6:27 PM Hvass-Labs notifications@github.com wrote:

I can see this is your first issue on github so I am going to be extremely nice. You cannot expect anyone to help you with a question like this. Look at the date when the tutorial was made - it was YEARS ago! You cannot expect me to remember the details anymore. So I would have to spend hours investigating this problem, and in the end my experience has always been, that it is the user who made problems, so I wasted my time trying to solve non-existent problems. You are coming across as very inconsiderate and selfish when you are posting a question like this. In the future when you post a question on github, stackoverflow, or somewhere else, you need to be very specific about exactly what you have done to the code and data, how you run it, and what the result is. And I would also recommend that you write proper English and capitalize and punctuate your sentences properly. You can't even put a tiny bit of effort into writing a legible question with proper syntax that makes it easy for me to read and maybe answer it, but you expect me to spend hours solving your problems. It really ticks me off when people are being so selfish and inconsiderate.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Hvass-Labs/TensorFlow-Tutorials/issues/125#issuecomment-716528158, or unsubscribe https://github.com/notifications/unsubscribe-auth/APIUDEHD7OON56HYRM24L53SMVW2XANCNFSM4SLCHMSA .

EmperorKonstantin commented 3 years ago

@John-p-v1999 fork this repo and commit your work to your fork, push it to github and link to it or just make a gist and also link it it... @Hvass-Labs wants to see some code, and in general it is good practice to provide your code so you can either be helped along or an actual bug is found and fixed. Or if it's short enough just provide a snippet here surrounded by code tags.