create a login/signup page
1. Build the login functionality,including form validation and error handling .
2. Implemention the user signup feature,allowing new users to register.

Issue
A time stamp needs to be added to the .csv file for plotting the data.

Implementation

• Add a time stamp to the csv file so that the graph can be plotted with respect to that.
• Start recording the time when the mission starts, refer #17

Introduction
Currently, I am using my own protocol, which is described in the README.

• It does not account for all the sensors and telemetry data.
• It is a single-way protocol and I want the protocol to be bidirectional so that I can send commands to the CANSAT.

Solution
I have considered implementing existing middleware, like MAVLINK or MSP. Since these are cross-compatible with other ground stations as well, this would make the GCS not specific to CANSAT and much more universal

Proposed Approach

1. MAVLink Integration:

• Integrate MAVLink libraries or modules into our ground station software to handle communication with UAVs.
• Utilize MAVLink message types to exchange telemetry data, send control commands, and receive status updates from connected UAVs.
• Ensure compatibility and interoperability with MAVLink-compliant UAV platforms and systems.

2. MSP Integration:

• Explore the possibility of integrating MSP support into our ground station software, particularly for compatibility with Multiwii-based flight controllers.
• Evaluate the advantages and limitations of MSP compared to MAVLink for our specific project requirements.
• Consider implementing MSP support as an optional feature or as part of a modular communication framework within our ground station software.

Links
MAVLINK Github
MSP Protocol

Since this is a big issue i am willing to convert it into 2 issue both of level3 in order to up the stakes.😉

Summary
We aim to migrate our existing Vite React application from JavaScript to TypeScript to leverage the benefits of static typing and improved developer tooling.

Tasks

1. Update Configuration Files
   • Rename jsconfig.json to tsconfig.json.
   • Modify Vite configuration (vite.config.js) to TypeScript (vite.config.ts).
2. Convert JavaScript Files to TypeScript
   • Rename all .js and .jsx files to .ts and .tsx respectively.
   • Add type annotations and interfaces to TypeScript files where necessary.
   • Utilize TypeScript features such as type inference and strict mode to enhance type safety.
3. Update Import Statements
   • Add TypeScript and related dependencies to package.json.
   • Update any npm/yarn scripts to include TypeScript compilation.
   • Install TypeScript type definitions for third-party libraries using @types packages where available.
4. Testing
   • Run the application and ensure it works as expected with TypeScript.
   • Fix any compile-time errors or issues that arise from the migration.
   • Update or create TypeScript-specific tests to validate type correctness.

Objective

Transition our web application from Vite to Electron to enhance its usability and provide a more native experience across different platforms.

Current State:

Our web application is currently built using Vite, which offers fast builds and a modern development experience for web projects. However, I would like to transistion to electron for a more native experience. The vite build process is only for initial testing and we are eventually going to package and distribute this app for native enviornment.

Learn repos should have a LEARN.md file to teach student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/Learn.md

https://react-redux.js.org/
Use this guide to implement redux in the ground station

Description:

We need to set up and create comprehensive documentation for our project using MkDocs. This will help in maintaining clear and structured documentation that is easy to navigate and contribute to.

Tasks:

1. Create Basic Documentation Structure:

• Add a Home page.
• Add a Getting Started guide.
• Add a section for Tutorials.
• Add a section for FAQs.

2. Content Development:

• Write content for each section mentioned above.
• Ensure all documentation is clear and concise.
• Add code examples where necessary.
• Include screenshots or diagrams to illustrate key points.
  Set Up Navigation:

3. Theme and Customization:

• Choose an appropriate MkDocs theme.
• Customize the theme to align with our project's branding.
• Ensure the documentation is responsive and accessible.

4. Deployment:

• Change the workflow to deploy if there is a Documentation tag

Additional Notes:

• Refer to the MkDocs documentation for detailed instructions on each step: https://www.mkdocs.org/
• Ensure all contributions follow the project's contributing guidelines.
• Consider adding versioning to the documentation to handle updates and changes over time.

