example: two crashed examples

[SAutum]

add two crashed examples in balance

Following up on issue #238 .

Proposed changes:

• add a 2d bowtie example in the balance example
• add a 2d drop example in the balance example
• some minor changes along the way to fix warnings in doc generation

[cburstedde]

Thanks; if you could add a line to the doc/release_notes.txt file, and another retroactively for your previous #236?

[cburstedde]

Thanks! I'm thinking that the 2D and 3D corner examples have much code in common. Do you think you could eliminate the 3.c file to the usual 2-liner we use in the library files and work with #ifdef P4_TO_P8 in the 2.c example file?

[SAutum]

Thanks! I'm thinking that the 2D and 3D corner examples have much code in common. Do you think you could eliminate the 3.c file to the usual 2-liner we use in the library files and work with #ifdef P4_TO_P8 in the 2.c example file?

OK. Will do.

[cburstedde]

Thanks! I'm thinking that the 2D and 3D corner examples have much code in common. Do you think you could eliminate the 3.c file to the usual 2-liner we use in the library files and work with #ifdef P4_TO_P8 in the 2.c example file?

OK. Will do.

Thanks; please note that I have pushed a small update to this branch in the meantime.

[cburstedde]

We may consistently produce output with file names, after calling the respective algorithms, like
P4EST_STRING "_corner_new",
P4EST_STRING "_corner_refine",
P4EST_STRING "_corner_balance",
which will allow us to write the VTK outside the dimension #ifdefs.

[SAutum]

Deleted. The statement serves a test on the p4-to-p8 functionality.

[cburstedde]

I don't mind writing a VTK after new, after refine, after balance, and after partition.
With the name convention as above, this should all work without conflict:
with P4EST_STRING, the vtk_write_file function can be called outside the #ifdef.

[cburstedde]

Thanks, I have pushed on top as discussed in our video meeting.