Affected files:
- TriangleMesh.*
- overExpressing.cfg
- phosphoDefective.cfg

ADD: option (AdvancePointsAlongFilopodiaSkeleton) to create less triangles along the filopodium skeleton.

Merge branch 'ISBI2016_TextureRenderer' of https://gitlab.fi.muni.cz/xulman/ISBI2016-filaSimu-TM into ISBI2016_TextureRenderer

TriangleMesh.cpp: Density parameter made transpared via cexternal config file.

Merge branch 'ISBI2016_TextureRenderer' of https://gitlab.fi.muni.cz/xulman/ISBI2016-filaSimu-TM into ISBI2016_TextureRenderer

It, however, does not make any use of it, currently...

present), it was unnecessarily loading (and not using) one more timepoint.

Merge branch 'ISBI2016_TextureRenderer' of https://gitlab.fi.muni.cz/xulman/ISBI2016-filaSimu-TM into ISBI2016_TextureRenderer

and various types of noise in the last simulation stage.
Additionally, the histogram is fine now. It is nearly the same as the
histogram of real images.

Tips are addressed as filoID+branchID (latter unique within only within its filopodium).

Ale the importer considers the skeleton segments ID as a guide for reliable filopodia tip tracking.

(which is a consequence of the new plan between GM and TM
that filopodia VTKs may not use sequential numbers in their
filenames... hence, if 04 fails to load, we cannot assume that
there is no 05..).

to determine size of the output images.