I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.

Could you please assign me the issue related to adding GitHub Desktop contribution instructions under gssoc24? I am excited about the opportunity to contribute to the project and help streamline the contribution process for others.

Add a button that Exports a csv file of the mission when pressed.

Describe the bug
In this Page not proper Resposive mode.

To Reproduce
Steps to reproduce the behavior:

1. see in our project
2. click on the inspect
3. go to the mobile site mode
4. see the responsive error

Expected behavior
The container outside the screen will overflow.

Screenshots

Desktop (please complete the following information):

• OS: Ubuntu
• Browser : chrome

Smartphone (please complete the following information):

• Device: Realme
• OS: Android 12
• Browser : chrome

Describe the bug
All redux and storybook files have not been migrated to TS.

Expected behavior
It should build without error.

Additional context
Error: tsconfig.json(10,25): error TS6046: Argument for '--moduleResolution' option must be: 'node', 'classic', 'node16', 'nodenext'.
Error: tsconfig.json(11,5): error TS5023: Unknown compiler option 'allowImportingTsExtensions'.
Error: tsconfig.json(12,5): error TS5070: Option '--resolveJsonModule' cannot be specified without 'node' module resolution strategy.

Detect the Header and Footer in application to parse packet, to eliminate false packet detection

This feature aims to solve the problem of inconsistent and delayed communication following the merging of PRs. By automating the commenting process, it ensures that contributors receive timely feedback and acknowledgments. It also reduces the administrative burden on maintainers, allowing them to focus more on code reviews and other critical tasks.

Could you please assign me this issue under GSSOC'24.

We need to transition our project from npm to Yarn for better dependency management, faster installations, and more reliable lock files.

Switching from npm to Yarn can offer several benefits:

1. Faster Installs: Yarn uses a global cache and parallelizes operations to improve speed.
2. Deterministic Dependency Resolution: Yarn's lock file (yarn.lock) ensures consistent installs across different environments.
3. Offline Mode: Yarn can install packages without an internet connection if they have been installed before.
4. Better Security: Yarn performs checksum verification of every installed package.

Tasks:

• Convert npm lock file to Yarn
• Update Documentation
• Update CI Configuration
• Remove package-lock.json
• Verify Compatibility

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template.
you can refer this: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Some suggested prompts/questions you can add to a “Report Bug” template are:

Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug
Some suggested prompts/questions you can add to a “Feature Request” issue template are:

Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/issues/new/choose
Click on Get Started button and copy the template to yours.

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

Add issues of varying difficulty to the repo often. you can add the tag GSSoC'24, Girlscript, good first issue etc.
Try to add some documentation issues as well it would be easy for beginner contributor to explore opensource through your repo.
Generate issues even if you plan on solving them, so the repository appears as active.
Contribute/commit often to the repo so it does not go stale.
Reference https://github.com/Recode-Hive/Stackoverflow-Analysis/issues

Problem
There can be a situation where the auto deployment of parachute and heat shield may fail, or if the decent rate of the CANSAT is too high.

Solution
We want a manual override button that we can either manually trigger if we observe anything unusual, or it prompts us as well in case of a too high decent rate.
The override button works essentially by sending a command to open the parachute.

Bugs:

1. The pitch ball of the component goes in the wrong opposite direction
2. The pitch ball goes out of the component boundary.

I propose to create a GitHub workflow named "Greetings". This workflow will automatically greet(using Github Bots) users who create new issues or pull requests in this repository. The Greeting will look like "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."

Please assign this issue to me

Hey
Pranjal here Contributor @GSSOC'24
repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.

could you assign this to me ?

Start Mission button

Add a button that would start the mission and the saving the csv file

Purpose

The purpose of the button is to send a command to the satellite through web serial that would tell the satellite to start send over the data

Implementation

• First implement a serial writer function ( Maybe a separate pull request ?)
• Once that is done send a command to the satellite, this would start the data transmission from the satellite side
• When the button is pressed and the data transmission starts change the button to Stop Mission, this would stop transmission and enable the Export CSV button allowing the user to download the CSV, for further analysis.
• Did I tell, the data export button should be disabled when the mission is in progress

