Socket restarts unexpectedly when PRINT_FORCES is not present #119
Description
Describe the bug
The socket restarts due to:
['positions', 'parameters'] have changed since last calculation. Restart the socket process.
To Reproduce
Run ab-initio coordinate relaxation with socket and remove the PRINT_FORCES from the calc_params dictionary.
Expected behavior
The relaxation should complete without the socket restarting. The forces are printed to the static file, as are positions. Not certain why failing to include PRINT_FORCES causes an error. Could be due to non graceful updating of SPARC parameters to ensure forces are printed when PRINT_FORCES is not passed via calc_params.
Actual output or error trace
No error, just not the expected behavior.