Kopernik - Cagkan Demir, Ilke Bayer
From CS486wiki
Week 1
Date: 01/30/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- We had our first meeting of the new semester with Drew and Prof. Jones. We looked over on what we did last semester and discussed our goals for this semester.
- Moreover, we got our first tasks of this semester. Prof. Jones stated that we have to simplify our source code and also train ourselves for FTP (File Transfer Protocol).
- We started of this week’s project by simplifying our code. We had 3 separate functions of each satellite; we successfully made these 3 functions into one. Also, we added command lines on the top each function about what the function does.
- Furthermore, we moved on to the second task of this week. We trained ourselves about what FTP does and how can we use it on our project. After we learned about FTP, we got into a conclusion that FTP is not necessary and not helpful for our project.
Problems:
- We believe that File Transfer Protocol should not be implemented to our project. Because of its major disadvantages, implementing FTP will be unhelpful and unnecessary to our project because of the reasons listed below:
- Even though we can add and delete files with the FTP, we cannot sort them in the folder.
- We believe that captions are one of the most important parts of our website because of the information that shares to our viewers. Since we are operating on Linux, as you know, we cannot change (or even view) the captions on the OS, and we do it on the Nextgen Gallery. If we implement the FTP to our project, we will be unable to change the captions as we wish.
To-Do:
- We will discuss the details with Drew and Prof. Jones about the prospective implementation of the File Transfer Protocol.
Week 2
Date: 02/06/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- In the last meeting, we settled our new goals for this week. Even though we simplified and added command lines last week, Prof. Jones stated that the source code can be much clearer to understand, and he asked us to add more command lines. Furthermore, as for a new task, he asked us to find a way to change or view the picture descriptions on Linux.
- We started of this week’s project by changing variable names that are the same but have different uses and we changed them to eliminate confusion. Furthermore, we added even more command lines with clear descriptions.
- Then, we moved on to the second task of this week. We looked upon how to view the captions on our OS, Linux. We found out that the captions/descriptions are called “metadata” which we think we can build a function to view the “metadata” on our source code.
Problems:
- All NOAA18 files that got into our system on Feb 5 3PM are broken and they are all same.
To-Do:
- For the next week, we are going to develop a function to view the captions on Linux.
Week 3
Date: 02/13/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- In the last meeting, we discussed our accomplishments of the past week. We let Prof. Jones and Drew know that the redesigning project of our source code is now complete. We showed them the updated variable names, the new command lines and getting rid of the excess empty lines. It all got approved by all of the team.
- For this week, we assigned for a new project, which is developing a function to read and write the metadata of the satellite images. As you know, we are currently reading and editing the metadata from the NextGen Gallery but we are planning to make these changes on Raspberry Pi to make it more convenient.
- We worked on how to read and edit the Metadata of the satellite images from the Raspberry Pi and we decided to write a Python function for that. After making some research and some trial and error, we managed to reach the metadata with our Python code.
Problems:
- Even though we have no problems at all on reading the metadata, we are getting “TypeError: 'iTXt' object does not support item assignment” error when we try to change the metadata. As you know, we need to change the metadata to get the desired captions of the satellite images on the website.
To-Do:
- For the next week, we are going to try the fix the “TypeError: 'iTXt' object does not support item assignment” error which we get when we try to edit the metadata to reach desired captions of the satellite images on the website.
Week 4
Date: 02/20/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- In the last meeting, we talked about how is our project doing with the new features. We informed Prof. Jones and Drew that even though we can read the metadata with the function we wrote on Python, we get errors when we try to edit the metadata. After we informed the team, Prof. Jones told us to work on to fix the error and work on build a function about FTP transfer.
- After Prof. Jones assigned our weekly work, we started fixing and building our new functions. First, we made the necessary edits to our Metadata Read/Write function and managed to fix the error code. Then, we started building on projected File Transfer Protocol implementation. Even though it is not ready to implement it yet, we built the code infrastructure to work on next week.
Problems:
- Even though now we can write on the metadata of the satellite images, now we have problems on saving those edits. For example, we made all those edits based on Drew’s suggestion but after the code ran based on the next satellite pass, all the edits we made is gone away.
To-Do:
- For the next week, we are going to work on our FTP function and improve it so we can add this implementation to our source code.
- Furthermore, we are going to work on saving those metadata edits so they do not go away after each satellite pass.
Week 5
Date: 02/27/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- In the last meeting, we talked about how our project is doing about new implementations. We informed Prof. Jones and Drew about the problems we are having on Metadata edit function, even though we can make all those suggested edits, we could not save it afterwards. Furthermore, we talked about our FTP implementation function, and we sent the code of it to Prof. Jones. We have been asked to fix the metadata edit function and improve the FTP implementation function.
- After we get those suggestions, we started our weekly work. First, we worked on the metadata edit function. We had problems for saving those edits, so we started to try different approach. We tried overwriting or saving it as a new file. With those approaches, while we can save most of the metadata like file name and size, we are still could not figure out saving the caption. Then, we checked out the validity of our File Transfer Protocol function. We are currently working on that, but it is still far away from a complete function.
Problems:
- While we can save most of the metadata like file size, file name etc., we cannot save the caption metadata.
To-Do:
- We are going to work on about FTP function and discuss how we can implement it.
- Also, we will keep working on the metadata edit function to find out a way for saving the whole metadata after we complete the suggested edits.
Week 6
Date: 03/06/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- In the last meeting, we talked about how our project is doing about new implementations. We informed Prof. Jones and Drew what are we trying to accomplish to fix the errors and implement the File Transfer Protocol. Furthermore, we talked about our FTP implementation function, and our trials and errors about editing the metadata.
- After we get those suggestions, we started our weekly work. First, we worked on the metadata edit function. Even though we were almost complete with metadata editing, we still had problems saving the caption metadata after we made suggested edits. After a couple of trial and errors, we finally fixed the problem by saving them as keys of the metadata and now this function is ready to use upon FTP.
- Then, as you know last week, we brainstormed about how we can improve our File Transfer Protocol. This week we focused on editing the current function and adding more into it to make it closer for an actual implementation as Prof. Jones suggested.
Problems:
- On March of 3rd, Drew let the team know that the issues he found on some archives. To be exact, after he rebooted the RPi on March 2, there are no images that updated to the archive on all 3 satellites.
- Even though we made some improvements, we could not implement the File Transfer Protocol to our source code.
To-Do:
- We are going to discuss the archive update problems that happened after Drew rebooted the system on March 2.
- Also, we will work together to implement the File Transfer Protocol to our source code.
Week 7
Date: 03/13/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- During our last team meeting, we reported that we had successfully fixed all of the errors in the metadata read/write function and that it was now ready for implementation upon File Transfer Protocol. We also shared information about the new File Transfer Protocol function. Following that, we received our task for this week, which is finalizing the FTP function.
- After we got our new task for this week, we began by analysing our current FTP implementation function and identified areas that required improvement. We revised our approach to the image sending function and implemented a for loop to send images to the website. Additionally, we added a file removal function to delete expired images (older than 7 days).
Problems:
- We did not encounter any problems.
To-Do:
- We will discuss with the team about our FTP implementation function.
Week 8
Date: 03/20/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- During our last team meeting, we reported that we had successfully built a File Transfer Protocol for our source code and let the team know that now it is ready for implementation. Also, for the second part of the meeting we discussed the multiple open tabs that we get sometimes and brainstormed about how we can overcome this situation. After the discussion we were on the same page about the solution, which is building an error checking system for our source code to eliminate this problem once and for all.
- After the weekly meeting, we decided how we are going to build the error checking system. We built a function to check and close all the open tabs, then start the automatic image upload process.
- Furthermore, we built another function to notify the team when we get any failures while uploading the images. Based on that function, we will get emails whenever there is an image upload problem.
- Last but not least, we tried a couple of plug-ins for our File Transfer Protocol function to implement the function to the source and make it work.
Problems:
- Even though we tried to implement the plug-ins to our File Transfer Protocol, we still got problems with all of the plug-ins.
To-Do:
- We will discuss with the team about our FTP plug-ins.
Week 9
Date: 03/27/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- During our last meeting on 03/20/2023, we discussed the progress we made so far and identified a few areas for improvement. One of the main issues we discussed was the website's dependence on external platforms for image captioning. We agreed that it was crucial to edit image captions from metadata to make the website less dependent on other platforms. Hence, we worked on writing a code to extract captions from metadata and uploading them to the weather folder. This would allow us to upload and display images without relying on external platforms for captioning. We successfully implemented this feature and tested it on the website.
- Another major issue we discussed in the last meeting was the Raspberry Pi's CPU usage. We identified that the CPU usage was high due to the image processing and uploading tasks. To address this issue, Prof. Jones suggested that we explore ways to optimize the CPU usage. While we did not work on this task this week, we agreed to explore this in future meetings.
- This week, we successfully wrote the code to edit the captions from metadata before adding the pictures to the website. This implementation allows us to upload the pictures to the weather folder and copy them, reducing our dependence on the website.
Problems:
- Our algorithm for the implementation did not remove images that were older than 7 days, as it should have.
To-Do:
- We will discuss this problem with the team and work on a solution.
Week 10
Date: 04/17/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- In the previous meeting, we discussed the problems we encountered with the current algorithm, which failed to remove images older than 7 days. We agreed to focus on finding a solution for this issue in the coming week.
- This week, we successfully developed and integrated the log writer and image removal functions into our project. These functions are designed to automatically delete images from the archive that are older than 7 days, helping to keep our storage clean and up-to-date.
- However, we were not able to test these new functions yet, due to the unavailability of the NextGen Gallery plugin on our WordPress website. Despite this limitation, we have implemented the functions and are ready to test them once the plugin becomes available.
Problems:
- We were unable to test the new functions (log writer and image removal) because the NextGen Gallery plugin is currently not available on our WordPress website.
To-Do:
- We will discuss the unavailability of the NextGen Gallery plugin with the team and explore possible solutions.
- Once the plugin issue is resolved, we will test the log writer and image removal functions to ensure they are working as intended.
Week 11
Date: 04/24/2023
Attendance: Andrew Deskur, Cagkan Demir, Ilke Bayar, Prof. Merwyn Jones
Accomplishments:
- In the last meeting, we discussed the progress we have made so far on various tasks, including 7-day image removal function and the logwriter.
- This week, we made significant progress in our error checking system. Our code now checks for any open Chromium tabs, and if there are any, it notes the information in the log.txt file. This improvement allows us to track any unexpected behavior and resolve it more efficiently.
- Furthermore, we successfully reintegrated the image removal functions into our project. These functions are designed to automatically delete images from the archive that are older than 7 days, keep our archives clean and up-to-date.
- We readded the logwriter function to our code, enabling us to maintain a record of events and errors that occur during the operation of our project. This log will help us identify and resolve issues more effectively.
Problems:
- No significant problems were encountered this week.
To-Do:
- We will discuss the progress and any additional improvements needed for the error checking system, logwriter function, and the 7-day image remover function with the team in our next meeting.
