• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

MMM-Face-Reco-DNN TypeError: '<' not supported between instances of 'numpy.ndarray' and 'str'

Scheduled Pinned Locked Moved Troubleshooting
8 Posts 3 Posters 1.2k Views 3 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    ghiesseldorf
    last edited by Jul 20, 2020, 8:45 PM

    It does look like there is a dataclass issue with the “tolerance” variable. Running facerecognition.py from the commandline with only the --cascade & --encodings parameters, the module executes. However, if adding the --tolerance parameter which alters the variable from the default value, it fails on the boolean statement. Also, even commenting out the variable in the MM config.js file apparently still passes something to the module for this variable, because it fails the same as including the --tolerance value at stand alone startup. So, any thoughts on how to fix it??

    1 Reply Last reply Reply Quote 0
    • G Offline
      ghiesseldorf
      last edited by Jul 20, 2020, 9:33 PM

      FIXED: updated the ap.add_argument statement (line 66) of facerecognition.py to include “type=float” on the --tolerance variable

      S K 2 Replies Last reply Jul 21, 2020, 12:41 AM Reply Quote 2
      • S Away
        sdetweil @ghiesseldorf
        last edited by Jul 21, 2020, 12:41 AM

        @ghiesseldorf good catch! why suddenly float after all this time?

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        G 1 Reply Last reply Jul 21, 2020, 11:20 PM Reply Quote 0
        • G Offline
          ghiesseldorf @sdetweil
          last edited by Jul 21, 2020, 11:20 PM

          @sdetweil “after all this time” is right! I kept telling myself the issue couldn’t be the code itself because there were no posts about it on the forum, so it had to be something I (or my environment) was doing wrong.

          S 1 Reply Last reply Jul 21, 2020, 11:34 PM Reply Quote 0
          • S Away
            sdetweil @ghiesseldorf
            last edited by Jul 21, 2020, 11:34 PM

            @ghiesseldorf I was working on a 4 yr old piece of code a couple weeks ago that was suddenly failing. turns out the node version fixed some expression evaluation problem, and boom it broke old unchanged code,
            now, the expression should have returned false, as it does now. but did return true.

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            1 Reply Last reply Reply Quote 0
            • K Offline
              kobiavr @ghiesseldorf
              last edited by Jul 24, 2020, 5:28 PM

              @ghiesseldorf Thanks a lot, I had the same error after the last update and it fixed it for me

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              1 / 1
              • First post
                7/8
                Last post
              Enjoying MagicMirror? Please consider a donation!
              MagicMirror created by Michael Teeuw.
              Forum managed by Sam, technical setup by Karsten.
              This forum is using NodeBB as its core | Contributors
              Contact | Privacy Policy