[DEFECT] RrR With 2 GA optimization

[alfoa]

Thank you for the defect report

• I am using the latest version of RAVEN.
• I have read the Wiki.
• I have created a minimum, reproducible example
  that demonstrates the defect.

Defect Description

If a RrR case Is used with 2 optimizers, and the outer Raven is linked to the out stream of the SolutionExport of the inner RAVEN, and in the inner RAVEN the user outputs the "batchId", the outer RAVEN fails because the "outer" bacthId is overwritten by the inner batchId (that does not match the outer)

Steps to Reproduce

Just change the RrR test in RAVEN regression test suite using GA in place of GradientDescant and output in the inner RAVEN the "batchId" (listed as variable in the inner SolutionExport)

Expected Behavior

The inner raven batchId is ignored in the outer

Screenshots and Input Files

No response

OS

Linux

OS Version

No response

Dependency Manager

PIP

For Change Control Board: Issue Review

• Is it tagged with a type: defect or task?
• Is it tagged with a priority: critical, normal or minor?
• If it will impact requirements or requirements tests, is it tagged with requirements?
• If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

• If the issue is a defect, is the defect fixed?
• If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?