Write to the output git versions

[peterrum]

motivated by the comment #204 (comment)

We should also output the parameter files and the list of particles to make everything reproducible. @vovannikov Could take this task take on?

See also: dealii/dealii#14204

@mschreter Are we somewhere monitoring the version of deal.II/MeltPoolDG?

[vovannikov]

@peterrum, yea, I could handle that. Do you have any preferences on how to store that data? I thought of outputting the corresponding *.prm and *.cloud files directly to the console as all those things would stay together. I think it is a bit better than storing those files separately and indicating somehow that the output is chained with them. Does it work for you?

[peterrum]

Yes dumping it to the same output file is reasonable to me. We print so much to console anyway.

[mschreter]

:-)

[mschreter]

@peterrum no, we don't track the particular deal.II version. In the ideal case it should be the deal.II master branch at the particular date of merging. However, I think your approach sounds reasonable and I'll open up an issue for that in MeltPoolDG. Thanks!

[peterrum]

SET(HYPER_DEAL_GIT_BRANCH "@HYPER_DEAL_GIT_BRANCH@")
SET(HYPER_DEAL_GIT_REVISION "@HYPER_DEAL_GIT_REVISION@")

@mschreter Haven't you heard about plasma state sintering?