Kopernik - Bayar, Ilke; Demir, Cagkan

Week 1:

Date: 09/26/2022

Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones

---

Accomplishments:

- Team members had meeting with Professor Jones and Andrew Deskur.

- Received information about the project.

- Introduced to necessary tools such as Selenium and Raspberry Pi.

- VNC Viewer installed to our PCs and remote access completed.

- Current coding files analysed and roadmap discussed.

- Company website analysed and problems founded about the uploading files to the archive section.

- https://www.n2yo.com/  --  this website is used to determine when a satellite will give us images in the today folder

Problems:

- No problems.

To-Do:

- Roadmap will be discussed with Prof. Jones and Andrew Deskur.

- To have information about how the current source code detects which satellite give those pictures.

Week 2:

Date: 10/03/2022

Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones

---

Accomplishments:

- We had the second meeting with Drew and Prof. Jones. Our meeting started off with Prof. Jones’ expectations about the improvement of the wiki and our progress. Moreover, we went to the details again about the source code and what it does.

- We cleared off the existing files for NOAA15 and NOAA19 archives. Last time they were put on that page was late April and early May so they needed to clear off. Also, the photographs on NOAA 19’s archive were inaccurate since they included the other NOAA’s photographs on it.

- For running the source code, first we run the existing source code to check out what is happening. The first thing the source code did was clearing off the existing satellite photographs that were on the page. After we realized that it was unnecessary to remove the existing satellite photographs, we checked out the source code to find out which function removed those files in the first place. After we found out which function removed the existing satellite photographs, we made it a command line to get rid of that function for now.

- We already had the last-7-days archive section on the website for showing off the archive files on the website. Although that was nice to have, we needed more sections on the website to accomplish not only showing the last 7 days’ files, but we also needed the last 15 days section and the last 30 days section. For this situation, this week we created the last 15 days section on the Selenium for all NOAA15, NOAA18 and NOAA19 satellites.

- After we did run through the source code and created the last 15 days section for all satellites, we modified the source code to publish the satellite images in the archive section. To accomplish this, we wrote a new function to copy the updated satellite images not only to the Kopernik Weather Satellite Images but 15-day archive sections on Selenium. That was a good accomplishment to have to improve our progress to our main goal.

- After we implemented our new function to the source code, when we ran the source code, we realized that the time sleep periods were too long for this source code, so we shortened the time sleep duration to run the source code.

Problems:

- To remove the satellite images at the correct timing when the archive file is full (like 7 days or 15 days) we need to figure out a function to find out when to delete the existing satellite images on time.

To-Do:

- We will create the 30 days archive files for each satellite. Then, we will implement a new function on the source code for the 30-day archive file, same as the 15-day archive file.

- We have to implement a function to remove the satellite images at the correct timing when the archive file is full. we need to figure out a function to find out when to delete the existing satellite images on time.

- In order to run the source code to update the website, we have to rearrange the time sleep duration on the source code all over.

- In the next meeting, we will have to discuss when the Selenium is going to work and when the computer gets the new images from the satellites.

Week 3:

Date: 10/10/2022

Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones

---

Accomplishments:

- We gathered for the third time for our weekly meeting with Drew and Prof. Jones. Unlike the last meeting, this week we received positive feedback from both ends. Ilke suggested an algorithm to get the pictures to the archive files but it got rejected by Prof. Jones since it was brute force coding. Furthermore, we learned that we do not need 15-day and 30-day archive files, just 7-day archive files will be sufficient for this project.

- One of the ideas we thought of on our brainstorming was source code would create a text file and keep tracking the amount of images coming on the same day. But unfortunately, we terminated that idea because it was taking too long to read and write up the text file again and again. So we need to change our the way we approach this situation.

- To make the 7-day archive directory correctly, first we needed to find the oldest images on the archive file to remove it when it expired. So, we managed to get the dates as string. But the problem was month was coming up as a word but what we needed was to get it as a number (for example Oct instead of 10). In order to fix this problem, we created a new library for translating words to integers.

- After we successfully transformed words to numbers on the files, we searched for a library to make the process efficient. We came up with the datetime library to compare the current date with the dates on the file at the archive to pull the oldest image. 

- Some of the archive files such as NOAA19ARCHIVE, NOAA18ARCHIVE, NOAA15ARCHIVE had a limit at the 21th file. This feature was both unnecessary and unhelpful for our project. We found out which line of code was causing this issue and we removed that feature from the source code.

- After making these edits, the source code now removes the expired images on the 7-day archive file.

- Typos on the website fixed for the archives. For example, it was shown as NOAA15 - Archive on the NOAA18 Archive section, we fixed that.

Problems:

- The source code is making some steps unnecessarily and it is making the process slower than it should be.

To-Do:

- Next week, we are going to figure out how to reduce the runtime of the source code and make it more efficiently.

- Tuesday is the 7th day of the source code working properly. We will check the website to see.