Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The tracking schedule and trk_midpoint are not correct in the CGGTTS Conventional Observation schedule. #285

Open
Tracked by #287
vicalloy opened this issue Dec 24, 2024 · 1 comment

Comments

@vicalloy
Copy link
Contributor

According to CGGTTS-Version 2E

  1. A minimum of 3 minutes was then foreseen in the BIPM schedule to give to the receiver the time to track the following scheduled satellite.
  2. The data to be used are the pseudorange measurements collected during the 13 minutes starting with the date specified in the BIPM tracking schedule.

If the Common-View Duration is 960 seconds, the trk_duration should be 780 seconds (13 minutes * 60 seconds). The trk_midpoint should be calculated as next_release - 3 minutes - (780 seconds / 2).

trk_midpoint = Some(next_release.unwrap() - trk_duration / 2);

@vicalloy
Copy link
Contributor Author

vicalloy commented Dec 27, 2024

Thank you for your work, but changing only the trk_midpoint is not sufficient.
The CV period is 16 minutes, which includes 3 minutes of preparation time and 13 minutes of tracking time. We should skip the 3-minute preparation time. The TRKL in CGGTTS should be 780, not 960.

I tried to create a pull request(#288) to fix this issue.
I tested it with my data, and it works. However, some variable names may still seem odd, which is why I didn’t fix them initially.

  • cggtts::track::Scheduler:
    • trk_duration should be renamed to cv_duration. (should keep trk_duration?)
    • bipm_tracking_duration should be renamed to bipm_cv_duration.
                  tracking start point                           
                    │                                            
      prepare(3min) │                                            
                    │  tracking(13mins)         │                
      │         │◄──┘                           │                
 ─────┼─────────┴───────────────────────────────┼────────        
      │                                         │                
             cv period(16min)                                    
      ▲                                         ▲                
      │                                         │                
    cv start point                       cv/tracking end point   

gwbres pushed a commit that referenced this issue Dec 27, 2024
* Fix track duration, in CGGTTS tracking #285
* Fix track midpoint determination, in CGGTTS tracking
* Fix debug info for CGGTTS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant