Allow structured output for "out-of-model" leaves

[phiweger]

Thanks a lot for this great tool!

TreeTime prints implausible leaves to stdout like so:

263.56	TreeTime: The following tips don't fit the clock model, please remove
      	them from the tree. Their dates have been reset:

263.56	4d9c8e7e-9fa5-4340-a1bd-994e42f1cd57, input date: [2010.0013698630137,
      	2010.9986301369863], apparent date: 2013.32

263.56	2e86535f-7904-433e-897b-cc0f3e2ff278, input date: 2013.8972602739725,
      	apparent date: 2013.90

263.56	6efab9a4-5723-4f1e-9d20-9077d64be651, input date: 2014.0917808219178,
      	apparent date: 2014.09

263.56	992884f2-12e3-453c-8d3c-0d49443dc999, input date: 2014.5246575342467,
      	apparent date: 2014.52

263.56	07ea690f-25f3-4761-bdbc-46e58baa2a5b, input date: [2012.0013661202186,
      	2012.9986338797814], apparent date: 2018.60

It would be great if there where a command line flag like --weird-leaves log.txt with the structure

name,stated,apparent
foobar,2013.3,2019.6

so that they could more easily be used programmatically in workflows down the line. ATM I parse the stdout, which is ok but feels a bit hacky.

Kind regards

[rneher]

Good point. I'll add this to the list of things...