BEAUti cloning of clocks sometimes clones tree prior

[rbouckaert]

To replicate:

• choose STACEY template,
• import a number of alignments,
• set first partition clock to ORC
• clone other clocks from first partition

Several PIOMSCoalescentDistributions appear while there should be only one.

[rbouckaert]

Marking the PIOMSCoalescentDistributions not cloneable by overriding notCloneable like so:

 @Override
   public boolean notCloneable() {
        return true;
    }

fixes the issue. It feels that it may be too hard to make the logic in BeautiDoc.deepCopyPlugin work it out by itself.

[bjoelle]

FYI I've had the same issue with an FBD tree prior being cloned (I imported two partitions, then accidentally linked the clock model, and when unlinking I got two tree priors) so it doesn't seem limited to STACEY.

[rbouckaert]

Thanks for the bug report. Now wondering whether perhaps the TreeDistribution or the FBD tree prior should have the same notClonable method as PIOMSCoalescentDistributions to get around this.