Skip to content

feat: new proposal (structured outputs) prompts#887

Merged
peteryang1 merged 26 commits intomainfrom
yuge/tool-call-proposal-only
May 22, 2025
Merged

feat: new proposal (structured outputs) prompts#887
peteryang1 merged 26 commits intomainfrom
yuge/tool-call-proposal-only

Conversation

@ultmaster
Copy link
Collaborator

@ultmaster ultmaster commented May 19, 2025

Description

A new version of prompts for proposal. Uses structured outputs.

Motivation and Context

How Has This Been Tested?

  • If you are adding a new feature, test on your own test scripts.

Screenshots of Test Results (if appropriate):

  1. Your own tests:

Types of changes

  • Fix bugs
  • Add new feature
  • Update documentation

📚 Documentation preview 📚: https://RDAgent--887.org.readthedocs.build/en/887/

@ultmaster ultmaster changed the title New proposal prompts feat: New proposal prompts May 19, 2025
@ultmaster ultmaster changed the title feat: New proposal prompts feat(prompt): New proposal (structured outputs) prompts May 19, 2025
@peteryang1 peteryang1 changed the title feat(prompt): New proposal (structured outputs) prompts feat: new proposal (structured outputs) prompts May 19, 2025
Your task is to analyze the provided information (primarily the scenario and current SOTA, if available) and identify a concise list of **Key Challenges** or **Core Problems** relevant to achieving success in this competition and improving the target metric. Aim for **FEWER BUT BETTER** challenges (e.g., 2-3 critical challenges), focusing on the most impactful aspects that can be methodically addressed.

### Core Analysis Dimensions for Identifying Challenges
1. **SOTA Alignment Analysis**: (If SOTA is provided) Systematically compare the current SOTA implementation against dataset properties and domain knowledge to identify discrepancies or areas representing core challenges to overcome for enhancement.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A question just because of curiosity. This description duplicates with the fields of BaseModel for structure_response. Will it work in practice if we only keep one of them?

Co-authored-by: you-n-g <you-n-g@users.noreply.github.com>
@peteryang1 peteryang1 merged commit 150796a into main May 22, 2025
9 checks passed
@peteryang1 peteryang1 deleted the yuge/tool-call-proposal-only branch May 22, 2025 07:08
Jensen246 pushed a commit to Jensen246/RD-Agent that referenced this pull request Jun 6, 2025
* some initial modifications

* first prompt

* refine prompts

* isolate to v3 exp gen

* Revert prompts

* Add hypothesis

* task gen prompt

* minor updates

* minor updates

* update proposal

* Move the pydantic schema upfront to avoid loading error

* Update first prompts

* New prompt

* Update prompt

* Update data folder

* .

* Revert changes

* support v3 in pipeline and feedback

* sort imports

* black format

* Update rdagent/scenarios/data_science/dev/prompts.yaml

Co-authored-by: you-n-g <you-n-g@users.noreply.github.com>

---------

Co-authored-by: Xu Yang <peteryang@vip.qq.com>
Co-authored-by: you-n-g <you-n-g@users.noreply.github.com>
licong01-cloud pushed a commit to licong01-cloud/RD-Agent that referenced this pull request Dec 13, 2025
* some initial modifications

* first prompt

* refine prompts

* isolate to v3 exp gen

* Revert prompts

* Add hypothesis

* task gen prompt

* minor updates

* minor updates

* update proposal

* Move the pydantic schema upfront to avoid loading error

* Update first prompts

* New prompt

* Update prompt

* Update data folder

* .

* Revert changes

* support v3 in pipeline and feedback

* sort imports

* black format

* Update rdagent/scenarios/data_science/dev/prompts.yaml

Co-authored-by: you-n-g <you-n-g@users.noreply.github.com>

---------

Co-authored-by: Xu Yang <peteryang@vip.qq.com>
Co-authored-by: you-n-g <you-n-g@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants