@getollie/cli 0.0.1

package/library/data_science-data_visualization_dashboards/create-visualizations-from-code-expert.json

@@ -0,0 +1,68 @@
+{
+  "index": 967,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for display. I want to create visualizations - I'll provide requirements, and you'll give me code that I can place in the left panel for the graph to display directly on the right.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is a comprehensive visualization framework implemented?",
+      "description": "Review whether the code includes a complete visualization rendering system with proper initialization, data binding, and responsive design. Score 0 if no visualization is implemented, 5 if basic static visualization exists, and 10 if the visualization supports dynamic data updates and responsive design.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are appropriate visualization techniques selected based on the requirements?",
+      "description": "Evaluate whether the chosen visualization type (chart, graph, map, etc.) matches the data characteristics and user requirements. Check if the visualization effectively communicates the intended information. Deduct 5 points if the visualization type is inappropriate, and 3 points if better alternatives exist but weren't considered. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is data processing correctly implemented?",
+      "description": "Check whether the code includes proper data preprocessing, normalization, aggregation, and filtering as needed. The implementation should handle different data formats and edge cases (empty data, outliers). Deduct 5 points for missing data validation, 3 points for inefficient data transformations, and 5 points if the code fails with edge cases. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are interactive elements properly implemented?",
+      "description": "Assess whether the visualization includes appropriate interactive features (tooltips, zooming, filtering, highlighting). Check if interactions are intuitive and enhance understanding of the data. Deduct 3 points for each missing essential interaction, and 5 points if interactions are implemented but not functioning correctly. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, browser incompatibilities, window resizing, etc.) and provide appropriate fallbacks or error handling. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Animation transitions between data states 2. Novel interaction techniques 3. Integration with external data sources). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant visualization elements that don't add information 2. Unnecessary graphical effects that distract from the data 3. Complex interactions that don't enhance understanding. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core visualization is compromised by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/visualization/interaction layers), code reusability, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if rendering performance is not optimized. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the visualization meet professional design standards?",
+      "description": "Evaluate whether the overall design follows data visualization principles: 1) Appropriate color palette with sufficient contrast 2) Clear visual hierarchy and layout 3) Proper labeling and legends. Deduct 3 points for each violation of perceptual principles, 5 points for misleading visual representations, and 5 points for cluttered design with poor information density. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the visualization accessible and cross-browser compatible?",
+      "description": "Judge whether the visualization is accessible to users with disabilities and works across modern browsers: 1) Color choices consider color blindness 2) Text elements are screen-reader friendly 3) Works consistently in Chrome, Firefox, Safari, and Edge. Deduct 3 points for each accessibility issue, 5 points for major cross-browser incompatibilities, and 5 points if the visualization is completely inaccessible to certain user groups. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "hard"
+}

package/library/data_science-data_visualization_dashboards/d3js-heatmap-from-scatter-data.json

