Two separate examples of the new idempotence check failing on the second point of a scan have been reported by @j-a-foster and @chris-ashe. The message reported in the terminal is: RuntimeError: Model evaluations at the current optimisation parameter vector don't produce idempotent values in the final output.
Given that this is happening identically for two separate scans using different input files, it would be helpful to understand what about them is causing the failure and/or having an option to continue the scan even if the idempotence check fails.
It's worth noting that the scan continues just fine if the error message is commented out of the code.
Two separate examples of the new idempotence check failing on the second point of a scan have been reported by @j-a-foster and @chris-ashe. The message reported in the terminal is:
RuntimeError: Model evaluations at the current optimisation parameter vector don't produce idempotent values in the final output.Given that this is happening identically for two separate scans using different input files, it would be helpful to understand what about them is causing the failure and/or having an option to continue the scan even if the idempotence check fails.
It's worth noting that the scan continues just fine if the error message is commented out of the code.