Data warnings over day lines about quakemigrate HOT 2 CLOSED

So it is likely that this sort of warning occurs as a result of the actual data in the archive - I suggest looking for overlaps/gaps in the raw data and performing some cleanup before using QuakeMigrate.

Another issue we have come across is that of leap seconds - currently there is no clean way to handle this, if it is not done so by the instrument itself (Guralp instruments, for example, simply introduce a static time shift in the data). QuakeMigrate will simply detect an overlap in the data that it cannot merge simply and reject the entire timestep. If you do not wish for this to happen, we suggest you merge the data in a way you see fit before running QuakeMigrate. You should only do this with careful consideration of the consequences.

from quakemigrate.

Data gaps/archive gaps are now handled internally by the code, with messages returned to the user if there is no available data at any of the stations.

from quakemigrate.