[Feature] The code and documentation are really terrible[Docs]

[TheHonestBob]

Branch

main branch https://mmagic.readthedocs.io/en/latest/

📚 The doc issue

when I use MMagicInferencer, I cannot specify any parameters, or in other words, after reading many levels of source code, I still cannot know which parameters I should pass in. For example, during VSR inference tasks, I cannot specify fps. For a 1920 * 1080 video with only 25 frames, it is OOM on a 24G 4090

Suggest a potential alternative/fix

No response

[limhasic]

Even though it hasn't been made yet, isn't it great to be able to gather all the references and get an idea of ​​what's out there?

[kvnsng]

Running into same OOM issues using MMagicInferencer... Any documentations on how to limit overloading the memory?

[rlewkowicz]

I think we have to monkey patch it. I also have these issues.
https://www.geeksforgeeks.org/monkey-patching-in-python-dynamic-behavior/

Among other things, you also cant pass a save path and mmengine complains. I've never been able to get these aios to work. It's always more time saving to go papers with code and just write my own for the single thing I need. I would love this stuff to work. paddle paddle feels the same.

But if I have to do all the work to read all of it to understand it, at that point I can just go write it faster with less complexity