@getollie/cli 0.0.4 → 0.2.0

package/library/data_science-data_visualization_dashboards/inverse-proportion-graphs-for-elementary-math.json

@@ -1,68 +0,0 @@
-{
-  "index": 1143,
-  "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 display. Generate code to plot inverse proportion graphs for sixth-grade elementary school mathematics.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the inverse proportion mathematical function correctly implemented?",
-      "description": "Review whether the code accurately implements the inverse proportion function y = k/x (where k ≠ 0) with proper mathematical calculation logic. Check if it handles different k values correctly and includes domain restrictions (x ≠ 0). Score 0 if the mathematical formula is incorrect, 5 if only basic calculation is implemented without domain handling, and 10 if the complete inverse proportion function with all mathematical properties is accurately represented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the graph plotting functionality comprehensively implemented?",
-      "description": "Evaluate whether the plotting system includes proper coordinate system setup, axis labeling, grid lines, and smooth curve rendering for hyperbola branches in both positive and negative quadrants. Check if the graph accurately represents the asymptotic behavior at x=0 and y=0. Deduct 5 points if asymptotes are not properly handled, 3 points if only one quadrant is plotted. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are interactive features suitable for sixth-grade learning implemented?",
-      "description": "Check whether the code includes age-appropriate interactive elements such as parameter adjustment (changing k values), point coordinates display on hover, and clear visual feedback. Evaluate if the interface provides educational tooltips or hints about inverse proportion properties. Deduct 5 points if no interactivity is provided, 3 points if interactions are too complex for elementary students. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the educational content mathematically accurate and grade-appropriate?",
-      "description": "Assess whether the implementation correctly demonstrates key inverse proportion concepts suitable for sixth-grade level: relationship between variables, hyperbola shape, and practical applications. Check if examples and explanations match curriculum standards. Deduct 5 points if mathematical concepts are too advanced, 3 points if key learning objectives are missing. Give 10 points if content perfectly aligns with sixth-grade mathematics curriculum.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as division by zero, invalid input values, 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 enhance learning?",
-      "description": "Check whether the code includes educational enhancements that improve learning experience (e.g., 1. Animation showing how the curve changes with different k values 2. Real-world problem examples with inverse proportion 3. Interactive quizzes or exercises). Add 3 points for each practical educational 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 plotting functions (e.g., multiple graphing libraries coexisting) 2. Function modules unrelated to mathematics education (e.g., social media sharing buttons) 3. Overly complex features inappropriate for sixth-grade level (e.g., advanced calculus annotations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core educational 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 math calculation/visualization/interaction layers), code organization, and maintainability. Deduct 5 points if global state pollution is found or no clear code structure exists; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the code lacks proper documentation for educational use. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet educational and professional standards?",
-      "description": "Evaluate whether the visual design follows educational interface principles: 1) Age-appropriate color scheme (bright but not distracting) 2) Clear mathematical notation and readable fonts (≥ 16px for better readability) 3) Intuitive layout with proper visual hierarchy for learning materials. Deduct 3 points for each confusing visual element, 5 points for color combinations that strain young eyes, and 5 points for unclear mathematical symbols or labels. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Are the dynamic interactions smooth and educationally effective?",
-      "description": "Judge whether the interactive elements enhance learning experience: 1) Immediate visual feedback when parameters change (≤ 200ms response time) 2) Smooth graph transitions that help students understand mathematical relationships 3) Clear visual cues for interactive elements. Deduct 5 points for each unresponsive interaction, 3 points for confusing transition effects, and 5 points for hidden or unclear interactive controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/javascript-module-dlis-imaging-log-curves-web-page.json

@@ -1,68 +0,0 @@
-{
-  "index": 733,
-  "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. Write a JavaScript module for displaying DLIS imaging log curves on a web page, with capabilities for panning, zooming, and other operations.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the DLIS file parsing implementation complete?",
-      "description": "Check if the code properly implements DLIS (Digital Log Interchange Standard) file parsing functionality, including handling of frame data, channel information, and curve data extraction. Score 0 if no DLIS parsing is implemented, 5 if only basic channel extraction is handled, and 10 if full DLIS standard compliance (including handling of complex frame structures, multi-frame data, and attribute metadata) is achieved.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the imaging log curves visualization components implemented correctly?",
-      "description": "Evaluate if the visualization accurately renders different curve types (density logs, resistivity logs, sonic logs, etc.) with appropriate scales, units, and visual representation. The implementation should include proper axis labeling, depth tracking, curve coloring based on log type, and handling of missing/null values in the data. Deduct 3 points if curve styling is incorrect, 5 points if depth tracking is inaccurate, and 3 points if null values aren't handled properly. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is interactive panning functionality properly implemented?",
-      "description": "Assess whether smooth panning of log curves is implemented with proper event handling (mouse drag, touch swipe), boundary constraints, and performance optimization. The implementation should maintain context during panning and handle both vertical (depth) and horizontal (time/value) panning. Deduct 5 points if panning is jerky or has performance issues with large datasets, and 3 points if boundary constraints are missing. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is interactive zooming functionality properly implemented?",
-      "description": "Check if zooming functionality includes both discrete zoom levels and continuous zooming, preserves the point of interest during zoom operations, and handles appropriate resampling/redrawing of curves at different zoom levels. The implementation should support mouse wheel, pinch gesture, and button-based zoom controls. Deduct 5 points if zooming causes visual artifacts, 3 points if zoom center point is incorrect, and 3 points if data resampling is inefficient. 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 DLIS data, browser compatibility issues, memory constraints with large logs, 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. Real-time depth correlation between multiple logs 2. Interactive curve filtering/highlighting 3. Log curve statistical analysis overlays). 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 visualization functions (e.g., multiple rendering engines coexisting) 2. Function modules unrelated to log visualization (e.g., unnecessary 3D effects) 3. Fancy effects that affect performance (e.g., excessive animations or rendering filters). 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 layers), unit test coverage, 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 no performance optimization exists for handling large log datasets. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional domain standards?",
-      "description": "Evaluate whether the visualization follows geoscience/petroleum engineering visualization standards: 1) Industry-standard curve color coding 2) Proper depth scale representation 3) Professional grid and annotation system. Deduct 3 points for non-standard log curve representation, 5 points for inaccurate depth visualization, and 5 points for poor data value readability. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether the interactive performance meets professional requirements: 1) Rendering updates within 60ms for smooth scrolling 2) Data loading/processing feedback for large logs 3) Responsive design across different screen sizes. Deduct 5 points for frame drops during scrolling/zooming, 3 points for inefficient canvas/SVG rendering techniques, and 5 points for poor handling of large datasets (>10MB). The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "hard"
-}

package/library/data_science-data_visualization_dashboards/javaweb-echarts-data-visualization-miniprogram.json

@@ -1,68 +0,0 @@
-{
-  "index": 1409,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure to ensure the generated code is executable for demonstration. Write a complete data visualization page using the MVC pattern in Javaweb and echarts that can interact with a mini-program.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the MVC architecture properly implemented in the JavaWeb application?",
-      "description": "Evaluate whether the code clearly separates Model (data handling), View (presentation), and Controller (business logic) components. Check for proper package structure, clear responsibilities between layers, and absence of logic leakage across layers. Score 0 if MVC is not implemented, 5 if basic separation exists but with some mixed responsibilities, and 10 if the architecture follows industry best practices with clean separation of concerns.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the ECharts implementation complete and correctly configured?",
-      "description": "Review whether ECharts is properly initialized, options are correctly configured, and data binding is implemented. Check for proper chart type selection based on data characteristics, responsive design implementation, and theme configuration. Deduct 3 points if chart options are incomplete, 5 points if charts don't adapt to container size changes, and 5 points if data binding mechanisms are missing or incorrect. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the mini-program interaction interface properly designed and implemented?",
-      "description": "Evaluate whether the code implements a clear API for mini-program communication (RESTful API, WebSocket, etc.), includes authentication mechanisms, proper data serialization/deserialization, and error handling. Deduct 5 points if no authentication is implemented, 3 points if error responses aren't standardized, and 5 points if the API doesn't follow best practices for mini-program interaction. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the data flow between components efficient and properly implemented?",
-      "description": "Check whether data transfer between backend, frontend visualization, and mini-program is optimized. Look for proper data transformation layers, caching mechanisms, and asynchronous loading patterns. Deduct 5 points if large datasets aren't paginated or chunked, 3 points if data isn't appropriately transformed for visualization, and 5 points if there's no real-time data refresh mechanism. 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 invalid input data, network errors, chart rendering 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 visualizations 2. Real-time collaborative viewing 3. AI-powered data insights 4. Custom theme switching). 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 visualization components 2. Function modules unrelated to data visualization 3. Fancy effects that affect performance (e.g., excessive animations or 3D effects that slow down rendering). 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 frontend/backend concerns, visualization logic/data processing), 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 interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern visualization design principles: 1) Harmonious color matching for charts and UI (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times) 4) Clear visual hierarchy for data visualization. Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for poor data-ink ratio. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the visualization interactions conform to human perception characteristics: 1) Chart hover/click feedback delay ≤ 100ms 2) Transition animations controlled between 300-500ms 3) Clear visual focus guidance 4) Intuitive controls for data exploration. Deduct 5 points for each operation without feedback, 3 points for laggy chart transitions during interactions, and 5 points for confusing or hidden interaction controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/job-displacement-risk-public-administration-digital-transformation-line-chart.json

@@ -1,68 +0,0 @@
-{
-  "index": 976,
-  "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. Create a line chart showing the risk of job displacement for the Public Administration major under the impact of digital transformation. Output in HTML format and ensure it is executable.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the data structure and content of the job displacement risk chart scientifically reasonable?",
-      "description": "Review whether the code includes realistic and reasonable data points for Public Administration job displacement risk under digital transformation. The data should cover multiple time periods (at least 5-10 years), include multiple risk dimensions (automation risk, skill gap, digital adaptation rate, etc.), and have logical data trends. Score 0 if using random or unrealistic data, 5 if basic trend data is provided but lacks depth, and 10 if comprehensive multi-dimensional risk data with proper scientific basis is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the line chart visualization technically complete and accurate?",
-      "description": "Check whether the HTML/JavaScript implementation correctly renders a professional line chart with proper axes, labels, legends, and data plotting. Must include responsive design, proper scaling, grid lines, data point markers, and tooltip functionality. Deduct 5 points if missing essential chart elements (axes labels, legend), 3 points if data plotting is inaccurate, and 3 points if the chart is not responsive. Full score requires complete technical implementation.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are interactive features and data exploration capabilities properly implemented?",
-      "description": "Evaluate whether the chart includes meaningful interactive features such as hover effects showing detailed risk values, clickable legend filtering, zoom functionality, or time period selection. The interactions should enhance data understanding rather than being decorative. Deduct 5 points if no interactive features exist, 3 points if interactions are buggy or unresponsive, and 2 points if interactions don't provide meaningful data insights. Full score for smooth, purposeful interactivity.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is contextual information and analytical depth adequately provided?",
-      "description": "Check whether the visualization includes proper context such as data sources, methodology explanation, risk factor definitions, and analytical insights about Public Administration digital transformation impact. Should include annotations for significant trend changes or key inflection points. Deduct 5 points if no contextual information is provided, 3 points if explanations are superficial, and 2 points if missing data source attribution. Full score requires comprehensive analytical context.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data points, browser compatibility issues, rendering errors, invalid data inputs, etc.) and provide friendly error handling or fallback mechanisms. Code with strong robustness should gracefully handle edge cases and provide clear error messages. Give 10 points if fully robust, 5 points if average robustness, and 0 points if no error handling exists.",
-      "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 data visualization experience (e.g., 1. Comparative overlay with other majors 2. Predictive trend modeling 3. Risk factor breakdown animations 4. Export functionality for reports). Add 3 points for each practical innovative feature implemented (maximum 10 points). Features must be functional and add real value to the analysis.",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization functions (e.g., multiple chart libraries coexisting) 2. Function modules unrelated to risk analysis (e.g., built-in games or music) 3. Excessive decorative effects that distract from data insights (e.g., spinning animations, flashy transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if core data visualization is compromised by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separating data processing/visualization/interaction layers), code organization, commenting quality, and maintainability. Deduct 5 points if global namespace pollution is found or no clear code structure exists; deduct 3 points if code lacks proper comments or documentation; deduct 5 points if the code is not modular or reusable. Full score requires clean, well-organized, professional code structure.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional data visualization standards?",
-      "description": "Evaluate whether the design follows data visualization best practices: 1) Professional color scheme suitable for data representation (avoiding misleading colors) 2) Proper typography hierarchy and readability (chart title, axis labels, legends clearly distinguishable) 3) Appropriate spacing and layout following design principles 4) Accessibility considerations. Deduct 3 points for poor color choices that hinder data interpretation, 5 points for illegible text or poor typography, and 5 points for cluttered or unprofessional layout.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the data visualization interaction smooth and intuitive?",
-      "description": "Judge whether the interactive elements provide immediate and clear feedback: 1) Hover effects respond within 100ms 2) Smooth transitions that aid data comprehension (200-400ms duration) 3) Clear visual hierarchy and focus management 4) Intuitive navigation and data exploration flow. Deduct 5 points for each interaction without proper feedback, 3 points for jarring or slow animations, and 5 points for confusing or non-intuitive user interface elements.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/logistics-flow-map-top-20-countries.json

@@ -1,68 +0,0 @@
-{
-  "index": 1303,
-  "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 when possible. Help me write a Python program to create a graphical representation of the logistics flow map for the top 20 countries in a panoramic view.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Data acquisition and preprocessing implementation",
-      "description": "Evaluate whether the code includes proper data acquisition methods (API calls, CSV imports, or database connections) and thorough data preprocessing. Check for data cleaning, normalization, and handling of missing values. Assess whether the top 20 countries are properly identified based on appropriate metrics (trade volume, GDP, etc.). Score 0 if data acquisition is missing, 5 if basic data handling is present but incomplete, and 10 if comprehensive data pipeline with validation is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Logistics flow visualization accuracy",
-      "description": "Check whether the visualization accurately represents logistics flows between countries using appropriate visual elements (arrows, line thickness for volume, color coding for direction/type). Verify if the flow magnitude is properly scaled and if the directionality is clear. Deduct 5 points if flows lack directional indicators, 3 points if scaling is inconsistent, and 3 points if the visualization misrepresents actual data patterns. Full score requires both accuracy and clarity in flow representation.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Panoramic view implementation",
-      "description": "Assess whether the code creates a true panoramic view showing all connections simultaneously. Verify the use of appropriate map projections (e.g., Mercator, Robinson, or Mollweide) that minimize distortion for global visualization. Check if the view allows for comprehensive understanding of global logistics patterns. Score 0 if the view is fragmented, 5 if basic global visualization is present but with significant distortion, and 10 if a well-implemented panoramic projection is used.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Interactive elements and functionality",
-      "description": "Evaluate the implementation of interactive elements such as zooming, panning, filtering by trade type/volume, and country selection. Check whether tooltips display relevant data on hover and if the interactivity enhances data exploration. Deduct 5 points if basic interactions are missing, 3 points if interactions are implemented but buggy, and 2 points if tooltips lack detailed information. The full score requires smooth, intuitive interactions.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, API failures, invalid inputs, 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. Time-series animation of flow changes 2. Comparative analysis tools 3. Prediction modeling of future flows). 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 visualization functions 2. Function modules unrelated to logistics flow mapping 3. Fancy effects that affect performance and readability (e.g., unnecessary 3D effects or animations). 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 layers), function documentation, and code maintainability. Deduct 5 points if global variable 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 comments or documentation. 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 modern data visualization principles: 1) Appropriate color scheme (colorblind-friendly, meaningful color mapping) 2) Clean layout with proper legends and labels 3) Balanced visual hierarchy that guides attention to important patterns. Deduct 3 points for cluttered visuals, 5 points for misleading color schemes, and 5 points for poor use of visual space. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the visualization performance optimized?",
-      "description": "Judge whether the visualization handles large datasets efficiently: 1) Rendering optimization for many data points 2) Appropriate use of aggregation or binning for dense data 3) Memory management for large datasets. Deduct 5 points for noticeable lag with full dataset, 3 points for inefficient data structures, and 5 points if the visualization crashes with the complete dataset. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "medium"
-}

package/library/data_science-data_visualization_dashboards/medical-visualization-dashboard-html.json

@@ -1,68 +0,0 @@
-{
-  "index": 407,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Try to ensure that the code generated is executable and can be displayed.\n\n```python\nfrom flask import app, jsonify\nfrom pyspark import SparkConf\nfrom pyspark.sql.session import SparkSession\n\nsparkconf = SparkConf() \\\n    .setMaster(\"local[*]\") \\\n    .setAppName(\"MartialArtsProfessional\") \\\n    .set(\"hive.metastore.uris\", \"thrift://node1:9083\") \\\n    .set(\"spark.sql.warehouse.dir\", \"hdfs://node1:8020/user/hive/warehouse\") \\\n    .set(\"hive.metastore.schema.verification\", \"true\") \\\n    .set(\"hive.metastore.schema.version.record\", \"true\") \\\n    .set(\"spark.sql.hive.convertMetastoreOrc\", \"false\") \\\n    .set(\"spark.sql.shuffle.partitions\", \"8\")\n\nspark = SparkSession.Builder() \\\n    .config(conf=sparkconf) \\\n    .enableHiveSupport() \\\n    .getOrCreate()\nspark.sql(\"select * from ads_medical_system.department_analysis\").show()\n\n\n@app.route(\"/department\", methods=[\"GET\"])\ndef department_analysis():\n    '''\n    Department analysis\n    '''\n    df = spark.sql(\"select department,total_visits from ads_medical_system.department_analysis\")\n    return jsonify(df.collect())\n\n\n@app.route(\"/avg_fee\", methods=[\"GET\"])\ndef avg_fee_analysis():\n    '''\n    Average fee analysis\n    '''\n    df = spark.sql(\"select department,avg_fee from ads_medical_system.department_analysis\")\n    return jsonify(df.collect())\n\n\n@app.route(\"/avg_workday_fee\", methods=[\"GET\"])\ndef avg_workday_fee_analysis():\n    '''\n    Average workday fee analysis\n    '''\n    df = spark.sql(\"select department,avg_workday_fee from ads_medical_system.department_analysis\")\n    return jsonify(df.collect())\n\n\n@app.route(\"/avg_holiday_fee\", methods=[\"GET\"])\ndef avg_holiday_fee_analysis():\n    '''\n    Average holiday fee analysis\n    '''\n    df = spark.sql(\"select department,avg_holiday_fee from ads_medical_system.department_analysis\")\n    return jsonify(df.collect())\n\n\n@app.route(\"/visit_rank\", methods=[\"GET\"])\ndef visit_rank_analysis():\n    '''\n    Visit volume ranking\n    '''\n    df = spark.sql(\"select department,visit_rank from ads_medical_system.department_analysis\")\n    return jsonify(df.collect())\n\n@app.router(\"/unique_patients\", methods=[\"GET\"])\ndef unique_patients_analysis():\n    '''\n    Unique patient count analysis\n    '''\n    df = spark.sql(\"select department,unique_patients from ads_medical_system.department_analysis\")\n    return jsonify(df.collect())\n\n\n@app.router(\"/most_common_test\", methods=[\"GET\"])\ndef most_common_test_analysis():\n    '''\n    Most common examination items\n    '''\n    df = spark.sql(\"select most_common_test,avg_holiday_fee from ads_medical_system.department_analysis\")\n    return jsonify(df.collect())\n\n@app.router(\"/age\", methods=[\"GET\"])\ndef age():\n    df=spark.sql(\"select age,count(1) as result from dim_medical_system.dim_patient\")\n    return jsonify(df.collect())\n```\n\nUsing these interfaces, create a visually stunning medical visualization dashboard with HTML. The frontend code should run normally. Please provide complete code for each chart in a single HTML file.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the medical dashboard visualization fully implemented?",
-      "description": "Review whether the code creates a comprehensive dashboard that visualizes all the available API endpoints: department analysis, average fees (regular, workday, holiday), visit rankings, unique patients, common tests, and age distribution. Score 0 if visualization is missing, 5 if only basic charts are implemented, and 10 if all endpoints are visualized with appropriate chart types (bar charts, line charts, pie charts, etc.) for each data type.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is data fetching and integration properly implemented?",
-      "description": "Check whether the frontend properly handles API requests to all 8 endpoints, including error handling for failed requests, loading states, and data transformation before visualization. Verify that the code correctly parses the JSON responses from Flask endpoints. Deduct 3 points for each missing endpoint integration, and 5 points if there's no error handling or loading indicators. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the dashboard layout and organization properly structured?",
-      "description": "Evaluate whether the dashboard follows best practices in information architecture: logical grouping of related metrics (e.g., fee-related charts together), hierarchical information display (overview first, details on demand), and responsive design principles. Deduct 5 points if charts are randomly placed without logical organization, and 5 points if the layout breaks on different screen sizes. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are interactive features implemented to enhance data exploration?",
-      "description": "Assess whether the dashboard includes interactive elements such as filtering capabilities, drill-down options, tooltips for detailed information, zoom functionality for dense visualizations, and cross-filtering between charts. Give 2 points for each well-implemented interactive feature up to a maximum of 10 points. Score 0 if no interactive features are implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API failures, empty data responses, unexpected data formats, 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. Auto-refreshing data 2. Export functionality for reports 3. Custom theming options 4. User-configurable dashboard layout). 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 charts showing the same data) 2. Visualization elements unrelated to medical data (e.g., irrelevant animations) 3. Fancy effects that affect performance (e.g., heavy animations causing lag). 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 fetching/processing/visualization logic), code reusability for chart generation, and proper script organization. Deduct 5 points if global variable pollution is found; deduct 5 points if there's significant code duplication across chart implementations; deduct 5 points if there's no separation between data processing and visualization. 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 medical context (calming blues/greens, clear contrast for data) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times). Deduct 3 points for each crowded visual element, 5 points for inappropriate color schemes for medical data, and 5 points for chaotic chart arrangement. 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 loading and transitions complete within 500ms 2) Interactive feedback delay ≤ 100ms 3) Clear visual cues for interactive elements. Deduct 5 points for sluggish chart rendering, 3 points for delayed interaction feedback, and 5 points for hidden or unclear interactive controls. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/mobile-executive-data-platform-product.json

@@ -1,68 +0,0 @@
-{
-  "index": 1262,
-  "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. Based on the uploaded operational data, create a data platform product for mobile devices for use by company executives.\n\nThe indicators at the top of the document are the metrics that executives are particularly concerned with. The first column of the document records all data from January 1, 2025 to March 10, 2025, where \"Group,\" \"Team,\" \"Region,\" \"Market,\" and \"Platform\" are dimensional data. Among them: Region stores several countries or regional areas, Market stores the names of countries and regions, and Platform is the platform that generates business volume. Order quantity, sales amount, receipt amount, spending, new product count, active product count are all natural indicators, while average order value, ROI, receipt rate, and return rate are derived indicators calculated from natural indicators using formulas. See the formulas in each cell of the document for calculation details.\n\nFlexibly utilize the combinations of dimensions and indicators in the document to create an HTML page for a mobile commerce data platform product suitable for company executives, and integrate it into a larger HTML page for display.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Executive Data Dashboard Implementation",
-      "description": "Evaluate whether the code implements a comprehensive executive dashboard that displays key metrics (order quantity, sales amount, receipt amount, spending, new product count, active product count, average order value, ROI, receipt rate, return rate) in an organized and easily scannable format. The implementation should prioritize the metrics explicitly mentioned as being of particular concern to executives.0 points if core metrics are missing, 5 points if basic metrics are displayed without proper organization, 10 points for a complete implementation with all required metrics visually highlighted for executive focus.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Dimensional Data Filtering & Exploration",
-      "description": "Check if the implementation allows executives to explore data across all required dimensions (Group, Team, Region, Market, Platform). The interface should enable filtering and drill-down capabilities appropriate for mobile executive use, with special attention to the hierarchical relationship between Region and Market.Deduct 2 points for each missing dimension filter. Deduct 5 points if hierarchical relationship between Region and Market is not properly implemented. Full score requires intuitive dimension navigation suitable for executive users.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Time Series Analysis & Trending",
-      "description": "Assess if the code provides time series visualization for the date range (January 1, 2025 to March 10, 2025) with appropriate granularity options (daily, weekly, monthly). Executives should be able to identify trends and patterns over time for key metrics.Deduct 5 points if time navigation is missing or severely limited. Deduct 3 points if trend visualization is basic without comparison functionality. Full score requires interactive time series charts with trend indicators and period-over-period comparisons.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Derived KPI Calculation Accuracy",
-      "description": "Verify that derived indicators (average order value, ROI, receipt rate, return rate) are calculated correctly according to the formulas provided in the document. The implementation should show both the result and provide access to the calculation method for transparency.Deduct 3 points for each incorrectly calculated derived metric. Deduct 2 points if the calculation method isn't accessible or transparent. Full implementation requires accurate calculations with tooltips or information panels explaining formulas.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Code Robustness",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, loading failures, filter combinations with no results, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases.0 points if no error handling exists, 5 points if basic error handling is present but not comprehensive, 10 points for robust error handling with user-friendly recovery options and appropriate executive-level messaging.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Innovative Executive Features",
-      "description": "Check whether the code includes surprise features that enhance the executive experience (e.g., 1. Automated insights highlighting significant changes 2. Executive summary with AI-generated narrative 3. One-click sharing to executive meetings 4. Custom alert thresholds for KPIs).Add 3 points for each practical innovative feature implemented specifically for executive users (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Redundant Features",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualizations 2. Function modules unrelated to executive decision-making 3. Fancy effects that affect mobile performance and distract from data comprehension.Deduct 3 points for each redundancy found, and directly deduct 10 points if core executive functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Code Engineering Quality",
-      "description": "Review modular design (such as separating data processing/visualization/interaction layers), reusable components, and mobile-specific optimizations. Analyze whether the code structure supports future extensions with new metrics or dimensions.Deduct 5 points if global state management is poor or design patterns are not used; deduct 5 points if code duplication rate is high; deduct 5 points if mobile optimization is insufficient (e.g., no consideration for touch interactions, offline capabilities). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Executive UI/UX Design Quality",
-      "description": "Evaluate whether the interface follows executive dashboard design principles: 1) Clean visual hierarchy highlighting key metrics 2) Proper information density for mobile screens (not overcrowded) 3) Professional typography system with excellent readability on mobile devices 4) Color coding that effectively communicates performance status (red/yellow/green or similar).Deduct 3 points for cluttered layouts, 5 points for poor information hierarchy, 3 points for hard-to-read text on mobile, and 3 points for ineffective use of color for status indication. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Mobile-First Interaction Design",
-      "description": "Judge whether the mobile interactions account for executive usage patterns: 1) Touch-optimized elements (min tap target size ≥ 44px) 2) One-handed operation capability for critical functions 3) Fast-loading visualizations (<2s) 4) Gesture support for common data exploration tasks 5) Orientation adaptability.Deduct 2 points for each mobile interaction pattern violation. Deduct 5 points if the interface requires constant zooming or precision tapping. Deduct 3 points if performance is sluggish on mobile devices. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "hard"
-}

package/library/data_science-data_visualization_dashboards/monthly-electricity-sales-and-prices-trend-chart.json

@@ -1,68 +0,0 @@
-{
-  "index": 442,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Make sure the generated code is executable for demonstration. Please quickly check the uploaded data. Draw a monthly trend chart of electricity sales and electricity prices. Present the analysis results in chart form and generate an HTML format file.\n\nRequirements: Generate HTML format results, ensure the code complies with W3C standards, with no errors or compatibility issues. Strictly verify the code, promptly correct error messages, and ensure the website's stability and accessibility.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the data loading and parsing functionality properly implemented?",
-      "description": "Check if the code correctly loads the uploaded data, handles various formats (CSV, Excel, JSON), and properly parses numeric values for electricity sales and prices. Score 0 if data loading is missing, 5 if basic loading exists but with format limitations, 10 if robust parsing with error handling is implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the monthly trend chart for electricity sales and prices accurately visualized?",
-      "description": "Evaluate whether the visualization correctly displays both electricity sales and price trends over months, with proper axes, scales, and data mapping. Check for dual Y-axes or appropriate normalization methods for displaying different units. Deduct 5 points if only one metric is shown, 3 points if scales are inappropriate for data ranges. Full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are appropriate chart types and visualization libraries utilized?",
-      "description": "Assess the choice of visualization library (D3.js, Chart.js, Highcharts, etc.) and chart type (line, area, combo) for representing time-series data. The implementation should leverage the library's features for responsive design and interactivity. Deduct 5 points for inappropriate chart type selection, 3 points for missing legend or inadequate labeling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is there adequate data analysis functionality included?",
-      "description": "Check if the code incorporates analysis features such as trend identification, correlation calculation between sales and prices, moving averages, or highlighting significant changes. Deduct 5 points if only raw data is displayed without any analysis, 3 points if analysis is superficial. Full score requires meaningful insights extraction from the data. 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 points, invalid data formats, 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. Interactive tooltips with additional metrics 2. Data filtering/zooming capabilities 3. Predictive trend lines or forecasting). 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 charting functions 2. Excessive visualization elements unrelated to electricity data analysis 3. Fancy effects that affect performance (e.g., unnecessary animations 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, and adherence to W3C standards. Deduct 5 points if global namespace pollution is found; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are W3C validation errors. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the chart design follows modern data visualization principles: 1) Harmonious color palette that distinguishes data series 2) Proper chart proportions and axis scales 3) Professional typography for labels and legends (readable font sizes, consistent styling). Deduct 3 points for poor color choices that hinder data interpretation, 5 points for misleading visual representations, and 5 points for cluttered axes or legends. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether the chart provides appropriate interactive features: 1) Responsive design that adapts to different screen sizes 2) Smooth transitions when hovering or filtering data 3) Accessible interaction methods (keyboard navigation, screen reader support). Deduct 5 points for non-responsive design, 3 points for jarring transitions or delayed rendering, and 5 points for inaccessible interaction patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}