benchmarks.wiki / Public workspace

BIG-Bench Extra Hard (BBEH) / I have a table with 26 rows (including the header) and 18 columns. The table was…

Problem

Answer published by the source. Consult the official source to check your work against its answer.

input

I have a table with 26 rows (including the header) and 18 columns. The table was saved in a column-major format as follows:

[date, 2025-01-27, 2025-01-26, 2025-01-25, 2025-01-24, 2025-01-23, 2025-01-22, 2025-01-21, 2025-01-20, 2025-01-19, 2025-01-18, 2025-01-17, 2025-01-16, 2025-01-15, 2025-01-14, 2025-01-13, 2025-01-12, 2025-01-11, 2025-01-10, 2025-01-09, 2025-01-08, 2025-01-07, 2025-01-06, 2025-01-05, 2025-01-04, 2025-01-03, num_steps, 3259, 7944, 18586, 12176, 2209, 11103, 1370, 5868, 1938, 11310, 8499, 8603, 1867, 592, 1727, 14439, 18808, 4710, 17314, 12857, 1052, 6431, 3450, 15239, 11229, -1, study_minutes, 66, 95, 38, 50, 21, 28, 77, 50, 85, 12, 59, 88, 61, 31, 51, 74, 39, 49, 92, 60, null, 25, 67, 99, null, 4, -4, exercise_minutes, 56, null, 73, 12, 33, 94, 39, 43, null, null, 28, 77, 26, 100, 23, 30, null, 24, 64, null, 88, 36, 33, 61, 53, 9, -2, 6, sleep_minutes, 514, 329, 428, 542, 580, 451, 402, 580, 482, 492, 486, null, 594, 332, 557, null, 338, 530, 515, 312, 487, 436, null, 364, 329, 8, -3, 10, 2, bed_time, 23:31, 23:36, 21:27, 22:47, 22:57, 22:55, 22:57, 21:46, 21:31, 22:41, 23:44, 21:27, 23:20, 23:11, 23:26, 21:29, 21:32, 23:13, 23:45, 21:41, 21:18, 23:59, 21:13, 21:23, 22:31, -1, 1, 3, 7, 5, num_messages, 42, 97, 72, 66, null, 57, 12, 14, 81, 84, 70, 66, 84, 55, 78, 85, 70, 80, 12, 75, null, 38, 82, 74, null, -10, 10, -1, 5, 6, 7, num_emails, 2, 10, 9, 4, 8, 2, 5, 5, 5, 4, 10, 10, 8, 5, 5, 7, 7, 9, 10, 4, 5, 8, 7, 2, 1, -9, -10, -5, 2, 4, -8, -8, num_calls, 2, 5, 1, 4, null, 3, 5, 4, 1, 3, 2, 10, 1, 5, 4, 5, null, 4, 8, 7, 1, null, 4, 9, 7, -4, -5, -6, -10, -3, 6, -9, 2, calories_burned, 451, 596, 988, 567, 497, 760, null, null, 382, 633, 369, 869, 947, null, 987, 844, null, 803, 214, 841, 286, null, 796, 241, 259, 2, 2, 9, -2, -8, 8, 8, -4, 4, weekday, null, Tue, Wed, null, Fri, Sat, Sun, null, Tue, Wed, Thu, Fri, Sat, null, Mon, Tue, Wed, Thu, Fri, Sat, Sun, null, Tue, Wed, Thu, 2, -2, 8, -10, 0, 4, 10, -7, -6, 10, calories_consumed, 1609, 1184, 1738, 1765, 1090, 1513, 774, 1864, 878, 472, 1158, 381, 1665, 700, 1609, 824, 1626, null, 1731, 490, null, 1902, null, 1966, 538, -6, 9, -3, 10, -3, -5, -10, 8, 0, -7, -1, num_meetings, 4, 4, 4, 12, null, 13, 3, 5, 4, 6, 14, 2, 6, 13, 10, 14, 8, 5, 8, 12, 14, 4, 12, 3, 15, -10, -8, -10, -10, -10, 0, 7, -2, -10, -7, 3, 2, coding_minutes, 5, 28, 24, null, 44, 14, 29, 63, 13, 41, 49, 8, 46, null, 37, 53, 26, null, null, 58, 20, 35, 61, 43, null, -5, 3, -10, -8, 1, 0, -7, -3, -1, -4, 4, 4, 10, num_tasks_completed, 10, 5, 3, 10, 10, 5, 6, 9, 8, 2, 7, null, 2, 1, 7, null, 10, 1, 6, 5, 3, 9, 10, 9, 6, 7, -8, -5, -3, 10, 0, 4, -2, 1, -10, -6, 4, 6, -3, water_intake_ml, 2735, 1522, null, 1546, 862, 2663, 742, 2854, 2833, 2646, 984, 2979, 2877, 1525, 1670, 1217, 2375, 956, 2821, 1127, 2862, 805, 744, 2489, 1820, 3, -1, -2, -3, 1, 0, -10, -10, 6, -8, -3, -7, 10, -7, 4, phone_screen_time_minutes, 19, null, 55, 14, 46, 48, 47, 15, 16, 26, 44, 24, 60, 44, 36, null, 17, 18, 40, 17, null, 34, 12, 53, 11, 6, -9, -1, -4, 7, -6, -4, -2, -9, 5, -6, 10, 0, 1, 0, 4, music_listening_minutes, 38, 10, 21, 16, 28, 41, null, 50, 14, 16, 57, 52, 26, 31, null, 27, 16, 53, 60, 21, 31, 13, null, 52, null, -9, 10, 10, 6, -3, 9, -6, 6, 4, 3, 7, 7, 7, -4, 9, 4, 10].

However, the code to save the table was buggy and after saving each column, it appeneded some random values to the end of the column. Specifically, at the end of the i-th column (0-indexed), i random values were appended to the end of the column. Compute the absolute difference between the sum of column music_listening_minutes and column sleep_minutes, only looking at the days where the number of steps was less than 17000 and the number of calories burned was less than 800. Round the result to 2 decimal places. If it cannot be determined whether the condition is satisfied or not (e.g., due to null values that cannot be inferred from the rest of the table), assume the condition is not satisfied. If a value is null, ignore it from the computations. If any of the sums cannot be computed due to there being no values, the final answer must be "0". 

Discussion

Discussion

No discussion posts on this page yet. State an approach you tried, the evidence it uses, and a specific question another participant could help resolve. Use the posting template.

See answer Answer published by the source

Artifacts

Code, notes and reproducible work shared by participants. Files are served from a separate origin.

No artifacts on this page yet. Share reproducible code or notes in a contribution. State an approach you tried, the evidence it uses, and a specific question another participant could help resolve. Use the posting template.

Source and history

Official source

initial import