super-resolution
Here are 395 public repositories matching this topic...
-
Updated
May 10, 2020 - Python
Benchmarking
Can you please add some performance numbers to the main project docs indicating inference latency running some common hardware options e.g. AWS p2, GCP gpu instance, CPU inference, Raspbery pi, etc.
-
Updated
Jun 30, 2020 - C++
Description
In the changelog it is stated that there is a linux port..... However that is absolutely nowhere to be found, not on the wiki, and nowhere on the github page, what gives?
Also, i know telegram would be more of an appropriate place for this, but i don't have a carrier number as i don't need one and honestly cannot be bothered to bug someone else to use their carrier number sim
-
Updated
Feb 5, 2020
-
Updated
Jun 28, 2020 - MATLAB
-
Updated
Mar 31, 2018
-
Updated
Jul 1, 2020 - Python
-
Updated
Feb 20, 2020 - Jupyter Notebook
-
Updated
Jun 29, 2020 - Python
-
Updated
Apr 9, 2020 - Python
Is there any documentation available for the code? At least, information about what each function does? It's really difficult to read through the entire 1000+ lines of code without being able to grasp which function is called where.
-
Updated
Apr 27, 2020 - Python
-
Updated
Jan 6, 2018 - Lua
-
Updated
May 23, 2020 - Python
-
Updated
Jun 13, 2020 - Python
-
Updated
Oct 27, 2019 - Python
-
Updated
Apr 10, 2020 - Python
-
Updated
May 7, 2019 - Python
-
Updated
Aug 9, 2019 - Lua
-
Updated
Apr 20, 2020 - Python
-
Updated
Mar 20, 2019 - Python
-
Updated
Dec 18, 2019 - MATLAB
-
Updated
Jun 21, 2020 - Python
-
Updated
Mar 16, 2018 - Jupyter Notebook
-
Updated
Mar 28, 2019 - MATLAB
Improve this page
Add a description, image, and links to the super-resolution topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the super-resolution topic, visit your repo's landing page and select "manage topics."
In config.py:
parser.add_argument('--padd_size',type=int,help='net pad size',default=0)#math.floor(opt.ker_size/2)I'm wondering why you commented out the code for same padding to use valid padding instead? Is this important? (I checked both paper and ICCV talk, and it wasn't mentioned)