Scores 

A list of all team scores from the competition round are posted to this page 48 hours after the individual teams score sheets are emailed to the team directors. Scores are typically posted to this page the Thursday following the end of the competition window.
​

PRACTICE ROUND 1

QUALIFICATION ROUND 1

ROUND 2
​(coming soon)

ROUND 3
​(coming soon)

QR1 Recap

SCENARIO OBSERVATIONS

SCENARIO OBSERVATIONS

This scenario was a standard “find the best orbit to collect the most data” scenario. The task was a straightforward “Access” calculation, using the Access function to determine the number of minutes RiftSat’s SAR sensor can “see” the East African Rift (EAR). To score well in the scenario, teams needed an orbit that accessed the EAR as many times as possible to collect imagery of the rift.  An orbit traveling east-west will accomplish this by performing multiple crossings and collecting small bits of data with every pass. A few teams attempted using a north-south orbit which resulted in passes that collected more imagery each pass. But the reduced number of passes from this orbit compared to the east-west orbit resulted in less data collection. Teams also needed to contact each of the 30 GPS Motion Sensors (GMS) to solidify the score based on the percentage of GMSs contacted. Again, the numerous east-west passes made it easier to contract all the sensors.
 
For this scenario, the best orbit found for RiftSat was Apogee: 2,000 km, Perigee: 1995.1 km, Inclination: 35°, Argument of Perigee: 270°, RAAN: 148.138° and True Anomaly: 261.85°.  This orbit results in a Scenario score of 103.365. One team selected this orbit. Twelve other teams had a very similar orbit and was less than 1 point from this score.  FYI: Our grader can score out to 18 decimal places. Forty-eight teams were within 5 points of the best scenario score. Congratulations!
 
Looking at the VDFs sent in, it appears that many teams went with a 2,000 km circular orbit at an Inclination of 35°. This results in a good score, but to get a higher score the satellite needs to visit the EAR as many times as possible while at this inclination and altitude. To do this, the team should adjust the Argument of Perigee, RAAN and True Anomaly. The average score including violations for teams that turned in their scenario VDF was 78.337. Only six teams had an Inclination, Apogee or Perigee violation. Excellent!
 
Note: We discovered a few instances where teams from the same school/organization had identical scenario scores. This would indicate that some discussions were probably held between the teams during the round. While not prohibited during a Practice Round, this is absolutely not allowed during a Qualification Round. This action would result in severe penalties for the teams involved.
 
ACADEMIC QUIZ
 
The average score on the Academic Quiz was 18.031 out of 20. Fifty teams scored 20 out of 20. For the best chance at success, we encourage all teams to review the study guides and the StellarXplorers Space Foundations course prior to starting the quiz.
 
The highest possible total score in this Practice Round was 123.365.

IMPORTANT REMINDER – DESTRUCTION OF STLX COMPETITION MATERIALS ​

All copies of the PR1 competition scenario booklet, score sheets, STK VDFs, and team-produced documents must be collected and destroyed, or deleted, prior to the start of Qualification Round 1 on ​October 31, 2024. ​
​​​

PROCEDURAL OBSERVATIONS

​Team Numbers
Your team number (STLX11-XXXX) is very important during the StellarXplorers competition. It is how we track your results, store your files, and most importantly grade your solution.

In QR1 68 teams generated 90 instances of bad team numbers on either the start form, academic quiz, VDF upload submission, or VDF file naming.
 
Our automated grading system looks for your team number in order to launch the scoring process. It looks for precisely 11 characters (STLX11-XXXX) to find and score your file. If there are more than or less than these 11 characters, the grader will abort the scoring process for all teams, and we must manually repair the incorrect team number. For example, say your team number is STLX11-0987.  Typing anything other than STLX11-0987 will cause the grader to abort.
 
To help you avoid this mistake in the future, view the newly created “Penalty Paper” to see a list of all the wrong ways (and the only right way) to provide your team number. This document also outlines other common penalties and how to avoid them. 

