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
Just wanted to make a suggestion. I think that if you added some simple visualizations in your README like starting from the simple ones which symbol (alpha, beta, ...) corresponds to what, visually, it would be so much easier to parse the code and the paper.
Performance information across different resolutions would be invaluable as well.
Research like this where the paper is super math heavy would go a long way if the authors could create an accompanying blog where you could go past the X-page limit and try and intuitively explain it.
I personally, for example, am capable of understanding (which is different from saying that I actually understood it) every single equation in the paper, but since it's out of context for me I lose a lot of time just to understand something which I'd understand with a single look at a good visualization.
Again awesome/innovative work, and if you ever find some time to explain this a bit more visually it would be an amazing service to the community!
The text was updated successfully, but these errors were encountered:
Awesome work!
Just wanted to make a suggestion. I think that if you added some simple visualizations in your README like starting from the simple ones which symbol (alpha, beta, ...) corresponds to what, visually, it would be so much easier to parse the code and the paper.
Performance information across different resolutions would be invaluable as well.
Research like this where the paper is super math heavy would go a long way if the authors could create an accompanying blog where you could go past the X-page limit and try and intuitively explain it.
I personally, for example, am capable of understanding (which is different from saying that I actually understood it) every single equation in the paper, but since it's out of context for me I lose a lot of time just to understand something which I'd understand with a single look at a good visualization.
Again awesome/innovative work, and if you ever find some time to explain this a bit more visually it would be an amazing service to the community!
The text was updated successfully, but these errors were encountered: