The file log52651211q.tps seems to have a collection interval of 86360 seconds!
The collection interval must be 1,2,3,5,10,15 or 30 seconds to be processed by OPUS.
Has anyone seen this message from OPUS?
This is a 4 hour observation.
> Has anyone seen this message from OPUS?
The second part, yes. My field crew had selected a 20 second collection interval for some reason. My solution was to download CORS data and resolve static vectors the old fashioned way.
I think that you should convert that .tps file to RINEX and resubmit.
You may have a residual observation from the day before, but that seconds interval works out to 23hr 59min 40sec so it may also be a result of 20 second epochs.
Convert it to a RINEX file and look art it using WordPad. If it is a 20 second file send it to me. I have a copy of "interpolate" so I could turn it into a 10 second file.
Paul in PA
The receiver probably wasn't fully initialized before the log file was started. This can result in the time stamp for the first epoch to show the wrong date. After full initialization the time stamp is correct and there will be a massive interval between those records. Editing the data to trim out the first minute or so should clear up the issue.
OK, I'll try the rinex. The receiver was set to 10 sec epochs.
OPUS won't accept the file as a share solution unless it is over 4 hours.
Trimming the data may be an issue. I'll post the results.
Thanks