Kopernik - Emir Tasan; Mert Bekirogullari; Taha Ucar; Teoman Kaman;: Difference between revisions

From CS486wiki
Jump to navigationJump to search
Content deleted Content added
No edit summary   (change visibility)
No edit summary   (change visibility)
Line 39: Line 39:


''<big><big>Week 3 09/20/2024</big></big>''
''<big><big>Week 3 09/20/2024</big></big>''
--------------------------------------------------------------------


<br>
<br>


Summary:
Summary:
- Conducted research on Gpredict vs Predict, focusing on platform differences, user interfaces, and satellite tracking capabilities.
- Conducted research on Gpredict vs Predict, focusing on platform differences, user interfaces, and satellite tracking capabilities.

Revision as of 21:06, 7 October 2024

Week 1 09/10/2024



Summary: This week, our goal was to successfully access the Raspberry Pi and demonstrate specific tasks related to file management and system understanding.

Accomplishments:


  1. Group meeting has been done.


To-Do: Successfully logged into the Raspberry Pi, demonstrating the ability to establish a connection. Understood the process of connecting to the Raspberry Pi and related it to the instructional link provided. Identified the folders containing the 'pi' folder within the Raspberry Pi directory structure. Demonstrated the ability to copy and move files from 'root/home/pi' to the new system.

  1. New images will be viewed to see if the crontab issue has been resolved.


Week 2 09/12/2024



Summary: This week focused on advancing the Kopernik project, specifically tasks related to the "pi" folder. The group conducted a detailed meeting to discuss the week's objectives, primarily centering on working with the system scripts. The key activities included exploring the system to locate the "schedule_all.sh" script, attempting to execute it, and investigating the integration and access of "wp_bot_sav.py." Despite facing challenges with the script's execution, valuable progress was made in familiarizing with the system and identifying potential issues for further resolution.


Accomplishments:

  1. Group meeting has been done.

Conducted a group meeting to discuss the tasks for the week and to align on the approach for working with the scripts. Explored the system to locate the "pi" folder and attempted to find the "schedule_all.sh" script. Attempted to run the "schedule_all.sh" script to ensure proper execution. Investigated how to access "wp_bot_sav.py" as part of the tasks. Although initial attempts to run the script(schedule_all.sh and schedule_satellite.sh) were unsuccessful(no directory found error in both scripts), progress was made in understanding the system and identifying potential issues.

Found the no directory found issue in the scripts. It was because we put the pi folder into new system so in the script the directories should be fixed.


Week 3 09/20/2024



Summary:

   - Conducted research on Gpredict vs Predict, focusing on platform differences, user interfaces, and satellite tracking capabilities.
   - Tested using schedule_all.sh with Gpredict, noting that the GUI is required for certain operations when working over SSH.
   - Continued exploring Selenium for task automation and integration with other tools.

Accomplishments:

   - Completed detailed comparison research between Gpredict and Predict for satellite tracking needs.
   - Successfully executed schedule_all.sh with Gpredict, identified that GUI support is required for full functionality.

To-Do:

   - Investigate methods for running Gpredict via SSH with screen sharing to bypass GUI limitations.(optional)
   - Develop on wx2 image file processing scripts, focusing on optimizing file handling and data output. Get familirazed with the image processing scripts
   - Finalize Selenium automation scripts for further testing and integration in the upcoming week.