Unterminated string and date/coordinate entries as keywords - Version 2.7.1

[mmpm]

I tested version 2.7.1 a bit with LM Studio. It generally works well.
As a test, I ran 10 images in a row with Gemma 3b and found that entries were still being created for the keywords that shouldn't be there (date, coordinates).
In a second run, all entries were correct (?)
Now I've started a third run with only one image, using a different AI model each time.

Firstly, the error with the entries doesn't appear everywhere, and it can't be reliably reproduced, but it hangs every time with the zai-org/glm-4.6v-flash model.

Log attached.
lrgenius-server.log

[bmachek]

Sounds more like a problem with the used LLMs. Which size of gemma3 are you using? 4b?
If so 12b might be a better solution, or using one of the much newer qwen-vl models in an appropriate size.

Also lowering the temperature in those cases always did a great job. Do not hesitate to use temperature = 0

[mmpm]

Thanks for the hint. I’m using gemma-3-12b with a temperature of 0.8, and I left the LM Studio defaults unchanged.

I’m unfortunately not deep enough into the subject to really understand the effect of that setting. I’m much more on the side of an ambitious end user than a technical expert.

One other thought: could the prompt itself also be influencing this? With the test image, the results changed completely after I modified the prompt, and the errors disappeared. I’ll take a closer look at that interaction over the next few days.

[bmachek]

You can set the temperature in the Analyze & Index dialog, which will override the setting in LM Studio.

Higher temperature makes the AI more creative but can lead to errors and hallucinations, where on the other hand lower temperatures lead to more consistent results which I find more useful in the context of LrGeniusAI.

Of course, the prompt has a very big impact and I'm not sure if the default prompt is even close be being ideal for LrGeniusAI. I didn't put much effort into that for now...

[bmachek]

Can this issue be closed?

[mmpm]

So far, it appears that the error has been resolved.