Move all demos out of DOLFIN into documentation

Registered by Anders Logg

The demos should be moved out of DOLFIN and into the documentation source tree. They should there be coordinated with the documentation. Furthermore, all demos should come in both a C++ and a Python version.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Essential
Drafter:
None
Direction:
Needs approval
Assignee:
Kristian B. ├ślgaard
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Garth Wells

Related branches

Sprints

Whiteboard

How thoroughly should we test the demos once they are moved to the documentation?

1) Check if they compile against DOLFIN (should UFL files be compiled by FFC, or do we add *.h files as well?)
2) Check different compiler flags (both gcc and FFC?)
3) Check if they run without crashing
4) Check results against some reference

What are the buildbots currently testing?

What infrastructure should be in the documentation to make life easier on the buildbots? Is it enough to put a simple script that runs through the demo directory and test the demos one at the time?

AL: After much discussion we came to the conclusion that the demos should remain as part of DOLFIN and be automatically imported into the documentation.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.