Tutorial for optimization

[TiKeil]

This PR contains a very detailed tutorial for optimization. The content is highly related to my talk on the online pymor school 2020.
I will rebase this PR after #1110 has been merged. So please ignore all commits except the last two and only look at this file.

@pymor/all it would be nice if you could read through it, there might be some typos or other issues.

Let me know what you think.

[HenKlei]

Very nice tutorial! Only some minor remarks from my side...

[TiKeil]

Very nice tutorial! Only some minor remarks from my side...

Thanks for the very nice review. I already included all comments.

[codecov]

Codecov Report

Merging #1205 (a040d4b) into master (4b84e1e) will decrease coverage by 0.00%.
The diff coverage is n/a.

Impacted Files	Coverage Δ
src/pymor/bindings/ngsolve.py	81.34% <0.00%> (-0.75%)	⬇️

[sdrave]

In general, this is a very nice tutorial! But maybe try to give a more direct and positive answer to: 'I have a PDE-constrained optimization problem, and I want to use pyMOR for speedup. What should I try as a first step?' Reading through the very long text, at the end you might get the impression that only an open problem has been presented. You should have a feeling of achievement.

[TiKeil]

Thanks @sdrave for the very nice and detailed review. I have addressed all your points except the citations.

I think, the text in the end reads way more positive now. I will see how I can improve this more but it should be okay already.

Removing Draft mode.

[renefritze]

Thanks @sdrave for the very nice and detailed review. I have addressed all your points except the citations.

I think, the text in the end reads way more positive now. I will see how I can improve this more but it should be okay already.

Looking good 👍
If you could get your last tweaks in by tomorrow evening, that would be great.

Also, can you do me a favor and also fix a typo in the mybinder box?

Please note that starting the notebook server make take a couple of minutes.

[pymor-lab-hub-bridge]

Hey @TiKeil it looks like this PR touches our CI config (and you are not in my contributor safelist), therefore I am not starting a gitlab-ci build for it and it will not be mergeable.

[TiKeil]

Thanks @sdrave for the very nice and detailed review. I have addressed all your points except the citations.
I think, the text in the end reads way more positive now. I will see how I can improve this more but it should be okay already.

Looking good +1
If you could get your last tweaks in by tomorrow evening, that would be great.

Also, can you do me a favor and also fix a typo in the mybinder box?

Please note that starting the notebook server make take a couple of minutes.

Thanks, I have fixed the typo and increased the timeout limit.

Furthermore I have added my last changes. Thus, this can be merged if there are no other objections.

[HenKlei]

You could also add the references to the bibliography file.

[renefritze]

Greenlight for CI again

[TiKeil]

You could also add the references to the bibliography file.

I intentionally did not do that because these references do not have anything to do with algorithms or implementational features in
pyMOR. Meaning, we do not provide any sort of content from these references. They are rather meant as "further reading" for the interested tutorial reader.

[HenKlei]

You could also add the references to the bibliography file.

I intentionally did not do that because these references do not have anything to do with algorithms or implementational features in
pyMOR. Meaning, we do not provide any sort of content from these references. They are rather meant as "further reading" for the interested tutorial reader.

Ah okay, sounds reasonable.

[ftalbrecht]

After fixing everything, I suggest to

• go through the intro once and unify the number of whitespace lines between the code and the text (say one before/after code blocks and two before headlines) and
• check the indentation of the code examples, in particular the creation of the data dicts.

[TiKeil]

After fixing everything, I suggest to

* go through the intro once and unify the number of whitespace lines between the code and the text (say one before/after code blocks and two before headlines) and

* check the indentation of the code examples, in particular the creation of the data dicts.

Thanks @ftalbrecht, I have added the files accordingly. Some of your remarks were outdated already such that I could not apply all requested changes.