Jump to content

mhenz

Members
  • Posts

    17
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by mhenz

  1. On 5/25/2023 at 12:45 PM, Rolf Kalbermatter said:

    No, I didn't go through the whole procedure to obtain a license.

    Shame on you 🙂

    I did it and I'm still active, even not on the frequencies, but making videos, mounting antennas for the contest, painting the truck, climbing on the mobile tower ...

    here it goes... 

     

  2. Has anyone tried to generate a client/server certificate for the NI OPC UA toolkit using the Encryption Compendium? I had no success, but it seems, that it has somethinh to do with incorrect attributes.

    BTW: The hexadecimal output of the ECL Sign.vi seems to have a final/additional 00h character at the end in the "Signature[HEX]" output. The "Signature[BYTES]" output is correct. The problem is located in RSA.lvlib:RSA_sign.vi, DSA.lvlib:DSA_sign.vi and ECDSA.lvlib:ECDSA_sign.vi. I can correct this, but don't know if this is a bug or a feature 😉 

     

  3. 15 hours ago, ensegre said:

    When I started thinking at it I had in mind an input corrector (which I'm not sure I'll really pursue) which warned the user about possible misspellings and likely corrections,

    I've never done somethig like this. I used the LevenshteinDistance to compare a lot of smaller strings (between 8 and 12 characters long). Because each of the strings was more or less significant, I used an additional factor for each of the strings and finally generated some king of an overall coefficient.

  4. Thanks for the 2019 VIs. I compared the three algorithms.

    Levenshtein works different. For better comparison, I normalized the value with:  1 - LevenshteinDistance / (Length(a)+Length(b)

    Dice: Sørensen–Dice coefficient
    CSC: Compare String Confidence.vi
    Lev.: Levenshtein

    snip.PNG.8425304390d0d27f6ba46680824ea68c.PNG

     

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.