example-04xx

[beauof]

Need to introduce a 'fast' and 'big' target to allow quick testing, see example-0101.
At the moment, creating the screenshots and animation are the bottleneck.

For example,

• less time steps and only one screenshot per test for 'fast' target
• all time steps and only one screenshot per test for 'big' target
• separate 'animations' target?

Open for discussion.

Need to significantly reduce size of reference data, e.g., only keep the last time step for each test (for both iron and matlab reference data).

Tasks in checkbox style:

• introduce fast/big/animations target
• significantly reduce amount of reference data stored on github

[maierbn]

I setup the comparison script to only compare against 6 iron files und removed all other reference files.
I did the same with the matlab files and just included them for 2 testcases of example-0401, because the values do not match anyways. They are left in to see how comparison with matlab data works in case we want to address the issue in future.

Also I created 'fast' and 'big' targets for all 3 examples, like in example-0101. The 'fast' target creates less output and has shorter end times. Also the visualization is very quick.

• The corresponding visualize target visualize-fast only creates images for the last computed data points. It works with the output of the 'fast' target
• visualize-big creates the animations, using all available data (either from 'fast' or usually from 'big')
• create-figures aliases to visualize-fast
• In the tex file only the output of the fast target is used
• compare uses the available data, therefore there are more test when running make big than with make fast
• Integration to the top level Makefile does not work yet because of bug 19 compare target not called #20. With the fix it works.