sky360

Observational Citizen Science of Earths atmosphere and beyond.

Sky360.org aims to contribute to the research and understanding of UAP by providing a robotic system capable of autonomously observing the skies and capturing relevant data.

Bug Reports and Feature Requests

If you encounter a bug or have a feature request related to either the ROS2 backend or the OpenMCT frontend, you can contribute by opening an issue in the Sky360.org repository. To create an issue:

1. Go to the issue tracker of the repository.
2. Click on “New Issue”.
3. Provide a descriptive title for the issue.
4. In the issue description, provide as much detail as possible, including steps to reproduce the bug or a clear explanation of the requested feature.
5. Submit the issue.

What is needed for the station

@richard

How to build the station

@richard or @christian

How to install the software

TBD

Contributing to Sky360.org

Please take a look at our contributing.md

System Architecture - WIP

The Sky360.org system follows a modular architecture, allowing different components to communicate and work together seamlessly. The primary components of the system include:

1. Fisheye Camera: The fisheye camera captures a wide field of view, enabling a comprehensive observation of the skies.
2. Recorder: Designed to record raw data from sensors as well as situational awarness. Currently in developement for the fisheye camera.
3. OpenMCT: OpenMCT (Open Mission Control Technologies) is utilized on the client side for visualizing and analyzing the collected data in a user-friendly manner.

The modular architecture of Sky360.org allows for flexibility and scalability. Additional components can be added in future versions to enhance the system’s capabilities. The communication between the components is facilitated through ROS2, ensuring seamless integration and interoperability.

Development team

FAQ

Read here

Contribute to Sky360

We appreciate your interest in contributing to the development of Sky360.org! By contributing, you can help improve the system, add new features, and make it more robust in observing and detecting UAP. This guide outlines the steps to contribute effectively.

Software Guidelines and Best Practices

• Follow the existing code style and guidelines used in the repository for both the ROS2 backend and the OpenMCT frontend.
• Write clear and concise commit messages and pull request descriptions.
• Provide appropriate documentation and tests for new fPeatures and bug fixes in both the ROS2 backend and the OpenMCT frontend.
• Be respectful and considerate in your interactions with other contributors.

*Note: This contribution guide provides a general overview. Please adapt it to match the specific contribution process and guidelines of your Sky360.org repository, taking into account the ROS2 backend and OpenMCT frontend contributions.

Guidelines for Commit Messages

When making commits to the Sky360.org project, please follow these guidelines for writing commit messages:

• Begin the commit message with a capitalized verb in the present tense (e.g., “Add,” “Fix,” “Update,” “Refactor”).
• Keep the commit message concise and descriptive, summarizing the purpose of the commit.
• Use imperative mood (e.g., “Add new feature” instead of “Added new feature”).
• Separate the subject from the body of the message with a blank line.
• In the body, provide more detailed information if necessary, such as explaining the rationale behind the change.

Example commit message:

Add new ROS2 feature: XYZ

This commit introduces a new ROS2 feature to improve the UAP detection accuracy. The XYZ module is responsible for performing advanced object tracking algorithms based on machine learning techniques. This feature enhances the system's ability to identify and track UAP effectively.
  

Guidelines for Pull Requests

When opening a pull request (PR) for the Sky360.org project, please adhere to the following guidelines:

• Provide a clear and concise title for the PR, summarizing the changes made.
• Include a detailed description of the purpose and scope of the PR.
• Reference any relevant issues or feature requests in the description.
• Ensure that the PR includes all necessary changes, including code updates, documentation modifications, and tests, if applicable.
• Respond to any feedback or comments promptly and make the necessary updates accordingly.

Example pull request description:

Feature: Implement Real-Time Data Visualization in OpenMCT

This PR adds a real-time data visualization feature to the OpenMCT frontend. It includes a new widget that displays live telemetry data from the Sky360 robotic system. Users can now monitor the detected objects and their attributes in real time, enhancing the situational awareness during UAP observations.

Closes #42

Contact

If you have any questions or need further assistance, feel free to reach out through the issue tracker.

We appreciate your contributions and thank you for your support in advancing the Sky360.org project!

Dependencies

• docker
• Visual Studio Code
• dev containers extension https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers

Develop

1. Fork the repository on GitHub.
2. Clone your forked repository to your local machine.

git clone https://github.com/sky360-repository/sky360.git

cd sky360

Guidelines

• ROS2 (backend)

  cd src/ros2
  code .
  

Then open the folder in dev. container. (Dev Containers: Open Folder in Container… command from the Command Palette or quick actions Status bar item)

• OpenMCT (frontend)

ROS2 (backend)

create a new ROS2 node.

C++

OpenMCT (frontend)