stardance has been extended another month! the new deadline is october 31 :)

You are browsing as a guest. Sign up (or log in) to start making projects!

SpaceRanger

@SpaceRanger

Joined May 31st, 2026

  • 29Devlogs
  • 2Projects
  • 0Ships
  • 0Votes
I'm Abdulgafar Abdurrasheed, and for the Summer, I'm a Space Ranger. I love Stardance's Theme, and I hope to Build Amazing stuff, and impress Amazing people.
Open comments for this post
Reposted by @SpaceRanger

1h 0m 19s logged

Changelog

  • Trajectory calculation Now uses universal timestamp (c842228)

Okay, Because Celestrak tracks and updates satellite data at different times, The data from the API doesn’t actually reflect the current coordinates of the satellites, especially when compared to one another. While the specific orbits were accurate, The timing was completely random, and so, if 2 satellites were recorded in the same position, 6 hours apart, My simulation will start them in the same coordinate. This is obviously dangerously inaccurate.
Fix: I removed the simulated “timestep” entirely, and Built the whole thing to Check current time, Check time the satellite’s data was recorded, and Simulate Orbit/Calculate trajectory and coordinates based on that.

Problem with that is, without the timestep, My previous calculation for How fast this thing can run in relation to real word time will be totally wrong. I’ll fix that next.

0
1
47
Open comments for this post
Reposted by @SpaceRanger

41m 8s logged

Changelog

  • Improve error handling for satellite and debris data fetching; adjust time step for simulation (7e7c487)

Coming back to this after legit leaving it for One month 😭. Anyway, I fixed error handling for Cases where the user is not able to ping the Celestrak servers to get the data needed. Now It just falls back to the Cache. I also reduced the amount of time That goes by in app, to perfectly mirror the real world.

0
1
29
Open comments for this post
Reposted by @SpaceRanger

1h 34m 37s logged

A few different things have bugged me since last I Devlogged.
For one, i’m not tntirely sure how to go on. What i need, to remove, and all.
Secondly, everything is so Unorganized rn. So many debris and satellites Just swimming around in Orbit against a static Earth And everything doesn’t even scale properly.
Lastly, I’ve tried to focus a bit more on Orging My own YSWS.
Thank goodness stardance was extended(Expected, but thank goodness still).

0
1
23
Open comments for this post

1h 0m 19s logged

Changelog

  • Trajectory calculation Now uses universal timestamp (c842228)

Okay, Because Celestrak tracks and updates satellite data at different times, The data from the API doesn’t actually reflect the current coordinates of the satellites, especially when compared to one another. While the specific orbits were accurate, The timing was completely random, and so, if 2 satellites were recorded in the same position, 6 hours apart, My simulation will start them in the same coordinate. This is obviously dangerously inaccurate.
Fix: I removed the simulated “timestep” entirely, and Built the whole thing to Check current time, Check time the satellite’s data was recorded, and Simulate Orbit/Calculate trajectory and coordinates based on that.

Problem with that is, without the timestep, My previous calculation for How fast this thing can run in relation to real word time will be totally wrong. I’ll fix that next.

0
1
47
Open comments for this post

41m 8s logged

Changelog

  • Improve error handling for satellite and debris data fetching; adjust time step for simulation (7e7c487)

Coming back to this after legit leaving it for One month 😭. Anyway, I fixed error handling for Cases where the user is not able to ping the Celestrak servers to get the data needed. Now It just falls back to the Cache. I also reduced the amount of time That goes by in app, to perfectly mirror the real world.

0
1
29
Open comments for this post

1h 34m 37s logged

A few different things have bugged me since last I Devlogged.
For one, i’m not tntirely sure how to go on. What i need, to remove, and all.
Secondly, everything is so Unorganized rn. So many debris and satellites Just swimming around in Orbit against a static Earth And everything doesn’t even scale properly.
Lastly, I’ve tried to focus a bit more on Orging My own YSWS.
Thank goodness stardance was extended(Expected, but thank goodness still).

0
1
23
Open comments for this post
Reposted by @SpaceRanger

1h 17m 33s logged

Changelog

  • Implement caching for live satellite data and adjust debris scaling for better visualization (0e71088)

Okay, so remember in my last Devlog, i noted that Celestrak didn’t like me pinging their servers more than once every 2 hours, which crashes my RUST backend. So today i implemented Caching. Basically, How this works is, I check if there is a file named “active_satellites.txt”, if there is not, i go ahead and create one, and add all the satellite TLE data from Celestrak here. If there already was one, I check the MetaData for time modified, and if this is more than 2 hours, I ping Celestrak again, and Update the File with new data. If it is less than 2 hours tho, i go ahead and use the one i already HAD.

0
1
92
Open comments for this post

1h 17m 33s logged

Changelog

  • Implement caching for live satellite data and adjust debris scaling for better visualization (0e71088)

Okay, so remember in my last Devlog, i noted that Celestrak didn’t like me pinging their servers more than once every 2 hours, which crashes my RUST backend. So today i implemented Caching. Basically, How this works is, I check if there is a file named “active_satellites.txt”, if there is not, i go ahead and create one, and add all the satellite TLE data from Celestrak here. If there already was one, I check the MetaData for time modified, and if this is more than 2 hours, I ping Celestrak again, and Update the File with new data. If it is less than 2 hours tho, i go ahead and use the one i already HAD.

0
1
92
Loading more…

Followers

Loading…