google-deepmind / google-deepmind/natural-plan
Another possible solution in Calendar Scheduling
- Dominant language
- Python
- Stars
- 59
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Hi Authors,
First, thank you for sharing this useful data and benchmark. While testing the Calendar Scheduling dataset, I discovered that another possible solution to certain exemplars might exist.
One example I found is **calendar_scheduling_example_98**:
"You are an expert at scheduling meetings. You are given a few constraints on the existing schedule of each participant, the meeting duration, and possibly some preferences on the meeting time. Note there exists a solution that works with existing schedule of every participant. Here are a few example tasks and solutions: TASK: You need to schedule a meeting for Juan, Marilyn and Ronald for half an hour between the work hours of 9:00 to 17:00 on Monday. Here are the existing schedules for everyone during the day: Juan is busy on Monday during 9:00 to 10:30, 15:30 to 16:00; Marilyn has blocked their calendar on Monday during 11:00 to 11:30, 12:30 to 13:00; Ronald has blocked their calendar on Monday during 9:00 to 10:30, 12:00 to 12:30, 13:00 to 13:30, 14:00 to 16:30; Juan can not meet on Monday after 16:00. Find a time that works for everyone's schedule and constraints. SOLUTION: "
where the **golden plan** is:
"Here is the proposed time: Monday, 13:30 - 14:00 "
However, according to the given constraints, I think **10:30 - 11:00** would also meet the conditions.
Could you review this question and check if there is anything I misunderstood in this dataset?
Thank you!
Contributor guide
Research direction
Start by locating the dataset entry for calendar_scheduling_example_98 and compare its constraints with the golden plan shown in the issue. Verify whether 10:30–11:00 satisfies every participant's schedule; done means the exemplar is corrected or the reported alternative is explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100