BranchDescription not properly handled in cases of merged files

[Dr15Jones]

The process has one and only one ProductRegistry. That registry is essentially a map of BranchKey to BranchDescriptions where a BranchDescription holds one module class type and one ParameterSetID. In the case of a merged file, it is possible that the two files might have different module class types or ParameterSetIDs for the same BranchKey. Then when the merge happens between the two files only one set is actually kept.

The relevant provenance information is not lost. Using the process name and the ProcessHistory one can get the top level ParameterSet for the associated process. From the top level ParameterSet and the module label one can then get the ParameterSet for the module which also includes information about the module class type.

[Dr15Jones]

assign core

[cmsbuild]

New categories assigned: core

@Dr15Jones,@makortel,@smuzaffar you have been requested to review this Pull request/Issue and eventually sign? Thanks

[cmsbuild]

cms-bot internal usage

[cmsbuild]

A new Issue was created by @Dr15Jones.

@Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here