Leaderboard questions about gorilla HOT 3 OPEN

Hey Xiaowei, let me try to answer your question as much as possible:

1. At berkeley-function-leaderboard/data/function/gorilla_openfunctions_v1_test_function.py, we have had all the executable functions ready. When we are evaluating the results, we import all the functions and exec() the function calls. We will have two types of results : (1) definitive result: meaning that those result will not change subject to time. Then we do a exact match (2) real-time result: for those result that will be changing subjected to time, we will perform a type match.

2. For the leaderboard ranking on the blog post, we compute the result as (num_of_entries_per_category * accuracy_per_category)/total_entries All categories are included except for "SQL" and "Chatable" which we generate to experiment.

3. Sorry for the confusion. The no_function_call is renamed to relevance as of now since we believe it's better representative of what we are testing. Those two should have same content but you should use the "relevance" one.

4. Thank you for pointing this out. I will perform a manual check on the indices you are mentioning. I will get back to you in this PR.

from gorilla.

Fanjia, thanks for the response! Add some comments inline.

Hey Xiaowei, let me try to answer your question as much as possible:

1. At berkeley-function-leaderboard/data/function/gorilla_openfunctions_v1_test_function.py, we have had all the executable functions ready. When we are evaluating the results, we import all the functions and exec() the function calls. We will have two types of results : (1) definitive result: meaning that those result will not change subject to time. Then we do a exact match (2) real-time result: for those result that will be changing subjected to time, we will perform a type match.

Is this execution script also in the repo?

2. For the leaderboard ranking on the blog post, we compute the result as (num_of_entries_per_category * accuracy_per_category)/total_entries All categories are included except for "SQL" and "Chatable" which we generate to experiment.

Do we also include REST, Java, JavaScript tests? I don't see those numbers in the table.

3. Sorry for the confusion. The no_function_call is renamed to relevance as of now since we believe it's better representative of what we are testing. Those two should have same content but you should use the "relevance" one.
4. Thank you for pointing this out. I will perform a manual check on the indices you are mentioning. I will get back to you in this PR.

Two more questions:

1. I see Gemini pro results have been put to the leaderboard. But I haven't seen the code checked in yet.
2. For each test example, there is a "human_eval_answer" field. Are they the same as the ones the possible_answer folder?

Thanks!

from gorilla.

Some additional minor data issues:
In the single_function (generic) test cases,
index 337, the cards parameter in poker_game_winner function definition is not complete.
"cards": {"type": "object", "description": "An object containing the player name as key and the cards as values in a list."}

index 297, the question is same as the target
"question": "music.theory.chordProgression(progression=['I', 'V', 'vi', 'IV'])",

In the possible_answers files, some function names have the "_1" suffix. Is this expected?

from gorilla.