This week mostly involves wrapping up the project. I worked on finishing the final report and revising it based on my mentor’s suggestions. I also worked on wrapping up the website as well as cleaning up the Github repository. I made sure to push all changes to the github website and worked on a ReadMe.

This week, I attended the PCW conference and presented my results in a poster session. I learned a lot from the conferences and really appreciated communicating my work with others during the poster session. After the conference, I continued working on the final report and created a draft for the final report.

This week, we worked on creating my poster for the Rubin 2022 Project & Community Workshop (PCW). We worked on plotting example plots and adding in contents of the poster. We used test results from the previous test runs to create plots for the efficiency of the algorithm and evaluate the results. We ended with plots giving examples for the three simulated satellite constellations, as well plots evaluating the relationship between the dodging weight and the amount of pixels loss in pointings and plots evaluating the tradeoff between reducing pixel loss and lossing pixel depth. We concluded that given the current satellite population, dodging satellites with the Rubin scheduler is still not worth it yet as we risk lossing significant amount of image depth with a small amount of reduction in pixel loss.

This week, we have wrapped up the work on calculate streak length. I merged the branch into main and practiced using source control. I also learned how to use a research server and created an executable file with calculate streak length functions so we can efficiently run the surveys on the research server. I also worked on milestone 3.

This week, we have wrapped up the work on calculate streak length. I merged the branch into main and practiced using source control. I also learned how to use a research server and created an executable file with calculate streak length functions so we can efficiently run the surveys on the research server. I also worked on milestone 3.

This week, I worked on testing and optimizing the code. I tested the calculate streak length function on the baseline observation dataset and fixed some bugs in the code. I then started working on optimizing the run time. Since datasets are generally very large, we used numpy and shapely to optimize the code to decrease run time.

This week, I have completed the majority of the calculate streak length function. I then worked on fixing style errors and adding in doc strings and other documentations.

This week, I have started modifying and pulling out methods from the original repo to create a method that can calculate the satellite streak length in any given pointing. Basically, the method should take a potential satellite population and a single Rubin/LSST observation and computes the sum of all the satellite streak lengths in the observation. This builds on the original method which simply detects whether a satellite is in the pointing or not. I also added comments and docstrings to keep the code more organized. I also worked on this website to submit for the second milestone.

My task during week 2 was mostly to understand and break apart a previous repository. Rubin already has some code written that could check if a statellite appeared in a particular pointing. My job is to understand the job and start pulling out pieces that could be useful for my project.

During week1, we started with setting up all the dependencies and environments that I need to run the rubin sim scheduler. I also read background readings to help me better understand the problem that I’m trying to tackle and to understand what related works have already been done on this problem. We also went through a demo of the current rubin sim scheduler.