You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to evaluate RPG on the T2I-CompBench but got different results than those in Table 1. So, I want to ask for the details about the evaluation of RPG on the T2I-CompBench.
About the MLLMs: GPT-4o or other MLLMs.
About the Base Ratio: As you said in your paper, the Base Ratio is important in RPG which affects the generation results. So I want to know the value of the Base Ratio you use to evaluate.
About the results: I use RPG to generate one image for each prompt in T2I-CompBench with GPT-4o-mini (300 images for each metric). However, the results are quite different from those in Table 1. Some results are as follows:
color -- 0.4464, shape -- 0.3863, texture -- 0.4289, spatial -- 0.1132, non-spatial -- 0.2950, complex -- 0.3012 (Base Ratio = 0.5)
I also evaluate SD v2 on T2I-CompBench and the difference between 300 images and 3000 images is around 0.05. So I don't think it is caused by the number of generated images. Moreover, I use GPT-4o as MLLMs and the results are similar to those using GPT-4o-mini.
About the code: When I use RPG on the T2I-CompBench, some bugs also happen.
When the 'Final split ratio' is '1': An error occurred: local variable 'split_ratio2' referenced before assignment.
Hope to see your reply.
Best regards.
The text was updated successfully, but these errors were encountered:
Thanks for your excellent work!
I tried to evaluate RPG on the T2I-CompBench but got different results than those in Table 1. So, I want to ask for the details about the evaluation of RPG on the T2I-CompBench.
I also evaluate SD v2 on T2I-CompBench and the difference between 300 images and 3000 images is around 0.05. So I don't think it is caused by the number of generated images. Moreover, I use GPT-4o as MLLMs and the results are similar to those using GPT-4o-mini.
Hope to see your reply.
Best regards.
The text was updated successfully, but these errors were encountered: