Enhancements to variables about bi-aidetection

[aesterling]

P.S. the variables were originally discussed in the ipcamtalk megathead the bottom of page 30, and top of page 31, but didn't include all the adjustments I requested above.

[VorlonCD]

Ok, I just implemented this but without new variables in the new push. Yet anyway.

See "DisplayPercentageFormat" setting in Json settings file. For your request you can change it from the default:

({0:0.00}%)
to:
{0:0}%

And I'm now forcing all object names to be case title in any case. I'm sure I'll find out if someone has done case insensitive checks against object names out there. :)

[VorlonCD]

@aesterling - is this working how you need it to?

https://github.com/VorlonCD/bi-aidetection/releases

[aesterling]

Awesome work, once again, @VorlonCD. Sorry for my delayed response! These changes are working nicely in the AI Tool interface, but the merged/annotated JPEG still shows percentage with the tenths or hundredths values. (99.97%) The title case works properly in the merged JPEG.

[VorlonCD]

@aesterling - DOH!! This fixes for image merging:
AITOOL-VORLONCD.zip

[aesterling]

:) Will download and test shortly! Thank you!

[aesterling]

Hmm, still showing the tenths/hundredths values on the merged JPEG.

Please forgive my ignorance, but am I updating the tool correctly?

1. I download the release ZIP. (in this case, from your comment above.)
2. I right-click > Properties > "Unblock" then unzip the contents.
3. Next I stop the running AI Tool, copy the contents from the unzipped folder to my AI Tool folder (C:\ai_tool) and overwrite the existing files.

Can I keep the AITool.exe.config and AITool.Settings.json files from the previous version to avoid re-configuring those settings, or do they need to be deleted and recreated from scratch?

Before leaving this comment, I deleted all the files and replaced them with the contents of the ZIP. I then changed the DisplayPercentageFormat in the JSON file to {0:0}%. The confidence percentage appears as expected in the AI Tool (97%) interface, but still with the decimal place digits in the merged JPEG (97.89%).

Thanks!

[VorlonCD]

That is the correct procedure, and you can keep your last json file, they should always be forward compatible, not always back.
That is my exact format setting here, and it reflects the change in merged files that were copied. You wont of course see the "merged" changes when viewing history tab.

[aesterling]

@VorlonCD great improvements in your latest release! I'm sure you've seen, BI just added the ability to use an external image as the "alert" image, specified using the &jpeg=path parameter in the trigger URL.

In testing this today, AI Tool's [ImagePath] variable appears to point to C:\Users\Name\AppData\Local\Temp... rather than to the location set in AI Tool > Cameras > Actions > Settings > Copy alert images to folder.

Please let me know if this is intentional or maybe I'm just misunderstanding something. The goal is to use the "Merge annotation into images" JPEG as my BI alert image. Thanks!

[VorlonCD]

@aesterling - I didnt know about that! Very nice. The push I made to the code just now should fix the imagepath issue - let me know.

[VorlonCD]

I also just added a new [ImagePathEscaped] variable for use with that. Seems to work great! I can see the merged annotations in BI now.

[aesterling]

Awesome, I always have to wait for you to compile, but looking forward to testing it!

I'm having some trouble and wondering if the JPEG is still being written to disk when BI tries to grab it. The same URL works fine when I load it in my browser, but not from AI Tool. Will keep testing!

[VorlonCD]

How is this latest version working with image copying and &jpeg=[ImagePathEscaped]?

AITOOL-VORLONCD.zip

[aesterling]

The annotated and merged image shows up as my alert image in BI! ...and then BI immediately crashes. Looking into that problem, but AI Tool is working as intended!

EDIT: Sounds like the crashing was a known BI bug and hopefully fixed in last night's v5.3.3.4 update.