I’m revisiting after two months. It does not look like there has been any activity here since then. Is there a way to have the instructors know? This is one of the coolest exercises but it’s not that useful if we can’t recreate it.
Well, I wasn’t able to run it in Azure. Fixed several typos and bugs in the code (like Fixed Attribute Access: Changed noise_scheduler.config_num_train_timesteps to noise_scheduler.config.num_train_timesteps.
Typo Correction: Fixed eduction="mean" to reduction="mean" in the MSE loss calculation.)
Then I got TypeError: argument of type ‘NoneType’ is not iterable.
Then tried to add added_conf_kwargs:
encoder_hidden_states = batch[“input_ids”]
# Prepare additional conditioning arguments (e.g., text embeddings)
added_cond_kwargs = {
"text_embeds": encoder_hidden_states # Example: You might need to generate or retrieve text embeddings
}
If run the codes in your local colab and made many changes, then surely one would need to see what changes you did with the codes.
As far the instructions shared here, it is stating the text embeddings would be required to retrieve or generate, means your inputs aren’t working with the codes provided.
csn you share a complete image of all the errors you got from beginning and you what changes you made for each error. I hope you have keep an error log documentation, so you have an idea from where you started.
@Deepti_Prasad Please, look at the github I provided. Text embeddings and with them time embeddings should be built somewhere in the code. And if for text it’s clear that it should be just encoder_hidden_states, it’s unclear how to build time embeddings.
Do you have some connection to engineers who wrote this notebook? I think it’s worth consulting them.
Hey @vgorovoy check if your requirement txt packages version matches with the information provided.
I am also suspecting
That’s true Vladimir, but if you check the error, text embeddings are being used from Unet2dconditionModel which is from which unet_2d_condition.py file
so according to what just @Mubsi shared information check if your diffusers package version match with your local environment.
check another discrepancy in version package
probably that’s why you had those bugs when you changed some of the attributes
Hope this helps resolve your issue.
@Mohsin_Ansari you can also try to with the information provided, sorry for the delayed response.