https://github.com/bwheelz36/seetreat_coding_task

https://github.com/bwheelz36/seetreat_coding_task

Science Score: 13.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (8.8%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

Basic Info
  • Host: GitHub
  • Owner: bwheelz36
  • License: mit
  • Default Branch: main
  • Size: 170 KB
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created almost 3 years ago · Last pushed almost 3 years ago
Metadata Files
Readme License

README.md

seetreatcodingtask

Make a new private repository for the following activities. When you are ready, add me as a colloborator so I can review.

  • Write some C++ code which reads and displays the stop sign image in this repo
  • Add some input checks - for instance: does the file exist? Is the image size acceptable (feel free to define some upper bounds on image size for instance). Is the image grey scale or RGB...etc.
  • Add some code that finds the location of the stop sign. hint: Keep this simple. We are looking for a simple thresold based approach, not a deep learning implementation!
  • Add a second plotting function (or update the first) such that the stop sign location is outlined based on the information above.
  • Write test cases for this code.
  • Write a 'build_instructions.md' describing how to build and run this code using markdown language
  • Write a 'test_instructions.md' describing how to run the tests
  • make a pull request back to the main branch

other points

  • you are welcome to but need not use cmake for build.
  • You are welcome to but do need not use third party libraries such as openCV. (but if you do make sure the build instructions reflect this)
  • You are welcome but do not need to use some existing test framework.

Owner

  • Login: bwheelz36
  • Kind: user

GitHub Events

Total
  • Pull request event: 1
  • Fork event: 1
Last Year
  • Pull request event: 1
  • Fork event: 1

Issues and Pull Requests

Last synced: over 1 year ago

All Time
  • Total issues: 0
  • Total pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Total issue authors: 0
  • Total pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
  • brendan-whelan-seetreat (1)
Top Labels
Issue Labels
Pull Request Labels