Closed demiangomez closed 3 months ago
Added a call to verify_rinex_date_multiday
in pyScanArchive to check if the RINEX file is multiday or not. If multiday, verify_rinex_date_multiday
sends each file to the repository and deletes the original rinex file. The file record is also removed from the rinex table. There is a possible problem when a gamit_soln exists for the file. In that case, the table record cannot be removed due to the foreign key between the rinex table and the gamit_soln table. In such case, the file can be deleted but the record will stay. This should be better handled.
There are still some files throwing the "No such file of directory" error. Need to investigate this.
We catched most of these errors, but some appear every now and then. Probably not related to multi day RINEX, so closing for now.
When a multiday RINEX file was already in the database (entered through an old version of pyScanArchive) PPP fails to process it because pyRinex by default bins it into the multiple days. Therefore, an IOError: [Errno 2] No such file or directory exception is thrown when normalizing the header.
See example:
IOError: [Errno 2] No such file or directory: 'production/rinex/8f77b22c-f0ee-4bcc-ab6d-3a4e8593c7d5/tuc12242.10o' processing: rms tuc1 2010 224 using node elvira END OF ERROR ===================
Should deal with these files correctly