Adding cache

VnaviApp/App.js

@@ -20,6 +20,9 @@ class App extends Component {
   // url = 'http://10.0.2.2:5000/';
   my_path = '';
   resized_img_path = '';
+  // Image resize
+  h = 1280;
+  w = 640;
 
   state = {
     takingPic: false,
@@ -44,7 +47,7 @@ class App extends Component {
         const cropData = {
           offset: {x: 0, y: 0},
           size: {width: data.width, height: data.height},
-          displaySize: {width: 480, height: 640},
+          displaySize: {width: this.w, height: this.h},
         };
         await ImageEditor.cropImage(data.uri, cropData).then(url => {
           this.resized_img_path = url;
@@ -105,7 +108,7 @@ class App extends Component {
         const cropData = {
           offset: {x: 0, y: 0},
           size: {width: data.width, height: data.height},
-          displaySize: {width: 480, height: 640},
+          displaySize: {width: this.w, height: this.h},
         };
         await ImageEditor.cropImage(data.uri, cropData).then(url => {
           this.resized_img_path = url;
@@ -227,8 +230,8 @@ const styles = StyleSheet.create({
     borderColor: '#fff',
   },
   image: {
-    width: '85%',
-    height: '85%',
+    width: '100%',
+    height: '95%',
   },
 });
 

vnavibackend/Dockerfile

@@ -22,8 +22,12 @@ RUN rm /etc/nginx/sites-enabled/default
 
 RUN rm /etc/nginx/nginx.conf
 
+RUN mkdir -p /root/.cache/torch/hub/ultralytics_yolov5_master/
+
 COPY ./vnavibackend /etc/nginx/sites-enabled/
 
+COPY ./ultralytics_yolov5_master /root/.cache/torch/hub/ultralytics_yolov5_master/
+
 COPY ./nginx.conf /etc/nginx/
 
 RUN /etc/init.d/nginx restart

vnavibackend/app.py

@@ -32,15 +32,15 @@ def detect():
     image = Image.open(io.BytesIO(file.read()))
     result = model(image, size=1280)
     h = result.imgs[0].shape[0]
-    y0 = int(0.039 * h)
+    y0 = int(0.1 * h)
     _, result_df = parse_result(result)
-    result_message = 'index ' + str(result_df)
+    result_message = str(result_df)
     result.render()
     for img in result.imgs:
         rgb_image = cv2.cvtColor(img, cv2.COLOR_BGR2RGB)
         for i, line in enumerate(result_message.split('\n')):
-            y = y0 + y0 * i
-            cv2.putText(rgb_image, line, (y0 + 30, y), cv2.FONT_HERSHEY_SIMPLEX, 0.4, (255, 170, 86), 1, cv2.LINE_AA)
+            y = int(y0 + 0.03 * h * i)
+            cv2.putText(rgb_image, line, (0, y), cv2.FONT_HERSHEY_PLAIN, 2.4, (255, 170, 86), 3, cv2.LINE_AA)
         arr = cv2.imencode('.jpg', rgb_image)[1]
         response = make_response(arr.tobytes())
         response.headers['Content-Type'] = 'image/jpeg'
@@ -69,7 +69,7 @@ def parse_result(result):
             est_orientation = 2
         est_distance = 999
         confidence = float(df.iloc[i]['confidence'])
-        if confidence >= 0.75:
+        if confidence >= 0.1:
             door_height = float(df.iloc[i]['ymax']) - float(df.iloc[i]['ymin'])
             dh_to_h_r = door_height / h
             if dh_to_h_r >= 1:
@@ -80,7 +80,7 @@ def parse_result(result):
                          [est_orientation,
                           float("{:.3f}".format(est_distance)),
                           float("{:.3f}".format(confidence))])
-    new_df = pd.DataFrame(data_list, columns=['orientation(clk)', 'distance(m)', 'confidence'])
+    new_df = pd.DataFrame(data_list, columns=['orie(clk)', 'dist(m)', 'conf'])
     df_json = new_df.to_json(orient='split')
     res_json = json.loads(df_json)
     return json.dumps(res_json, indent=4), new_df

vnavibackend/ultralytics_yolov5_master/.gitattributes

@@ -0,0 +1,2 @@
+# this drop notebooks from GitHub language stats
+*.ipynb linguist-vendored

vnavibackend/ultralytics_yolov5_master/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# YOLOv5 🚀 Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.
+
+[homepage]: https://www.contributor-covenant.org

vnavibackend/ultralytics_yolov5_master/.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,85 @@
+name: 🐛 Bug Report
+# title: " "
+description: Problems with YOLOv5
+labels: [bug, triage]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for submitting a YOLOv5 🐛 Bug Report!
+
+  - type: checkboxes
+    attributes:
+      label: Search before asking
+      description: >
+        Please search the [issues](https://github.com/ultralytics/yolov5/issues) to see if a similar bug report already exists.
+      options:
+        - label: >
+            I have searched the YOLOv5 [issues](https://github.com/ultralytics/yolov5/issues) and found no similar bug report.
+          required: true
+
+  - type: dropdown
+    attributes:
+      label: YOLOv5 Component
+      description: |
+        Please select the part of YOLOv5 where you found the bug.
+      multiple: true
+      options:
+        - "Training"
+        - "Validation"
+        - "Detection"
+        - "Export"
+        - "PyTorch Hub"
+        - "Multi-GPU"
+        - "Evolution"
+        - "Integrations"
+        - "Other"
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Bug
+      description: Provide console output with error messages and/or screenshots of the bug.
+      placeholder: |
+        💡 ProTip! Include as much information as possible (screenshots, logs, tracebacks etc.) to receive the most helpful response.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Environment
+      description: Please specify the software and hardware you used to produce the bug.
+      placeholder: |
+        - YOLO: YOLOv5 🚀 v6.0-67-g60e42e1 torch 1.9.0+cu111 CUDA:0 (A100-SXM4-40GB, 40536MiB)
+        - OS: Ubuntu 20.04
+        - Python: 3.9.0
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Minimal Reproducible Example
+      description: >
+        When asking a question, people will be better able to provide help if you provide code that they can easily understand and use to **reproduce** the problem.
+        This is referred to by community members as creating a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example).
+      placeholder: |
+        ```
+        # Code to reproduce your issue here
+        ```
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Additional
+      description: Anything else you would like to share?
+
+  - type: checkboxes
+    attributes:
+      label: Are you willing to submit a PR?
+      description: >
+        (Optional) We encourage you to submit a [Pull Request](https://github.com/ultralytics/yolov5/pulls) (PR) to help improve YOLOv5 for everyone, especially if you have a good understanding of how to implement a fix or feature.
+        See the YOLOv5 [Contributing Guide](https://github.com/ultralytics/yolov5/blob/master/CONTRIBUTING.md) to get started.
+      options:
+        - label: Yes I'd like to help by submitting a PR!

vnavibackend/ultralytics_yolov5_master/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: 💬 Forum
+    url: https://community.ultralytics.com/
+    about: Ask on Ultralytics Community Forum
+  - name: Stack Overflow
+    url: https://stackoverflow.com/search?q=YOLOv5
+    about: Ask on Stack Overflow with 'YOLOv5' tag

vnavibackend/ultralytics_yolov5_master/.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,50 @@
+name: 🚀 Feature Request
+description: Suggest a YOLOv5 idea
+# title: " "
+labels: [enhancement]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for submitting a YOLOv5 🚀 Feature Request!
+
+  - type: checkboxes
+    attributes:
+      label: Search before asking
+      description: >
+        Please search the [issues](https://github.com/ultralytics/yolov5/issues) to see if a similar feature request already exists.
+      options:
+        - label: >
+            I have searched the YOLOv5 [issues](https://github.com/ultralytics/yolov5/issues) and found no similar feature requests.
+          required: true
+
+  - type: textarea
+    attributes:
+      label: Description
+      description: A short description of your feature.
+      placeholder: |
+        What new feature would you like to see in YOLOv5?
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Use case
+      description: |
+        Describe the use case of your feature request. It will help us understand and prioritize the feature request.
+      placeholder: |
+        How would this feature be used, and who would use it?
+
+  - type: textarea
+    attributes:
+      label: Additional
+      description: Anything else you would like to share?
+
+  - type: checkboxes
+    attributes:
+      label: Are you willing to submit a PR?
+      description: >
+        (Optional) We encourage you to submit a [Pull Request](https://github.com/ultralytics/yolov5/pulls) (PR) to help improve YOLOv5 for everyone, especially if you have a good understanding of how to implement a fix or feature.
+        See the YOLOv5 [Contributing Guide](https://github.com/ultralytics/yolov5/blob/master/CONTRIBUTING.md) to get started.
+      options:
+        - label: Yes I'd like to help by submitting a PR!