multiphysics

Reason

There is no reason to call the "higher level" app the "master"... better terminology is the "parent" app. We should change everything in the MultiApp system that mentions "master" including the documentation.

Design

See above.

Impact

May modify some documentation - but shouldn't do much more than that.

utils::ptr_vector<T> serves a similar purpose like smart pointers from std. We should remove this implementation in favor of smart pointers from std.

I already took care of replacing utils::ptr_vector<T> with std::unique_ptr in precice/precice#1159, but there are many more places, where utils::ptr_vector<T> is used.

I am using SimPEG.Utils.download for gpgLabs. The download messages are distracting in notebooks, so I wanted to suppress them. The option is controlled by "verbose=false", but it does not stop writing "Downloading ... Saved to:.." message.
Can verbose=false swtich kill all the print output?

![image](https://user-images.githubusercontent.com/5066933/28143500-b531e30c-671a-11e7-85d2-4d62d23d26a

Looking at the FluidSolver.py, I noticed that a few things are a bit uncommon in the time loop:

https://github.com/precice/tutorials/blob/95eea58160af574f8f1ab4ace248d5be53d8e140/elastic-tube-1d/fluid-python/FluidSolver.py#L127-L156

It looks like the checkpointing assumes that the solver time step is equal to the coupling time window. More specifically, whenever preCICE does not ask the solv