OPAL GA interface does not raise error when design variable is not actually in tmpl file, and it writes spurious data to json
The GA input file writes to the json file which values it sent to the simulation even if those variables cannot be found in the tmpl file.(Example: in our case, LRAD was set in the GA input file, but in the tmpl file the value that actually needs to be changed is Rc, so, Rc was constant, but our data from the json file shows a spurious change in LRAD)
The same issue likely applies to the random sample interface.
--> OPAL should raise an error when a variable from the GA input file cannot be found in the tmpl file.