Convolutions tasks divided into different files

[AryanNanda17]

This issue involves refactoring the provided convolution code into three separate files, each focusing on a specific aspect of convolution operations, and creating a separate folder for benchmarking the results of each file.
Resolved issue #120

[AryanNanda17]

@PritK99, please checkout the PR and let me know if any change is required.

[PritK99]

Why are folders such as /src and /include a part of /benchmark directory? The idea was to just create a new folder /benchmark to deal with the time features.

[PritK99]

@advait-0 Could you please review this PR and suggest changes.

[AryanNanda17]

In the benchmarks folder time taken by each convolution is also being printed. In order to Benchmark(time taken by convolution operation), we would have to perform convolution, so the folders /src and /include are important.

[advait-0]

@AryanNanda17 please add the usage instructions to run each file in the sub-folder readme.

[AryanNanda17]

@advait-0, I made the required changes please check it out.

[aPR0T0]

Hello @AryanNanda17, Please add benchmarks to each file or remove them from the separable convolutions as they all should have a common standard. The point of the benchmark here is to understand the reason behind the use of separable convolutions

[aPR0T0]

Please add / remove benchmarks

[AryanNanda17]

Hello @AryanNanda17, Please add benchmarks to each file or remove them from the separable convolutions as they all should have a common standard. The point of the benchmark here is to understand the reason behind the use of separable convolutions

Hello @aPR0T0, could you please elaborate on this?
Because from what I understand issue #120 aims to make the code easier. So, I have separated all three approaches of convolutions in our case into three different files without benchmarks. For benchmarks, I have created a separate folder /benchmarks

The benchmarks folder benchmarks all three types of convolutions in our case!

[aPR0T0]

Sure @AryanNanda17 , makes sense then. Great work!

Just a small change, add benchmark ka example execution in readme

[AryanNanda17]

Sure @AryanNanda17 , makes sense then. Great work!

Just a small change, add benchmark ka example execution in readme

Thanks!

[AryanNanda17]

@aPR0T0, I added the results of Benchmarks in Readme.
Please check it out.

[SuperChamp234]

Why does the benchmarking folder contain the same files from the parent folder?

Ideally, the benchmarking folder should just have a file that will use the convolutions demonstrated in it’s parent folder and show the difference. Different files for each of the convolutions is not necessary.

[SuperChamp234]

Please make the change of removing unnecessary files and merge the benchmarking code into one file @AryanNanda17. Good job so far!

[AryanNanda17]

Please make the change of removing unnecessary files and merge the benchmarking code into one file @AryanNanda17.

Hello @SuperChamp234!

• In issue Refactoring Convolution Filtering #120 , @PritK99 suggested to make three separate files for each type of convolution and create a separate folder to benchmark the results of each convolution file. If we merge all three convolution files into one code, the code would become hard as before. But our goal here is to enhance code modularity, readability, and maintainability by isolating different functionalities into distinct files.

[aPR0T0]

Please make the change of removing unnecessary files and merge the benchmarking code into one file @AryanNanda17.

Hello @SuperChamp234!

* In issue [Refactoring Convolution Filtering #120](https://github.com/SRA-VJTI/Pixels_Seminar/issues/120) , @PritK99 suggested to make three separate files for each type of convolution and create a separate folder to benchmark the results of **each convolution file**. If we merge all three convolution files into one code, the code would become hard as before. But our goal here is to enhance code modularity, readability, and maintainability by isolating different functionalities into distinct files.

Hello @AryanNanda17 , that's right we need to simplify the code

Just restructure the directories as ->

1. benchmark
2. include
3. src
4. assets
   other files

and inside benchmark just keep cpp files, this way the folder remains generic

[AryanNanda17]

@aPR0T0, I made the changes. Please check it out.

[aPR0T0]

LGTM!
Great work @AryanNanda17 !