Display the following data:

1. Latitude
2. Longitude
3. GPS Time

Is your feature request related to a problem? Please describe.
Over time, repositories can accumulate a large number of open issues, including some that may no longer be relevant or actively worked on. Manually closing these old issues can be time-consuming and tedious.

Describe the solution you'd like
I would like a workflow that automatically identifies and closes old issues based on certain criteria, such as no recent activity or being open for a specific duration.

Additional context

Map

Load a map into the app for position estimation and mission planning

• Refer to #6
• Load the map in png format

Describe the bug
favion is not present

please assign me under Gssoc24

Description:
To enrich the data analysis capabilities of the new data analysis page created using React Router, we propose implementing functionality to load CSV (Comma-Separated Values) data and visualize it on a graph. This feature will enable users to upload CSV files containing data sets and dynamically generate corresponding graphs for visual analysis.

#32, check this issue first

Proposed Solution:

• CSV Data Loading: Develop functionality to allow users to upload CSV files directly from their devices or provide a URL to fetch CSV data from external sources. Utilize appropriate libraries or APIs to parse the CSV data and extract relevant information for visualization.
• Graph Visualization: Implement graph visualization capabilities to represent the loaded CSV data in a meaningful and intuitive manner. Consider using popular charting libraries such as Chart.js, D3.js, or Plotly to generate various types of graphs, including line charts, bar charts, scatter plots, etc. I would suggest using D3.js.

Refer to this URL for Material UI
https://mui.com/material-ui/

Problem Description
Currently, our JavaScript application supports reading data from web serial but lacks the capability to send data over web serial. This limitation prevents us from fully utilizing the potential of web serial communication in our application.

Solution
Implement functionality in our JavaScript application to enable sending data over web serial. This would involve creating a feature that allows users to transmit data from the application to connected serial devices via the web serial API.

Alternatives Considered

1. Third-Party Libraries: Explore existing third-party libraries or frameworks that provide support for sending data over web serial. Evaluate the feasibility and compatibility of integrating such libraries into our application.
2. Custom Implementation: Consider developing a custom solution within our application to facilitate data transmission via web serial. This approach may require in-depth knowledge of the web serial API and JavaScript programming.

The current code has a severe lack of comments add comments!!!.

