amazon-braket-examples
amazon-braket-examples copied to clipboard
amazon-braket
add deutsch jozsa algorithm
Issue #, if available:
Description of changes: Adding the Deutsch-Jozsa Algorithm example notebook.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Check out this pull request on 
See visual diffs & provide feedback on Jupyter Notebooks.
Powered by ReviewNB
![review-notebook-app[bot] avatar](https://avatars.githubusercontent.com/in/15474?v=4 "Published by a pub.dev verified publisher"){kind=small}
General comment: the notebook should be a mix of code and exposition, rather than just code is it currently is. For example take a look at the superdense coding and Simon's algorithm notebooks. They have many Markdown cells including background, explanations of steps, and diagrams.
General comment: the notebook should be a mix of code and exposition, rather than just code is it currently is. For example take a look at the superdense coding and Simon's algorithm notebooks. They have many Markdown cells including background, explanations of steps, and diagrams.
Hi Cody! Yes that's my next task, I'll be adding markdown to support my code and adding to my PR.
I would like to see some markdown discussion in between the code cells. It's helpful to set up what's about to happen preceding some action, then discuss / reflect on the outcome in the markdown cell after some code is executed.
Thanks for the updated PR, Tanisha. While Braket notebooks don't have to conform to SageMaker's, there are some best practices to be found in the SageMaker notebooks template. Most notably, I was wondering if there's any cleanup of resources to be done at the end. And how about any references? Is there a recommended next tutorial after this one?
Added some resources at the end of the tutorial and referenced a textbook from where I learnt a lot about the algorithm.
I would like to see some markdown discussion in between the code cells. It's helpful to set up what's about to happen preceding some action, then discuss / reflect on the outcome in the markdown cell after some code is executed.
Implemented in most recent PR