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.

Week 4

Date: 10/17/2022

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

---

Accomplishments:

- In the last meeting, because we successfully completed all of the objectives for the project, we have given additional tasks about the archives. Prof. Jones stated that the archive section of the website is working correctly but it might be too confusing for viewers because it has got a lot of pictures and the dates were unclear. 

- After this suggestion, Cagkan stated that an archive is supposed to be confusing since the meaning of the “archive” is gathering data from previous days. Prof. Jones insisted that we have to design the archive section of the website in a much clear way.

- After this suggestion, we started brainstorming about how we can design the archive section so that website visitors can see the pictures more clearly. In the meeting, we came up with an idea that we will make 7 sections in the archive folders, so visitors can see the archive files day-by-day. After this suggestion was finally accepted by everybody in attendance, we concluded our weekly meeting and started our work.

- In order to achieve this objective Ilke and Cagkan had a meeting to figure out the best way to make the archive folder with a day-by-day section. We looked at the source code, checked out the website and spent time on Wordpress.

- Ilke came up with an idea of creating 7 archive files and after each day passes, the pictures are going to be sent in their respective folders. Although this strategy, this way of thinking did not got approved by Prof. Jones, this is the solution we came up with.

- To accomplish our objective, we created 7 additional folders named NOAA15D1, NOAA15D2 and all the way to the NOAA15D7 on Wordpress. Then we improved our source code with these folders.

Problems:

- While we were closing on finishing our objective, we encountered a VNC Viewer error and it denied our connection to the Raspberry Pi. “VNC Server is not currently listening for Cloud connections.”

- Now we have got too many folders to deal with, working on source code is a lot more difficult now. Note that Prof. Jones predicted that result on the last meeting.

To-Do:

- We need to find a more efficient way to make the archive section based on a day-by-day view.

Week 5

Date: 10/24/2022

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

---

Accomplishments:

- In the last meeting, we kept our focus on the archive section of our website. For the viewers it was too confusing to check out the photos since it has a lot of pictures and the dates were unclear.

- Since we brainstormed but could not find a way for showing it day-by-day basis last week, this week we changed our way of approach and tried to show it what we called “pass-by-pass basis” which can be described as putting the photos took on each satellite pass on the very same row. Note that this way of approach already mentioned by Prof. Jones in the last meeting.

- After this work of thought, we tried numerous ways to show the photos on the archive to be 7 photos on each row. First, Cagkan reduced the width of the photos from 120 to 90 to fit 7 photos on each row. While the width of the photos got smaller, 7 photos on a row did not fit properly.

- Then we looked out for a better way to make it a fit. We looked for source codes on Wordpress, tried to reach out for size settings on Wordpress and gave it some try. Then Ilke found the correct setting to fit 7 photos in a row, and he made the width of the photos section of the website 1110. Note that the width was 860 before.

- In order to reach out the setting for photo section width, Ilke followed settings, appearance, team editor, style.css, nextgen gallery position path and made the changes there. After doing that, now we can see 7 photos in a row in our archive sections and it is a pretty good way to start making archive sections easier to look into.

- Also we changed the view of the photos to “caption view”. As it is seen and discussed in the last meeting, with this type of view, we can get additional information about each photo.

Problems:

- We tried to figure out a way of changing captions automatically but could not figure it out. Instead, we changed 10-20 pictures’ captions on NOAA15 Archive to show everyone on the team how it is going to look if we changed all of the captions. 

- Moreover, we still do not know where the captions are coming from and how to view them on the computer before it is released on Wordpress.

To-Do:

- We are going to have a team discussion in our next meeting about the captions with all details. How to view it on file and how to run a code to copy the title and paste it on description.

Week 6

Date: 10/31/2022

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

---

Accomplishments:

- In the last meeting, Cagkan and Ilke explained their accomplishments about how they fit 7 photos in one row on archive sections by changing the photo sections width and changing the view settings as “caption view”.

- Later on, even though Drew and Prof. Jones impressed the way the archive folders looking with 7 photos on each row, they expressed that the archive folders have to be clearer and better looking. Then, we concluded our meeting by pointing that: we need to have better captions, we need to change the sorting (sort by newest, instead of sort by oldest).

- After the meeting, we started our weekly work with writing a function that edits the caption properly. Since the caption is coming from the description part of the photos, we implemented a function that edits description with the “title” and “type”. Note that photos coming with “Pristine” does not have any “type” on the description, so each photo with null “type”, our function adds “Pristine” on their caption. 

- Moreover, we changed the sorting to be shown as newest photo first. It was showing the oldest photos on top before we made this innovation. Since both Drew and Prof. Jones addressed that newer photos on top would be much better, we edited the sorting section like that. Note that we had a problem with deletion of the photos since the delete function works based on oldest photos sorted on top. We fixed that problem by making the sorting with oldest on top when the program needs to clear old photos, then turning it back to newest on top when the deletion is successfully completed, automatically.

- Last but not least, we also implemented these innovations the weather section of our website along with the archive section.

Problems:

- No problems.

To-Do:

- We are going to implement a function to our project to keep a log about satellite passes and website updates. Based on Prof. Jones’ recommendations, what we are planning to do about the forthcoming log system is creating a .txt file and implement a program to fill out the .txt on each website update.

- Also, as discussed on last week’s meeting, we are going to clear the archive sections all together to give our archive sections on the website a clean start. Part of the reason why we are going to do this is that some of the satellite photos came out faulty when we are implementing our functions during our project.