-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Looping example #169
Looping example #169
Conversation
8745513
to
1825824
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks good to me, thanks @jatkinson1000. Just some minor comments and suggestions.
@@ -3,5 +3,6 @@ if(CMAKE_BUILD_TESTS) | |||
add_subdirectory(2_ResNet18) | |||
# add_subdirectory(3_MultiGPU) | |||
add_subdirectory(4_MultiIO) | |||
add_subdirectory(5_Autograd) | |||
# add_subdirectory(5_Looping) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this gets merged first then I can add tests for it in #166.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is an option, though I think this one isn't really 'testing' anything, but rather demonstrating, so for the sake of saving time/resource in the test suite it could be left.
I'll let you decide in #166
…tran with instructions on how to do this.
c06f220
to
d69d51a
Compare
The PR adds an example to demonstrate how best to structure code when inference is being called many times as part of an iterative procedure.
It demonstrates two approaches, the 'bad' naive way following exercise 1, and the 'good' substructured way.
Users are guided through both codes before building and then and timing them to see the significant performance increase of the 'good' approach.
Review of the explanations, instructions, code, and a check that things can be build and run correctly appreciated.