eyuep.sueyruege
/
IP_13_Playing_Cards
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Rewiev of 21.12.2023 #34

New Issue
Closed
opened 2023-12-21 12:33:56 +01:00 by eyuep.sueyruege · 0 comments
eyuep.sueyruege commented 2023-12-21 12:33:56 +01:00
Owner

1 . Client was ill and the Customer Meeting got cancled.

  1. Many Difficulties appeared, because of the OpenCv Card Detection.

  2. Alternatives:

  • Wearable+Cardset:

Pros:

  • Simplest solution
  • Keeping the Card Handling Feeling
  • Small and Efficient for reading a Card with the accuracy of 100%.
  • Get rid of complex configuration (By reducing the connection to one bluetooth capeable device (Earphone))

Cons:

  • No Multiple Detection Possible (Not Reliable in connection to multiple ddetection )

  • Wearable+Cardsorter(Color)

Pro:

  • Easy Sorted set s to to speed up the Detection Process

Cons:

  • time consuming

  • complex and tedious to implement because of Construction

  • OpenCv Card Detection via Camera

Pro:

  • Could detect multiple cards
  • very fast

Cons:

  • Time Consumption (Implementing , Optimizeing)

  • Not Reliable (Changing Predictions by the same conditions )

  • Needs a Component for communicating with the user (Server , which makes it much more complex for client)

  • Movable Construction with Multiple NFC

Pro:

  • Multiple Detection with less latency and interference

Cons:

  • To much complexity by building the constructions and calculating the Positions , electric fields etc.
  • Consumption of Time , Resources
1 . Client was ill and the Customer Meeting got cancled. 2. Many Difficulties appeared, because of the OpenCv Card Detection. 3. Alternatives: - Wearable+Cardset: Pros: - Simplest solution - Keeping the Card Handling Feeling - Small and Efficient for reading a Card with the accuracy of 100%. - Get rid of complex configuration (By reducing the connection to one bluetooth capeable device (Earphone)) Cons: - No Multiple Detection Possible (Not Reliable in connection to multiple ddetection ) - Wearable+Cardsorter(Color) Pro: - Easy Sorted set s to to speed up the Detection Process Cons: - time consuming - complex and tedious to implement because of Construction - OpenCv Card Detection via Camera Pro: - Could detect multiple cards - very fast Cons: - Time Consumption (Implementing , Optimizeing) - Not Reliable (Changing Predictions by the same conditions ) - Needs a Component for communicating with the user (Server , which makes it much more complex for client) - Movable Construction with Multiple NFC Pro: - Multiple Detection with less latency and interference Cons: - To much complexity by building the constructions and calculating the Positions , electric fields etc. - Consumption of Time , Resources
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
Labels
Clear labels   
Backend

System Side   
Frontend

UI-Interaction   
Technical

Modules and Devices   
Usability

MCI-Methods
No Label
Backend
Frontend
Technical
Usability
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: eyuep.sueyruege/IP_13_Playing_Cards#34
There is no content yet.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?