Murnaghan: Round children names

[pmrv]

When the job name of the murnaghan is long; using ~10 digits for the strain can blow the job name limit. So I added some rounding here.

The PR helps, but doesn't allow to influence the rounding. Since Murnaghan job knows how much to safely round, this PR takes advantage of this here.

Alternatively one could drop the murnaghan job name from the names of the children. It's redundant, but I thought it might be a larger change, in that users will see their jobs changing. I feel ambivalent about this though.

[coveralls]

Pull Request Test Coverage Report for Build 6232695844

• 10 of 10 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 68.302%

---

Totals
Change from base Build 6221151764:	0.02%
Covered Lines:	10750
Relevant Lines:	15739

---

💛 - Coveralls

[samwaseda]

I'm actually not sure if we should define job_name in the first place in Murnaghan. At least I don't see why we shouldn't simply use the default job_name from JobGenerator everywhere.

[pmrv]

Am open to that as well. I kind of like seeing the strain in the job name, though, because you tell quickly which ones e.g. failed.

[samwaseda]

But is it really possible to see the problem by looking at the strain value?

[pmrv]

Not often, but I just find it generally informative.

[samwaseda]

Ok then at least I would like to make the job name function accessible from outside, because I might want to get the data based on the strain values.

[pmrv]

Ok then at least I would like to make the job name function accessible from outside, because I might want to get the data based on the strain values.

Not sure what you mean. So that I can set a function from outside that determines the child names?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.