fix: arrange output parser classes

Put all the output parser classes in one place.
Remove redundant output parser classes.
Reuse output parser classes with the same functionality.

agentverse/tasks/__init__.py

@@ -1,30 +1,4 @@
 import os
 import yaml
 
-from .simulation.math_problem_2players_tools.output_parser import (
-    MathProblem2PlayersToolsParser,
-)
-from .simulation.nlp_classroom_3players.output_parser import NlpClassroom3PlayersParser
-from .simulation.nlp_classroom_9players.output_parser import NlpClassroom9PlayersParser
-from .simulation.nlp_classroom_3players_withtool.output_parser import (
-    NlpClassroom3PlayersWithtoolParser,
-)
-from .simulation.nlp_classroom_9players_group.output_parser import (
-    NlpClassroom9PlayersGroupParser,
-)
-from .simulation.db_diag.output_parser import DBDiag
-
-from .simulation.prisoner_dilemma.output_parser import PrisonerDilemmaParser
-
-from .simulation.pokemon.output_parser import PokemonParser
-from .simulation.sde_team.sde_team_3players.output_parser import SdeTeamParser
-from .simulation.sde_team.sde_team_2players.output_parser import SdeTeamGivenTestsParser
-
-from .tasksolving.pythoncalculator.output_parser import PipelinePythoncalculatorParser
-from .tasksolving.brainstorming.output_parser import *
-from .tasksolving.humaneval.output_parser import *
-from .tasksolving.tool_using.output_parser import *
-from .tasksolving.mgsm.output_parser import *
-from .tasksolving.responsegen.output_parser import *
-from .tasksolving.logic_grid.output_parser import *
-from .tasksolving.commongen.output_parser import *
+from agentverse.output_parser import *

agentverse/tasks/simulation/math_problem_2players_tools/config.yaml

@@ -12,20 +12,20 @@ prompts:
     When responding, please use the following two-line format:
 
     [Option 1]: When you need to use a tool, output in the following format (omit the "[]" bracket when responding)
-    ACTION: (a tool name, it can be one of [${tool_names}])
-    ACTION INPUT: (input arguments for the tool)
+    Action: (a tool name, it can be one of [${tool_names}])
+    Action Input: (input arguments for the tool)
 
     [Option 2]: When you want to speak, you can use the following format:
-    ACTION: Speak
-    ACTION INPUT: (what you want to say in a single line)
+    Action: Speak
+    Action Input: (what you want to say in a single line)
 
     Here is the conversation history
     ${chat_history}
 
     Here is the observations from tool execution:
     ${tool_observation}
 
-    Now the game starts! ${role_description} You should give your action based on the above history. Remember, you should ALWAYS give your response STRICTLY in the above response format with the TWO lines start with "ACTION:" and "ACTION INPUT:" respectively!
+    Now the game starts! ${role_description} You should give your action based on the above history. Remember, you should ALWAYS give your response STRICTLY in the above response format with the TWO lines start with "Action:" and "Action Input:" respectively!
 
   summary_prompt: &summary_prompt |
     Progressively summarize the lines of a record that you uses tools, which contains inputs for certain tools and the results returned by these tools. Based on the current summary, you need to summarize from the record the goals that the you intended to solve with each call to the tool, add it onto the previous summary, and eventually return a new summary.