@@ -0,0 +1,68 @@
+{
+  "index": 334,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable whenever possible. Given a large scatter dataset [x,y,value], create a heatmap using d3.js.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the core heatmap visualization properly implemented?",
+      "description": "Evaluate whether the code correctly creates a d3.js heatmap from [x,y,value] data. Check if it properly handles data binning, color mapping, and heat intensity visualization. Score 0 if the heatmap is not implemented, 5 if only basic visualization is present without proper data processing, and 10 if it includes proper data binning, smoothing, and appropriate color scales for the heatmap.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data processing and binning logic correctly implemented?",
+      "description": "Check whether the code includes adequate data processing for converting scattered [x,y,value] points into a gridded heatmap. Verify the binning algorithm (hexagonal or rectangular), density calculation method, and handling of overlapping points. Deduct 5 points if the binning algorithm is inefficient for large datasets (>1000 points), and 3 points if edge cases (like outliers or sparse areas) are not handled. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the color scale appropriately designed and implemented?",
+      "description": "Assess the color scale implementation – whether it uses appropriate sequential/diverging color schemes, provides proper contrast for data visibility, and includes color legend integration. The scale should respect perceptual uniformity and accessibility standards. Deduct 5 points if the color scale does not match data distribution, 3 points for poor color accessibility, and 2 points if no legend is provided. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are appropriate interactions and responsiveness implemented?",
+      "description": "Evaluate whether the heatmap includes useful interactions like tooltips for data points, zooming/panning capabilities, and whether it's responsive to different screen sizes. Check for smooth transitions when filtering or updating data. Deduct 3 points for each missing key interaction (tooltip, zoom, responsive sizing), and 5 points if transitions between data updates are jarring. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty datasets, non-numeric values, extremely large datasets, browser resize events, etc.) and provide friendly error handling or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic kernel density estimation 2. Animated transitions between different dataset views 3. Customizable smoothing parameters 4. Integration with statistical analysis tools). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant data processing loops that could be optimized 2. Function modules unrelated to heatmap visualization 3. Fancy effects that affect performance (e.g., unnecessary animations or DOM manipulations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/visualization/interaction logic), reusable components, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no performance optimizations for large datasets (>10,000 points). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern visualization principles: 1) Clean, non-distracting container design 2) Proper aspect ratio and use of space (data-ink ratio) 3) Professional labeling and typography (consistent font family, readable sizes). Deduct 3 points for cluttered axes or legends, 5 points for poor use of visualization space, and 5 points for inconsistent or unreadable text elements. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Hover feedback delay ≤ 100ms 2) Transition animation duration controlled between 200-400ms 3) Clear visual cues for interactive elements. Deduct 5 points for each interaction without feedback, 3 points for laggy rendering with large datasets, and 5 points for confusing or inconsistent interaction patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "hard"
+}

package/library/data_science-data_visualization_dashboards/dash-plotly-temperature-pressure-visualization.json

