@kvedala there are some file which are not using doxygen comment style are we suppose to ignore those too in this PR?

Yes please, only if these are the files that exist in the parent repo. All code that I have written includes extensive documentation.

Please note that before merging, some links will need to be updated to reflect to parent repo links. These can be done in one last commit

@mishraabhinn could you please also help @ayaankhan98 to review this pull. It is quite an extensive one trying to improve the standards of this repo.
Thank you.

i have reviewed approx 160 files, half of them are still remaning

@ayaankhan98 appreciate your work, then I am starting from file 161.

I wish there was a better way to do this but the repo is so bad that to fit it up consistently, it was the best I could. I tried to help by pointing to the merges to master branch - and still think that would be the easiest thing to do.

@kvedala we are have finished half of the work, it will take some more time then we are all done, further improvement will be easy as after this PR we have automation checks

@kvedala we are have finished half of the work, it will take some more time then we are all done, further improvement will be easy as after this PR we have automation checks

Thats the goal - that from this point on, the documentation, program execution checks, etc would all be streamlined - simplifying it for both the authors and the reviewers.

@mishraabhinn could you please also help @ayaankhan98 to review this pull. It is quite an extensive one trying to improve the standards of this repo.
Thank you.

I have np @kvedala in doing that, I have forked this for contribution only. If @ayaankhan98 can guide me little bit I will happy to help because of new to all this.