Kopernik - Ezgi Cakir

Week One

Title: Meeting with Prof. Jones

Date: 09/07/2020

Subject: Overview and Planning of Kopernik

Attendance: Ezgi Cakir, Prof. Merwyn Jones

Meeting Agenda

- Introduced to necessary tools such as Selenium and Raspberry Pi. Selenium will be used to control Wordpress which deals with Kopernik website. After getting photos of the satellite during 24 hours, new photos must be posted on the Kopernik's website. Selenium through Python will organize how the photos will be posted and updated/deleted.

- It will be possible to access Raspberry Pi with VNC Viewer remotely whereas, when needed Raspberry Pi could be used manually to change the source code. When necessary Prof. Jones will lend me a Raspberry Pi. In order to connect to Raspberry Pi interface, Andrew Deskur will provide me the credentials (userid and password).

- One of the current problems within the project is the chrome file does not work properly after the microSD card got burned. Chrome file needs to be rebooted for the root and the user. Since amplifier between the satellite and Raspberry Pi depends on it, it has a high priority.

- For future improvements, the photos of last 7 days of satellites could be saved on the website. Currently, it displays the recent photos while deleting the old ones from the website.

Current Status

- Meeting with Andrew Deskur will be scheduled to discuss the details and requirements of Kopernik. Till that meeting, available material and research on the project will be done.

- Prof. Jones has shared possible resources to help me get started on the project research and understanding wise. I will be checking those resources to prepare the meeting with Andrew Deskur.

- CPT form is yet to be processed to ISSS to get started with the project in terms of source code and access.

- Time for weekly meetings with Prof. Jones is scheduled. Every week at that time I will be providing status update and insight about the project. Time of the weekly meetings is titled to change dependent on Mr. Deskur's schedule.

Accomplishments

- I have filled out the CPT form and sent it to Prof. Jones.

- I have contacted to Mr. Deskur to set up a meeting to discuss further details on the project.

- I got my access to edit and create on Wiki.

Week Two

Title: Weekly Development

Date: 09/14/2020

Subject: Access to Kopernik System

Attendance: Ezgi Cakir, Prof. Merwyn Jones, Andrew Deskur

Weekly Progress

· Meeting is canceled or postponed due to CPT form delay. The status of the meeting of this week depends on the process. This update includes the written communication of attendants.

- Set up VNC Viewer to access Raspberry Pi remotely. There was a drawback about my access being confirmed. I have contacted Prof Jones and Andrew Deskur. Andrew has given me additional credentials to confirm my access. I have logged in to the email address to confirm. Got familiar with Raspberry Pi interface as well as VNC Viewer. - The BiasT has to be booted every time the system starts. Right now, booting takes place manually because there is a problem with the chrontab. Learned the right way to access the file and started to figure out a way to debug it. For scripts, there are several IDEs or tools to debug. Currently working on the best way or the possible way to debug the chron file to boot automatically.

- Filled out the CPT electronic form in the ISSS page. Requested an express mail and made the payment. Added Prof Jones and Mr. Deskur to email notifications to let them know about the new I-20 process. Agreed on rescheduling the weekly meeting after I-20 arrives.

Current Status

- Learning and getting accustomed with Raspberry Pi and VNC Viewer interfaces. I examine the source codes without making any changes to figure out how it is working and what the problems are. Chron files and script debugging in this sense are prioritized. Going through the resources Prof Jones provided me last week to have a clear sense of the project requirements.

- Waiting for new I-20 to arrive to get started with the project officially.

Accomplishments

- I have completed Electronic request for CPT form to ISSS as well as requesting an express mail. I have provided necessary information such as address, delivery option and payment details to create a shipping ID ticket. I have emailed the shipping ID to ISSS and confirmed that they got the email.

- Mr. Deskur will be attending the weekly meetings with Prof Jones every Monday mornings to discuss developments in the course of the project. This week’s meeting is likely to be rescheduled due to CPT form.

- I could access Raspberry Pi through VNC Viewer remotely. Currently I only use it to examine the code and nothing else.

Week Three

Title: Weekly Meeting

Date: 09/21/2020

Subject: Issue with Cron File

Attendance: Ezgi Cakir, Prof. Merwyn Jones, Andrew Deskur

Meeting Agenda

- We have discussed the possible reasons why the Cron file stopped working after SD card got burned. I got filled in the tried solutions so far to have an appropriate starting point to solve the problem. Cron file has been deleted and recreated the same way in case the file got damaged. However, the same problem kept going on.

- Mr. Deskur recommended me an app to keep track of the times that satellites send the images. Thanks to that, I will be able to comprehend if the system is working right or not. During those hours when the system is booted, I am supposed to be getting clear images with no noise.

- Some of the sensors of the satellites do not work properly with the current parameter. Most probably the parameter of the bandwidth will be changed in RPI to also display red and green colors. In order to achieve that, I will be working on how to set the frequency right.

Current Status

- I got clarification on Cron files. The current Cron file consists of two lines in which line 1 does not work while line 2 works. It also came to my attention that there are two Cron files: one for the root and the other for the user. It is not specific which one BiasT uses to reboot itself. Our guess is it is using both of them combined. Next week I’ll be working on debugging the Cron file.

- Mr. Deskur added a new improvement to the improvements. On the Kopernik website where the satellite images are displayed, sometimes there are 2-3 of the same thumbnails and only one of those thumbnails opens when clicked on. Mr. Deskur wishes the repeated thumbnails fixed.

Accomplishments

- I have my new I-20 which means I will be able to update/change the source code of the project from on. The current version of the project is backed up for any disastrous possibility.

