Suggesting Clarification in UID0022 and UID0100
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- content, documentation
Research direction
Locate the benchmark entries for UID0022 and UID0100, then read their current question wording and expected-answer instructions. Clarify that UID0022 uses millions of dollars and make UID0100's rounding instructions consistent with its expected answer; done means both prompts remove the reported ambiguities.
Written by the indexing model from the issue text.
Description
Hi there!
I believe that UID0022 may benefit from a small clarification that the predicted value is expected in millions of dollars.
Currently, the answer to the question is:
[273.28, 54244, 56703]
Which is the projection you get if you run linear regression using the values in millions of dollars (e.g. [46011, 54119, ..., 53949]) reported in the FFO-3 tables. However, if you interpret the question as asking for the value in dollars, then you get an answer which is incorrectly scaled by 1 million
I think any one of the following edits to the question text could resolve the ambiguity:
Predict the total outlays (in millions of dollars) of the US department of agriculture...
... Perform all calculations in nominal millions of dollars....
... Report all values in millions of dollars inside square brackets,
On an even more minor note, UID0100 asks:
What is the average Year-over-Year (YoY) growth rate... expressed as a percent rounded to the nearest hundredths place? Additionally, run an OLS regression... All numbers should be rounded to the nearest thousandth place.
The tiny conflict in rounding instructions would only make a difference for the first value (avg. YoY growth rate) when evaluating at an absolute relative error of 0.0%, but I figured I'd point it out while I was in the weeds of the dataset.
(The expected answer rounds to the hundredths for YoY growth and thousandths for the OLS slope and y-intercept).
- Dominant language
- Jupyter Notebook
- Stars
- 199
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databricks/officeqa
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
databricks/officeqa#51 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
databricks/officeqa#50 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
databricks/officeqa#57 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
databricks/officeqa#56 ·
-
Clarification on benchmark-specific web search, potential answer leakage, and no-web evaluation Open
Difficulty 4/5 3-5 days Newbie friendliness 42/100
databricks/officeqa#55 ·
All issues in databricks/officeqa
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
TheOdinProject/curriculum#31408 ·
-
archived coursework help wanted scope: curriculum
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
freeCodeCamp/freeCodeCamp#70260 · 1 comment ·
-
雪鸿集 Open待处理 申请收录
Difficulty 1/5 Under an hour Newbie friendliness 72/100
travellings-link/travellings#4000 · 1 comment ·