@@ -0,0 +1,68 @@
+{
+  "index": 1708,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable where possible. Create code for uploading data automatically through Dash and Plotly, and visualize it by time intervals and values of temperature and pressure.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the data uploading functionality properly implemented?",
+      "description": "Examine whether the code provides a complete file upload component in Dash that supports various file formats (CSV, Excel, JSON), with proper validation of file types and size limits. Check for clear user feedback during the upload process and appropriate error handling for invalid files. Score 0 if no upload functionality exists, 5 if basic upload exists but lacks validation, 10 if the upload component is robust with all necessary validations and user feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data parsing and preprocessing implemented effectively?",
+      "description": "Verify that the code includes proper parsing of uploaded data, handling of time-series conversion (string to datetime), data cleaning (removing nulls, duplicates), and appropriate sampling/aggregation for large datasets. Check for robust error handling for malformed data. Deduct 5 points if time parsing is incorrect, 3 points if data cleaning is absent, and 3 points if there's no handling for large datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the time interval visualization functionality correctly implemented?",
+      "description": "Evaluate whether the code implements time-based visualizations with proper time axis formatting, zoom/pan capabilities, and time interval selection tools. Check if users can select custom time ranges or use predefined intervals (hourly, daily, weekly, monthly). Deduct 5 points if the time axis is not properly formatted, 5 points if time interval selection is missing, and 3 points if zoom/pan capabilities are absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are temperature and pressure visualizations implemented with appropriate charts and features?",
+      "description": "Review if the code provides appropriate visualization types for temperature and pressure data (line charts, scatter plots, heatmaps), with proper color scales, legends, and dual y-axes where needed. Check for correlation views between temperature and pressure. Deduct 5 points if inappropriate chart types are used, 3 points if color scales are misleading, and 3 points if correlation views are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, incorrect data formats, server disconnection, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Dynamic statistical summary updates 2. Anomaly detection for temperature/pressure spikes 3. Interactive threshold alerts 4. Export options for visualizations). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant visualization components showing the same data in similar ways 2. Unnecessary data transformations that don't improve visualization quality 3. Excessive animations or effects that slow down performance without adding analytical value. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/visualization/callback functions), code reusability, and appropriate comments. Deduct 5 points if global variables are overused; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if critical sections lack comments or documentation. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the dashboard design follows modern design principles: 1) Harmonious color matching for temperature/pressure indicators (no more than 3 primary colors) 2) Proper layout spacing between charts and controls 3) Professional typography with consistent font sizes. Deduct 3 points for each cluttered dashboard section, 5 points for poorly contrasting colors that hinder data interpretation, and 5 points for inconsistent layout causing poor visual hierarchy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Chart updates occur within 300ms of user input 2) Smooth transitions when filtering or changing time intervals 3) Clear visual indication of loading states during data processing. Deduct 5 points for each interaction without feedback, 3 points for choppy animations during transitions, and 5 points for controls that don't visually indicate their state. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/data-analysis-dashboard-html-output.json

@@ -0,0 +1,68 @@
+{
+  "index": 754,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for demonstration. Help create a data analysis dashboard based on the file, output it in HTML format so that the dashboard can be viewed on computers or mobile phones.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the dashboard's data import and parsing mechanism properly implemented?",
+      "description": "Evaluate whether the code properly handles file uploads, parses different file formats (CSV, Excel, JSON), and includes error handling for invalid data. Check for sanitization of input data and proper memory management for large files. Score 0 if data import is missing, 5 if only basic parsing is implemented, and 10 if full validation, sanitization, and handling of multiple formats is included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the dashboard implement comprehensive data visualization components?",
+      "description": "Check for a variety of chart types (bar charts, line charts, pie charts, etc.) and their appropriateness for different data types. Assess whether charts include proper axes, legends, tooltips, and responsive scaling. Deduct 2 points for each missing essential chart type relevant to data analysis, and 3 points if interactive features (zoom, filtering) are absent. Give full points if visualizations are properly implemented with D3.js, Chart.js, or equivalent libraries.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are data filtering and manipulation capabilities implemented?",
+      "description": "Evaluate whether the dashboard allows users to filter, sort, and transform data dynamically. Check for features like date range selectors, category filters, search functionality, and real-time data updates. Deduct 3 points if filtering is limited to basic sorting, 5 points if dynamic filtering is absent, and 2 points if the filtering UI is not intuitive.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the responsive design properly implemented for cross-device compatibility?",
+      "description": "Check whether the dashboard properly adapts to different screen sizes (desktop, tablet, mobile) using media queries, flexible grids, and responsive design patterns. Verify that charts resize appropriately without loss of functionality. Deduct 5 points if the design breaks on mobile devices, 3 points if only partial responsiveness is implemented, and 2 points if touch interactions are not optimized for mobile users.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as malformed data, network interruption, browser compatibility issues) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered insights highlighting trends automatically 2. Export capabilities to multiple formats with customization 3. Dashboard state preservation between sessions). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple chart libraries doing the same thing) 2. Function modules unrelated to data analysis (e.g., unnecessary animations or decorations) 3. Fancy effects that affect performance (e.g., excessive 3D effects or transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/visualization/UI components), code organization patterns, and performance optimization. Deduct 5 points if global variable pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance considerations (like lazy loading or data pagination) are implemented. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the dashboard design follows modern design principles: 1) Harmonious color matching appropriate for data visualization (proper contrast, colorblind-friendly palette) 2) Proper layout with clear information hierarchy 3) Professional typography with appropriate font sizes for readability. Deduct 3 points for each cluttered dashboard section, 5 points for poor color choices that hinder data interpretation, and 5 points for inconsistent design patterns. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Chart animations and transitions complete within 300-500ms 2) Filter applications reflect immediately in visualizations 3) Clear loading states during data processing. Deduct 5 points for laggy interactions, 3 points for missing feedback during user actions, and 5 points for confusing navigation between dashboard sections. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/data-analysis-visual-presentation-html-output.json

@@ -0,0 +1,68 @@
+{
+  "index": 988,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Pay attention to ensuring that the generated code is executable for demonstration. Please analyze the data in the attachment and provide a visual presentation, outputting in HTML code format.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the data loading and parsing mechanism properly implemented?",
+      "description": "Review whether the code includes proper data loading methods (AJAX, fetch API, or FileReader) and correct parsing logic for different data formats (JSON, CSV, XML). Score 0 if no data loading/parsing is implemented, 5 if basic loading works but lacks error handling, and 10 if comprehensive loading with format detection and error handling is included.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is data preprocessing and transformation logic complete?",
+      "description": "Evaluate whether the code includes necessary data preprocessing steps such as cleaning (handling missing values, outliers), normalization, aggregation, and transformation to prepare raw data for visualization. Deduct 3 points if missing value handling is absent, 3 points if no data normalization when needed, and 4 points if data aggregation is missing for complex datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the visualization type appropriate for the data characteristics?",
+      "description": "Check whether the chosen visualization type (bar charts, line charts, scatter plots, etc.) matches the data properties and analysis goals. Score 0 if the visualization type completely mismatches the data (e.g., pie chart for time series), 5 if the visualization type is adequate but not optimal, and 10 if the visualization perfectly represents the data relationships and patterns.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are interactive elements implemented effectively?",
+      "description": "Assess whether the visualization includes appropriate interactive features (tooltips, filtering, zooming, drill-down capabilities) that enhance data exploration. Deduct 3 points for missing basic tooltips, 3 points for lack of filtering options when needed, and 4 points if no zoom/pan functionality is provided for complex visualizations. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as malformed data, browser compatibility issues, resizing windows, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Animated transitions between data views 2. Novel interaction methods 3. Integrated analytical insights alongside visualization). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple ways to filter the same data) 2. Function modules unrelated to the visualization task 3. Fancy effects that affect performance (e.g., excessive animations or 3D effects when unnecessary). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data handling/visualization rendering/interaction logic), code reusability, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if rendering performance is poor (visible lag on standard hardware). The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern visualization principles: 1) Harmonious color matching with appropriate contrast for data encoding 2) Proper layout with clear visual hierarchy 3) Professional typography with readable labels and legends. Deduct 3 points for each crowded visual element, 5 points for a color scheme that hinders data interpretation, and 5 points for poor labeling that makes the visualization hard to understand. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual feedback for interactive elements. Deduct 5 points for each operation without feedback, 3 points for janky animations during transitions, and 5 points for confusing interaction patterns. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/desktop-bi-analysis-software.json

@@ -0,0 +1,68 @@
+{
+  "index": 293,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the generated code is executable when possible. I want to create a desktop BI analysis software. Could you help me generate one that can import Excel files, properly map the imported fields, and automatically generate BI analysis reports?",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Excel import functionality properly implemented?",
+      "description": "Verify that the code can handle various Excel file formats (XLS, XLSX, CSV), supports multiple sheets, and properly manages data types during import (numbers, dates, text, etc.). Check for error handling for corrupted files, large datasets, and character encoding issues. Score 0 if import is not implemented, 5 if basic import exists with limitations, and 10 if the implementation is robust with comprehensive error handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the data field mapping system fully developed?",
+      "description": "Evaluate whether the code implements an intelligent field mapping system that can auto-detect data types, suggest appropriate mappings, and allow manual overrides. Check for data cleansing capabilities, handling of missing values, and validation of mapped fields. Deduct 3 points if automatic field type detection is missing, 3 points if there's no data preview functionality, and 4 points if field relationship detection is absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the BI analysis functions comprehensive and appropriate?",
+      "description": "Check whether the code includes essential BI analysis capabilities: descriptive statistics, trend analysis, correlation analysis, outlier detection, and predictive modeling. Verify that the analysis methods match the data types (categorical vs. numerical). Deduct 2 points for each missing core analysis function. Give 10 points if all essential analyses are implemented with appropriate algorithms and statistical validations.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the report generation system provide meaningful insights?",
+      "description": "Assess whether the automatic report generation system produces actionable insights rather than just raw data. Check if it includes anomaly highlighting, trend identification, key metric summaries, and comparative analysis. Verify that reports can be customized and saved in multiple formats (PDF, HTML, etc.). Deduct 3 points if insights are not highlighted, 3 points if export options are limited, and 4 points if report templates are missing. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as out-of-memory errors with large datasets, unexpected input values, application crashes). Check for proper exception handling, graceful degradation, and data recovery mechanisms. Code with strong robustness should provide meaningful error messages and recovery paths, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. AI-powered insight generation 2. Natural language query interface 3. Automatic dashboard recommendations based on data patterns 4. Real-time collaboration features). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant analysis calculations that could be optimized 2. Function modules unrelated to BI analytics (e.g., unnecessary multimedia features) 3. Resource-intensive visualizations that don't contribute to data understanding. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/analysis/visualization layers), unit test coverage, and performance optimization techniques. Deduct 5 points if global state management is poorly implemented; deduct 3 points if the code lacks comments and documentation; deduct 2 points if there's no consideration for memory management with large datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the UI follows modern data visualization principles: 1) Consistent data visualization style 2) Clear information hierarchy with proper emphasis on key metrics 3) Appropriate use of white space and grid alignment 4) Color schemes that account for data types and accessibility. Deduct 3 points for cluttered dashboards, 3 points for improper chart selection for data types, and 4 points for poor readability of data labels and values. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the interactive elements enhance data exploration: 1) Filtering and drill-down capabilities respond within 300ms 2) Smooth transitions between different views and analyses 3) Intuitive interactions for data selection and comparison. Deduct 3 points for laggy visualizations with large datasets, 3 points for unintuitive interaction patterns, and 4 points if essential interactions (zoom, filter, details-on-demand) are missing. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/drowning-victim-behavior-dashboard.json

@@ -0,0 +1,68 @@
+{
+  "index": 850,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable for demonstration. Create a comprehensive dashboard for drowning victim behavior description data, which should include a comparison of data between witnesses, rescuers, and drowning victims, visualization design, and detailed data presentation. Output in HTML format to ensure it's executable.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the dashboard data structure and model properly implemented?",
+      "description": "Review whether the code correctly implements data models for the three subject types (witnesses, rescuers, and drowning victims). Check if the data structure allows for comparison across these groups. The implementation should include data normalization and proper typing. Score 0 if data models are missing, 5 if basic models exist but lack comparative capabilities, and 10 if comprehensive models with comparison functionality are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are appropriate visualization components selected and implemented?",
+      "description": "Evaluate the selection and implementation of visualization components (charts, graphs, heatmaps, etc.) for drowning behavior data. Components should match the data type being displayed (e.g., timeline charts for temporal data, spatial visualizations for location data). Deduct 5 points if visualizations are inappropriate for the data type, 3 points if they lack interactivity. The visualizations must effectively communicate differences between the three stakeholder groups. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the comparative analysis functionality comprehensive?",
+      "description": "Check whether the dashboard effectively enables comparison between witness, rescuer, and victim data. Look for side-by-side visualizations, differential metrics, and highlighting of discrepancies. The system should provide both quantitative and qualitative comparison mechanisms. Deduct 5 points if comparison is limited to basic metrics, and 8 points if no meaningful comparison functionality exists. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the dashboard implement effective filtering and drill-down capabilities?",
+      "description": "Assess whether the code includes robust filtering mechanisms that allow users to focus on specific aspects of drowning behavior data. Check for time-based filters, demographic filters, environmental condition filters, and the ability to drill down into specific incidents. The implementation should maintain context during exploration. Deduct 5 points if filtering is basic, and 8 points if drill-down capabilities are absent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data fields, malformed data, empty datasets, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Machine learning-based pattern detection in drowning behavior 2. Augmented reality visualization of drowning scenarios 3. Multi-language support for international incident comparison). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualizations (e.g., multiple similar charts showing the same data) 2. Function modules unrelated to drowning behavior analysis (e.g., weather forecasting) 3. Fancy effects that affect performance (e.g., excessive animations that distract from data interpretation). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/visualization/UI layers), reusable components, and responsive design implementation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the dashboard is not responsive across device sizes. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching suitable for data visualization (consideration for colorblind users) 2) Proper layout spacing with clear information hierarchy 3) Professional typography system (clear labels, legible data points, consistent styling). Deduct 3 points for each cluttered visualization, 5 points for poor color choices that hinder data interpretation, and 5 points for inconsistent layout that disrupts the analytical flow. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Data filtering response time ≤ 200ms 2) Smooth transitions between different views/filters 3) Clear visual feedback for user interactions with data points. Deduct 5 points for laggy transitions between visualization states, 3 points for lack of hover/selection states on interactive elements, and 5 points for unintuitive navigation between dashboard sections. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/dual-curve-backtest-stock-returns-visualization.json

@@ -0,0 +1,68 @@
+{
+  "index": 987,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you provide is executable for demonstration. Include visualization with dual curves showing backtest returns and stock returns.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the backtesting system properly implemented?",
+      "description": "Review whether the code accurately implements the backtesting framework with proper time series handling, transaction cost modeling, and performance calculation. Score 0 if the backtesting logic is missing, 5 if only basic backtesting is implemented without accounting for market frictions, and 10 if slippage, commission, and other market mechanics are fully modeled.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the dual curve visualization correctly implemented?",
+      "description": "Evaluate whether the code includes a proper visualization component that clearly displays both backtest returns and stock returns on the same chart. Check for proper labeling, legends, time axis handling, and scaling methods. Deduct 5 points if curves lack proper scaling, 3 points if legends or axes are missing/unclear, and 2 points if the visualization is not interactive when it should be. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the data handling and financial calculations accurate?",
+      "description": "Assess the correctness of financial calculations such as returns, drawdowns, Sharpe ratio, and other performance metrics. Check if data preprocessing handles missing values, adjusts for splits/dividends, and maintains point-in-time integrity. Deduct 5 points for look-ahead bias, 3 points for incorrect return calculations, and 5 points for improper handling of financial time series data. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the code modular and reusable for different strategy implementations?",
+      "description": "Check whether the code architecture separates data handling, strategy logic, execution, and visualization components. The design should allow for easy swapping of different strategies or stocks while maintaining the same backtesting framework. Deduct 5 points if components are tightly coupled, 3 points if strategy parameters cannot be easily modified, and 2 points if the code doesn't support multiple asset types. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, outliers, API failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive drill-down into specific time periods 2. Risk attribution analysis 3. Automated strategy parameter optimization). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar calculations (e.g., multiple ways to calculate returns) 2. Function modules unrelated to financial analysis (e.g., excessive decorative elements) 3. Computationally expensive operations that don't add analytical value. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data acquisition/processing/visualization layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the visualization meet professional financial charting standards?",
+      "description": "Evaluate whether the charts follow financial industry standards: 1) Proper color scheme for gains/losses (typically green/red) 2) Clear labeling of key events and metrics 3) Appropriate scale for returns (log scale or percentage) 4) Inclusion of benchmark comparison. Deduct 3 points for each misleading visual element, 5 points for improper scaling that distorts performance perception, and 3 points for missing critical information like drawdowns or volatility. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the chart interaction smooth and informative?",
+      "description": "Judge whether the chart interactions enhance financial analysis: 1) Tooltips showing precise values on hover 2) Ability to zoom into specific time periods 3) Toggle visibility of different metrics 4) Export functionality for research purposes. Deduct 3 points for each missing key interaction, 5 points for laggy/unresponsive charts with large datasets, and 3 points for interactions that don't add analytical value. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}