Feature request
We have the GPS coordinates via telemetry (#6). We wish to view the position of the CANSAT in real-time on maps

Proposed solution
Something like this can be made in a box

Description:
As our web application continues to grow, it's crucial to establish a robust testing framework to ensure code reliability and maintainability. Integrating Jest, a popular JavaScript testing framework, will streamline our unit testing process and enhance our development workflow. Jest offers features such as automatic mocking, snapshot testing, and parallel test execution, which can significantly improve the efficiency and effectiveness of our testing suite.

Tasks:

Install Jest: Set up Jest as a dev dependency using npm or yarn.

• Configuration: Configure Jest to work seamlessly with our project structure, including any necessary custom configurations.
• Write Tests: Create unit tests for existing and new functionalities using Jest's syntax and features.
• CI/CD Integration: Configure GitHub Actions to execute Jest tests automatically on each push to the repository.
• Documentation: Update project documentation to include instructions for running tests with Jest and guidelines for writing effective tests.

Description

We currently use Web Serial for serial communication in our Electron application. However, due to limitations or requirements, we need to migrate to using Node Serial Port. This issue tracks the migration process.

Context

Web Serial API provides a browser-based approach for communicating with serial devices, which is suitable for web applications. However, in Electron, we have access to Node.js APIs, including the serialport module, which offers more flexibility and control over serial communication.

Reasoning

There could be several reasons for migrating to Node Serial Port:

• Access to Node.js Ecosystem: Utilizing Node.js APIs allows us to leverage the entire Node.js ecosystem, including the serialport module and its extensive features.
• Platform Compatibility: Node Serial Port may offer better compatibility with various platforms compared to Web Serial, especially in an Electron environment.
• Advanced Features: Node Serial Port provides advanced features and configurations for serial communication, which may be required for our application.

Proposed Steps

• Replace Web Serial Calls: Identify and replace all instances of Web Serial API calls in the codebase with equivalent functionality using the serialport module.
• Update Dependencies: Ensure that the serialport module is installed as a dependency in the project.
• Refactor Serial Communication Logic: Refactor the serial communication logic to work with the serialport module, considering differences in API and behavior.
• Testing: Test the migration thoroughly to ensure proper functionality and compatibility across platforms.
• Documentation: Update relevant documentation, including README and code comments, to reflect the changes and provide guidance on using Node Serial Port.

Related Issues:

First implement Electron as in #39

Display the satellite's current position, trajectory, and flight path overlaid on a map

Analyse button

Add a analyse button to view and analyse the data in graph format.

Implementation

• To start with this first resolve #15
• On pressing the button route to a new page where the graph can be plotted (use D3.js)
• When a Mission is in progress disable the Analyse button, refer #17 .
• Give user option to upload there own CSV file that they can view.

The objective of this issue is to Dockerize the project to enhance portability, scalability, and ease of deployment.

Tasks:

• Create Dockerfile: Write Dockerfiles for each component of the project, including the application server, database, or any other services required.
• Configure Docker Compose: Set up Docker Compose configuration to define the services, networks, and volumes required for running the project.
• Containerize Dependencies: Identify project dependencies and ensure they are properly containerized and integrated into the Docker setup.
• Docker for Gitpod: Implement Docker configurations for Gitpod, enabling seamless integration with the Gitpod development environment.
• Docker for devcontainer: Create Docker configurations for Visual Studio Code's devcontainer, facilitating consistent development environments for contributors.
• Setup GitHub Action for Docker: Create a GitHub Action workflow to automate Docker-related tasks such as building Docker images, running tests within Docker containers, and deploying Docker containers to specified environments.
• Testing: Conduct thorough testing to ensure that the Dockerized environment behaves as expected and that the application functions correctly within the containers.
• Documentation: Update project documentation to include instructions for Docker usage, including building, running, and deploying the Docker containers.

Manual Override

• In case of failure of auto deployment of parachute and heat shield, add a button for manual deployment of the parachute.
• Prompt the user if the decent rate too high.

It lacks a landing page /home page

I will work on this issue .please assign this to me

Is your feature request related to a problem? Please describe.
Yes, the feature request is related to the problem of lack of communication and acknowledgment when issues are closed in the repository. Contributors may feel neglected or uncertain about the status of their issues if they are closed without any feedback or acknowledgment. This can lead to frustration and a decrease in motivation to contribute further.

Describe the solution you'd like
The solution is to automatically post a comment on the issue whenever it gets closed. This comment should thank the issue creator for their contribution and inform them that their issue has been closed. The message can include the issue number and a friendly greeting to make it more personal. This automation ensures that every closed issue receives a consistent and timely response, improving communication and contributor experience.

Additional context

I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.

Could you please assign me the issue related to adding GitHub Desktop contribution instructions under gssoc24? I am excited about the opportunity to contribute to the project and help streamline the contribution process for others.

What Docs changes are you proposing?
Provide a clear description of the changes you're proposing for the documentation. Are you suggesting corrections, clarifications, additions, or updates?
I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

Why do the Docs need this improvement? What is the motivation for this change? How will this change benefit the community?
Explain the motivation behind the proposed changes and how they will benefit the community or users of the documentation.
I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.

Describe the solution you'd like
Provide a clear and concise description of the changes you'd like to see implemented in the documentation.
I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

Describe alternatives you've considered
If you've thought about alternative approaches or solutions, briefly describe them here.

Additional context
Add any additional context, examples, or screenshots related to the proposed documentation changes.
Could you please assign me the issue related to adding GitHub Desktop contribution instructions under gssoc24? I am excited about the opportunity to contribute to the project and help streamline the contribution process for others.

Create 2 different files for handling serial data connection and UI component

Description:
The current version of the code lacks sufficient comments, making it challenging for developers to understand its functionality and implementation details.

Proposed Solution:

• Understanding the Code: Before adding comments, it's essential to thoroughly understand the codebase. Take time to analyze each block of code, understand its purpose, inputs, outputs, and any dependencies it relies on.
• Write Comments: Once you have a clear understanding of the code, start writing comments. Comments should be added next to each significant block of code, explaining its purpose, logic, and any relevant information that might help future developers comprehend it more easily.

How it Helps:

• Improved Code Comprehension: By adding comments, we enhance the code's readability and maintainability. Developers, including both current and future team members, can quickly grasp the code's functionality and make necessary modifications without extensive reverse engineering.
• Facilitates Collaboration: Clear comments promote collaboration among team members. When the codebase is well-documented, developers can collaborate more effectively, share insights, and provide constructive feedback, leading to better overall project outcomes.

👋 Hi @Witty-Wizard ,

I am Sanjay, program Manager Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program

Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.

As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.

This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you

• #23
• #22
• #21

What's missing in this repository !!
The README file is the first thing users and contributors see when they visit your repository. It serves several key purposes:

Introduction and Overview: It provides a clear and concise introduction to your project, explaining what it does, its purpose, and why it’s valuable.
Installation Instructions: It guides users on how to set up and install the project on their local machines, ensuring they can quickly get started.
Usage Guidelines: It offers detailed instructions on how to use the project, including examples and common use cases.
Contribution Information: It informs potential contributors on how they can contribute to the project, including any guidelines or requirements they should follow.
License Information: It specifies the licensing terms under which the project is distributed, ensuring users and contributors understand their rights and obligations.

Kindly assign this issue to me under GSSoC'24

Time Stamp

Add time stamp for data plotting

Implementation

• Add a time stamp to the csv file so that the graph can be plotted with respect to that.
• Start recording the time when the mission starts, refer #17

The current user interface and user experience of our ground station software have been identified as areas needing improvement. A more intuitive and visually appealing design will enhance usability, reduce operator errors, and provide a better overall experience for users.

Goals

Improve the visual design of the ground station interface.
Enhance user experience by making the interface more intuitive and user-friendly.
Ensure the redesign supports all existing functionalities without introducing new bugs.
Requirements

Visual Design:

Update the color scheme to be more modern and visually appealing.
Redesign icons and buttons to be more intuitive.
Improve the layout for better readability and ease of use.
Ensure that the interface is responsive and works well on various screen sizes.

User Experience:

Simplify the navigation structure.

Improve feedback mechanisms (e.g., success/failure notifications, loading indicators).
Enhance data visualization (e.g., graphs, charts) to provide clear and concise information.
Functionality:

Ensure all current functionalities are retained.

Test the redesigned interface thoroughly to avoid any new bugs or issues.
Provide clear documentation on the new design for future reference and user onboarding.

Description

We currently lack proper documentation for our project, which is crucial for onboarding new contributors and users. To address this, I propose using MkDocs, a popular static site generator geared towards creating project documentation.

Proposed Solution:

1. Set up MkDocs in our project repository.
2. Organize existing project information into Markdown files compatible with MkDocs.
3. Write comprehensive documentation covering installation instructions, usage guidelines, API references (if applicable), and contribution guidelines.
4. Integrate MkDocs with GitHub Pages for easy hosting and access.

I would like to add a pull request template for this repository. Please assign me this issue under GSSOC'24.

Feature
While the telemetry data is saved onto a .csv file, an analyse button on the webpage, that allows us to load the .csv file and view the data saved in it in graphical format for analysis of the mission.

Implementation

• To start with this first resolve #31.
• On pressing the button route to a new page where the graph can be plotted (use D3.js).
• When a Mission is in progress disable the Analyse button, refer #17.
• Give user option to upload their own CSV file that they can view.