PENALTY PAPER PDF

In all future rounds, teams will be penalized 5 POINTS each time they submit something with an incorrect team number. This includes the start form, academic quiz, solution upload/submission form, and/or VDF filename. It is imperative that you are using the correct team number and inputting it with the correct STLX11-XXXX format.
 
And as always, include your team number in the subject line of all messages to us. It makes it easier for us to find you in our database and to file the information that you send to us.
 
Running Systems Tool Kit (STK)
As emphasized in prior communications, teams should load STK 12.5 Pro with the Planetary Data Supplement onto their computers and test that the software is operating successfully BEFORE STARTING THE ROUND. By “before” we mean days before, not hours or minutes. We cannot guarantee staff support for last-minute technical issues, and teams will not be given any time relief if they do not have STK running on their computers at the start of the competition period. If needed, sample VDFs are available with our Training Materials, and can be used to test the software.
 
For those still needing licenses, please reach out to the StellarXplorers Program Staff as soon as possible to request them.

Changing Fixed Variables
Teams should NOT change any of the Fixed Variables in STK. These variables include but are not limited to: Start Time, Stop Time, Propagator, Step Size, Coord Epoch Time, etc. Additionally, teams should not change any component on the satellite, a target or a facility on the ground. We use a team’s VDF to determine that team’s score. Therefore, these variables must remain the same so that we can fairly evaluate every team (this is why we impose severe penalties if these items are changed). Teams should only be changing the orbital elements of the satellite.
 
Several teams changed the Orbit Coord System from ICFR to TrueofDate and the Propagator from J2 to J4. In previous seasons, we have seen changes like this when teams use the STK Orbit Wizard. If you use Orbit Wizard, be sure to check that the Fixed Variables, shown in Appendix I of the scenario booklet, have not been changed.

Incomplete Submissions
Several teams failed to submit all the files required for StellarXplorers staff to score their solution.

• Six teams failed to submit their STK VDF solution file. Without the VDF, we have no way to score the solution because we have nothing to enter into the automatic grader that calculates the team’s score.
• Eleven teams sent us the starting case scenario (the original VDF file downloaded at the start of the round). This “starting case” is guaranteed to result in a poor score and does not represent the work accomplished by the team.
• Three teams sent us an incorrect file type, such as a .sc, .lic, or .zip file. These files cannot be scored by our automated grading system.

 
If you are one of the teams that failed to provide your correct VDF file, please send us the file via email so our competition staff can calculate what your score would have been.
 
​Space Foundations Course (Nova Space)
Please make sure your team has access to the Nova Space learning platform BEFORE starting the round. Utilization of this course is instrumental in preparing for the academic quiz. If you need help accessing the course, please contact the StellarXplorers Program Office.
 
Confirmation Emails
Team directors will receive automated confirmation emails upon submission of a team’s start form and academic quiz. We are unable to provide automated confirmation emails for receipt of VDF submissions.
 
Confirmation emails are sent to the email address provided in the “Team Director Email” field of the forms. To ensure there’s no delay in the delivery of these automated emails, competitors should pay close attention to the email address they are providing. There were many instances of incorrect email addresses, leading to bounce-back of the automated email and delays in the competition process.
 
QR1 Prep and Start Emails
QR1’s Prep Email will be sent out at 12:00 PM ET on Tuesday, October 22 and QR1’s Start Email will be sent out at 12:00 PM ET on Wednesday, October 30 (the day prior to the start of the competition window). To prevent delays in prepping for, or starting, the round, please contact [email protected] ASAP if you haven’t received the email by 2:00 PM ET on either day.

Finalizing Team Rosters
Team rosters must be finalized no later than October 25. Once finalized, no changes can be made to the roster other than removal of a member for the remainder of the competition. Review your team approval email for the link to register your competitors, or reach out to the StellarXplorers Program Office to make any edits to your already submitted team rosters.