-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable editable scenarios #7
Conversation
Good point! This is just a feature that I am suggesting. Cuz once people want to edit things, that usually implies they want full control. This is basically making things easier to handle. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Instead of listing the "create your own scenario" on the side bar. Create a button on the above to with text like "editable", once it is selected, all the things become editable and goals become omniscient
- Put scenario in a single row, besides just listing the codename, include a few tokens of the scenario, so people could have a preview of the scenario before choing them
- Allow choose models for each agent, include a special human model, which would require human input. If all models are not humans, then we do normal sotopia simulation.
@bugsz thanks for the update, some new feedback |
Still in progress.. |
A bit strange behavior on my end: |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the efforts, I left some comments but for the sake of moving fast. I will let you decide what to merge.
set_from_env_agent_profile_combo(env_agent_combo=env_agent_combo, reset_msgs=False) | ||
|
||
|
||
from sotopia.database import EpisodeLog |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
move this to the top
rewards=rewards, | ||
rewards_prompt="", | ||
) | ||
from socialstream.rendering_utils import render_messages |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
move this?
message_list = [message.replace("**", "") for message in message_list] | ||
return "\n".join(message_list) | ||
|
||
# print(epilog.render_for_humans()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove this
return agent_profile_to_secret_info(profile, display_name=display_name) | ||
|
||
|
||
def _agent_profile_to_friendabove_self( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why we are re-writing this?
return agent_to_render | ||
|
||
|
||
def render_messages( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't this be in the rendering folder?
socialstream/chat/chat_omniscient.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
qq, isn't chat_omniscient kind of replicating a lot of features in chat.py? Can we combine them?
Also, I notice that we use the callback functions. Any chance you can update the readme to introduce/explain that concept? |
@XuhuiZhou I think ready to merge! |
The same as #6, but in a new branch name.
The first commit addresses #3, and the following commits address #4
Btw whether the scenario is editable does not relate to the omniscient? (i.e. we can still only show partial information while making the scenario editable?)