- I found several resources on how to debug the crontab file to fix the issue of rebooting the BiasT automatically. I got familiar with using the VNC Viewer and the whereabouts of the source files. Started to use an app to know the exact time when satellites NOAA-15, NOAA-18 and NOAA-19 will send photos.

- I went over the resources Prof. Jones and Andrew Deskur provided me. For the moment, I will be using VNC Viewer to access to RPI remotely. In case of need, I might build my own system to work on the project.

Week Four

Title: Weekly Meeting

Date: 09/28/2020

Subject: Issue with Cron File

Attendance: Ezgi Cakir, Prof. Merwyn Jones, Andrew Deskur

Meeting Agenda

- I have been researching to find a way to debug the cron file. In order to see how it executes, I tried to execute it from the terminal. I got the following error: Failed to execute child process “xterm” (No such file or directory). Thus, I ran the command “sudo apt-get install xterm to complete the missing process.

- When the command line “sed ‘s.. /var/log/boot” is ran, we get the “Nothing has been logged yet. If you’re still seeing this message your current init system might not write bootup messages to the system console at all” error. This error supports the log problem I have encountered on the Internet during my research. I will be looking at this for the next week.

Current Status

- The relationship of cron file and rebooting had made clear for me. Mostly cron files have a schedule that they run. In this project, the cron file is expected to run every time the system restarts. As far as I know, there are other types of files that make it possible and more efficient. If cron file problem cannot be averted, I might choose a different approach to solve it. - The error I fixed so far does not solve the cron file crisis on its own. The images we get from the satellites are still distorted. BiasT has to reboot itself automatically for the images to be clear of noise.

Accomplishments

- The error about xterm file I was getting is fixed. The terminal window at the bottom right opens and closes. Prof. Jones directed me to how to keep the window open.

- Since the cron file only consists of two lines of script, I suspect that the issue has got to do with booting files not being logged or a PATH issue. Drew helped me figure out possible ways to monitor the cron file activities to specify the problem. There could be several command lines I could use to fix the problem.

- I found tools like Cronitor that monitors the activities of the cron file and notifies you. There is a trial version available. It could be used as a last resource to debug.

Week Five

Title: Weekly Meeting

Date: 10/05/2020

Subject: Issue with Cron File

Attendance: Ezgi Cakir, Prof. Merwyn Jones, Andrew Deskur

Meeting Agenda

- I have been trying to send the log files of crontab to syslog. When logs are kept and sent, there is a good chance to figure out what is the issue. Crontab permissions and changing the frequency of the crontab are my priorities to debug the crontab. I have located several logs which I could not make sense yet.

- There was an issue with the website that prevented it from working. Apart from BiasT not getting the images, the website was down. The cause is unknown.

Current Status

- There are multiple cron file logs which include one ‘pi’ and many ‘root’ logs. I am trying to make sense of what that means. Originally, there was supposed to be one user and one root crontab. - The images from the satellite remain still distorted which means that BiasT is still not working properly.

Accomplishments

- After taking back some of the changes the script of the website is running. The table of logs is as follows:

pi@raspberrypi:~/rtl_biast/build/src $ grep CRON /var/log/syslog Oct 4 00:02:01 raspberrypi CRON[18029]: (pi) CMD (/home/pi/weather/predict/schedule_all.sh) Oct 4 00:17:01 raspberrypi CRON[19117]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 01:17:02 raspberrypi CRON[20949]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 02:17:01 raspberrypi CRON[23033]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 03:17:01 raspberrypi CRON[24613]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 04:17:01 raspberrypi CRON[26390]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 05:17:01 raspberrypi CRON[28326]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 06:17:01 raspberrypi CRON[30258]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 06:25:01 raspberrypi CRON[30486]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Oct 4 06:47:02 raspberrypi CRON[31214]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )) Oct 4 07:17:01 raspberrypi CRON[32137]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 08:17:01 raspberrypi CRON[2564]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 09:17:01 raspberrypi CRON[4451]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 10:17:01 raspberrypi CRON[6926]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 11:17:01 raspberrypi CRON[8934]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 12:17:01 raspberrypi CRON[11181]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 13:17:02 raspberrypi CRON[13051]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 14:17:01 raspberrypi CRON[14868]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 15:17:01 raspberrypi CRON[16702]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 16:17:01 raspberrypi CRON[18558]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 17:17:01 raspberrypi CRON[20527]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 18:17:01 raspberrypi CRON[23086]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 19:17:01 raspberrypi CRON[24852]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 20:17:02 raspberrypi CRON[27606]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 21:17:01 raspberrypi CRON[30389]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 22:17:01 raspberrypi CRON[32185]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 4 23:17:01 raspberrypi CRON[2579]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

The root crontab keeps trying to execute itself but pi crontab tries to execute only once. If they are both supposed to be working at the same time, I might have found which crontab has the issue.

Week Six

Title: Weekly Meeting

Date: 10/12/2020

Subject: BiasT

Attendance: Ezgi Cakir, Prof. Merwyn Jones, Andrew Deskur

Meeting Agenda

- In order to get clear images, BiasT needs to be rebooted automatically. Cron file is responsible to make that schedule happen. For the past weeks, I have been trying to figure out the issue with the cron file and how to debug it. My two suspicions were a PATH issue or log problem. A recent debugging made it clear that it was a log problem.

Current Status

- Ever since I have run a command about the cron file tracking down the logs, the images are clear. BiasT processes the images that are collected from satellites. Two cron files reboot themselves at the same time at midnight.

- Prof Jones and Andrew will direct me what to do next at tomorrow’s meeting.

Accomplishments

- BiasT reboots itself automatically which was the first and the most important problem to solve. - Sensors collect green and red colors as well which was one of the problems Drew mentioned when I took the requirements of the project.