When analyzing GROMACS data, uncorrupted .xvg files are overwritten with extra zeros (fmt = '%.10f'). This is unnecessary and also potentially dangerous; e.g. if the process is interrupted during writing, the result (as I found out the hard way) is replacement of a perfectly good .xvg file with a partially written one. [Perhaps the final lines of corruptxvg.py were once part of the else statement starting on line 106?]
Meanwhile, minimally corrupted files (default: <10% corrupt) are backed up to ./xvg-bak/ before being overwritten with corrupt lines removed. This is OK, but perhaps not ideal. As a user, I would prefer my input data to be neither overwritten nor moved to a new location without explicit notification.
When analyzing GROMACS data, uncorrupted .xvg files are overwritten with extra zeros (fmt = '%.10f'). This is unnecessary and also potentially dangerous; e.g. if the process is interrupted during writing, the result (as I found out the hard way) is replacement of a perfectly good .xvg file with a partially written one. [Perhaps the final lines of corruptxvg.py were once part of the
elsestatement starting on line 106?]Meanwhile, minimally corrupted files (default: <10% corrupt) are backed up to ./xvg-bak/ before being overwritten with corrupt lines removed. This is OK, but perhaps not ideal. As a user, I would prefer my input data to be neither overwritten nor moved to a new location without explicit notification.