History-preserving move from qiskit-tutorials/algorithms to qiskit_algorithms/tutorials

[robotAstray]

Summary

This PR aims to resolve part of the issue #14, to be specific the first step (i.e. history preserving migration of qiskit-tutorials 's ./tutorials/algorithms folder).

Details and comments

• The git history preserving method was used to migrate the content of qiskit-tutorials\algorithms into qiskit-algorithms\docs\tutorials
• Since the initial repo already had 01_introduction.ipynb I made sure that the file is included with the previous changes
• Tutorial 09_IQPE.ipynb was removed since it does not contain any reference to qiskit-algorithms

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
18 out of 31 committers have signed the CLA.

✅ woodsp-ibm
✅ schulta
✅ a-matsuo
✅ divshacker
✅ q-inho
✅ HwajungKang
✅ t-imamichi
✅ epelaaez
✅ garrison
✅ HuangJunye
✅ mtreinish
✅ clausia
✅ Cryoris
✅ ElePT
✅ 1ucian0
✅ JGeipel
✅ robotAstray
✅ Eric-Arellano
❌ ljmf00
❌ SooluThomas
❌ manoelmarques
❌ Dongsin Kim
❌ ajavadia
❌ jwoehr
❌ NG-Glen
❌ padraignix
❌ Vanimiaou
❌ declanmillar
❌ wenxh0718
❌ maxwell04-wq
❌ TannerTorrey3

---

Dongsin Kim seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[woodsp-ibm]

I might need to fix the last 3-5 commits

Having one or two extra commits is probably ok, but whatever they are will end up getting kept since we want the complete commit history. As far as the 01 tutorial I guess I was expecting to override what was already here so we got the history. Taking the original it would need fixing up again, but the others all need fixing too and it all could be done in a follow up. As I mentioned it was just quickly copied over here so we could have CI up an running with the docs.

[robotAstray]

I might need to fix the last 3-5 commits

Having one or two extra commits is probably ok, but whatever they are will end up getting kept since we want the coomplete commit history. As far as the 01 tutorial I guess I was expecting to override what was already here so we got the history. Taking the original it would need fixing up again, but the others all need fixing too and it all could be done in a follow up. As I mentioned it was just quickly copied over here so we could have CI up an running with the docs.

Hello @woodsp-ibm, thank you for your feedback, it is really helpful.

I see now the mistake. Just to confirm, would you like me to leave it as it is for this time?

[coveralls]

Pull Request Test Coverage Report for Build 5789709778

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 89.994%

---

Totals
Change from base Build 5692627482:	0.0%
Covered Lines:	6395
Relevant Lines:	7106

---

💛 - Coveralls

[robotAstray]

I can see the error is No module named 'qiskit_aer' I can add

qiskit-aer >= 0.12.2

in the requirements.txt file if you are happy with that, and I think that should resolve the matter.

[woodsp-ibm]

qiskit_aer would be added to requirements-dev.txt (not requirements) That is extra installs needed for development, like building/running the tutorials. Requirements is just what is needed as dependents for when you install/run qiskit_algorithms and no code is dependent on that. As a user you may want to use it - e.g. like the tutorials do, but for the base code its not needed for it to run/work at all. Of course adding this here adds another commit...

For me there are a couple of things.

1. As I explained the one tutorial was copied here with a view to fixing it correctly when the rest were brought over so what we had there was the version with history. Yes it would need fixing up again like all the rest will need fixing in terms of their imports etc. but that would be a next step,
2. As I also mentioned the references to the issue/PR numbers all really need fixing up. If you look back at the history here of the main code you will see commits brought over point back to original repo where the issue/PR so you can click on it and get the information (compare that to the history you have where its unaltered).

[woodsp-ibm]

@robotAstray Thanks for giving this a shot though!