what to do next question

[jkoschinsky]

I loaded the old stlouis file into webgeoda and asked a more open-ended question that a new user would ask: "I just uploaded my data. How should I get started with the analysis?"

It then gives the following answer:

but then this answer disappears and is replaced by the following, which doesn't make sense:

I ask it to list the existing variables in the spatial file and the answer confirms that it doesn't recognize the question:

Can we add a prompt for the user to re-specify the question in a way that the bot can identify the existing variables?

[lixun910]

Good point! We used to have a function to tell the LLM the meta data like variable names and types (not the raw data). We disabled it because it is a little slow when sending the meta data to openai. With the boosted performance of the new gpt4o model, I think it is time to enable this function so the LLM knows the meta data like variable names etc. The issues like this should be solved then.

[lixun910]

But this could be a potential privacy issue that users may argue. We can make it optional later.

[jkoschinsky]

Thx! It would also be good to leave the original answer without overriding it since that's what we can tweak for suggesting reasoning steps.

…

On Mon, Jul 1, 2024, 6:44 PM Xun Li ***@***.***> wrote: Good point! We used to have a function to tell the LLM the meta data like variable names and types (not the raw data). We disabled it because it is a little slow when sending the meta data to openai. With the boosted performance of the new gpt4o model, I think it is time to enable this function so the LLM knows the meta data like variable names etc. The issues like this should be solved then. — Reply to this email directly, view it on GitHub <#144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADILY72K4UD6MQMXRBCALWLZKGBP3AVCNFSM6AAAAABKF4ZH7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGYYDQNZSGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[lixun910]

Should be fixed. Please help to check, Thanks! :)