diff --git a/foundational_analysis/cases/case01/case01_01.json b/foundational_analysis/cases/case01/case01_01.json deleted file mode 100644 index 34fb851d422ec91ce06dc9819c174dd5f26933dc..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_01.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_01.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 11.81567963841674, - "tolerance": 1.181567963841674 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_02.json b/foundational_analysis/cases/case01/case01_02.json deleted file mode 100644 index 0c279932e97ae3dbd68a71a37a5fcf900e003782..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_02.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_02.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 9.26960186255792, - "tolerance": 0.926960186255792 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_03.json b/foundational_analysis/cases/case01/case01_03.json deleted file mode 100644 index 9e5ff1661c5a1f1e75ad7a6ecacd0a0c8224844f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_03.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_03.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 11.932442037349787, - "tolerance": 1.1932442037349789 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_04.json b/foundational_analysis/cases/case01/case01_04.json deleted file mode 100644 index 462b56eb9a283a62b26bc901b52cf7089983d24a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_04.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_04.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 5.878455525394873, - "tolerance": 0.5878455525394873 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_05.json b/foundational_analysis/cases/case01/case01_05.json deleted file mode 100644 index 90d6f444b50b7f185c627d02061d97d466b34b56..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_05.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_05.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 7.919897825685701, - "tolerance": 0.7919897825685701 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_06.json b/foundational_analysis/cases/case01/case01_06.json deleted file mode 100644 index 8beaee0c075d6afc84f3465bcf2a4c28ceb46d86..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_06.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_01.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 13.560618171116563, - "tolerance": 1.3560624385726978 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_07.json b/foundational_analysis/cases/case01/case01_07.json deleted file mode 100644 index 9cd3fd246814f9e3a34e5ecd0ee2d5eaf567af31..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_07.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_02.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 12.075784079421299, - "tolerance": 1.2075783110068763 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_08.json b/foundational_analysis/cases/case01/case01_08.json deleted file mode 100644 index 91f44233e91f07f271f2c102afe00351651f0c02..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_08.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_03.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 12.149602175318517, - "tolerance": 1.2149599789598067 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_09.json b/foundational_analysis/cases/case01/case01_09.json deleted file mode 100644 index 15014940263d6eb4d696b8dad645dd1b8ade6c35..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_09.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_04.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 14.652083592026083, - "tolerance": 1.4652082512405658 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_10.json b/foundational_analysis/cases/case01/case01_10.json deleted file mode 100644 index b2d8fe009b999a934ff560104d2a72cafbe6eeed..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_10.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_05.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 13.166214068045193, - "tolerance": 1.3166212097326537 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_11.json b/foundational_analysis/cases/case01/case01_11.json deleted file mode 100644 index ee8d11035faeb3a3a5242f97134df74c9027a94d..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_11.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-01.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-01.cnt", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 4.836610733624954, - "tolerance": 0.4836610733624954 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_12.json b/foundational_analysis/cases/case01/case01_12.json deleted file mode 100644 index 0864974f423fe9720a360aa99d46d1257afdb9a0..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_12.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-02.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-02.cnt", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 6.833748557175907, - "tolerance": 0.6833748557175907 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_13.json b/foundational_analysis/cases/case01/case01_13.json deleted file mode 100644 index 4ef18b9df34060ea6abdaae2b9cb68cd1345cba2..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_13.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-03.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-03.cnt", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 7.544371519964062, - "tolerance": 0.7544371519964063 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_14.json b/foundational_analysis/cases/case01/case01_14.json deleted file mode 100644 index ef786fe50a837dd0c73b1c5f4fd5c6640363608b..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_14.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-04.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-04.cnt", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 13.23650829225669, - "tolerance": 1.3236508292256692 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_15.json b/foundational_analysis/cases/case01/case01_15.json deleted file mode 100644 index 8721039db0da5baa1034b6a4495236bcca686432..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_15.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-05.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-05.cnt", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 9.461418170390266, - "tolerance": 0.9461418170390266 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_16.json b/foundational_analysis/cases/case01/case01_16.json deleted file mode 100644 index 913bccfe4b421f6ed064c4242c615094947c927a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_16.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_01.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 25.60839634754504, - "tolerance": 2.560839634754504 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_17.json b/foundational_analysis/cases/case01/case01_17.json deleted file mode 100644 index 71276bd0fb33a05782d915f2e2ea7664cc445382..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_17.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_02.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 26.963042816030004, - "tolerance": 2.6963042816030005 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_18.json b/foundational_analysis/cases/case01/case01_18.json deleted file mode 100644 index 3a3dd28541820aa59be6a5417da67f51d34c7fd2..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_18.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_03.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 58.63472717305611, - "tolerance": 5.863472717305612 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_19.json b/foundational_analysis/cases/case01/case01_19.json deleted file mode 100644 index aeed29a23a2e1189c3c83a44b7c67009dc08e663..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_19.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_04.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 21.885057050117236, - "tolerance": 2.188505705011724 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_20.json b/foundational_analysis/cases/case01/case01_20.json deleted file mode 100644 index 207a28f85862cfbd29a58b2f673287883034e0e3..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_20.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_05.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 36.11783061563106, - "tolerance": 3.6117830615631057 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_21.json b/foundational_analysis/cases/case01/case01_21.json deleted file mode 100644 index 999030abff2ad84afb488731ae6e30964255af5d..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_21.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_01.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 41.33018074506845, - "tolerance": 4.133018074506846 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_22.json b/foundational_analysis/cases/case01/case01_22.json deleted file mode 100644 index 03777bbf6203a32c6a5ce4879c9e590e14e39f57..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_22.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_02.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 18.30015063387382, - "tolerance": 1.830015063387382 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_23.json b/foundational_analysis/cases/case01/case01_23.json deleted file mode 100644 index f6ff2dcdb3bc5901e2edbb8d71083f6b33253b7e..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_23.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_03.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 23.478518914155703, - "tolerance": 2.3478518914155706 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_24.json b/foundational_analysis/cases/case01/case01_24.json deleted file mode 100644 index ab0eed5ea01c9f60e3521173d64b957e1c73542d..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_24.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_04.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 40.95759770354007, - "tolerance": 4.0957597703540065 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case01/case01_25.json b/foundational_analysis/cases/case01/case01_25.json deleted file mode 100644 index 49c7b9e62b597d8c8a191c07594596d62c83a87f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case01/case01_25.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_05.edf", - "instruction": "Please first extract only the EEG channels from the raw signal, and then apply a 0.5-40Hz FIR bandpass filter to these channels. After filtering, obtain each channel's Alpha-band power and total filtered-signal power by integrating the PSD over frequency. Calculate Alpha relative power separately for each channel, then average the channel-wise ratios and report the final percentage value clearly in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the 'Alpha Relative Power Percentage' from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units (%).\n4. The Key in the JSON must be EXACTLY \"alpha_ratio\".\n5. The Value must be a FLOAT (e.g., if the report says 25.5%, output 25.5).\n6. If the value is missing or cannot be found, return {\"alpha_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"alpha_ratio\": }", - "metrics": [ - { - "metric_id": "alpha_ratio_accuracy", - "type": "numeric_check", - "target_key": "alpha_ratio", - "weight": 100, - "params": { - "gt_value": 18.87056907818833, - "tolerance": 1.8870569078188328 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case02/case02_01.json b/foundational_analysis/cases/case02/case02_01.json deleted file mode 100644 index 7cc73c724f25482ac71b7ee9491ab01ea8fd7845..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_01.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_01.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 2.344264, - "tolerance": 0.234426 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 3.603543, - "tolerance": 0.360354 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_02.json b/foundational_analysis/cases/case02/case02_02.json deleted file mode 100644 index 92e0e0e49ee7b5653e4c8f222c39056a28108493..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_02.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_02.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.950857, - "tolerance": 0.095086 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 0.989856, - "tolerance": 0.098986 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_03.json b/foundational_analysis/cases/case02/case02_03.json deleted file mode 100644 index a21e481776636ac3842ca5f5c43459f94d1bccdf..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_03.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_03.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 1.168239, - "tolerance": 0.116824 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 1.684525, - "tolerance": 0.168453 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_04.json b/foundational_analysis/cases/case02/case02_04.json deleted file mode 100644 index bcf03a3f669380955fd74559ecb6c08b3fd6a243..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_04.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_04.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 1.161963, - "tolerance": 0.116196 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 2.076704, - "tolerance": 0.20767 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_05.json b/foundational_analysis/cases/case02/case02_05.json deleted file mode 100644 index 84ac0626822fa0b8033cdbbb61489e706c362bcf..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_05.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_05.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.669702, - "tolerance": 0.06697 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 0.774508, - "tolerance": 0.077451 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_06.json b/foundational_analysis/cases/case02/case02_06.json deleted file mode 100644 index b9b1ab9bc2769483d781b079658a7279d90b0cd5..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_06.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_01.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.293048, - "tolerance": 0.029305 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 0.232857, - "tolerance": 0.023286 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_07.json b/foundational_analysis/cases/case02/case02_07.json deleted file mode 100644 index eda8bf4d9aa25534afd052ac06faa0c73f13d64a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_07.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_02.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.323811, - "tolerance": 0.032381 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 0.202792, - "tolerance": 0.020279 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_08.json b/foundational_analysis/cases/case02/case02_08.json deleted file mode 100644 index a80d40f73de17b37f8f4c9a882b4e3c00c11bce9..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_08.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_03.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.264357, - "tolerance": 0.026436 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 0.244232, - "tolerance": 0.024423 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_09.json b/foundational_analysis/cases/case02/case02_09.json deleted file mode 100644 index 2d0e653a5467ce53e2b1df39847fdfa195d9fce0..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_09.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_04.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.408242, - "tolerance": 0.040824 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 0.212913, - "tolerance": 0.021291 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_10.json b/foundational_analysis/cases/case02/case02_10.json deleted file mode 100644 index 3c2d0d67df8d3a9e6b537830e342aaca6fe56ab9..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_10.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_05.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.184103, - "tolerance": 0.01841 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 0.181707, - "tolerance": 0.018171 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_11.json b/foundational_analysis/cases/case02/case02_11.json deleted file mode 100644 index 4f3be6f718a3a5adbcb1de5f3cb1bc1c4e3a564c..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_11.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-01.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-01.cnt", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.372668, - "tolerance": 0.037267 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 1.702498, - "tolerance": 0.17025 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_12.json b/foundational_analysis/cases/case02/case02_12.json deleted file mode 100644 index e941a38cdb1ea9edd8fe8dd92ff16b3e7bd77966..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_12.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-02.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-02.cnt", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 1.048704, - "tolerance": 0.10487 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 2.825685, - "tolerance": 0.282569 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_13.json b/foundational_analysis/cases/case02/case02_13.json deleted file mode 100644 index d79441d0029cb6c3a370c560c1bbb4a09436af1d..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_13.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-03.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-03.cnt", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.618508, - "tolerance": 0.061851 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 2.884954, - "tolerance": 0.288495 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_14.json b/foundational_analysis/cases/case02/case02_14.json deleted file mode 100644 index 8cc8a8aec1e6f83d5d8beb02d4076d39f34be853..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_14.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-04.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-04.cnt", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.826021, - "tolerance": 0.082602 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 1.513809, - "tolerance": 0.151381 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_15.json b/foundational_analysis/cases/case02/case02_15.json deleted file mode 100644 index ef52b4de76a0b9096a1700b36686740936698c76..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_15.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-05.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-05.cnt", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 1.554786, - "tolerance": 0.155479 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 7.43622, - "tolerance": 0.743622 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_16.json b/foundational_analysis/cases/case02/case02_16.json deleted file mode 100644 index 51a0036b0d0657f6962b72477b01e476f04a7f7d..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_16.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_01.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.904181, - "tolerance": 0.090418 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 1.133355, - "tolerance": 0.113335 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_17.json b/foundational_analysis/cases/case02/case02_17.json deleted file mode 100644 index 3ad438601daefc8d5b6c36a73b6e43d2ae2ea353..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_17.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_02.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 3.290876, - "tolerance": 0.329088 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 1.536704, - "tolerance": 0.15367 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_18.json b/foundational_analysis/cases/case02/case02_18.json deleted file mode 100644 index a0bcabddc2edcb175659b8e6eea9ecf65aa5ca03..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_18.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_03.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 6.319008, - "tolerance": 0.631901 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 1.504666, - "tolerance": 0.150467 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_19.json b/foundational_analysis/cases/case02/case02_19.json deleted file mode 100644 index 9c980c0d6b93c8bffbcca1fa617c0fd586e355fa..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_19.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_04.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 1.254156, - "tolerance": 0.125416 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 5.571346, - "tolerance": 0.557135 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_20.json b/foundational_analysis/cases/case02/case02_20.json deleted file mode 100644 index f1159d5815946aebe4ef29615bdc981785e96e6b..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_20.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_05.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 3.528239, - "tolerance": 0.352824 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 2.723892, - "tolerance": 0.272389 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_21.json b/foundational_analysis/cases/case02/case02_21.json deleted file mode 100644 index 584ba22d7c2db7081388c47331301c38c4d207c1..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_21.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_01.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 2.952141, - "tolerance": 0.295214 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 0.846158, - "tolerance": 0.084616 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_22.json b/foundational_analysis/cases/case02/case02_22.json deleted file mode 100644 index f6b4ed5533014556728de4766ea7ed2345e503df..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_22.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_02.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 1.128332, - "tolerance": 0.112833 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 1.040372, - "tolerance": 0.104037 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_23.json b/foundational_analysis/cases/case02/case02_23.json deleted file mode 100644 index ea6f2a6dc475c0611b646e789fd52e35dffc5dee..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_23.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_03.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 1.035565, - "tolerance": 0.103557 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 0.463546, - "tolerance": 0.046355 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_24.json b/foundational_analysis/cases/case02/case02_24.json deleted file mode 100644 index ce140165b44a76a5d484b05517e5f0005fc04c8e..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_24.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_04.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 2.892534, - "tolerance": 0.289253 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 1.24287, - "tolerance": 0.124287 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case02/case02_25.json b/foundational_analysis/cases/case02/case02_25.json deleted file mode 100644 index 249378b93e6165a2320847af78c89c368f354ffb..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case02/case02_25.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_05.edf", - "instruction": "Please select all available prefrontal EEG channels (FP*/AF* channels) from the raw signal; if the recording has no FP or AF channels, use F3/F4 as frontal proxies. Apply a 1-40Hz FIR bandpass filter and estimate the PSD using the Welch method. Obtain theta [4,8)Hz, alpha [8,13)Hz, and beta [13,30]Hz band power by integrating the PSD over each frequency band. First sum each band power across all selected channels, then calculate ABR = summed alpha power / summed beta power and TBR = summed theta power / summed beta power. Clearly report both final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Alpha/Beta Ratio (ABR)\n2) Theta/Beta Ratio (TBR)\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"abr\" and \"tbr\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"abr\": , \"tbr\": }", - "metrics": [ - { - "metric_id": "prefrontal_abr_accuracy", - "type": "numeric_check", - "target_key": "abr", - "weight": 50, - "params": { - "gt_value": 0.996986, - "tolerance": 0.099699 - } - }, - { - "metric_id": "prefrontal_tbr_accuracy", - "type": "numeric_check", - "target_key": "tbr", - "weight": 50, - "params": { - "gt_value": 1.322632, - "tolerance": 0.132263 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_01.json b/foundational_analysis/cases/case03/case03_01.json deleted file mode 100644 index 48e2793d35b57085cfc846bdcc8eda9262cb1797..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_01.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_01.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.706401, - "tolerance": 0.03532 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_02.json b/foundational_analysis/cases/case03/case03_02.json deleted file mode 100644 index 52a2f7f7f28dfedd135519e1a8f472fc54a4e812..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_02.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_02.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.581186, - "tolerance": 0.029059 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_03.json b/foundational_analysis/cases/case03/case03_03.json deleted file mode 100644 index f0fd61dd8bd65e3904b40381246989b8d23aa52a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_03.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_03.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.797815, - "tolerance": 0.039891 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_04.json b/foundational_analysis/cases/case03/case03_04.json deleted file mode 100644 index c4b8d7cac835028b1d27533e07ed08e742921f4f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_04.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_04.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.259607, - "tolerance": 0.01298 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_05.json b/foundational_analysis/cases/case03/case03_05.json deleted file mode 100644 index 885d551217a2052c223bb2535e8bcc0a5e2c5bd8..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_05.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_05.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.413254, - "tolerance": 0.020663 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_06.json b/foundational_analysis/cases/case03/case03_06.json deleted file mode 100644 index 9bf370c77c8c0c67529b16323587e84784e277f1..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_06.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_01.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 1.923324, - "tolerance": 0.096168 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_07.json b/foundational_analysis/cases/case03/case03_07.json deleted file mode 100644 index dbaba622056d46a5938ce2f370688940c928a991..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_07.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_02.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 1.954942, - "tolerance": 0.097744 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_08.json b/foundational_analysis/cases/case03/case03_08.json deleted file mode 100644 index eb22d44083de15cf244feb4b8acbdf4e75a019a0..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_08.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_03.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 2.011129, - "tolerance": 0.100559 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_09.json b/foundational_analysis/cases/case03/case03_09.json deleted file mode 100644 index 5ea022b784c88224d779a53e0767c76c569226ca..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_09.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_04.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 1.673776, - "tolerance": 0.083687 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_10.json b/foundational_analysis/cases/case03/case03_10.json deleted file mode 100644 index e738e2c7a53b794718e17ed266d0e0ed4aa6366e..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_10.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_05.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 2.1144, - "tolerance": 0.105719 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_11.json b/foundational_analysis/cases/case03/case03_11.json deleted file mode 100644 index 05263b6689657f17487a8ddfc04ced9e8f3aa14f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_11.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-01.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-01.cnt", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.41036, - "tolerance": 0.020518 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_12.json b/foundational_analysis/cases/case03/case03_12.json deleted file mode 100644 index d9ff83e6b1d64de47c0ffff899a90f0a3a854f3f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_12.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-02.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-02.cnt", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.194173, - "tolerance": 0.009709 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_13.json b/foundational_analysis/cases/case03/case03_13.json deleted file mode 100644 index 0f6cd873438b21292428e991d0ffdf914123644d..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_13.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-03.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-03.cnt", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.409418, - "tolerance": 0.020471 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_14.json b/foundational_analysis/cases/case03/case03_14.json deleted file mode 100644 index 670c39b54e0aafce6b42d96e1fcc8071c8062c85..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_14.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-04.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-04.cnt", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.559666, - "tolerance": 0.027983 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_15.json b/foundational_analysis/cases/case03/case03_15.json deleted file mode 100644 index c2d49fa5d28649a4b983523e25eb98727d4513d6..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_15.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-05.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-05.cnt", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.225895, - "tolerance": 0.011295 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_16.json b/foundational_analysis/cases/case03/case03_16.json deleted file mode 100644 index 2cd847688fc777c2dd4f1c51f674735081b4d344..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_16.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_01.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.956782, - "tolerance": 0.047839 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_17.json b/foundational_analysis/cases/case03/case03_17.json deleted file mode 100644 index c5f9871fdd8466c138785d7ebd6899d109313e3b..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_17.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_02.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.396196, - "tolerance": 0.01981 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_18.json b/foundational_analysis/cases/case03/case03_18.json deleted file mode 100644 index 4756ac1e1376cb2bcae6a8b01affe4a0e5a1b59a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_18.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_03.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.652412, - "tolerance": 0.032621 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_19.json b/foundational_analysis/cases/case03/case03_19.json deleted file mode 100644 index 11bd3f7b88a6d9bb3e321b80fdf6fb62211576fd..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_19.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_04.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.949021, - "tolerance": 0.047451 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_20.json b/foundational_analysis/cases/case03/case03_20.json deleted file mode 100644 index 90b3c330cf118a7ad976eff86007f195273d4afe..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_20.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_05.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 1.275055, - "tolerance": 0.063753 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_21.json b/foundational_analysis/cases/case03/case03_21.json deleted file mode 100644 index 5bb7c20b603e8afdf2079d693adfd3129f0113ce..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_21.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_01.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.43688, - "tolerance": 0.021844 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_22.json b/foundational_analysis/cases/case03/case03_22.json deleted file mode 100644 index cf3836b5e11599a0c1de2cbb4641b0ac1fd43f48..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_22.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_02.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.47464, - "tolerance": 0.023732 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_23.json b/foundational_analysis/cases/case03/case03_23.json deleted file mode 100644 index 300be7ed11c90e8e685e19048ac189201a0fa3ab..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_23.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_03.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.49237, - "tolerance": 0.024619 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_24.json b/foundational_analysis/cases/case03/case03_24.json deleted file mode 100644 index 878f846839a7419ce96f32949de23fe19c4fbfe0..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_24.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_04.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.416207, - "tolerance": 0.02081 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case03/case03_25.json b/foundational_analysis/cases/case03/case03_25.json deleted file mode 100644 index 62221d739d7c853a7d5e443b64a13cbb959f44ba..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case03/case03_25.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_05.edf", - "instruction": "Please select only the occipital EEG channels from the raw signal first. For each selected channel, use only the first 30 seconds of signal and compute Sample Entropy (SampEn) with m=2 and r=0.2 times the standard deviation of that channel segment. Then calculate the average SampEn across all selected channels and report the final mean value clearly." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final 'Mean Sample Entropy' value from the agent report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in JSON must be EXACTLY \"sampen_mean\".\n5. The value must be a FLOAT.\n6. If missing or unrecognized, return {\"sampen_mean\": null}.\n\n### OUTPUT TEMPLATE\n{\"sampen_mean\": }", - "metrics": [ - { - "metric_id": "sampen_mean_accuracy", - "type": "numeric_check", - "target_key": "sampen_mean", - "weight": 100, - "params": { - "gt_value": 0.394084, - "tolerance": 0.019704 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case04/case04_01.json b/foundational_analysis/cases/case04/case04_01.json deleted file mode 100644 index fac48c3f212f737bf6bb4d61812e2d32eb2cea59..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_01.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_01.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.586117, - "tolerance": 0.029306 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.26804, - "tolerance": 0.113402 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_02.json b/foundational_analysis/cases/case04/case04_02.json deleted file mode 100644 index 5d6f04bab97a809e47d37976a034eca6f3e47969..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_02.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_02.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 1.005496, - "tolerance": 0.050275 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.452115, - "tolerance": 0.072606 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_03.json b/foundational_analysis/cases/case04/case04_03.json deleted file mode 100644 index 19b22243096106d7466d5f6468d830d61ec17105..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_03.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_03.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.716345, - "tolerance": 0.035817 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.65056, - "tolerance": 0.082528 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_04.json b/foundational_analysis/cases/case04/case04_04.json deleted file mode 100644 index e371f5b1d6a74caa932c5402e2c4a142bf24495d..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_04.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_04.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.753642, - "tolerance": 0.037682 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.961207, - "tolerance": 0.09806 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_05.json b/foundational_analysis/cases/case04/case04_05.json deleted file mode 100644 index efe2edb8862c690920d4442ff84346ab0d29d7f1..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_05.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_05.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.852665, - "tolerance": 0.042633 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.723293, - "tolerance": 0.086165 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_06.json b/foundational_analysis/cases/case04/case04_06.json deleted file mode 100644 index 007dfe17a0f8f84c1aaa27db74b9bc782fb9a465..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_06.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_01.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 1.400182, - "tolerance": 0.070009 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.223736, - "tolerance": 0.061187 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_07.json b/foundational_analysis/cases/case04/case04_07.json deleted file mode 100644 index 2c575d87b4c9f9a01705b27e83508ba21ed7a74f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_07.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_02.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 1.393716, - "tolerance": 0.069686 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.21654, - "tolerance": 0.060827 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_08.json b/foundational_analysis/cases/case04/case04_08.json deleted file mode 100644 index b1b1a3953838e162a8afc31fdd0a1db4c61444df..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_08.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_03.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 1.343013, - "tolerance": 0.067151 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.264461, - "tolerance": 0.063223 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_09.json b/foundational_analysis/cases/case04/case04_09.json deleted file mode 100644 index da0311f304886a593420048a088534b2a4809a0e..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_09.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_04.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 1.377489, - "tolerance": 0.068874 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.248801, - "tolerance": 0.06244 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_10.json b/foundational_analysis/cases/case04/case04_10.json deleted file mode 100644 index 4d48636c1036c759bb41e3bf9fccd9271d145bd7..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_10.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_05.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 1.374781, - "tolerance": 0.068739 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.243467, - "tolerance": 0.062173 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_11.json b/foundational_analysis/cases/case04/case04_11.json deleted file mode 100644 index 10355ae9ddb4a3d1e43e7ec66b3cca562d0343cb..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_11.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-01.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-01.cnt", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.69919, - "tolerance": 0.034959 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.390286, - "tolerance": 0.119514 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_12.json b/foundational_analysis/cases/case04/case04_12.json deleted file mode 100644 index 9b9b4a6e4ebf60a1f4d741d1de31f48cb61d5f21..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_12.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-02.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-02.cnt", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.637071, - "tolerance": 0.031854 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.338962, - "tolerance": 0.116948 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_13.json b/foundational_analysis/cases/case04/case04_13.json deleted file mode 100644 index f045169411ed12e544ac06c5ef934a07ccd5d5f2..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_13.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-03.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-03.cnt", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.683709, - "tolerance": 0.034185 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.266517, - "tolerance": 0.113326 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_14.json b/foundational_analysis/cases/case04/case04_14.json deleted file mode 100644 index 4fda1e17b24f7e82c9b2deb753d5fb4df3675049..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_14.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-04.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-04.cnt", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.648689, - "tolerance": 0.032434 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.144298, - "tolerance": 0.107215 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_15.json b/foundational_analysis/cases/case04/case04_15.json deleted file mode 100644 index 3eb3dcc6f54fa48b96e1a2c2a12047020ae95801..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_15.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-05.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-05.cnt", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.491138, - "tolerance": 0.024557 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.642507, - "tolerance": 0.132125 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_16.json b/foundational_analysis/cases/case04/case04_16.json deleted file mode 100644 index c76f32a1f612cfccb8dd04701732d634983b4321..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_16.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_01.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.765497, - "tolerance": 0.038275 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.706374, - "tolerance": 0.085319 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_17.json b/foundational_analysis/cases/case04/case04_17.json deleted file mode 100644 index c968c1a5677edcf86d718ab6de8292b57974296a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_17.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_02.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.337763, - "tolerance": 0.016888 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 3.750052, - "tolerance": 0.187503 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_18.json b/foundational_analysis/cases/case04/case04_18.json deleted file mode 100644 index 5b114efe85a4a01ee260383eb99f14cd4434d5ce..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_18.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_03.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.71508, - "tolerance": 0.035754 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.525094, - "tolerance": 0.076255 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_19.json b/foundational_analysis/cases/case04/case04_19.json deleted file mode 100644 index 9e607886372edce8a04f7384e57ce1236fc5b2dc..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_19.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_04.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.530136, - "tolerance": 0.026507 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.620176, - "tolerance": 0.131009 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_20.json b/foundational_analysis/cases/case04/case04_20.json deleted file mode 100644 index b9b2ff6a823d3fa2b3da087b474e64dea7589dda..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_20.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_05.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.9439, - "tolerance": 0.047195 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.745986, - "tolerance": 0.087299 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_21.json b/foundational_analysis/cases/case04/case04_21.json deleted file mode 100644 index 27f7550f072d93d27325a5d575d98d69174a1e5c..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_21.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_01.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.53272, - "tolerance": 0.026636 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.117709, - "tolerance": 0.105885 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_22.json b/foundational_analysis/cases/case04/case04_22.json deleted file mode 100644 index bddfe0e09719febaca500f21a6ca1f17295f1d23..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_22.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_02.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.591011, - "tolerance": 0.029551 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.248344, - "tolerance": 0.112417 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_23.json b/foundational_analysis/cases/case04/case04_23.json deleted file mode 100644 index 21964ca5155c214c7f1b7a3ae0b62706c0a63c21..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_23.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_03.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.578241, - "tolerance": 0.028912 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.118097, - "tolerance": 0.105905 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_24.json b/foundational_analysis/cases/case04/case04_24.json deleted file mode 100644 index 0c9a35650c6d4b0db79f486250c36ae306645409..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_24.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_04.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.49839, - "tolerance": 0.02492 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 1.781463, - "tolerance": 0.089073 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case04/case04_25.json b/foundational_analysis/cases/case04/case04_25.json deleted file mode 100644 index b40693f0ab2cdfa893956cafebc5ec21310e6233..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case04/case04_25.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_05.edf", - "instruction": "Please select only the central-region EEG channels (C* and CP*). Apply a 50 Hz FIR notch filter, then a 0.5-45 Hz FIR bandpass filter, resample to 100 Hz, and re-reference using average reference. Use the first 90 seconds of each selected channel. Compute Hjorth Mobility and Hjorth Complexity for each channel, then report the channel-mean values as hjorth_mobility_mean and hjorth_complexity_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean Hjorth Mobility\n2) Mean Hjorth Complexity\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"hjorth_mobility_mean\" and \"hjorth_complexity_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"hjorth_mobility_mean\": , \"hjorth_complexity_mean\": }", - "metrics": [ - { - "metric_id": "hjorth_mobility_accuracy", - "type": "numeric_check", - "target_key": "hjorth_mobility_mean", - "weight": 50, - "params": { - "gt_value": 0.5692, - "tolerance": 0.02846 - } - }, - { - "metric_id": "hjorth_complexity_accuracy", - "type": "numeric_check", - "target_key": "hjorth_complexity_mean", - "weight": 50, - "params": { - "gt_value": 2.190244, - "tolerance": 0.109512 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_01.json b/foundational_analysis/cases/case05/case05_01.json deleted file mode 100644 index 15c0676a1c218afc02055843048c0cb8cf581fc0..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_01.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_01.edf", - "instruction": "Please select only the central (C*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_c_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of central channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_c_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_c_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_c_accuracy", - "type": "numeric_check", - "target_key": "sef95_c_mean", - "weight": 50, - "params": { - "gt_value": 20.875, - "tolerance": 1.04375 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 14.0, - "tolerance": 0.7 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_02.json b/foundational_analysis/cases/case05/case05_02.json deleted file mode 100644 index f6c2618fe93f7e6e2f9b898a3c889bc0075cc683..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_02.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_02.edf", - "instruction": "Please select only the central (C*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_c_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of central channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_c_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_c_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_c_accuracy", - "type": "numeric_check", - "target_key": "sef95_c_mean", - "weight": 50, - "params": { - "gt_value": 18.25, - "tolerance": 0.9125 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 16.125, - "tolerance": 0.80625 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_03.json b/foundational_analysis/cases/case05/case05_03.json deleted file mode 100644 index 3e1c3055685047df033660a2ee1fddd0b42427ac..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_03.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_03.edf", - "instruction": "Please select only the central (C*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_c_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of central channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_c_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_c_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_c_accuracy", - "type": "numeric_check", - "target_key": "sef95_c_mean", - "weight": 50, - "params": { - "gt_value": 18.625, - "tolerance": 0.93125 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 17.375, - "tolerance": 0.86875 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_04.json b/foundational_analysis/cases/case05/case05_04.json deleted file mode 100644 index 460dae66842029b4b3b3d3a9734f0db6bae241d3..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_04.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_04.edf", - "instruction": "Please select only the central (C*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_c_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of central channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_c_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_c_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_c_accuracy", - "type": "numeric_check", - "target_key": "sef95_c_mean", - "weight": 50, - "params": { - "gt_value": 13.75, - "tolerance": 0.6875 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 17.25, - "tolerance": 0.8625 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_05.json b/foundational_analysis/cases/case05/case05_05.json deleted file mode 100644 index e61c7509e5af8b2ca3c48dbe9257566f77154237..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_05.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_05.edf", - "instruction": "Please select only the central (C*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_c_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of central channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_c_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_c_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_c_accuracy", - "type": "numeric_check", - "target_key": "sef95_c_mean", - "weight": 50, - "params": { - "gt_value": 21.5, - "tolerance": 1.075 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 25.25, - "tolerance": 1.2625 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_06.json b/foundational_analysis/cases/case05/case05_06.json deleted file mode 100644 index 9415ea25184ec9b16e9e0430d81d43fa7def007b..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_06.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_01.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 37.833333, - "tolerance": 1.891667 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 38.75, - "tolerance": 1.9375 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_07.json b/foundational_analysis/cases/case05/case05_07.json deleted file mode 100644 index a2a72d51e1b68ae1ffdd39d2718cdee77893ae91..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_07.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_02.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 37.972222, - "tolerance": 1.898611 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 37.833333, - "tolerance": 1.891667 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_08.json b/foundational_analysis/cases/case05/case05_08.json deleted file mode 100644 index f963459010e43ae2e660be839c6746b2e6512e37..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_08.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_03.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 37.0, - "tolerance": 1.85 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 37.5, - "tolerance": 1.875 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_09.json b/foundational_analysis/cases/case05/case05_09.json deleted file mode 100644 index 3b0503288a7e2a5ac1262449d95d986a5c9df034..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_09.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_04.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 37.583333, - "tolerance": 1.879167 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 38.083333, - "tolerance": 1.904167 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_10.json b/foundational_analysis/cases/case05/case05_10.json deleted file mode 100644 index ac1f836205f1a8fd5872ac27bd05f653701c8816..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_10.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_05.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 37.638889, - "tolerance": 1.881944 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 37.75, - "tolerance": 1.8875 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_11.json b/foundational_analysis/cases/case05/case05_11.json deleted file mode 100644 index 65a82fd95fe1fa6adcd81d9dc93cb589cb79c949..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_11.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-01.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-01.cnt", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 26.527778, - "tolerance": 1.326389 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 30.916667, - "tolerance": 1.545833 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_12.json b/foundational_analysis/cases/case05/case05_12.json deleted file mode 100644 index 600e2509da00b0c7a796b8227b1c27cc104c01ff..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_12.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-02.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-02.cnt", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 19.277778, - "tolerance": 0.963889 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 19.333333, - "tolerance": 0.966667 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_13.json b/foundational_analysis/cases/case05/case05_13.json deleted file mode 100644 index 6ff8830f0dd00bf4f890859043e08d3cd91a264d..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_13.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-03.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-03.cnt", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 26.277778, - "tolerance": 1.313889 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 32.5, - "tolerance": 1.625 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_14.json b/foundational_analysis/cases/case05/case05_14.json deleted file mode 100644 index 4474259a868d72faecfddec4ad5f368e2b9ed244..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_14.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-04.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-04.cnt", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 27.416667, - "tolerance": 1.370833 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 30.416667, - "tolerance": 1.520833 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_15.json b/foundational_analysis/cases/case05/case05_15.json deleted file mode 100644 index bfed5c81c1c6aca81248f6591b84775a36424870..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_15.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-05.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-05.cnt", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 17.555556, - "tolerance": 0.877778 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 19.583333, - "tolerance": 0.979167 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_16.json b/foundational_analysis/cases/case05/case05_16.json deleted file mode 100644 index 9b954ee7eb4e498ad932bf490a8427e32ec1eeb1..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_16.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_01.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 23.166667, - "tolerance": 1.158333 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 27.25, - "tolerance": 1.3625 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_17.json b/foundational_analysis/cases/case05/case05_17.json deleted file mode 100644 index 3521923da17039a1454481ff83c86a099e12393e..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_17.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_02.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 17.416667, - "tolerance": 0.870833 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 19.125, - "tolerance": 0.95625 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_18.json b/foundational_analysis/cases/case05/case05_18.json deleted file mode 100644 index 27e5623e09b1ae1fdf753b81e808c57ac6f07d47..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_18.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_03.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 18.583333, - "tolerance": 0.929167 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 18.375, - "tolerance": 0.91875 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_19.json b/foundational_analysis/cases/case05/case05_19.json deleted file mode 100644 index 9c94597775262d67f02ab03422df1bfebf95f32f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_19.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_04.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 23.0, - "tolerance": 1.15 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 24.25, - "tolerance": 1.2125 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_20.json b/foundational_analysis/cases/case05/case05_20.json deleted file mode 100644 index e04f8c2d0c728911d5a043dbf3d9f2549341af8e..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_20.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_05.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 18.166667, - "tolerance": 0.908333 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 17.25, - "tolerance": 0.8625 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_21.json b/foundational_analysis/cases/case05/case05_21.json deleted file mode 100644 index 6d063366f20ad6989c0794948b273524032f832a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_21.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_01.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 21.916667, - "tolerance": 1.095833 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 21.125, - "tolerance": 1.05625 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_22.json b/foundational_analysis/cases/case05/case05_22.json deleted file mode 100644 index 045cf97c73d2af307ecc9acd7023a1cd04333e82..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_22.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_02.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 19.0, - "tolerance": 0.95 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 18.75, - "tolerance": 0.9375 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_23.json b/foundational_analysis/cases/case05/case05_23.json deleted file mode 100644 index b6cdadb4fadf77ebb9b9fd9e6b834516b03a7885..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_23.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_03.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 18.333333, - "tolerance": 0.916667 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 19.625, - "tolerance": 0.98125 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_24.json b/foundational_analysis/cases/case05/case05_24.json deleted file mode 100644 index db9538d8bc5749ba4bd9e60840526c53a52ca803..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_24.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_04.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 17.5, - "tolerance": 0.875 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 17.875, - "tolerance": 0.89375 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case05/case05_25.json b/foundational_analysis/cases/case05/case05_25.json deleted file mode 100644 index 858f6957b74f6cc37e59b45cba3fb7d092662c8a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case05/case05_25.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_05.edf", - "instruction": "Please select only the parietal (P*) and occipital (O*) EEG channels from the raw signal. Apply a 0.5-40 Hz FIR bandpass filter, then a 60 Hz FIR notch filter, and resample to 200 Hz. Compute the SEF95 value for each selected channel over the full available signal, then report the region-mean values as sef95_p_mean and sef95_o_mean." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final values from the agent report:\n1) Mean SEF95 of parietal channels\n2) Mean SEF95 of occipital channels\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"sef95_p_mean\" and \"sef95_o_mean\".\n5. Both values must be FLOAT.\n6. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"sef95_p_mean\": , \"sef95_o_mean\": }", - "metrics": [ - { - "metric_id": "sef95_p_accuracy", - "type": "numeric_check", - "target_key": "sef95_p_mean", - "weight": 50, - "params": { - "gt_value": 18.25, - "tolerance": 0.9125 - } - }, - { - "metric_id": "sef95_o_accuracy", - "type": "numeric_check", - "target_key": "sef95_o_mean", - "weight": 50, - "params": { - "gt_value": 17.125, - "tolerance": 0.85625 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case06/case06_01.json b/foundational_analysis/cases/case06/case06_01.json deleted file mode 100644 index 9a3143caeafcd0ee7fc729a7f0cbc2095c60e89e..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_01.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_01.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "MEDIUM" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.134972, - "tolerance": 0.013497 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_02.json b/foundational_analysis/cases/case06/case06_02.json deleted file mode 100644 index 7813ced041018c7cb8d976e6a753ef2939c769e6..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_02.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_02.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "MEDIUM" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.199948, - "tolerance": 0.019995 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_03.json b/foundational_analysis/cases/case06/case06_03.json deleted file mode 100644 index 7f84ce7cd83e485955b9e401f4114b2debd6070c..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_03.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_03.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "MEDIUM" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.118846, - "tolerance": 0.011885 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_04.json b/foundational_analysis/cases/case06/case06_04.json deleted file mode 100644 index ec53e2debfa84622c22f2bad76b86adcb2e9ce14..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_04.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_04.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "MEDIUM" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.156256, - "tolerance": 0.015626 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_05.json b/foundational_analysis/cases/case06/case06_05.json deleted file mode 100644 index be321ddb3bc832d2636c925db36ce2a1bdf6b151..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_05.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_05.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "MEDIUM" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.171527, - "tolerance": 0.017153 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_06.json b/foundational_analysis/cases/case06/case06_06.json deleted file mode 100644 index dc9ae946a40268c462b1194bf12be60004789e24..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_06.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_01.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.000668, - "tolerance": 6.7e-05 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_07.json b/foundational_analysis/cases/case06/case06_07.json deleted file mode 100644 index 8f2d8634f0385d8dced06cf12d51593644a50475..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_07.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_02.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.000156, - "tolerance": 1.6e-05 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_08.json b/foundational_analysis/cases/case06/case06_08.json deleted file mode 100644 index f9e9b9c54f805d4a44c7b082c48f55bc250e4c6d..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_08.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_03.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.000908, - "tolerance": 9.1e-05 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_09.json b/foundational_analysis/cases/case06/case06_09.json deleted file mode 100644 index 78afe38a548696dc64f11c2663798957c5162a2c..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_09.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_04.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.000111, - "tolerance": 1.1e-05 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_10.json b/foundational_analysis/cases/case06/case06_10.json deleted file mode 100644 index b4c1266d83e13ff25ee69d9723b1906b519f58e4..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_10.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_05.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.000463, - "tolerance": 4.6e-05 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_11.json b/foundational_analysis/cases/case06/case06_11.json deleted file mode 100644 index a8fe02a0df82d73cebc95fa00c8a929641a91f5f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_11.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_01.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.032954, - "tolerance": 0.003295 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_12.json b/foundational_analysis/cases/case06/case06_12.json deleted file mode 100644 index cf5a8a193596f9317c1a0e0a1543a809504f2bdd..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_12.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_02.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.046012, - "tolerance": 0.004601 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_13.json b/foundational_analysis/cases/case06/case06_13.json deleted file mode 100644 index eebbb10abf471debd25c80136ed79dfd2d96610a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_13.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_03.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.004734, - "tolerance": 0.000473 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_14.json b/foundational_analysis/cases/case06/case06_14.json deleted file mode 100644 index c74e0f1ffaa88d41dde7d5b69186f2fe6cfb0501..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_14.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_04.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.003685, - "tolerance": 0.000369 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_15.json b/foundational_analysis/cases/case06/case06_15.json deleted file mode 100644 index 579660167191ac4794434a8a396c3e4e3e1b3b74..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_15.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_05.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.011306, - "tolerance": 0.001131 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_16.json b/foundational_analysis/cases/case06/case06_16.json deleted file mode 100644 index 6254540caa2b7c09018f755c1a6534e6a2574b19..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_16.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_01.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.010642, - "tolerance": 0.001064 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_17.json b/foundational_analysis/cases/case06/case06_17.json deleted file mode 100644 index 2c01b1955f992989ba3cc77007dc0be8bcbf7fca..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_17.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_02.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.054164, - "tolerance": 0.005416 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_18.json b/foundational_analysis/cases/case06/case06_18.json deleted file mode 100644 index f52d45bec11f83792345b025aad53962d3688459..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_18.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_03.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.047591, - "tolerance": 0.004759 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_19.json b/foundational_analysis/cases/case06/case06_19.json deleted file mode 100644 index 4018ba1d5234b4fc80b52f5c5e0450da876036b1..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_19.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_04.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.013472, - "tolerance": 0.001347 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case06/case06_20.json b/foundational_analysis/cases/case06/case06_20.json deleted file mode 100644 index 371c500e9313c26f066a196dd3d8009f10fa6611..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case06/case06_20.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_05.edf", - "instruction": "Please select only the real EEG channels from the raw signal (excluding non-EEG channels). Do not apply linear detrending. For each selected channel, obtain the power in the 0.1-0.5 Hz band and the total power in the 0.1-45 Hz band by integrating the PSD over frequency, then calculate the channel-wise baseline-drift power ratio. Average these channel-wise ratios to obtain the final ratio. Classify the baseline drift level as LOW, MEDIUM, or HIGH using these thresholds: LOW if ratio < 0.08, MEDIUM if 0.08 <= ratio < 0.25, and HIGH if ratio >= 0.25. Report both the final ratio value and the final level in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two final outputs from the agent report:\n1) Baseline-drift power ratio (0.1-0.5 Hz / 0.1-45 Hz)\n2) Baseline-drift level\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks (e.g., no backticks or json tags).\n3. DO NOT include any conversational text, explanations, or units.\n4. The keys in JSON must be EXACTLY \"drift_ratio\" and \"drift_level\".\n5. \"drift_ratio\" must be a FLOAT.\n6. \"drift_level\" must be one of \"LOW\", \"MEDIUM\", \"HIGH\".\n7. If one value is missing, return it as null.\n\n### OUTPUT TEMPLATE\n{\"drift_ratio\": , \"drift_level\": }", - "metrics": [ - { - "metric_id": "baseline_drift_level_accuracy", - "type": "categorical_check", - "target_key": "drift_level", - "weight": 100, - "params": { - "gt_value": "LOW" - } - }, - { - "metric_id": "baseline_drift_ratio_reference", - "type": "numeric_check", - "target_key": "drift_ratio", - "weight": 0, - "params": { - "gt_value": 0.055766, - "tolerance": 0.005577 - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case07/case07_01.json b/foundational_analysis/cases/case07/case07_01.json deleted file mode 100644 index 874caa4b177c74ebe784bac5fd0f1bca17997c42..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case07/case07_01.json +++ /dev/null @@ -1,50 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_01.edf", - "instruction": "Please determine which lead-distribution system this recording follows (10-20, 10-10 or 10-5), and then list all channels that do not belong to standard measurement electrodes of that system. Return the non-standard channels using their original channel names exactly as they appear in the data. If all channels belong to standard measurement electrodes, return an empty list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) lead system classification\n2) final list of channels that are not standard measurement electrodes of that system\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys in JSON must be EXACTLY \"lead_system\" and \"non_standard_channels\".\n5. \"lead_system\" must be exactly one of \"10-20\", \"10-10\", \"10-5\", or null.\n6. Extract the explicitly reported final non-standard-channel list, not the full channel inventory or the standard-channel list.\n7. Normalize each returned display name only to the benchmark naming contract: trim whitespace and remove one leading acquisition prefix EEG followed by a space, hyphen, or underscore.\n8. If a modality prefix is immediately duplicated, collapse it to one label; for example, \"ECG ECG\" becomes \"ECG\". Preserve the remaining spelling, case, punctuation, and reference identity exactly.\n9. Do NOT remove terminal reference parts and do NOT convert legacy aliases for this case. Required examples: \"EEG A2-A1\" -> \"A2-A1\"; \"EEG 23A-23R\" -> \"23A-23R\"; \"ECG ECG\" -> \"ECG\"; \"SaO2\" -> \"SaO2\".\n10. If the report explicitly says no non-standard channel exists, return an empty array []. If the final list is missing or unclear, set non_standard_channels to null.\n11. If lead_system is missing or unclear, set only lead_system to null; do not guess either value.\n\n### OUTPUT TEMPLATE\n{\"lead_system\": <\"10-20\"|\"10-10\"|\"10-5\"|null>, \"non_standard_channels\": }", - "metrics": [ - { - "metric_id": "lead_system_accuracy", - "type": "categorical_check", - "target_key": "lead_system", - "weight": 50, - "params": { - "gt_value": "10-20" - } - }, - { - "metric_id": "non_standard_channels_match", - "type": "set_match_check", - "target_key": "non_standard_channels", - "weight": 50, - "params": { - "gt_value": [ - "LOC-A2", - "ROC-A1", - "X1", - "X2", - "X3", - "X4", - "X5", - "X6", - "DC3", - "X7", - "X8", - "SaO2", - "DC8" - ], - "match_mode": "exact" - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case07/case07_02.json b/foundational_analysis/cases/case07/case07_02.json deleted file mode 100644 index e43b52b1f092871ebc15492603daa4bcf2bd125f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case07/case07_02.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_01.edf", - "instruction": "Please determine which lead-distribution system this recording follows (10-20, 10-10 or 10-5), and then list all channels that do not belong to standard measurement electrodes of that system. Return the non-standard channels using their original channel names exactly as they appear in the data. If all channels belong to standard measurement electrodes, return an empty list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) lead system classification\n2) final list of channels that are not standard measurement electrodes of that system\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys in JSON must be EXACTLY \"lead_system\" and \"non_standard_channels\".\n5. \"lead_system\" must be exactly one of \"10-20\", \"10-10\", \"10-5\", or null.\n6. Extract the explicitly reported final non-standard-channel list, not the full channel inventory or the standard-channel list.\n7. Normalize each returned display name only to the benchmark naming contract: trim whitespace and remove one leading acquisition prefix EEG followed by a space, hyphen, or underscore.\n8. If a modality prefix is immediately duplicated, collapse it to one label; for example, \"ECG ECG\" becomes \"ECG\". Preserve the remaining spelling, case, punctuation, and reference identity exactly.\n9. Do NOT remove terminal reference parts and do NOT convert legacy aliases for this case. Required examples: \"EEG A2-A1\" -> \"A2-A1\"; \"EEG 23A-23R\" -> \"23A-23R\"; \"ECG ECG\" -> \"ECG\"; \"SaO2\" -> \"SaO2\".\n10. If the report explicitly says no non-standard channel exists, return an empty array []. If the final list is missing or unclear, set non_standard_channels to null.\n11. If lead_system is missing or unclear, set only lead_system to null; do not guess either value.\n\n### OUTPUT TEMPLATE\n{\"lead_system\": <\"10-20\"|\"10-10\"|\"10-5\"|null>, \"non_standard_channels\": }", - "metrics": [ - { - "metric_id": "lead_system_accuracy", - "type": "categorical_check", - "target_key": "lead_system", - "weight": 50, - "params": { - "gt_value": "10-10" - } - }, - { - "metric_id": "non_standard_channels_match", - "type": "set_match_check", - "target_key": "non_standard_channels", - "weight": 50, - "params": { - "gt_value": [], - "match_mode": "exact" - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case07/case07_03.json b/foundational_analysis/cases/case07/case07_03.json deleted file mode 100644 index 4a9024ea28b51321b2005e1d68c3a484187b3066..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case07/case07_03.json +++ /dev/null @@ -1,43 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-01.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-01.cnt", - "instruction": "Please determine which lead-distribution system this recording follows (10-20, 10-10 or 10-5), and then list all channels that do not belong to standard measurement electrodes of that system. Return the non-standard channels using their original channel names exactly as they appear in the data. If all channels belong to standard measurement electrodes, return an empty list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) lead system classification\n2) final list of channels that are not standard measurement electrodes of that system\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys in JSON must be EXACTLY \"lead_system\" and \"non_standard_channels\".\n5. \"lead_system\" must be exactly one of \"10-20\", \"10-10\", \"10-5\", or null.\n6. Extract the explicitly reported final non-standard-channel list, not the full channel inventory or the standard-channel list.\n7. Normalize each returned display name only to the benchmark naming contract: trim whitespace and remove one leading acquisition prefix EEG followed by a space, hyphen, or underscore.\n8. If a modality prefix is immediately duplicated, collapse it to one label; for example, \"ECG ECG\" becomes \"ECG\". Preserve the remaining spelling, case, punctuation, and reference identity exactly.\n9. Do NOT remove terminal reference parts and do NOT convert legacy aliases for this case. Required examples: \"EEG A2-A1\" -> \"A2-A1\"; \"EEG 23A-23R\" -> \"23A-23R\"; \"ECG ECG\" -> \"ECG\"; \"SaO2\" -> \"SaO2\".\n10. If the report explicitly says no non-standard channel exists, return an empty array []. If the final list is missing or unclear, set non_standard_channels to null.\n11. If lead_system is missing or unclear, set only lead_system to null; do not guess either value.\n\n### OUTPUT TEMPLATE\n{\"lead_system\": <\"10-20\"|\"10-10\"|\"10-5\"|null>, \"non_standard_channels\": }", - "metrics": [ - { - "metric_id": "lead_system_accuracy", - "type": "categorical_check", - "target_key": "lead_system", - "weight": 50, - "params": { - "gt_value": "10-10" - } - }, - { - "metric_id": "non_standard_channels_match", - "type": "set_match_check", - "target_key": "non_standard_channels", - "weight": 50, - "params": { - "gt_value": [ - "M1", - "M2", - "CB1", - "CB2", - "VEO", - "HEO" - ], - "match_mode": "exact" - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case07/case07_04.json b/foundational_analysis/cases/case07/case07_04.json deleted file mode 100644 index 85210fbd290a07c3894d468348c92b461d7dd173..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case07/case07_04.json +++ /dev/null @@ -1,40 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_01.edf", - "instruction": "Please determine which lead-distribution system this recording follows (10-20, 10-10 or 10-5), and then list all channels that do not belong to standard measurement electrodes of that system. Return the non-standard channels using their original channel names exactly as they appear in the data. If all channels belong to standard measurement electrodes, return an empty list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) lead system classification\n2) final list of channels that are not standard measurement electrodes of that system\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys in JSON must be EXACTLY \"lead_system\" and \"non_standard_channels\".\n5. \"lead_system\" must be exactly one of \"10-20\", \"10-10\", \"10-5\", or null.\n6. Extract the explicitly reported final non-standard-channel list, not the full channel inventory or the standard-channel list.\n7. Normalize each returned display name only to the benchmark naming contract: trim whitespace and remove one leading acquisition prefix EEG followed by a space, hyphen, or underscore.\n8. If a modality prefix is immediately duplicated, collapse it to one label; for example, \"ECG ECG\" becomes \"ECG\". Preserve the remaining spelling, case, punctuation, and reference identity exactly.\n9. Do NOT remove terminal reference parts and do NOT convert legacy aliases for this case. Required examples: \"EEG A2-A1\" -> \"A2-A1\"; \"EEG 23A-23R\" -> \"23A-23R\"; \"ECG ECG\" -> \"ECG\"; \"SaO2\" -> \"SaO2\".\n10. If the report explicitly says no non-standard channel exists, return an empty array []. If the final list is missing or unclear, set non_standard_channels to null.\n11. If lead_system is missing or unclear, set only lead_system to null; do not guess either value.\n\n### OUTPUT TEMPLATE\n{\"lead_system\": <\"10-20\"|\"10-10\"|\"10-5\"|null>, \"non_standard_channels\": }", - "metrics": [ - { - "metric_id": "lead_system_accuracy", - "type": "categorical_check", - "target_key": "lead_system", - "weight": 50, - "params": { - "gt_value": "10-20" - } - }, - { - "metric_id": "non_standard_channels_match", - "type": "set_match_check", - "target_key": "non_standard_channels", - "weight": 50, - "params": { - "gt_value": [ - "A2-A1", - "23A-23R", - "24A-24R" - ], - "match_mode": "exact" - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case07/case07_05.json b/foundational_analysis/cases/case07/case07_05.json deleted file mode 100644 index e3dff11abfb0d8199d2804879629a6f5ca95d362..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case07/case07_05.json +++ /dev/null @@ -1,39 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_01.edf", - "instruction": "Please determine which lead-distribution system this recording follows (10-20, 10-10 or 10-5), and then list all channels that do not belong to standard measurement electrodes of that system. Return the non-standard channels using their original channel names exactly as they appear in the data. If all channels belong to standard measurement electrodes, return an empty list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) lead system classification\n2) final list of channels that are not standard measurement electrodes of that system\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys in JSON must be EXACTLY \"lead_system\" and \"non_standard_channels\".\n5. \"lead_system\" must be exactly one of \"10-20\", \"10-10\", \"10-5\", or null.\n6. Extract the explicitly reported final non-standard-channel list, not the full channel inventory or the standard-channel list.\n7. Normalize each returned display name only to the benchmark naming contract: trim whitespace and remove one leading acquisition prefix EEG followed by a space, hyphen, or underscore.\n8. If a modality prefix is immediately duplicated, collapse it to one label; for example, \"ECG ECG\" becomes \"ECG\". Preserve the remaining spelling, case, punctuation, and reference identity exactly.\n9. Do NOT remove terminal reference parts and do NOT convert legacy aliases for this case. Required examples: \"EEG A2-A1\" -> \"A2-A1\"; \"EEG 23A-23R\" -> \"23A-23R\"; \"ECG ECG\" -> \"ECG\"; \"SaO2\" -> \"SaO2\".\n10. If the report explicitly says no non-standard channel exists, return an empty array []. If the final list is missing or unclear, set non_standard_channels to null.\n11. If lead_system is missing or unclear, set only lead_system to null; do not guess either value.\n\n### OUTPUT TEMPLATE\n{\"lead_system\": <\"10-20\"|\"10-10\"|\"10-5\"|null>, \"non_standard_channels\": }", - "metrics": [ - { - "metric_id": "lead_system_accuracy", - "type": "categorical_check", - "target_key": "lead_system", - "weight": 50, - "params": { - "gt_value": "10-20" - } - }, - { - "metric_id": "non_standard_channels_match", - "type": "set_match_check", - "target_key": "non_standard_channels", - "weight": 50, - "params": { - "gt_value": [ - "A2-A1", - "ECG" - ], - "match_mode": "exact" - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case08/case08_01.json b/foundational_analysis/cases/case08/case08_01.json deleted file mode 100644 index f334abfff54b581b2752009a281ea06779d13dcc..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case08/case08_01.json +++ /dev/null @@ -1,26 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_01.edf", - "instruction": "Please judge whether this EEG recording is suitable for spectral asymmetry analysis (left-vs-right spectral asymmetry). Your final answer must be exactly one word: \"Yes\" or \"No\"." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final suitability decision for spectral asymmetry analysis.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The key in JSON must be EXACTLY \"asymmetry_suitable\".\n5. The value must be exactly \"Yes\" or \"No\".\n6. If missing or unclear, return {\"asymmetry_suitable\": null}.\n\n### OUTPUT TEMPLATE\n{\"asymmetry_suitable\": <\"Yes\"|\"No\"|null>}", - "metrics": [ - { - "metric_id": "asymmetry_suitability_accuracy", - "type": "categorical_check", - "target_key": "asymmetry_suitable", - "weight": 100, - "params": { - "gt_value": "Yes" - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case08/case08_02.json b/foundational_analysis/cases/case08/case08_02.json deleted file mode 100644 index 638a9aea4f077f6ef2a066204a1950bb4d01361f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case08/case08_02.json +++ /dev/null @@ -1,26 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_01.edf", - "instruction": "Please judge whether this EEG recording is suitable for spectral asymmetry analysis (left-vs-right spectral asymmetry). Your final answer must be exactly one word: \"Yes\" or \"No\"." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final suitability decision for spectral asymmetry analysis.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The key in JSON must be EXACTLY \"asymmetry_suitable\".\n5. The value must be exactly \"Yes\" or \"No\".\n6. If missing or unclear, return {\"asymmetry_suitable\": null}.\n\n### OUTPUT TEMPLATE\n{\"asymmetry_suitable\": <\"Yes\"|\"No\"|null>}", - "metrics": [ - { - "metric_id": "asymmetry_suitability_accuracy", - "type": "categorical_check", - "target_key": "asymmetry_suitable", - "weight": 100, - "params": { - "gt_value": "Yes" - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case08/case08_03.json b/foundational_analysis/cases/case08/case08_03.json deleted file mode 100644 index e9c05908128b1b726ac772502f18e1ab822e4f6c..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case08/case08_03.json +++ /dev/null @@ -1,26 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-01.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-01.cnt", - "instruction": "Please judge whether this EEG recording is suitable for spectral asymmetry analysis (left-vs-right spectral asymmetry). Your final answer must be exactly one word: \"Yes\" or \"No\"." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final suitability decision for spectral asymmetry analysis.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The key in JSON must be EXACTLY \"asymmetry_suitable\".\n5. The value must be exactly \"Yes\" or \"No\".\n6. If missing or unclear, return {\"asymmetry_suitable\": null}.\n\n### OUTPUT TEMPLATE\n{\"asymmetry_suitable\": <\"Yes\"|\"No\"|null>}", - "metrics": [ - { - "metric_id": "asymmetry_suitability_accuracy", - "type": "categorical_check", - "target_key": "asymmetry_suitable", - "weight": 100, - "params": { - "gt_value": "Yes" - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case08/case08_04.json b/foundational_analysis/cases/case08/case08_04.json deleted file mode 100644 index 1bf92f291d83c4143b4ef088f15a5865d06ed5da..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case08/case08_04.json +++ /dev/null @@ -1,26 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_01.edf", - "instruction": "Please judge whether this EEG recording is suitable for spectral asymmetry analysis (left-vs-right spectral asymmetry). Your final answer must be exactly one word: \"Yes\" or \"No\"." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final suitability decision for spectral asymmetry analysis.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The key in JSON must be EXACTLY \"asymmetry_suitable\".\n5. The value must be exactly \"Yes\" or \"No\".\n6. If missing or unclear, return {\"asymmetry_suitable\": null}.\n\n### OUTPUT TEMPLATE\n{\"asymmetry_suitable\": <\"Yes\"|\"No\"|null>}", - "metrics": [ - { - "metric_id": "asymmetry_suitability_accuracy", - "type": "categorical_check", - "target_key": "asymmetry_suitable", - "weight": 100, - "params": { - "gt_value": "Yes" - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case08/case08_05.json b/foundational_analysis/cases/case08/case08_05.json deleted file mode 100644 index 86d7a47cf49bc153f297f229e809d6b162ed3c4b..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case08/case08_05.json +++ /dev/null @@ -1,26 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.0, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_01.edf", - "instruction": "Please judge whether this EEG recording is suitable for spectral asymmetry analysis (left-vs-right spectral asymmetry). Your final answer must be exactly one word: \"Yes\" or \"No\"." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final suitability decision for spectral asymmetry analysis.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The key in JSON must be EXACTLY \"asymmetry_suitable\".\n5. The value must be exactly \"Yes\" or \"No\".\n6. If missing or unclear, return {\"asymmetry_suitable\": null}.\n\n### OUTPUT TEMPLATE\n{\"asymmetry_suitable\": <\"Yes\"|\"No\"|null>}", - "metrics": [ - { - "metric_id": "asymmetry_suitability_accuracy", - "type": "categorical_check", - "target_key": "asymmetry_suitable", - "weight": 100, - "params": { - "gt_value": "Yes" - } - } - ] - } -} \ No newline at end of file diff --git a/foundational_analysis/cases/case09/case09_01.json b/foundational_analysis/cases/case09/case09_01.json deleted file mode 100644 index f3422b45120b1709264b492786a86aa826ff733a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_01.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_01.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "C4-F4", - "F3-F4", - "C4-O2" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_02.json b/foundational_analysis/cases/case09/case09_02.json deleted file mode 100644 index 569698d827b23a0c9555f6a21c2cdb1b4ac262e2..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_02.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_02.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "C4-F4", - "C3-F3", - "F3-F4" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_03.json b/foundational_analysis/cases/case09/case09_03.json deleted file mode 100644 index 8b3b05551c92dc07d1eed690199c58e17c61cbd4..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_03.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_03.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "C3-F3", - "C4-F4", - "F3-F4" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_04.json b/foundational_analysis/cases/case09/case09_04.json deleted file mode 100644 index a44b17ad1c57bf60aff72b811b7e76f5ef5c947c..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_04.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_04.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "C3-F3", - "C4-F4", - "F3-F4" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_05.json b/foundational_analysis/cases/case09/case09_05.json deleted file mode 100644 index e7e9503eb9704c9d1cb8b82cae058459b887a9c6..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_05.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/core/ISRUC_05.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "C3-F3", - "C4-F4", - "C4-O2" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_06.json b/foundational_analysis/cases/case09/case09_06.json deleted file mode 100644 index 4bdbe78216afd2443c05d4756170b27d85192ee4..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_06.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_01.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "P3-P5", - "CPZ-PZ", - "P6-PO4" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_07.json b/foundational_analysis/cases/case09/case09_07.json deleted file mode 100644 index 78f20809c729c41f2507ded265a65d73d3e502c2..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_07.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_02.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "F5-F7", - "AF4-F4", - "CP6-P8" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_08.json b/foundational_analysis/cases/case09/case09_08.json deleted file mode 100644 index 020d99ad17e6b23e10dab9313877edc73966c695..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_08.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_03.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "AF7-F5", - "F5-F7", - "AF7-F7" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_09.json b/foundational_analysis/cases/case09/case09_09.json deleted file mode 100644 index c2a888c4479a6b939701b1639bde44f7133fcbf0..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_09.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_04.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "F7-FT7", - "F4-F6", - "P4-P6" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_10.json b/foundational_analysis/cases/case09/case09_10.json deleted file mode 100644 index 80e3420540845d1480678a750b771373c2e44673..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_10.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "BCIC2020-3_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "BCIC2020-3" - }, - "agent_input": { - "data_path": "data/core/BCIC2020-3_05.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "P3-P5", - "P1-P3", - "P4-PO8" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_11.json b/foundational_analysis/cases/case09/case09_11.json deleted file mode 100644 index 5657c4d31b86148fbbcc601c04e10499b84fe112..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_11.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-01.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-01.cnt", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "AF3-FP1", - "AF4-FP2", - "FP2-FPZ" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_12.json b/foundational_analysis/cases/case09/case09_12.json deleted file mode 100644 index fb0d92de2876045bdd718de2249eec45f3e508bb..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_12.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-02.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-02.cnt", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "PO3-PO5", - "P8-PO8", - "CB1-O1" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_13.json b/foundational_analysis/cases/case09/case09_13.json deleted file mode 100644 index d5b3cced2298aa1187bb1d54e011f0394ff933d2..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_13.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-03.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-03.cnt", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "PO4-PO6", - "FP2-FPZ", - "P4-P6" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_14.json b/foundational_analysis/cases/case09/case09_14.json deleted file mode 100644 index 4681ed4c31f324fde3dafd130d69a86cc8137a15..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_14.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-04.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-04.cnt", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "O2-PO4", - "PO6-PO8", - "P4-P6" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_15.json b/foundational_analysis/cases/case09/case09_15.json deleted file mode 100644 index d04d07c7e39f7189d7eade9e15dfe095c5c45e22..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_15.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "SEED-V-05.cnt", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "SEED-V" - }, - "agent_input": { - "data_path": "data/core/SEED-V-05.cnt", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "P4-P6", - "AF3-FP1", - "FP2-FPZ" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_16.json b/foundational_analysis/cases/case09/case09_16.json deleted file mode 100644 index a6c3a56421e64df7652f616f369dd490c9d65b46..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_16.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_01.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "FP1-FP2", - "F4-FZ", - "F3-FZ" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_17.json b/foundational_analysis/cases/case09/case09_17.json deleted file mode 100644 index 6d8c164665062996bcf1325b5a8a517c26fd706d..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_17.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_02.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "P3-P7", - "T7-T8", - "F3-FP1" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_18.json b/foundational_analysis/cases/case09/case09_18.json deleted file mode 100644 index 8e6c4ebcc3fa37a266f1059c52955f2a84962d8f..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_18.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_03.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "F4-FZ", - "F3-FZ", - "FP1-FP2" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_19.json b/foundational_analysis/cases/case09/case09_19.json deleted file mode 100644 index 448926e9d1bd8b0ad6ce60f4ed85636fe2588265..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_19.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_04.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "FP1-FZ", - "P4-P8", - "P3-P7" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_20.json b/foundational_analysis/cases/case09/case09_20.json deleted file mode 100644 index 753528b2953f7ce45221e5e88dab9c65c32f46f6..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_20.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "Mumtaz2016_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "Mumtaz2016" - }, - "agent_input": { - "data_path": "data/core/Mumtaz2016_05.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "P3-P7", - "O1-P7", - "C4-CZ" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_21.json b/foundational_analysis/cases/case09/case09_21.json deleted file mode 100644 index 34d8fbf3aa15b219be43bd93284283248bd92843..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_21.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_01.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_01.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "F4-FZ", - "FP1-FP2", - "F3-FP1" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_22.json b/foundational_analysis/cases/case09/case09_22.json deleted file mode 100644 index eaedb65e09e37c165b3720012bef8e9b071c2242..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_22.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_02.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_02.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "F7-FP1", - "FP1-FP2", - "F3-FZ" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_23.json b/foundational_analysis/cases/case09/case09_23.json deleted file mode 100644 index 6aa27763cf2d1f4579fbd0ff866856af5f0d4ca5..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_23.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_03.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_03.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "P3-PZ", - "C4-CZ", - "C3-CZ" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_24.json b/foundational_analysis/cases/case09/case09_24.json deleted file mode 100644 index 83bfc2e7ed9486a9a371445f9a72143c005211ee..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_24.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_04.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_04.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "F3-FZ", - "F4-FZ", - "O2-P4" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/foundational_analysis/cases/case09/case09_25.json b/foundational_analysis/cases/case09/case09_25.json deleted file mode 100644 index efdea2e644100932b716de45454cd366729e581a..0000000000000000000000000000000000000000 --- a/foundational_analysis/cases/case09/case09_25.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "meta_info": { - "case_id": "MentalArithmetic_05.edf", - "bench_subset": "NeuroBench-Core", - "difficult": 1.5, - "original_dataset": "MentalArithmetic" - }, - "agent_input": { - "data_path": "data/core/MentalArithmetic_05.edf", - "instruction": "Please select EEG channels from the raw signal, apply a 0.5-40Hz FIR bandpass filter, compute pairwise Pearson correlation coefficients between EEG channels, and then return the top 3 channel pairs sorted by coefficient from highest to lowest. Report only channel pairs in descending order." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for neurophysiological data. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the final Top-3 channel-pair sequence ranked by Pearson correlation coefficient from high to low.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include any conversational text or explanations.\n4. The key in JSON must be EXACTLY \"top3_pairs\".\n5. The value of \"top3_pairs\" must be an array of exactly 3 strings.\n6. Normalize EACH reported pair independently. First identify the two complete source channel labels; a referenced label such as F4-A1 is one complete channel label, and its hyphen must not be treated as the pair separator.\n7. For each source channel separately, uppercase it and remove one terminal reference suffix if present: -A1, -A2, -LE, -REF, -M1, -M2, or -AVG. Never output a reference electrode (A1/A2/LE/REF/M1/M2/AVG) as a pair member.\n8. Convert legacy aliases after removing the reference suffix: T3->T7, T4->T8, T5->P7, T6->P8.\n9. Sort the two normalized channel labels in ascending lexicographic order, then join them with exactly one hyphen using format \"CH1-CH2\" (uppercase, no spaces). If the report already uses a canonical pair such as F4-C4, normalize it to C4-F4. Each final label may contain only uppercase A-Z letters and digits; mixed-case forms such as Fp1 or Fp2 are forbidden and must become FP1 or FP2.\n10. Required examples: \"F4-A1 and C4-A1\" -> \"C4-F4\"; \"F4-C4\" -> \"C4-F4\"; \"T4-A1 and T3-A2\" -> \"T7-T8\"; \"Fp2 and Fp1\" -> \"FP1-FP2\".\n11. Preserve the three pairs in descending correlation order as reported. Do not sort the three-element array lexicographically.\n12. If any pair cannot be resolved into exactly two non-reference channels, return {\"top3_pairs\": null}; do not guess.\n\n### OUTPUT TEMPLATE\n{\"top3_pairs\": [\"CH1-CH2\", \"CH3-CH4\", \"CH5-CH6\"]}", - "metrics": [ - { - "metric_id": "top3_corr_pairs_sequence", - "type": "sequence_match_check", - "target_key": "top3_pairs", - "weight": 100, - "params": { - "gt_value": [ - "F8-FP2", - "F7-FP1", - "F3-FP1" - ], - "match_mode": "exact_order", - "top_k": 3 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_01.json b/sleep_assessment/cases/case01/case01_01.json deleted file mode 100644 index 856c183d8a167f648bbcbdb9e7c1b99b607acbf2..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_01.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/ISRUC_01.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 5.5, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_02.json b/sleep_assessment/cases/case01/case01_02.json deleted file mode 100644 index 551aa4180a58609764e0fe9653a8b20c3f911a8d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_02.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/ISRUC_02.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 55.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_03.json b/sleep_assessment/cases/case01/case01_03.json deleted file mode 100644 index 31701d7d40f4be49f88af9141b7b94eab4195bc5..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_03.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/ISRUC_03.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 3.5, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_04.json b/sleep_assessment/cases/case01/case01_04.json deleted file mode 100644 index 29aa3f6515b3e377c17e6647a369f64e6ce9475f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_04.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/ISRUC_04.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 1.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_05.json b/sleep_assessment/cases/case01/case01_05.json deleted file mode 100644 index d77500a4e69e7acf2c0d9995972d5ea4fc3b8458..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_05.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/ISRUC_05.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 75.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_06.json b/sleep_assessment/cases/case01/case01_06.json deleted file mode 100644 index af6e9a26287715c29787f5a3c56f8742ff1642ed..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_06.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/HMC_01.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 4.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_07.json b/sleep_assessment/cases/case01/case01_07.json deleted file mode 100644 index f118ded3d54196df439a1c314d6c83ab42e0f9df..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_07.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/HMC_02.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 3.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_08.json b/sleep_assessment/cases/case01/case01_08.json deleted file mode 100644 index 11b3292f117ef35620028d0944fedba60f6024ae..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_08.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/HMC_03.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 1.5, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_09.json b/sleep_assessment/cases/case01/case01_09.json deleted file mode 100644 index 30dfc6dbd3346fd16caa203f62f7dcff1f941f99..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_09.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/HMC_04.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 3.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_10.json b/sleep_assessment/cases/case01/case01_10.json deleted file mode 100644 index bdaca0ec5a138f750040457d96afa6f68bfdd44c..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_10.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/HMC_05.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 22.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_11.json b/sleep_assessment/cases/case01/case01_11.json deleted file mode 100644 index a72386ed162819b9ea58d5fd15c0c363837d4b6f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_11.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/SHHS1_01.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 14.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_12.json b/sleep_assessment/cases/case01/case01_12.json deleted file mode 100644 index a4f57e20ac397906a8b668055ea2339bc29d1743..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_12.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/SHHS1_02.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 0.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_13.json b/sleep_assessment/cases/case01/case01_13.json deleted file mode 100644 index 099c3452496c2ba86ba8aa249e19fb049373e509..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_13.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/SHHS1_03.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 83.5, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_14.json b/sleep_assessment/cases/case01/case01_14.json deleted file mode 100644 index e9e52dbfb67f74f9073632a0994b00b9aa3ef7cc..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_14.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/SHHS1_04.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 41.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_15.json b/sleep_assessment/cases/case01/case01_15.json deleted file mode 100644 index d5c91122d07c521a0530d4112a360e2791b91c83..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_15.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/SHHS1_05.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 10.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_16.json b/sleep_assessment/cases/case01/case01_16.json deleted file mode 100644 index 442ab0c15c811b5bbd8a75d556b53d1c9c5bb247..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_16.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/MASSSS3_01.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 3.5, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_17.json b/sleep_assessment/cases/case01/case01_17.json deleted file mode 100644 index f758c7471e724d71fc66d9457afde45399dbd27f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_17.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/MASSSS3_02.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 21.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_18.json b/sleep_assessment/cases/case01/case01_18.json deleted file mode 100644 index 647b67fdfd0c53f080eb1ecd9afb1ebf64138818..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_18.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/MASSSS3_03.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 7.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_19.json b/sleep_assessment/cases/case01/case01_19.json deleted file mode 100644 index df74312d3659193edc99990903b0d5aa0e4de81d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_19.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/MASSSS3_04.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 2.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_20.json b/sleep_assessment/cases/case01/case01_20.json deleted file mode 100644 index 67ab17e447a33f00346166f61f7476c9ade492f3..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_20.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/MASSSS3_05.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 7.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_21.json b/sleep_assessment/cases/case01/case01_21.json deleted file mode 100644 index e1cd3431b7f3749c7673ada0f4105d8f27f9a15c..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_21.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/Physionet2018_01.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 4.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_22.json b/sleep_assessment/cases/case01/case01_22.json deleted file mode 100644 index 507c040797260415ce3a91f64a26ff5718e3afea..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_22.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/Physionet2018_02.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 10.5, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_23.json b/sleep_assessment/cases/case01/case01_23.json deleted file mode 100644 index e9f3c90211d7dcafab0eb7588085a115324b01c3..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_23.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/Physionet2018_03.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 4.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_24.json b/sleep_assessment/cases/case01/case01_24.json deleted file mode 100644 index 66c036c7472a64580859297774f77d570dedcc74..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_24.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/Physionet2018_04.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 0.5, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case01/case01_25.json b/sleep_assessment/cases/case01/case01_25.json deleted file mode 100644 index 124296a400b0b16b8848bd54f4c2c21704b894fb..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case01/case01_25.json +++ /dev/null @@ -1,27 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "instruction": "Please use the provided sleep-stage label file to calculate the Sleep Onset Latency (SOL) for the provided sleep EEG/PSG recording. SOL is defined as the time in minutes from the first scored 30-second epoch to the first sleep epoch (N1, N2, N3, or REM). Please clearly state the final SOL value in minutes in your response.", - "label_path": "data/sleep/Physionet2018_05.npy" - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the Sleep Onset Latency (SOL) value in minutes from the agent's report. SOL is defined in this benchmark as the time from the first scored 30-second epoch to the first sleep epoch.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key in the JSON must be EXACTLY \"sleep_onset_latency_min\".\n5. The value must be a FLOAT in minutes.\n6. If the value is missing or cannot be found, return {\"sleep_onset_latency_min\": null}.\n\n### OUTPUT TEMPLATE\n{\"sleep_onset_latency_min\": }", - "metrics": [ - { - "metric_id": "sleep_onset_latency_accuracy", - "type": "numeric_check", - "target_key": "sleep_onset_latency_min", - "weight": 100, - "params": { - "gt_value": 1.0, - "tolerance": 2.0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_01.json b/sleep_assessment/cases/case02/case02_01.json deleted file mode 100644 index 089b69cb9e979a552d32606fc1f13a198b86c6f5..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_01.json +++ /dev/null @@ -1,44 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/sleep/ISRUC_01.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 19, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "F3-A2", - "C3-A2", - "O1-A2", - "F4-A1", - "C4-A1", - "O2-A1" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_02.json b/sleep_assessment/cases/case02/case02_02.json deleted file mode 100644 index 50e05304ebf2e686cdaa1835c2a829ce2fbd1172..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_02.json +++ /dev/null @@ -1,44 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/sleep/ISRUC_02.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 19, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "F3-A2", - "C3-A2", - "O1-A2", - "F4-A1", - "C4-A1", - "O2-A1" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_03.json b/sleep_assessment/cases/case02/case02_03.json deleted file mode 100644 index e39db6d9606a333646c2ff980b544064eac8ae99..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_03.json +++ /dev/null @@ -1,44 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "data_path": "data/sleep/ISRUC_03.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 19, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "F3-A2", - "C3-A2", - "O1-A2", - "F4-A1", - "C4-A1", - "O2-A1" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_04.json b/sleep_assessment/cases/case02/case02_04.json deleted file mode 100644 index 405f399610e52fe8738cbd15c52cb9767b0fa5d6..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_04.json +++ /dev/null @@ -1,42 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "data_path": "data/sleep/HMC_01.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 8, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "EEG F4-M1", - "EEG C4-M1", - "EEG O2-M1", - "EEG C3-M2" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_05.json b/sleep_assessment/cases/case02/case02_05.json deleted file mode 100644 index 107feb18f89abc8743790b233d0d8f8b4e9ab2c4..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_05.json +++ /dev/null @@ -1,42 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "data_path": "data/sleep/HMC_02.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 8, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "EEG F4-M1", - "EEG C4-M1", - "EEG O2-M1", - "EEG C3-M2" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_06.json b/sleep_assessment/cases/case02/case02_06.json deleted file mode 100644 index b28cf34a76adaeb467ca06e8e686b3d27e862986..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_06.json +++ /dev/null @@ -1,42 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "data_path": "data/sleep/HMC_03.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 8, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "EEG F4-M1", - "EEG C4-M1", - "EEG O2-M1", - "EEG C3-M2" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_07.json b/sleep_assessment/cases/case02/case02_07.json deleted file mode 100644 index 48694927a80fe89b227a4e3afc3c3ec276ea3a98..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_07.json +++ /dev/null @@ -1,40 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "data_path": "data/sleep/SHHS1_01.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 14, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "EEG(sec)", - "EEG" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_08.json b/sleep_assessment/cases/case02/case02_08.json deleted file mode 100644 index 9c728acbdc4a842016487b97444bce028561ca80..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_08.json +++ /dev/null @@ -1,40 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "data_path": "data/sleep/SHHS1_02.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 14, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "EEG(sec)", - "EEG" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_09.json b/sleep_assessment/cases/case02/case02_09.json deleted file mode 100644 index 8d70cc6b07a509ca4d7264d8fdd57ec2021511db..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_09.json +++ /dev/null @@ -1,40 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "data_path": "data/sleep/SHHS1_03.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 14, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "EEG(sec)", - "EEG" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_10.json b/sleep_assessment/cases/case02/case02_10.json deleted file mode 100644 index 590819106e05397d56f17c237399f9faaa34a027..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_10.json +++ /dev/null @@ -1,58 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "data_path": "data/sleep/MASSSS3_01.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 27, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "EEG Fp1-LER", - "EEG Fp2-LER", - "EEG F7-LER", - "EEG F8-LER", - "EEG F3-LER", - "EEG F4-LER", - "EEG T3-LER", - "EEG T4-LER", - "EEG C3-LER", - "EEG C4-LER", - "EEG T5-LER", - "EEG T6-LER", - "EEG P3-LER", - "EEG P4-LER", - "EEG O1-LER", - "EEG O2-LER", - "EEG Fz-LER", - "EEG Cz-LER", - "EEG Pz-LER", - "EEG Oz-LER" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_11.json b/sleep_assessment/cases/case02/case02_11.json deleted file mode 100644 index 9231bbe0cc5344b0afd39f401db752ddf1cd7077..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_11.json +++ /dev/null @@ -1,58 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "data_path": "data/sleep/MASSSS3_02.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 27, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "EEG Fp1-LER", - "EEG Fp2-LER", - "EEG F7-LER", - "EEG F8-LER", - "EEG F3-LER", - "EEG F4-LER", - "EEG T3-LER", - "EEG T4-LER", - "EEG C3-LER", - "EEG C4-LER", - "EEG T5-LER", - "EEG T6-LER", - "EEG P3-LER", - "EEG P4-LER", - "EEG O1-LER", - "EEG O2-LER", - "EEG Fz-LER", - "EEG Cz-LER", - "EEG Pz-LER", - "EEG Oz-LER" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_12.json b/sleep_assessment/cases/case02/case02_12.json deleted file mode 100644 index b34c2c889557f9c91565f7b3c365a38d51796dc1..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_12.json +++ /dev/null @@ -1,58 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "data_path": "data/sleep/MASSSS3_03.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 27, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "EEG Fp1-LER", - "EEG Fp2-LER", - "EEG F7-LER", - "EEG F8-LER", - "EEG F3-LER", - "EEG F4-LER", - "EEG T3-LER", - "EEG T4-LER", - "EEG C3-LER", - "EEG C4-LER", - "EEG T5-LER", - "EEG T6-LER", - "EEG P3-LER", - "EEG P4-LER", - "EEG O1-LER", - "EEG O2-LER", - "EEG Fz-LER", - "EEG Cz-LER", - "EEG Pz-LER", - "EEG Oz-LER" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_13.json b/sleep_assessment/cases/case02/case02_13.json deleted file mode 100644 index 0aee35f9954abcc0f68fb49182dd1b9a47875d5d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_13.json +++ /dev/null @@ -1,44 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "data_path": "data/sleep/Physionet2018_01.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 13, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "F3-M2", - "F4-M1", - "C3-M2", - "C4-M1", - "O1-M2", - "O2-M1" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_14.json b/sleep_assessment/cases/case02/case02_14.json deleted file mode 100644 index cf1009b5f78313510f2226924251ea81e9cda991..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_14.json +++ /dev/null @@ -1,44 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "data_path": "data/sleep/Physionet2018_02.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 13, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "F3-M2", - "F4-M1", - "C3-M2", - "C4-M1", - "O1-M2", - "O2-M1" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case02/case02_15.json b/sleep_assessment/cases/case02/case02_15.json deleted file mode 100644 index 3c1c503132eb2cff1271dab40074e773c4f28f3a..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case02/case02_15.json +++ /dev/null @@ -1,44 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "data_path": "data/sleep/Physionet2018_03.edf", - "instruction": "Please inspect the provided raw sleep EEG/PSG file. Report the total number of channels in the file, and list all EEG channels that can be used for sleep analysis. Use the original channel names exactly as they appear in the raw file. Do not include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or other auxiliary channels in the EEG channel list." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep EEG/PSG reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two outputs from the agent report:\n1) the total number of channels in the raw file\n2) the list of all EEG channels using original raw-file channel names\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text or explanations.\n4. The keys must be EXACTLY \"channel_count\" and \"eeg_channels\".\n5. \"channel_count\" must be an INTEGER or null.\n6. \"eeg_channels\" must be a JSON array of strings or null.\n7. Preserve original EEG channel names exactly as written in the raw file.\n8. Do NOT normalize references, casing, spacing, parentheses, hyphens, or symbols.\n9. Do NOT include EOG, EMG, ECG, respiratory, SpO2/SaO2, light, position, or auxiliary channels in \"eeg_channels\".\n10. For SHHS1 reports, only \"EEG(sec)\" and \"EEG\" count as EEG channels; \"THOR RES\", \"POSITION\", and \"OX stat\" are not EEG channels.\n11. Remove duplicate EEG channel names if the report repeats them.\n12. If one value is missing or unclear, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"channel_count\": , \"eeg_channels\": }", - "metrics": [ - { - "metric_id": "channel_count_accuracy", - "type": "numeric_check", - "target_key": "channel_count", - "weight": 30, - "params": { - "gt_value": 13, - "tolerance": 0.1 - } - }, - { - "metric_id": "eeg_channel_set_match", - "type": "set_match_check", - "target_key": "eeg_channels", - "weight": 70, - "params": { - "gt_value": [ - "F3-M2", - "F4-M1", - "C3-M2", - "C4-M1", - "O1-M2", - "O2-M1" - ], - "match_mode": "exact" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_01.json b/sleep_assessment/cases/case03/case03_01.json deleted file mode 100644 index ecbda64beb7db99bfa5daa2ba88e5c8f419f2345..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_01.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 308.0, - "tolerance": 9.24 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 440.0, - "tolerance": 13.2 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 70.0, - "tolerance": 2.1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_02.json b/sleep_assessment/cases/case03/case03_02.json deleted file mode 100644 index be3ccd63143bfc55e34995dd6324b21f958eb42f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_02.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 359.5, - "tolerance": 10.785 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 482.0, - "tolerance": 14.459999999999999 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 74.5850622406639, - "tolerance": 2.237551867219917 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_03.json b/sleep_assessment/cases/case03/case03_03.json deleted file mode 100644 index 8fd9ea099fbae464fb0a785d21fe9f0ae817c81f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_03.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 405.5, - "tolerance": 12.165 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 471.5, - "tolerance": 14.145 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 86.00212089077412, - "tolerance": 2.5800636267232235 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_04.json b/sleep_assessment/cases/case03/case03_04.json deleted file mode 100644 index bdc7c36f2047d0f3257a69249f9c34d43e656b32..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_04.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 467.5, - "tolerance": 14.025 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 481.5, - "tolerance": 14.445 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 97.09241952232607, - "tolerance": 2.912772585669782 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_05.json b/sleep_assessment/cases/case03/case03_05.json deleted file mode 100644 index ac969ce28d0d104a53c879b57b754de684318222..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_05.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 289.5, - "tolerance": 8.685 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 437.5, - "tolerance": 13.125 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 66.17142857142856, - "tolerance": 1.9851428571428569 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_06.json b/sleep_assessment/cases/case03/case03_06.json deleted file mode 100644 index 82998aa1873ceb5a25ebc406e4ff66eb8ea59135..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_06.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 351.5, - "tolerance": 10.545 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 427.0, - "tolerance": 12.809999999999999 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 82.31850117096019, - "tolerance": 2.469555035128806 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_07.json b/sleep_assessment/cases/case03/case03_07.json deleted file mode 100644 index 61a74522dfd4e188245b5086d018a68d5cb1df78..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_07.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 387.0, - "tolerance": 11.61 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 428.0, - "tolerance": 12.84 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 90.42056074766354, - "tolerance": 2.712616822429906 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_08.json b/sleep_assessment/cases/case03/case03_08.json deleted file mode 100644 index c16f03a94da896bf0612bfc8d49e6c6bf5df18ad..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_08.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 275.5, - "tolerance": 8.265 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 477.0, - "tolerance": 14.309999999999999 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 57.75681341719078, - "tolerance": 1.7327044025157232 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_09.json b/sleep_assessment/cases/case03/case03_09.json deleted file mode 100644 index de8af8acac3fab1a4652fa580bc3827e9e127304..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_09.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 468.0, - "tolerance": 14.04 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 508.0, - "tolerance": 15.24 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 92.1259842519685, - "tolerance": 2.763779527559055 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_10.json b/sleep_assessment/cases/case03/case03_10.json deleted file mode 100644 index 17915d328d9fac960796e9d09cb13cba37a50b20..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_10.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 379.0, - "tolerance": 11.37 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 479.5, - "tolerance": 14.385 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 79.04066736183525, - "tolerance": 2.3712200208550573 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_11.json b/sleep_assessment/cases/case03/case03_11.json deleted file mode 100644 index 19dae0da2f64a95f19e8a64ec99ca88abcfe82e8..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_11.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 375.5, - "tolerance": 11.264999999999999 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 542.0, - "tolerance": 16.259999999999998 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 69.28044280442805, - "tolerance": 2.0784132841328415 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_12.json b/sleep_assessment/cases/case03/case03_12.json deleted file mode 100644 index 481a41a4c46a260c7db5cbf971f7d1f4bd02de90..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_12.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 182.0, - "tolerance": 5.46 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 539.5, - "tolerance": 16.185 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 33.734939759036145, - "tolerance": 1.0120481927710843 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_13.json b/sleep_assessment/cases/case03/case03_13.json deleted file mode 100644 index 3dea68ed8fb9f912731c5e6c19e46ce997cad466..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_13.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 358.5, - "tolerance": 10.754999999999999 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 524.5, - "tolerance": 15.735 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 68.35081029551954, - "tolerance": 2.0505243088655862 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_14.json b/sleep_assessment/cases/case03/case03_14.json deleted file mode 100644 index 41424c1e83657fe5bf367b48e30fd9f73c533f9f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_14.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 301.0, - "tolerance": 9.03 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 437.5, - "tolerance": 13.125 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 68.8, - "tolerance": 2.064 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_15.json b/sleep_assessment/cases/case03/case03_15.json deleted file mode 100644 index 24c468bda69cb2bd6310bbf9f7b8199e8e9fe243..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_15.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 370.0, - "tolerance": 11.1 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 542.0, - "tolerance": 16.259999999999998 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 68.26568265682657, - "tolerance": 2.047970479704797 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_16.json b/sleep_assessment/cases/case03/case03_16.json deleted file mode 100644 index 564edfe983c7d9b05c7b2b15c161a3d05c76e951..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_16.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 469.5, - "tolerance": 14.084999999999999 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 504.0, - "tolerance": 15.12 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 93.15476190476191, - "tolerance": 2.794642857142857 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_17.json b/sleep_assessment/cases/case03/case03_17.json deleted file mode 100644 index ac4a79820cb874674b5dee59efeddca070853fa7..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_17.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 477.5, - "tolerance": 14.325 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 536.0, - "tolerance": 16.08 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 89.08582089552239, - "tolerance": 2.6725746268656714 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_18.json b/sleep_assessment/cases/case03/case03_18.json deleted file mode 100644 index 470d6eddbcaf3b1675f365762096cdcd423d881f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_18.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 451.5, - "tolerance": 13.545 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 477.5, - "tolerance": 14.325 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 94.55497382198953, - "tolerance": 2.836649214659686 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_19.json b/sleep_assessment/cases/case03/case03_19.json deleted file mode 100644 index f69cd06329b6f305eb5271caceb333f09655f00c..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_19.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 450.5, - "tolerance": 13.514999999999999 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 456.0, - "tolerance": 13.68 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 98.79385964912281, - "tolerance": 2.963815789473684 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_20.json b/sleep_assessment/cases/case03/case03_20.json deleted file mode 100644 index c21a7324b4f77f1c61787e2314c56e01b6fa62e5..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_20.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 508.0, - "tolerance": 15.24 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 534.5, - "tolerance": 16.035 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 95.0420954162769, - "tolerance": 2.8512628624883067 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_21.json b/sleep_assessment/cases/case03/case03_21.json deleted file mode 100644 index 44cf9102a0c6892c1b78bfcfb83ff3cd2ca699d0..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_21.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 239.0, - "tolerance": 7.17 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 422.5, - "tolerance": 12.674999999999999 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 56.5680473372781, - "tolerance": 1.697041420118343 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_22.json b/sleep_assessment/cases/case03/case03_22.json deleted file mode 100644 index a07fa9d2eb50c470624fdd42bba369d12fbf42ba..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_22.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 230.0, - "tolerance": 6.8999999999999995 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 388.5, - "tolerance": 11.655 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 59.202059202059196, - "tolerance": 1.7760617760617758 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_23.json b/sleep_assessment/cases/case03/case03_23.json deleted file mode 100644 index 0ada6b2af0ec0fb9fdf5434d633c01665432eb22..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_23.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 226.0, - "tolerance": 6.779999999999999 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 489.0, - "tolerance": 14.67 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 46.216768916155424, - "tolerance": 1.3865030674846626 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_24.json b/sleep_assessment/cases/case03/case03_24.json deleted file mode 100644 index 850058f023b3a77c2bbaeb321d2996e27b00d6d6..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_24.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 381.5, - "tolerance": 11.445 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 422.0, - "tolerance": 12.66 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 90.40284360189574, - "tolerance": 2.712085308056872 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case03/case03_25.json b/sleep_assessment/cases/case03/case03_25.json deleted file mode 100644 index 67a12fb96300c0e839f51ab4ed5264625ac4eacc..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case03/case03_25.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three values for the recording: Total Sleep Time (TST) in minutes, Total In Bed Time (TIB) in minutes, and Sleep Efficiency (SE) as a percentage. TIB must be computed from the label file duration. Please clearly report all three final values in your response." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) Total Sleep Time (TST) in minutes\n2) Total In Bed Time (TIB) in minutes\n3) Sleep Efficiency (SE) as a percentage\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys in the JSON must be EXACTLY \"tst_min\", \"tib_min\", and \"se_percent\".\n5. \"tst_min\" and \"tib_min\" must be FLOAT values in minutes or null.\n6. \"se_percent\" must be a FLOAT percentage value or null.\n7. If a value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"tst_min\": , \"tib_min\": , \"se_percent\": }", - "metrics": [ - { - "metric_id": "tst_accuracy", - "type": "numeric_check", - "target_key": "tst_min", - "weight": 30, - "params": { - "gt_value": 450.0, - "tolerance": 13.5 - } - }, - { - "metric_id": "tib_accuracy", - "type": "numeric_check", - "target_key": "tib_min", - "weight": 30, - "params": { - "gt_value": 479.5, - "tolerance": 14.385 - } - }, - { - "metric_id": "se_accuracy", - "type": "numeric_check", - "target_key": "se_percent", - "weight": 40, - "params": { - "gt_value": 93.84775808133472, - "tolerance": 2.8154327424400414 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_01.json b/sleep_assessment/cases/case04/case04_01.json deleted file mode 100644 index d90ff7eedda29fa72d5d5d2ff02cb13d72c6358f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_01.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 126.5, - "tolerance": 6.325 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 27, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_02.json b/sleep_assessment/cases/case04/case04_02.json deleted file mode 100644 index 26098a718a854fd6c92d84c0177359b84dbf16fc..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_02.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 67.5, - "tolerance": 3.375 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 30, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_03.json b/sleep_assessment/cases/case04/case04_03.json deleted file mode 100644 index 66d21af5fb38b1bf972d978995fc863243c5a9af..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_03.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 62.5, - "tolerance": 3.125 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 49, - "tolerance": 2 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_04.json b/sleep_assessment/cases/case04/case04_04.json deleted file mode 100644 index 93b47abfc9638fcb38d91e57cdee1a48130510c0..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_04.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 13.0, - "tolerance": 0.65 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 22, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_05.json b/sleep_assessment/cases/case04/case04_05.json deleted file mode 100644 index 5e928f8ac3b622452384b8f511da4deb8c26c716..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_05.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 47.5, - "tolerance": 2.375 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 20, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_06.json b/sleep_assessment/cases/case04/case04_06.json deleted file mode 100644 index 5dff3457c273c5568e10467a0cd120c9c7a2d608..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_06.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 66.5, - "tolerance": 3.325 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 12, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_07.json b/sleep_assessment/cases/case04/case04_07.json deleted file mode 100644 index 82caa58a61c2a01a8c9a0c18ebdcfea965d9c02c..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_07.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 37.0, - "tolerance": 1.85 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 20, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_08.json b/sleep_assessment/cases/case04/case04_08.json deleted file mode 100644 index 92c226c906bdcfde0bcc923cfffd089277f0bc9a..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_08.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 195.5, - "tolerance": 9.775 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 33, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_09.json b/sleep_assessment/cases/case04/case04_09.json deleted file mode 100644 index ae40268e67b63974b0f6bf64ea1189b63c4473d5..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_09.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 33.5, - "tolerance": 1.675 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 28, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_10.json b/sleep_assessment/cases/case04/case04_10.json deleted file mode 100644 index 9b8cda3d8e9a2eba45750092e46264d1c36e5a72..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_10.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 76.5, - "tolerance": 3.825 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 44, - "tolerance": 2 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_11.json b/sleep_assessment/cases/case04/case04_11.json deleted file mode 100644 index 13970e1a6a78a9700d2d7e7c624ee923c8778437..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_11.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 65.0, - "tolerance": 3.25 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 46, - "tolerance": 2 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_12.json b/sleep_assessment/cases/case04/case04_12.json deleted file mode 100644 index 8e8ee87ce2273eb294eef47811a3f8e93e55b751..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_12.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 43.0, - "tolerance": 2.15 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 14, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_13.json b/sleep_assessment/cases/case04/case04_13.json deleted file mode 100644 index 651961cadcb5d946da3743c04c0e20279ce940d9..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_13.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 73.0, - "tolerance": 3.6500000000000004 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 31, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_14.json b/sleep_assessment/cases/case04/case04_14.json deleted file mode 100644 index b6381e2880dbfdc096dab091e1f19850ea827270..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_14.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 43.5, - "tolerance": 2.1750000000000003 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 23, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_15.json b/sleep_assessment/cases/case04/case04_15.json deleted file mode 100644 index 8407cbb4dd6563b432ac4ed7acdd091384212303..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_15.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 100.0, - "tolerance": 5.0 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 35, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_16.json b/sleep_assessment/cases/case04/case04_16.json deleted file mode 100644 index 2cc4545dbd539063b887e8ad0b5b530b43829c7e..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_16.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 30.5, - "tolerance": 1.5250000000000001 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 22, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_17.json b/sleep_assessment/cases/case04/case04_17.json deleted file mode 100644 index 10e6deb7cb514337843354317d0038389e3172b5..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_17.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 37.5, - "tolerance": 1.875 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 31, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_18.json b/sleep_assessment/cases/case04/case04_18.json deleted file mode 100644 index 91c1d1d75f5e6540313b001bf4efbea6037521d8..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_18.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 19.0, - "tolerance": 0.9500000000000001 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 19, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_19.json b/sleep_assessment/cases/case04/case04_19.json deleted file mode 100644 index 914a9ed923e6bc05a6b59fbac48035cf4d62f666..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_19.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 3.5, - "tolerance": 0.5 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 7, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_20.json b/sleep_assessment/cases/case04/case04_20.json deleted file mode 100644 index 36c530f0df5d8ab8a1674ed62919a1bf2b3e22f8..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_20.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 19.5, - "tolerance": 0.9750000000000001 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 23, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_21.json b/sleep_assessment/cases/case04/case04_21.json deleted file mode 100644 index b72b7f8afa232806b3ab94b3790c264ffc3752d5..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_21.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 151.5, - "tolerance": 7.575 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 27, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_22.json b/sleep_assessment/cases/case04/case04_22.json deleted file mode 100644 index 72abb7dac0a0f9fbe0025a1346607eefa530d469..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_22.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 148.0, - "tolerance": 7.4 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 31, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_23.json b/sleep_assessment/cases/case04/case04_23.json deleted file mode 100644 index 75ad85b5409176c22cf181f0a52321ff16234eec..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_23.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 168.5, - "tolerance": 8.425 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 11, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_24.json b/sleep_assessment/cases/case04/case04_24.json deleted file mode 100644 index 1ab15c16d149299833a7f2a037e6f2160c7182b8..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_24.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 40.0, - "tolerance": 2.0 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 21, - "tolerance": 1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case04/case04_25.json b/sleep_assessment/cases/case04/case04_25.json deleted file mode 100644 index 7b45ecbede8b069ded756bc47e18b68dba357a08..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case04/case04_25.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two sleep continuity metrics for the recording: Wake After Sleep Onset (WASO) in minutes, and the number of awakenings after sleep onset. Define the analysis interval from the first sleep epoch to the last sleep epoch, and count awakenings as contiguous Wake segments within that interval. Please clearly report both final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two values from the agent's report:\n1) Wake After Sleep Onset (WASO) in minutes\n2) the number of awakenings after sleep onset\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"waso_min\" and \"awakening_count\".\n5. \"waso_min\" must be a FLOAT in minutes or null.\n6. \"awakening_count\" must be an INTEGER or null.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"waso_min\": , \"awakening_count\": }", - "metrics": [ - { - "metric_id": "waso_accuracy", - "type": "numeric_check", - "target_key": "waso_min", - "weight": 50, - "params": { - "gt_value": 28.5, - "tolerance": 1.425 - } - }, - { - "metric_id": "awakening_count_accuracy", - "type": "numeric_check", - "target_key": "awakening_count", - "weight": 50, - "params": { - "gt_value": 4, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_01.json b/sleep_assessment/cases/case05/case05_01.json deleted file mode 100644 index a29814c7cabc476bdf5fa6e3b433f22ca85b63d2..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_01.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 249.0, - "tolerance": 12.450000000000001 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 19.155844155844157, - "tolerance": 0.9577922077922079 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 165.5, - "tolerance": 8.275 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_02.json b/sleep_assessment/cases/case05/case05_02.json deleted file mode 100644 index 0392f3c3ccc0be1a424de09c498c9de82b5fb9b7..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_02.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 308.5, - "tolerance": 15.425 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 14.186369958275382, - "tolerance": 0.7093184979137691 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 105.5, - "tolerance": 5.275 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_03.json b/sleep_assessment/cases/case05/case05_03.json deleted file mode 100644 index 5bdd267cf7bb2cdedb5292c31b4ae365da93b028..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_03.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 292.0, - "tolerance": 14.600000000000001 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 27.990135635018497, - "tolerance": 1.399506781750925 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 158.0, - "tolerance": 7.9 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_04.json b/sleep_assessment/cases/case05/case05_04.json deleted file mode 100644 index 875737dd2c8cad491054385ad84582ab7a84efcd..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_04.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 352.5, - "tolerance": 17.625 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 24.59893048128342, - "tolerance": 1.2299465240641712 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 79.5, - "tolerance": 3.975 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_05.json b/sleep_assessment/cases/case05/case05_05.json deleted file mode 100644 index b4db5ed151d06b04de92419665aae0bb432c8815..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_05.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 268.5, - "tolerance": 13.425 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 7.253886010362694, - "tolerance": 0.3626943005181347 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 126.5, - "tolerance": 6.325 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_06.json b/sleep_assessment/cases/case05/case05_06.json deleted file mode 100644 index 03cc5c38e9a316590637b54047f27f1e10cf457b..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_06.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 281.0, - "tolerance": 14.05 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 20.056899004267425, - "tolerance": 1.0028449502133714 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 73.5, - "tolerance": 3.6750000000000003 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_07.json b/sleep_assessment/cases/case05/case05_07.json deleted file mode 100644 index 6d2f09936dafd09c8a233c9490307708d7d20464..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_07.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 300.0, - "tolerance": 15.0 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 22.48062015503876, - "tolerance": 1.124031007751938 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 109.5, - "tolerance": 5.4750000000000005 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_08.json b/sleep_assessment/cases/case05/case05_08.json deleted file mode 100644 index 1a0a18a3369d9c6f23d333a61cf85b0c1178c842..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_08.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 199.5, - "tolerance": 9.975000000000001 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 27.586206896551722, - "tolerance": 1.3793103448275863 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 263.0, - "tolerance": 13.15 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_09.json b/sleep_assessment/cases/case05/case05_09.json deleted file mode 100644 index 7700045b33eb9ed105fbcd5ee0f0154d85ffee0b..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_09.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 344.5, - "tolerance": 17.225 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 26.38888888888889, - "tolerance": 1.3194444444444446 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 46.0, - "tolerance": 2.3000000000000003 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_10.json b/sleep_assessment/cases/case05/case05_10.json deleted file mode 100644 index 4f63ce1edbe16cb81b0dec4eb6ffd5cbec8decfa..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_10.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 315.5, - "tolerance": 15.775 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 16.75461741424802, - "tolerance": 0.837730870712401 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 186.0, - "tolerance": 9.3 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_11.json b/sleep_assessment/cases/case05/case05_11.json deleted file mode 100644 index 9508480bc551c5f0f27f9b8599cf79893c91b03d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_11.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 324.5, - "tolerance": 16.225 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 13.581890812250332, - "tolerance": 0.6790945406125166 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 114.0, - "tolerance": 5.7 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_12.json b/sleep_assessment/cases/case05/case05_12.json deleted file mode 100644 index a5cba3e672226688fd202c041e56b415e61c6588..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_12.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 151.5, - "tolerance": 7.575 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 16.75824175824176, - "tolerance": 0.837912087912088 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 37.5, - "tolerance": 1.875 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_13.json b/sleep_assessment/cases/case05/case05_13.json deleted file mode 100644 index a543d4c898195cf47eeb849a5060dab681f52133..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_13.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 315.5, - "tolerance": 15.775 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 11.99442119944212, - "tolerance": 0.599721059972106 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 142.0, - "tolerance": 7.1000000000000005 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_14.json b/sleep_assessment/cases/case05/case05_14.json deleted file mode 100644 index 290b077e2c658a932d61825df7870536a3a3dea8..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_14.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 255.0, - "tolerance": 12.75 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 15.282392026578073, - "tolerance": 0.7641196013289037 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 45.0, - "tolerance": 2.25 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_15.json b/sleep_assessment/cases/case05/case05_15.json deleted file mode 100644 index 8c6d1a50d5e074d180355abc81651b8ff4c1dd11..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_15.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 324.5, - "tolerance": 16.225 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 12.297297297297296, - "tolerance": 0.6148648648648649 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 126.5, - "tolerance": 6.325 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_16.json b/sleep_assessment/cases/case05/case05_16.json deleted file mode 100644 index 9ed3a9944509829edca1adfca480727aa15911ec..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_16.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 379.0, - "tolerance": 18.95 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 19.275825346112885, - "tolerance": 0.9637912673056444 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 53.5, - "tolerance": 2.6750000000000003 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_17.json b/sleep_assessment/cases/case05/case05_17.json deleted file mode 100644 index 77b59b092bd09672ab890c8f19b394f9883bee97..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_17.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 356.5, - "tolerance": 17.825 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 25.340314136125656, - "tolerance": 1.2670157068062828 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 42.0, - "tolerance": 2.1 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_18.json b/sleep_assessment/cases/case05/case05_18.json deleted file mode 100644 index 0e647f060b47557ac0981dc3500dc94f73871672..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_18.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 317.5, - "tolerance": 15.875 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 29.678848283499445, - "tolerance": 1.4839424141749724 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 81.5, - "tolerance": 4.075 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_19.json b/sleep_assessment/cases/case05/case05_19.json deleted file mode 100644 index 1e02702db3dc9174b67fe4ba954d4e10d3c56d1b..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_19.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 328.0, - "tolerance": 16.400000000000002 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 27.19200887902331, - "tolerance": 1.3596004439511655 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 71.5, - "tolerance": 3.575 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_20.json b/sleep_assessment/cases/case05/case05_20.json deleted file mode 100644 index 862d280070a4bc88b12bf62408cf291ef076e1e2..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_20.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 369.5, - "tolerance": 18.475 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 27.263779527559056, - "tolerance": 1.3631889763779528 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 85.0, - "tolerance": 4.25 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_21.json b/sleep_assessment/cases/case05/case05_21.json deleted file mode 100644 index 9d6a8940ace2dbe0cf9ce19f2b0f7b4843d0bc7f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_21.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 198.5, - "tolerance": 9.925 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 16.94560669456067, - "tolerance": 0.8472803347280335 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 82.0, - "tolerance": 4.1000000000000005 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_22.json b/sleep_assessment/cases/case05/case05_22.json deleted file mode 100644 index 60ec1bb068247eebdf742b25411f89e9f86a3207..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_22.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 229.5, - "tolerance": 11.475000000000001 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 0.21739130434782608, - "tolerance": 0.010869565217391304 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 352.0, - "tolerance": 17.6 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_23.json b/sleep_assessment/cases/case05/case05_23.json deleted file mode 100644 index 11de5ed67be603fd0b49fb4f1e7d0b29b71d5d76..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_23.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 225.5, - "tolerance": 11.275 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 0.22123893805309736, - "tolerance": 0.011061946902654869 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 101.0, - "tolerance": 5.050000000000001 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_24.json b/sleep_assessment/cases/case05/case05_24.json deleted file mode 100644 index 75f1a6e599153b3430891aa0d9c7d08aff462e10..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_24.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 336.5, - "tolerance": 16.825 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 11.795543905635649, - "tolerance": 0.5897771952817824 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 55.0, - "tolerance": 2.75 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case05/case05_25.json b/sleep_assessment/cases/case05/case05_25.json deleted file mode 100644 index d28faeb56b404fac441d82656072af03aa64186d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case05/case05_25.json +++ /dev/null @@ -1,47 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate three sleep-stage metrics for the recording: NREM duration in minutes, REM sleep ratio as a percentage of total sleep time, and REM latency in minutes. Define REM latency as the time from the first sleep epoch to the first REM epoch. Please clearly report all three final values." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract three values from the agent's report:\n1) NREM duration in minutes\n2) REM sleep ratio as a percentage of total sleep time\n3) REM latency in minutes\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"nrem_duration_min\", \"rem_sleep_ratio_percent\", and \"rem_latency_min\".\n5. All values must be FLOATS or null.\n6. \"nrem_duration_min\" and \"rem_latency_min\" are measured in minutes.\n7. \"rem_sleep_ratio_percent\" is a percentage value; if the report says 18.5%, output 18.5.\n8. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"nrem_duration_min\": , \"rem_sleep_ratio_percent\": , \"rem_latency_min\": }", - "metrics": [ - { - "metric_id": "nrem_duration_accuracy", - "type": "numeric_check", - "target_key": "nrem_duration_min", - "weight": 34, - "params": { - "gt_value": 399.0, - "tolerance": 19.950000000000003 - } - }, - { - "metric_id": "rem_sleep_ratio_accuracy", - "type": "numeric_check", - "target_key": "rem_sleep_ratio_percent", - "weight": 33, - "params": { - "gt_value": 11.333333333333334, - "tolerance": 0.5666666666666668 - } - }, - { - "metric_id": "rem_latency_accuracy", - "type": "numeric_check", - "target_key": "rem_latency_min", - "weight": 33, - "params": { - "gt_value": 105.0, - "tolerance": 5.25 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_01.json b/sleep_assessment/cases/case06/case06_01.json deleted file mode 100644 index 3ea82f1f81b7895d3f11dd7ab2212ac171b5d56f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_01.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_01.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "W" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N3" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_02.json b/sleep_assessment/cases/case06/case06_02.json deleted file mode 100644 index 42fa7318ce63a9673887f1a6400b35aa92c56596..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_02.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_02.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "W" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_03.json b/sleep_assessment/cases/case06/case06_03.json deleted file mode 100644 index 45987926f2af7a397518599dfb41a5124aea4b67..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_03.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_03.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "R" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_04.json b/sleep_assessment/cases/case06/case06_04.json deleted file mode 100644 index 56759bcbf357f1511c333dff6e42d92b8d126a84..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_04.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_04.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "R" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_05.json b/sleep_assessment/cases/case06/case06_05.json deleted file mode 100644 index 44be1a3c6acf83af094de64869299dfb81d6e62b..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_05.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_05.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "W" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N2" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_06.json b/sleep_assessment/cases/case06/case06_06.json deleted file mode 100644 index 789596439599386f280a4502fb86d3ec4ab57d53..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_06.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_01.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "W" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_07.json b/sleep_assessment/cases/case06/case06_07.json deleted file mode 100644 index 6a250e832b8f0233e8867a912546cd2d0a70bce5..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_07.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_02.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N3" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_08.json b/sleep_assessment/cases/case06/case06_08.json deleted file mode 100644 index da92c9aebec9c6b829a89229cc8eb5fb653c0705..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_08.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_03.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "W" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N2" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_09.json b/sleep_assessment/cases/case06/case06_09.json deleted file mode 100644 index 0640e0b4de483557d1b6a8601b16013fc0ec63ff..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_09.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_04.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "R" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_10.json b/sleep_assessment/cases/case06/case06_10.json deleted file mode 100644 index 8d86b7860c3693364a3665e5fd58b549bc56787f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_10.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_05.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "W" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_11.json b/sleep_assessment/cases/case06/case06_11.json deleted file mode 100644 index 8e256cf760bcb89f7d460e7a957208606c39136f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_11.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_01.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "W" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_12.json b/sleep_assessment/cases/case06/case06_12.json deleted file mode 100644 index a019ae0fb77e26801003e292d85309cc7a97727c..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_12.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_02.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "W" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N2" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_13.json b/sleep_assessment/cases/case06/case06_13.json deleted file mode 100644 index 118bee7ced9dae362d5cffeb4bad6c69e143cda1..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_13.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_03.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "W" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N3" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_14.json b/sleep_assessment/cases/case06/case06_14.json deleted file mode 100644 index f3a5d246372d62817fedee1d2216a643fe17ac87..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_14.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_04.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N3" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "W" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_15.json b/sleep_assessment/cases/case06/case06_15.json deleted file mode 100644 index 01f4d90fa64a8bfaabaa39ba57ffc9431f36c3c1..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_15.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_05.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "W" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_16.json b/sleep_assessment/cases/case06/case06_16.json deleted file mode 100644 index 4db2b5679570f32a453badc41f1de3bd8cc5fd17..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_16.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_01.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "R" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_17.json b/sleep_assessment/cases/case06/case06_17.json deleted file mode 100644 index 895fabfbd5b96099e372e1a8f57e33142cd95381..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_17.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_02.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "R" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_18.json b/sleep_assessment/cases/case06/case06_18.json deleted file mode 100644 index 9073932f1832c386bbc6aa5e9e4879a800bd5749..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_18.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_03.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "R" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_19.json b/sleep_assessment/cases/case06/case06_19.json deleted file mode 100644 index 630b74657b22b56f9512759e8b4fc8a202b2baf0..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_19.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_04.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "R" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_20.json b/sleep_assessment/cases/case06/case06_20.json deleted file mode 100644 index 6232d3c856888e4b17decaf9f3f8bfa14c096d14..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_20.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_05.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "R" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_21.json b/sleep_assessment/cases/case06/case06_21.json deleted file mode 100644 index 21c9f9a7ba3baf8a30828e2c7dc3e33c7b284def..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_21.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_01.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "W" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N2" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_22.json b/sleep_assessment/cases/case06/case06_22.json deleted file mode 100644 index 94ed4993e182e149d7482094d7e52b2b3b3b256d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_22.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_02.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "W" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N2" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_23.json b/sleep_assessment/cases/case06/case06_23.json deleted file mode 100644 index 6c4ccce752488619939a22402d3f1a586248114b..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_23.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_03.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "W" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N2" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_24.json b/sleep_assessment/cases/case06/case06_24.json deleted file mode 100644 index 3b07f3c7d25c47a1bb89a710b450fe8de6d40c6a..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_24.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_04.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N3" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case06/case06_25.json b/sleep_assessment/cases/case06/case06_25.json deleted file mode 100644 index 8b3cee71f5bc45d873703fe6a7b455cd95b64348..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case06/case06_25.json +++ /dev/null @@ -1,35 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_05.npy", - "instruction": "Please use the provided sleep-stage label file to analyze the whole-night stage distribution. Determine the dominant sleep stage and the secondary sleep stage across the entire recording, and report both using the fixed stage labels W, N1, N2, N3, and R." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two stage labels from the agent's report:\n1) the dominant sleep stage across the whole night\n2) the secondary sleep stage across the whole night\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"dominant_sleep_stage\" and \"secondary_sleep_stage\".\n5. Each value must be exactly one of: \"W\", \"N1\", \"N2\", \"N3\", \"R\", or null.\n6. Normalize any synonyms to the fixed field set above. For example: Wake -> W, REM -> R.\n7. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"dominant_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>, \"secondary_sleep_stage\": <\"W\"|\"N1\"|\"N2\"|\"N3\"|\"R\"|null>}", - "metrics": [ - { - "metric_id": "dominant_stage_accuracy", - "type": "categorical_check", - "target_key": "dominant_sleep_stage", - "weight": 60, - "params": { - "gt_value": "N2" - } - }, - { - "metric_id": "secondary_stage_accuracy", - "type": "categorical_check", - "target_key": "secondary_sleep_stage", - "weight": 40, - "params": { - "gt_value": "N1" - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_01.json b/sleep_assessment/cases/case07/case07_01.json deleted file mode 100644 index c0a86fc5a55e3a45efbbdc6a06fad2d923227d4c..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_01.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 1.155844155844156, - "tolerance": 0.0577922077922078 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is ISRUC_01.edf. The ground-truth light/deep sleep ratio is 1.155844, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is relatively high and that the sleep shows an enhanced restorative tendency. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_02.json b/sleep_assessment/cases/case07/case07_02.json deleted file mode 100644 index c329f490bf453107c17ad82e24925bc1eee5d441..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_02.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 2.929936305732484, - "tolerance": 0.1464968152866242 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is ISRUC_02.edf. The ground-truth light/deep sleep ratio is 2.929936, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that the sleep structure is balanced or normal. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_03.json b/sleep_assessment/cases/case07/case07_03.json deleted file mode 100644 index 52dbee1ddfad5c4fc65b33a9a6e11f6e479f9e03..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_03.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 2.3757225433526012, - "tolerance": 0.11878612716763007 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is ISRUC_03.edf. The ground-truth light/deep sleep ratio is 2.375723, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that the sleep structure is balanced or normal. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_04.json b/sleep_assessment/cases/case07/case07_04.json deleted file mode 100644 index 70e43873234b67d807cf342e5c541a1f9de12cb7..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_04.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 2.294392523364486, - "tolerance": 0.11471962616822431 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is ISRUC_04.edf. The ground-truth light/deep sleep ratio is 2.294393, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that the sleep structure is balanced or normal. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_05.json b/sleep_assessment/cases/case07/case07_05.json deleted file mode 100644 index 105b97c3688427fbcd9f4285d4d97dfebb683e67..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_05.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 2.274390243902439, - "tolerance": 0.11371951219512196 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is ISRUC_05.edf. The ground-truth light/deep sleep ratio is 2.274390, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that the sleep structure is balanced or normal. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_06.json b/sleep_assessment/cases/case07/case07_06.json deleted file mode 100644 index e7da1e15e1be5a669b457d7f908bac1072b50fba..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_06.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 23.434782608695652, - "tolerance": 1.1717391304347826 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is HMC_01.edf. The ground-truth light/deep sleep ratio is 23.434783, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is markedly insufficient and that the sleep structure is abnormally shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_07.json b/sleep_assessment/cases/case07/case07_07.json deleted file mode 100644 index fdf26ba0070543e522c44e2367c49b333862807c..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_07.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 1.6785714285714286, - "tolerance": 0.08392857142857144 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is HMC_02.edf. The ground-truth light/deep sleep ratio is 1.678571, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that the sleep structure is balanced or normal. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_08.json b/sleep_assessment/cases/case07/case07_08.json deleted file mode 100644 index e5d2862b8badb270258d738df90cad1346a1e749..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_08.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 1.66, - "tolerance": 0.083 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is HMC_03.edf. The ground-truth light/deep sleep ratio is 1.660000, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that the sleep structure is balanced or normal. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_09.json b/sleep_assessment/cases/case07/case07_09.json deleted file mode 100644 index 21fd035d5fa167fb6695da71126c4705af617570..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_09.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 9.765625, - "tolerance": 0.48828125 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is HMC_04.edf. The ground-truth light/deep sleep ratio is 9.765625, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is markedly insufficient and that the sleep structure is abnormally shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_10.json b/sleep_assessment/cases/case07/case07_10.json deleted file mode 100644 index 3c7831286d33bca9d41113ee9771c45cd27fa3a3..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_10.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 3.2348993288590604, - "tolerance": 0.16174496644295303 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is HMC_05.edf. The ground-truth light/deep sleep ratio is 3.234899, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that sleep is somewhat shallow and that deep sleep is slightly insufficient. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_11.json b/sleep_assessment/cases/case07/case07_11.json deleted file mode 100644 index c4ebf19131c8fce7fbca5ba97107a60faf39a0d9..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_11.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 3.475862068965517, - "tolerance": 0.17379310344827587 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is SHHS1_01.edf. The ground-truth light/deep sleep ratio is 3.475862, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that sleep is somewhat shallow and that deep sleep is slightly insufficient. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_12.json b/sleep_assessment/cases/case07/case07_12.json deleted file mode 100644 index afc5864385ae7be9a99220ba6de2a3f46a3f1e5d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_12.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 3.9672131147540983, - "tolerance": 0.19836065573770492 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is SHHS1_02.edf. The ground-truth light/deep sleep ratio is 3.967213, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that sleep is somewhat shallow and that deep sleep is slightly insufficient. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_13.json b/sleep_assessment/cases/case07/case07_13.json deleted file mode 100644 index c9ee4fcaaac2c525fb1a628823a3556938be3e94..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_13.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 1.0553745928338762, - "tolerance": 0.052768729641693816 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is SHHS1_03.edf. The ground-truth light/deep sleep ratio is 1.055375, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is relatively high and that the sleep shows an enhanced restorative tendency. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_14.json b/sleep_assessment/cases/case07/case07_14.json deleted file mode 100644 index 787d42e891f44e740412ad712c750706cad3eb0c..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_14.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 0.6190476190476191, - "tolerance": 0.05 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is SHHS1_04.edf. The ground-truth light/deep sleep ratio is 0.619048, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is unusually high and that the overall sleep structure is atypical. It must not describe the structure as balanced, normal, or shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_15.json b/sleep_assessment/cases/case07/case07_15.json deleted file mode 100644 index c49bc0010f9d8cc3cf1364383cdbddbc2360658e..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_15.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 5.555555555555555, - "tolerance": 0.2777777777777778 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is SHHS1_05.edf. The ground-truth light/deep sleep ratio is 5.555556, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is markedly insufficient and that the sleep structure is abnormally shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_16.json b/sleep_assessment/cases/case07/case07_16.json deleted file mode 100644 index cc32e3c15f935d6413ea066fa836348e13a62d92..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_16.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 4.191780821917808, - "tolerance": 0.2095890410958904 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is MASSSS3_01.edf. The ground-truth light/deep sleep ratio is 4.191781, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is markedly insufficient and that the sleep structure is abnormally shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_17.json b/sleep_assessment/cases/case07/case07_17.json deleted file mode 100644 index 220bf60f49758a0932b9f1a69c7e0e7d89365948..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_17.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 3.0977011494252875, - "tolerance": 0.15488505747126438 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is MASSSS3_02.edf. The ground-truth light/deep sleep ratio is 3.097701, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that sleep is somewhat shallow and that deep sleep is slightly insufficient. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_18.json b/sleep_assessment/cases/case07/case07_18.json deleted file mode 100644 index 4af68e9f37437174ebe096064023e82748a55c82..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_18.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 4.120967741935484, - "tolerance": 0.2060483870967742 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is MASSSS3_03.edf. The ground-truth light/deep sleep ratio is 4.120968, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is markedly insufficient and that the sleep structure is abnormally shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_19.json b/sleep_assessment/cases/case07/case07_19.json deleted file mode 100644 index 68279e8d65a1209af7665753d90eb164d5de3219..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_19.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 9.25, - "tolerance": 0.4625 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is MASSSS3_04.edf. The ground-truth light/deep sleep ratio is 9.250000, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is markedly insufficient and that the sleep structure is abnormally shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_20.json b/sleep_assessment/cases/case07/case07_20.json deleted file mode 100644 index 0c111fc37179638b5bd6f2b709869556e3090674..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_20.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 2.7897435897435896, - "tolerance": 0.13948717948717948 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is MASSSS3_05.edf. The ground-truth light/deep sleep ratio is 2.789744, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that the sleep structure is balanced or normal. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_21.json b/sleep_assessment/cases/case07/case07_21.json deleted file mode 100644 index ecfac0ae2fd375ff046c71b38f1c0664de5d7724..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_21.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 4.513888888888889, - "tolerance": 0.22569444444444448 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is Physionet2018_01.edf. The ground-truth light/deep sleep ratio is 4.513889, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is markedly insufficient and that the sleep structure is abnormally shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_22.json b/sleep_assessment/cases/case07/case07_22.json deleted file mode 100644 index 1a11bffa7f832fd1c531ad40eb437d5107e71293..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_22.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 20.857142857142858, - "tolerance": 1.042857142857143 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is Physionet2018_02.edf. The ground-truth light/deep sleep ratio is 20.857143, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is markedly insufficient and that the sleep structure is abnormally shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_23.json b/sleep_assessment/cases/case07/case07_23.json deleted file mode 100644 index 09a6353805a46f794e85d33e5309e53d45613c04..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_23.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 6.274193548387097, - "tolerance": 0.31370967741935485 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is Physionet2018_03.edf. The ground-truth light/deep sleep ratio is 6.274194, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is markedly insufficient and that the sleep structure is abnormally shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_24.json b/sleep_assessment/cases/case07/case07_24.json deleted file mode 100644 index 4c4fb2ffae62baf33d07b7a59f32d33a47ebbe3b..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_24.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 2.9127906976744184, - "tolerance": 0.14563953488372092 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is Physionet2018_04.edf. The ground-truth light/deep sleep ratio is 2.912791, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that the sleep structure is balanced or normal. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case07/case07_25.json b/sleep_assessment/cases/case07/case07_25.json deleted file mode 100644 index 8b33e9d7c914c63cf6817c0aae70573e99857206..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case07/case07_25.json +++ /dev/null @@ -1,36 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate the light-sleep to deep-sleep ratio for the whole night. Then interpret what this ratio suggests about the sleep architecture, including whether sleep appears balanced, relatively restorative, too shallow, or atypical. Please report the final ratio and give a brief explanation of the sleep quality implication." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the light-sleep to deep-sleep ratio from the agent's report.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The key must be EXACTLY \"light_deep_sleep_ratio\".\n5. The value must be a FLOAT or null.\n6. If the value is missing or cannot be found, return {\"light_deep_sleep_ratio\": null}.\n\n### OUTPUT TEMPLATE\n{\"light_deep_sleep_ratio\": }", - "metrics": [ - { - "metric_id": "light_deep_ratio_accuracy", - "type": "numeric_check", - "target_key": "light_deep_sleep_ratio", - "weight": 40, - "params": { - "gt_value": 7.0606060606060606, - "tolerance": 0.353030303030303 - } - }, - { - "metric_id": "sleep_quality_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 60, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is Physionet2018_05.edf. The ground-truth light/deep sleep ratio is 7.060606, where the ratio is defined as (N1+N2)/N3. The correct response must explicitly conclude that deep sleep is markedly insufficient and that the sleep structure is abnormally shallow. Mark the response as correct only if its final conclusion matches that rule. If the response gives the opposite conclusion or contradicts that rule, mark it as incorrect. Output only a valid JSON object with exactly one key named status whose value is either True or False. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_01.json b/sleep_assessment/cases/case08/case08_01.json deleted file mode 100644 index cf5a8f0cfa0afef94d809979229ba83fb7e6ee9f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_01.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_01.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 101.5, - "tolerance": 5.075 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 43.5, - "tolerance": 2.1750000000000003 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 43.0, - "tolerance": 2.15 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is ISRUC_01.edf. The three longest uninterrupted sleep episodes are 101.500000, 43.500000, and 43.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that there is at least one clearly good continuous sleep episode. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_02.json b/sleep_assessment/cases/case08/case08_02.json deleted file mode 100644 index 762b7581b46729d5954114b16b566ab3b5facedd..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_02.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_02.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 60.5, - "tolerance": 3.0250000000000004 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 37.0, - "tolerance": 1.85 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 34.5, - "tolerance": 1.725 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is ISRUC_02.edf. The three longest uninterrupted sleep episodes are 60.500000, 37.000000, and 34.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_03.json b/sleep_assessment/cases/case08/case08_03.json deleted file mode 100644 index a2a55236d60d4f2f9ae2b86ffc13a5d4260edd91..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_03.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_03.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 67.5, - "tolerance": 3.375 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 45.0, - "tolerance": 2.25 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 42.0, - "tolerance": 2.1 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is ISRUC_03.edf. The three longest uninterrupted sleep episodes are 67.500000, 45.000000, and 42.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_04.json b/sleep_assessment/cases/case08/case08_04.json deleted file mode 100644 index 12ab01b16fcb2cb608f20b765c1494e9f02d3df2..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_04.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_04.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 97.5, - "tolerance": 4.875 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 87.0, - "tolerance": 4.3500000000000005 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 74.0, - "tolerance": 3.7 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is ISRUC_04.edf. The three longest uninterrupted sleep episodes are 97.500000, 87.000000, and 74.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that there is at least one clearly good continuous sleep episode. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_05.json b/sleep_assessment/cases/case08/case08_05.json deleted file mode 100644 index 20910355b112a0028fe6dee99d96c66434b1921a..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_05.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_05.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 68.0, - "tolerance": 3.4000000000000004 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 63.5, - "tolerance": 3.1750000000000003 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 57.5, - "tolerance": 2.875 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is ISRUC_05.edf. The three longest uninterrupted sleep episodes are 68.000000, 63.500000, and 57.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_06.json b/sleep_assessment/cases/case08/case08_06.json deleted file mode 100644 index 37ef8caef35c73af5c518ac17a51fee01d1c2fea..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_06.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_01.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 84.5, - "tolerance": 4.2250000000000005 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 70.5, - "tolerance": 3.5250000000000004 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 50.0, - "tolerance": 2.5 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is HMC_01.edf. The three longest uninterrupted sleep episodes are 84.500000, 70.500000, and 50.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_07.json b/sleep_assessment/cases/case08/case08_07.json deleted file mode 100644 index 99ed3261f3a207a5aeaffa3ad3cba1a59b12492f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_07.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_02.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 90.0, - "tolerance": 4.5 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 66.0, - "tolerance": 3.3000000000000003 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 64.0, - "tolerance": 3.2 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is HMC_02.edf. The three longest uninterrupted sleep episodes are 90.000000, 66.000000, and 64.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that there is at least one clearly good continuous sleep episode. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_08.json b/sleep_assessment/cases/case08/case08_08.json deleted file mode 100644 index bbfde4872db368f8dc6dc8f17b404eac4ac4d963..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_08.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_03.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 116.5, - "tolerance": 5.825 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 48.0, - "tolerance": 2.4000000000000004 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 33.5, - "tolerance": 1.675 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is HMC_03.edf. The three longest uninterrupted sleep episodes are 116.500000, 48.000000, and 33.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that there is at least one clearly good continuous sleep episode. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_09.json b/sleep_assessment/cases/case08/case08_09.json deleted file mode 100644 index d7df0c8c96202870c646abfce11f7a1cc5286e26..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_09.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_04.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 85.0, - "tolerance": 4.25 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 65.5, - "tolerance": 3.2750000000000004 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 53.5, - "tolerance": 2.6750000000000003 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is HMC_04.edf. The three longest uninterrupted sleep episodes are 85.000000, 65.500000, and 53.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_10.json b/sleep_assessment/cases/case08/case08_10.json deleted file mode 100644 index 0b6dca80b5c741e04b482fbaa49c216ee8f9812d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_10.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_05.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 52.5, - "tolerance": 2.625 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 46.0, - "tolerance": 2.3000000000000003 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 35.0, - "tolerance": 1.75 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is HMC_05.edf. The three longest uninterrupted sleep episodes are 52.500000, 46.000000, and 35.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_11.json b/sleep_assessment/cases/case08/case08_11.json deleted file mode 100644 index 5fce9053817c7498fe87c6201aa56cc8cddd8fd1..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_11.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_01.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 60.5, - "tolerance": 3.0250000000000004 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 43.5, - "tolerance": 2.1750000000000003 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 31.5, - "tolerance": 1.5750000000000002 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is SHHS1_01.edf. The three longest uninterrupted sleep episodes are 60.500000, 43.500000, and 31.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_12.json b/sleep_assessment/cases/case08/case08_12.json deleted file mode 100644 index 0cd9f6bfb38a67ba7934ce94d2e6d16a4466d08e..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_12.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_02.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 66.5, - "tolerance": 3.325 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 37.5, - "tolerance": 1.875 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 28.5, - "tolerance": 1.425 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is SHHS1_02.edf. The three longest uninterrupted sleep episodes are 66.500000, 37.500000, and 28.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_13.json b/sleep_assessment/cases/case08/case08_13.json deleted file mode 100644 index 60a2166699b0f59e40fd6459580f526d2933804b..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_13.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_03.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 52.5, - "tolerance": 2.625 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 51.5, - "tolerance": 2.575 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 38.5, - "tolerance": 1.925 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is SHHS1_03.edf. The three longest uninterrupted sleep episodes are 52.500000, 51.500000, and 38.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_14.json b/sleep_assessment/cases/case08/case08_14.json deleted file mode 100644 index 14d60fbd890bcfccb5272046a4f664d82e83e288..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_14.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_04.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 50.5, - "tolerance": 2.5250000000000004 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 50.0, - "tolerance": 2.5 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 42.0, - "tolerance": 2.1 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is SHHS1_04.edf. The three longest uninterrupted sleep episodes are 50.500000, 50.000000, and 42.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_15.json b/sleep_assessment/cases/case08/case08_15.json deleted file mode 100644 index 17cf9b3605a2e7f8e994177cbf732316412cd076..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_15.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_05.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 61.0, - "tolerance": 3.0500000000000003 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 39.0, - "tolerance": 1.9500000000000002 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 29.0, - "tolerance": 1.4500000000000002 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is SHHS1_05.edf. The three longest uninterrupted sleep episodes are 61.000000, 39.000000, and 29.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_16.json b/sleep_assessment/cases/case08/case08_16.json deleted file mode 100644 index f2b07554ea00b2fea3e1f6a05d1c07f350c5296f..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_16.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_01.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 164.0, - "tolerance": 8.200000000000001 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 76.0, - "tolerance": 3.8000000000000003 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 56.5, - "tolerance": 2.825 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is MASSSS3_01.edf. The three longest uninterrupted sleep episodes are 164.000000, 76.000000, and 56.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that there is at least one clearly good continuous sleep episode. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_17.json b/sleep_assessment/cases/case08/case08_17.json deleted file mode 100644 index 344364afdf3dd5e04323cdf7b1a3368652f0a561..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_17.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_02.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 77.0, - "tolerance": 3.85 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 71.0, - "tolerance": 3.5500000000000003 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 45.0, - "tolerance": 2.25 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is MASSSS3_02.edf. The three longest uninterrupted sleep episodes are 77.000000, 71.000000, and 45.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_18.json b/sleep_assessment/cases/case08/case08_18.json deleted file mode 100644 index 31cf79d147b6f9d7c4b02bc09a307c4d4c77c449..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_18.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_03.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 101.0, - "tolerance": 5.050000000000001 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 76.5, - "tolerance": 3.825 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 62.0, - "tolerance": 3.1 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is MASSSS3_03.edf. The three longest uninterrupted sleep episodes are 101.000000, 76.500000, and 62.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that there is at least one clearly good continuous sleep episode. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_19.json b/sleep_assessment/cases/case08/case08_19.json deleted file mode 100644 index 6dcda708c2c1ffd163abcf96a0ce318ea0579b07..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_19.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_04.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 174.0, - "tolerance": 8.700000000000001 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 161.5, - "tolerance": 8.075000000000001 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 48.5, - "tolerance": 2.4250000000000003 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is MASSSS3_04.edf. The three longest uninterrupted sleep episodes are 174.000000, 161.500000, and 48.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that there is at least one clearly good continuous sleep episode. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_20.json b/sleep_assessment/cases/case08/case08_20.json deleted file mode 100644 index 7625cf3a48efb3797c17f2e1897e63812d19f1d9..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_20.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_05.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 87.5, - "tolerance": 4.375 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 54.0, - "tolerance": 2.7 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 51.0, - "tolerance": 2.5500000000000003 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is MASSSS3_05.edf. The three longest uninterrupted sleep episodes are 87.500000, 54.000000, and 51.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because the second and third longest episodes are also at least 40 minutes, the response must also say that overall sleep continuity is relatively stable. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_21.json b/sleep_assessment/cases/case08/case08_21.json deleted file mode 100644 index b3af72a979b27f7908593fa052c158b86946c2c9..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_21.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_01.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 41.5, - "tolerance": 2.075 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 40.0, - "tolerance": 2.0 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 31.0, - "tolerance": 1.55 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is Physionet2018_01.edf. The three longest uninterrupted sleep episodes are 41.500000, 40.000000, and 31.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_22.json b/sleep_assessment/cases/case08/case08_22.json deleted file mode 100644 index 6dd1d2e2f03bf29e4288de1e2b650b25ebde2b0e..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_22.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_02.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 82.5, - "tolerance": 4.125 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 26.0, - "tolerance": 1.3 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 21.5, - "tolerance": 1.075 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is Physionet2018_02.edf. The three longest uninterrupted sleep episodes are 82.500000, 26.000000, and 21.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_23.json b/sleep_assessment/cases/case08/case08_23.json deleted file mode 100644 index f49035c8ff14c92f24d005213749c72ab6cc4708..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_23.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_03.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 43.0, - "tolerance": 2.15 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 38.0, - "tolerance": 1.9000000000000001 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 36.5, - "tolerance": 1.8250000000000002 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is Physionet2018_03.edf. The three longest uninterrupted sleep episodes are 43.000000, 38.000000, and 36.500000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that sleep continuity is moderate or average. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_24.json b/sleep_assessment/cases/case08/case08_24.json deleted file mode 100644 index 33560cb84b25cab8cc5ef9762c7042f96f497392..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_24.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_04.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 141.0, - "tolerance": 7.050000000000001 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 55.0, - "tolerance": 2.75 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 36.0, - "tolerance": 1.8 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is Physionet2018_04.edf. The three longest uninterrupted sleep episodes are 141.000000, 55.000000, and 36.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that there is at least one clearly good continuous sleep episode. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case08/case08_25.json b/sleep_assessment/cases/case08/case08_25.json deleted file mode 100644 index 925003870decbada784da3c858347767b134ece0..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case08/case08_25.json +++ /dev/null @@ -1,56 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1.5, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_05.npy", - "instruction": "Please use the provided sleep-stage label file to identify the three longest uninterrupted sleep episodes across the whole night and report their lengths in descending order. Then briefly interpret what these episodes suggest about the overall sleep continuity of the night." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract the lengths of the three longest uninterrupted sleep episodes in minutes.\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"top1_sleep_episode_min\", \"top2_sleep_episode_min\", and \"top3_sleep_episode_min\".\n5. All three values must be FLOATS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"top1_sleep_episode_min\": , \"top2_sleep_episode_min\": , \"top3_sleep_episode_min\": }", - "metrics": [ - { - "metric_id": "top1_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top1_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 207.0, - "tolerance": 10.350000000000001 - } - }, - { - "metric_id": "top2_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top2_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 170.5, - "tolerance": 8.525 - } - }, - { - "metric_id": "top3_sleep_episode_accuracy", - "type": "numeric_check", - "target_key": "top3_sleep_episode_min", - "weight": 20, - "params": { - "gt_value": 33.0, - "tolerance": 1.6500000000000001 - } - }, - { - "metric_id": "sleep_continuity_semantic_consistency", - "type": "semantic_consistency", - "target_key": "full_text", - "weight": 40, - "params": { - "judge_prompt": "You are judging semantic consistency for a sleep-medicine benchmark. The sample is Physionet2018_05.edf. The three longest uninterrupted sleep episodes are 207.000000, 170.500000, and 33.000000 minutes. The benchmark rule is: if the longest episode is <20 minutes, sleep is severely fragmented; 20-40 minutes means poor continuity; 40-90 minutes means moderate continuity; >=90 minutes means at least one good continuous sleep episode. The correct response must explicitly conclude that there is at least one clearly good continuous sleep episode. Because only the longest episode is clearly long while the other long episodes are shorter, the response must also note that the overall night still shows some fragmentation. Score the response in two parts. Give 0.5 points if the base continuity judgement is correct. Give 0.5 points if the secondary stability-or-fragmentation judgement is correct. The total score must therefore be exactly one of 0.0, 0.5, or 1.0. Output only a valid JSON object with exactly one key named score whose value is 0.0, 0.5, or 1.0. Do not output Markdown, explanations, or additional fields." - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_01.json b/sleep_assessment/cases/case09/case09_01.json deleted file mode 100644 index d1c7ca57b62be350fdc4f46a95370ce290070fd8..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_01.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 133, - "tolerance": 3 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 3, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_02.json b/sleep_assessment/cases/case09/case09_02.json deleted file mode 100644 index 9473ad1bc02ebbca55a8665e60f2234b47a2143a..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_02.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 180, - "tolerance": 5 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 3, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_03.json b/sleep_assessment/cases/case09/case09_03.json deleted file mode 100644 index 94e7d6e59d97aacfcab00c92ad75c2bb13ddbbc5..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_03.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 184, - "tolerance": 5 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 1, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_04.json b/sleep_assessment/cases/case09/case09_04.json deleted file mode 100644 index a7fff26ee19328db50a1d46d155badb01d83e3b7..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_04.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 123, - "tolerance": 3 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 4, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_05.json b/sleep_assessment/cases/case09/case09_05.json deleted file mode 100644 index 02553e77521ecf4186883aa33d31294aa72a9600..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_05.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "ISRUC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "ISRUC" - }, - "agent_input": { - "label_path": "data/sleep/ISRUC_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 123, - "tolerance": 3 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 0, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_06.json b/sleep_assessment/cases/case09/case09_06.json deleted file mode 100644 index f8202b9b5f2abe81fe192447cb543b460cc6bc33..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_06.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 98, - "tolerance": 2 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 0, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_07.json b/sleep_assessment/cases/case09/case09_07.json deleted file mode 100644 index 170dedfe84d8b26efd5a811a99c336a1a0b2497a..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_07.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 111, - "tolerance": 3 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 0, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_08.json b/sleep_assessment/cases/case09/case09_08.json deleted file mode 100644 index 5fcfad8cf8aaa9a8980f7b18dfd273b664248d00..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_08.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 151, - "tolerance": 4 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 4, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_09.json b/sleep_assessment/cases/case09/case09_09.json deleted file mode 100644 index 9f8850b1d16f769a0bfaa862143a8cd3b3201870..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_09.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 135, - "tolerance": 4 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 0, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_10.json b/sleep_assessment/cases/case09/case09_10.json deleted file mode 100644 index a521e0b3530d945f38c808aa6a7c128503294378..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_10.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "HMC_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "HMC" - }, - "agent_input": { - "label_path": "data/sleep/HMC_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 249, - "tolerance": 7 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 2, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_11.json b/sleep_assessment/cases/case09/case09_11.json deleted file mode 100644 index cd891995c7a0e1a463455411ebdc503346c41fed..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_11.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 180, - "tolerance": 5 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 4, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_12.json b/sleep_assessment/cases/case09/case09_12.json deleted file mode 100644 index fcd04d85c0e1011a446f625ce53a796a5c74865c..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_12.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 95, - "tolerance": 2 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 0, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_13.json b/sleep_assessment/cases/case09/case09_13.json deleted file mode 100644 index 3b6acd059f4a2cd7f2d21d6db419d0aad535eabc..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_13.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 143, - "tolerance": 4 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 6, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_14.json b/sleep_assessment/cases/case09/case09_14.json deleted file mode 100644 index d656123a15d5d4153f40efd4dbacd418362a5d2d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_14.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 138, - "tolerance": 4 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 4, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_15.json b/sleep_assessment/cases/case09/case09_15.json deleted file mode 100644 index 07a7c23619c7cb14e5a3bd2289f5c19754786055..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_15.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "SHHS1_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "SHHS1" - }, - "agent_input": { - "label_path": "data/sleep/SHHS1_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 133, - "tolerance": 3 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 2, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_16.json b/sleep_assessment/cases/case09/case09_16.json deleted file mode 100644 index 078da77d1dc8837186f9ba616f9cff24574b83bd..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_16.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 179, - "tolerance": 5 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 0, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_17.json b/sleep_assessment/cases/case09/case09_17.json deleted file mode 100644 index d16cb749fa1df7b60f3dc7c7c1885fdf2833d093..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_17.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 195, - "tolerance": 5 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 3, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_18.json b/sleep_assessment/cases/case09/case09_18.json deleted file mode 100644 index fe55487c768e864d5e2cf141db904c80fbaddeaf..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_18.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 144, - "tolerance": 4 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 1, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_19.json b/sleep_assessment/cases/case09/case09_19.json deleted file mode 100644 index 6158b94b18ef94a899a44b366cbd4f5daaad889d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_19.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 100, - "tolerance": 3 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 0, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_20.json b/sleep_assessment/cases/case09/case09_20.json deleted file mode 100644 index fb7f9abb83cffbf315c2847675aa336b9b40b95b..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_20.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "MASSSS3_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "MASSSS3" - }, - "agent_input": { - "label_path": "data/sleep/MASSSS3_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 117, - "tolerance": 3 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 2, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_21.json b/sleep_assessment/cases/case09/case09_21.json deleted file mode 100644 index e61165d392fdce717f1b91d4e48cf19a66ba0e59..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_21.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_01.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_01.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 99, - "tolerance": 2 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 0, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_22.json b/sleep_assessment/cases/case09/case09_22.json deleted file mode 100644 index c59dacadbbef97e788a4c8c6a5df50af347bfada..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_22.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_02.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_02.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 101, - "tolerance": 3 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 0, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_23.json b/sleep_assessment/cases/case09/case09_23.json deleted file mode 100644 index 28a916acd2105dbd343801e9bba3ca588e24555d..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_23.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_03.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_03.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 84, - "tolerance": 2 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 1, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_24.json b/sleep_assessment/cases/case09/case09_24.json deleted file mode 100644 index 0509f2cc514c408a2fae6f53bcf5a6ced7d6f41a..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_24.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_04.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_04.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 155, - "tolerance": 4 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 1, - "tolerance": 0 - } - } - ] - } -} diff --git a/sleep_assessment/cases/case09/case09_25.json b/sleep_assessment/cases/case09/case09_25.json deleted file mode 100644 index e9c6a741e9102c10217bf193ede5539b05b37a14..0000000000000000000000000000000000000000 --- a/sleep_assessment/cases/case09/case09_25.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "meta_info": { - "case_id": "Physionet2018_05.edf", - "bench_subset": "NeuroBench-Sleep", - "difficult": 1, - "original_dataset": "Physionet2018" - }, - "agent_input": { - "label_path": "data/sleep/Physionet2018_05.npy", - "instruction": "Please use the provided sleep-stage label file to calculate two transition-based metrics for the whole night: the total number of sleep-stage transitions, and the number of interruptions from deep sleep into wakefulness. Please clearly report both final counts." - }, - "eval_config": { - "parser_prompt": "### ROLE\nYou are a precise JSON Extraction Engine for sleep medicine reports. Your sole task is to convert natural language reports into structured JSON data.\n\n### TASK\nExtract two transition counts from the agent's report:\n1) the total number of sleep-stage transitions across the whole night\n2) the number of deep-sleep interruptions into wakefulness\n\n### STRICT CONSTRAINTS (MANDATORY)\n1. Output ONLY a valid JSON object.\n2. DO NOT include Markdown code blocks.\n3. DO NOT include conversational text, explanations, or units.\n4. The keys must be EXACTLY \"total_stage_transitions\" and \"n3_to_w_interruptions\".\n5. Both values must be INTEGERS or null.\n6. If one value is missing or cannot be found, return null for that value.\n\n### OUTPUT TEMPLATE\n{\"total_stage_transitions\": , \"n3_to_w_interruptions\": }", - "metrics": [ - { - "metric_id": "total_stage_transition_accuracy", - "type": "numeric_check", - "target_key": "total_stage_transitions", - "weight": 50, - "params": { - "gt_value": 83, - "tolerance": 2 - } - }, - { - "metric_id": "n3_to_w_interruptions_accuracy", - "type": "numeric_check", - "target_key": "n3_to_w_interruptions", - "weight": 50, - "params": { - "gt_value": 0, - "tolerance": 0 - } - } - ] - } -}