TypeError in Global Error Trapper #1011

Activity

1. thkruz

   added

   Wontfix

   on Mar 18, 2025
2. thkruz

   self-assigned this

   on Mar 18, 2025
3. thkruz commented on Mar 18, 2025

   

   thkruz

   on Mar 18, 2025

   Owner

   More actions

   This was likely from the github page code that is no longer up-to-date. I will be updating the readme tonight, but try using the latest code from the main branch.
4. thkruz

   closed this as completedon Mar 18, 2025
5. ClaudioLefante commented on Mar 18, 2025

   

   ClaudioLefante

   on Mar 18, 2025 via email

   Author

   More actions

   Hi! Thank you for your  response to the error I encountered. I’m Claudio Lefante, a member of UC3-BASE at Universidad Carlos III de Madrid. We’re working on integrating KeepTrack with Gpredict to enhance our satellite tracking capabilities. To provide more context: We’re currently running KeepTrack locally on our systems. While the web application at KeepTrack functions perfectly, we’ve opted for a local implementation to customize certain features and ensure data security. During this process, we encountered a specific error that I’ve reported. Our goal is to synchronize KeepTrack with Gpredict, a real-time satellite tracking and orbit prediction application. The idea is to utilize KeepTrack’s visualization capabilities alongside Gpredict’s prediction functions to achieve a more robust and accurate tool. Given your familiarity with KeepTrack’s architecture, I would like to know if you can assist us with the following aspects: 1. Best Practices for Local Implementation: Are there guides or documentation detailing how to set up and run KeepTrack in a local environment? Any advice on dependencies, configurations, or potential pitfalls would be invaluable. 2. Integration with Gpredict: Do you have experience or knowledge on how to connect KeepTrack with applications like Gpredict? Are there APIs, plugins, or recommended methods to achieve this integration efficiently? We understand that the official KeepTrack documentation is a valuable resource, but any additional insights or specific recommendations you can provide would be greatly appreciated. Thank you in advance for your support and for the incredible work you do with KeepTrack! Best regards, Claudio Lefante UC3-BASE

   …

   Message ID: ***@***.***>
6. thkruz commented on Mar 31, 2025

   

   thkruz

   on Mar 31, 2025

   Owner

   More actions

   Claudio, sorry I didn't see this message when you posted it.

   There isn't a direct way to link gpredict and KeepTrack together but both are using TLEs/GPs from Celestrak so that should be all you need to keep them synced. If they are both using the same orbital data they will show the same positions at a given time.

   Given that gpredict has not been actively maintained in some time, perhaps you can point out which features you would like me to port directly into KeepTrack. The majority of what I can see in the screenshots is already included in KeepTrack.

   As for a guide to run it locally, I will toss that on my to-do list for tomorrow morning before work. Expect it before the end of the day tomorrow.
7. thkruz commented on Mar 31, 2025

   

   thkruz

   on Mar 31, 2025

   Owner

   More actions

   I have uploaded a more detailed tutorial on setting up KeepTrack locally: https://keeptrack.space/resources/getting-keeptrack-running-locally/

   After looking at gpredict's code I think the issue you are running into is that they only have a small subsect of the catalog and you want more of the TLEs that KeepTrack has?

   It looks like you can modify gpredict/src/sat-cfg.c to add https://r2.keeptrack.space/celestrak-catalog-latest.txt

   {"TLE", "SERVER", "https://r2.keeptrack.space/"},
   {"TLE", "FILES", "celestrak-catalog-latest.txt"},
   {"TLE", "PROXY", NULL},
   {"TLE", "URLS",
   "https://r2.keeptrack.space/celestrak-catalog-latest.txt"},

   Obviously I don't develop gpredict and have never used it, so there may be more reasons why that won't work, but it appears to be what you are looking for.

   Let me know if that works, and my offer stands that if you can explain what features you feel are missing I am happy to get them added. Good luck!
8. Repository owner locked and limited conversation to collaborators on Mar 31, 2025
9. thkruz

   converted this issue into a discussion #1039 on Mar 31, 2025