You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To my understanding, if (fabs(timediff(data[0].time,time1)-dtime1)>=DTTOL), then the new ely read epoch is valid. So why do you want to discard the current epoch data and read the next epoch in turn?
Fwiw this code is specific to time events, when flag is 5, so does not affect common uses. At a guess it was to assign the event to a set of observation data, but it needs some work. It does not appear that the events are used for anything. Perhaps the only code paths tested were the output paths, to get events from the receiver data into rinex files.
@ourairquality Thanks for your response! I think there might be an underlying assumption that with a flag of 5, the observations in next epoch might be unhealthy or of poor quality. Subsequently, if the next epoch does not occur at the established interval, the epoch is considered unavailable and skips to the next epoch. What do you think?
The flag of 5 is just the rinex epoch event flag, and for 5 that is an 'external event'. There is no reason that the next epoch would be of poor quality, there is no reason to skip an epoch. If you don't need to handle external events then I would not bother over that code, and if you do then you might want to reconsider the entire implementation and the various code paths.
Is the symbol "<=" correct?
To my understanding, if (fabs(timediff(data[0].time,time1)-dtime1)>=DTTOL), then the new ely read epoch is valid. So why do you want to discard the current epoch data and read the next epoch in turn?
RTKLIB/src/rinex.c
Line 1134 in 61ca04f
The text was updated successfully, but these errors were encountered: