sanidhyakr18 / Care4ther-

This code will help the users to get an idea of the accidents well before the accident took place

CARE4THER APP USING ML AND ANDROID

Nearly 80% of accidents take place yearly . this piece of code will help the users to detect an accident an a early stage and it is detected by different libraries like Deep learning etc. Code Requirements

You can install Conda for python which resolves all the dependencies for machine learning.

pip install requirements.txt Procedure

Run create_dataset.py for converting the video to images. Then run main.py to train the model. Finally, run model.py for testing your model. The Algorithm: Each video is a set of individual images that are time-dependent sequences. The algorithm - a hierarchical recurrent neural network - is able to treat each video as a time-dependent sequence, but still allow each video to be an independent data point.

The algorithm uses two layers of long short-term memory neural networks. The first neural network (NN) is a recurrent network that analyzes the time-dependent sequence of the images within each video. The second takes the encoding of the first NN and builds a second NN that reflects which videos contain accidents and which do not. The resulting model enables a prediction of whether new dashcam footage has an accident.

Through this method, the HRNN incorporates a time-dependent aspect of the frames within each video to predict how likely it is a new video contains a car accident.

VARIOUS TECHNOLOGIES USED IN THE PROJECT

1. DEEP LEARNING
2. MACHINE LEARNING
3. ANDROID
4. JAVA
5. CNN

Why this project is important

To prevent accidents , this is the app that can tell the location of the accident and it could prevent the accidents.

FEATURES OF THE APP

The app is made using Java language, various features are being added in the app like.. alert system for an accident,sensors,etc The app is made using Java language, various features are being added in the app like.. alert system for an accident,sensors,etc

Try implementing this project and suggest changes:) Try implementing this project and suggest changes:) Happy Learning! Happy Learning!

Roadmap

• Create android project
• Integrate ML model into app.
• Create App Design.
• Add getUserlocation feature.
• Add option to add/edit/view emergency contacts.
• Fetch nearby hospital's information using Google Maps API.
• Use hardware sensors to detect motion of vehicle.

Features

Feature	Description	Status
Predict accident	Predict accident prone areas using ML model	✔️
Home Screen	Show User's location, SOS button, Show emergency contacts	❌

How to set up the Android app in your development environment

Development Setup

Before you begin, make sure you have the Android Studio SDK downloaded and set up correctly. You can find a guide here: Setting up Android Studio

Setting up the Android Project

1. Download the Care4ther- project source either by forking and cloning the repository (recommended if you want to contribute) or by downloading it as a ZIP file and extracting it.

2. Open Android Studio, you will see a Welcome to Android window. Under Quick Start, select Import Project (Eclipse ADT, Gradle, etc.)

3. Navigate to the directory where you saved the Care4ther- project, select the "Care4ther-/Care4therApp" folder, and hit OK. Android Studio should now begin building the project with Gradle.

4. Once this process is complete and Android Studio opens, check the Console for any build errors.

5. Once all build errors have been resolved, you should be all set to build the app and test it.

6. To Build the app, go to Build>Make Project (or alternatively press the Make Project icon in the toolbar).

7. After the app is built successfully, you can test it by running it on either a real device or an emulator by going to Run>Run 'app' or pressing the Run icon in the toolbar.

If you want to build apk only, go to Build>Build apk and apk would be build and directory where apk is generated would be prompted by Android Studio.

Contributions Best Practices

Code practices

Please help us follow the best practice to make it easy for the reviewer as well as the contributor. We want to focus on the code quality more than on managing pull request ethics.

• Single commit per pull request (So that commit history doesn't become messy)
• Reference the issue numbers in the commit message. Follow the pattern Fixed #<issue number> <commit message>
• Follow uniform design practices. The design language must be consistent throughout the app.
• The pull request will not get merged until and unless the commits are squashed. In case there are multiple commits on the PR, the commit author needs to squash them and not the maintainers cherrypicking and merging squashes.
• If the PR is related to any front end change, please attach relevant screenshots in the pull request description.

How to git squash?

As a tip for new developers those who struggle with squashing commits into one, multiple commits may appear in your pull request mostly due to following reasons.

• Intentionally adding multiple commit messages after each change without just git adding.
• Updating the current branch with the remote so a merge commit takes place.

You can also follow this easy and helpful tutorial: How to squash commits Despite any reason, follow the steps given below to squash all commits into one adhering to our best practices.

• Setup remote to upstream branch if not set before;

$ git remote add upstream https://github.com/unnati914/Care4ther-.git

• Check into the branch related to the pull request

$ git checkout <branch-name>

• Perform a soft reset to retain the changes while removing all the commit details

$ git reset --soft upstream/main

• Add files to the staging area

$ git add <file paths or "." to add everything>

• Create a new commit with a proper message following commit message guidelines

$ git commit -m "tag: commit message"

• If you have already made a pull request,

$ git push -f origin <branch-name>

Code style

Please try to follow the mentioned guidelines while before submitting your code as so that uniform code style is maintained in the project. It also makes it easier for the reviewer and other developers to understand.

• While naming the layout files, ensure that the convention followed is (activity/fragment) _ (name).xml like activity_main.xml , fragment_user_location.xml .
• • The activity/fragment file name corresponding to the layout files should be named as (activity/fragment name)(activity/fragment).java like UserLocationActivity.java corresponding to the layout file activity_user_location.xml , UserLocationFragment.java corresponding to the layout file fragment_user_location.xml .
• Name the views and widgets defined in the layout files as (viewtype/widget) _ (name) _ (no. in the file if any) like button_save , editText_user_location .