Pint vs. tempo2 par/tim files #7
Description
This is not really a pta_replicator issue, but wanted to flag here to investigate further. It looks like if one produces simulated par and tim files with pint (through pta_replicator), and reads those in to analyze with enterprise without specifying the timing software, enterprise reads them in with tempo2 and the data will be compromised. I'm not too sure about what goes wrong exactly, but the data becomes completely useless (maybe something with toa sorting?).
It can easily be solved by specifying timing_package='pint' when reading in the par/tim files with enterprise, but this may be an easy thing to miss and can be an issue that many new users of pta_replicator will run into. I'm also not too sure why enterprise cannot automatically recognize where the par file comes from.
@emikocgardiner ran into this issue