3 ms·
Oh shit yeah that really does look good! Amazing really. Ok...I'm going to put these notes on the project board. Yes..I definitely glossed over the proposed
by citnaj 8y ago
Oh shit yeah that really does look good! Amazing really. Ok...I'm going to put these notes on the project board.
Yes..I definitely glossed over the proposed workaround and I apologize. Thanks for this.
- MayeulC 8y agoNo problem :) Although I would have made it a fully-fledged github issue, with a link in your board, instead of a text entry, to add supplementary material in the issue thread. Bonus: if you are only interested in chrominance, you can train your network to use YUV as an input instead, and output only UV. I suspect this might lead to substantial gains in the training time and network complexity.
- citnaj 8y agoYeah the more I churn over this idea in my head the more excited I get about it. This really sounds like a big win. I'm not sure what I want to do about the Kanban board versus issues tracker yet... I'm used to JIRA mostly. I'll figure it out but do know your contribution is very very much appreciated. I don't think I would have come up with that.
- citnaj 8y agoUpdate: I got this working, and dude- it's so awesome in every way. This is the most substantial improvement I've seen yet. Most importantly- it massively reduces memory requirements. Thank you so much. I'll commit within a day or so and make sure to mention you, on Twitter.
- MayeulC 8y agoHey, thank you a lot, that's awesome! One more thing I recently thought about, but didn't get around to mention, is that you can probably reduce the input of your net to the Y (luminance) channel (with UV-only output), to trim it further ;) But that might already be what you are doing, for all I know. I am just really glad I could be of any help! And this feels like an "free-lunch" improvement.