RinexDates now incompatible with FixDatTGO
After Chris changed RinexDates to cope with leap year, we have a problem. Instead of subtracting six years as before, he now subtracts 5 years to keep the day of the week the same.
FixDatTGO only changes the week number, it doesn’t try to keep the date the same, although it did do that prior to 2/29/2012 to work with RinexDates. It was subtracting 6 years.
So, trying to use rinex data and dat files will no longer work, they are in different years after being modified.
Any suggestions?
One idea would be to check if the date is later than 2/28/2012, and subtract 5 years instead of 6. However, since the GPS system (and TGO) works with week numbers and seconds of the week, I would rather keep mine as is, and hopefully RinexDates could modify the way they do it?
Or I could put an option in to chose the year offset? In actuality, as far as using the dat file in TGO it could be any week before the 1 billion seconds, I just picked 6 years to be compatible with RinexDates.
- 7 Replies
Hi John
I just helped a TGO user with this very problem.
I suspect that as time goes forward this will become less of a problem because people will be upgrading to TBC or some other program. Probably the most important thing to do at this point is to get the word out, as you have done, that the two programs are no longer completely compatible. As for changing either program, that would be up to you and Christof as the programmers. I don’t have any idea how much work it would take to make a change. I know both of you have written these programs on your own time and graciously given them to the survey community and I give both of you a big THANK YOU for that.Is the problem only with FixDatTGO? I mean I use regular TGO with RINEX dates and it still works. Is that correct?
True
There isn’t a “problem” with either Rinex Dates or FixDatTgo. Both programs work fine by themselves. The “problem” results when the user tries to date adjust data with both programs in the same project. After Feb 29 leap year considerations entered into Rinex Dates causing a different time offset to be injected. The leap year didn’t affect FixDatTGO but now the programs are out of sync.Hope this answered your question.
John
Yeah, it did. Thanks for the quick reply.
After some thought about this, I have decided to have my program use -6 for dates before 2/29 and -5 for dates after that, same as RinexDates does.
Shouldn’t take much time to change it, hopefully I can get to it this evening. I will post a link when it is ready.
Thanks John
It will make things easier for everybody. I look forward to the update. I have mentioned to Wendell that it would be a good idea to include your program under the services tab along with Rinex Dates. Maybe after your update he will do it. I assume you wouldn’t object?John
John: I had told Wendell long ago that I had no problem with that, but I never heard anything back.
I think what I will do is to make the program default to -6/-5 depending on before/after 2/29/12, but then also include an option to actually select a number of years offset or a GPS week number to go back to. That should make it work going forward with Rinexdates after the next leap year (in case anyone is still using TGO by then!)
Log in to reply.