@getollie/cli 0.0.1

package/library/data_science-data_visualization_dashboards/html-quadratic-function-graph-plotter.json

@@ -0,0 +1,68 @@
+{
+  "index": 1496,
+  "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. I'm a programming beginner, and I want to create an application that plots a quadratic function graph based on coefficients a, b, and c using a programming language. Please recommend detailed step-by-step instructions for implementing this with HTML.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the quadratic function plotting functionality fully implemented?",
+      "description": "Review whether the code accurately implements the plotting of a quadratic function (y = ax² + bx + c) with correct mathematical calculations. Check if the graph correctly responds to different coefficient values (a, b, c) and handles edge cases (e.g., a=0). Score 0 if plotting is not implemented, 5 if only basic plotting is done, and 10 if the implementation includes proper scaling and axis display.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the user interface for coefficient input well-designed?",
+      "description": "Evaluate the user interface for inputting coefficients a, b, and c. Check if the input fields are clearly labeled, have appropriate validation, and provide immediate feedback. Score 0 if there's no input interface, 5 if basic inputs are present but lack validation or clear labeling, and 10 if the interface is intuitive with proper validation and real-time feedback.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the graph visualization properly implemented with axis scaling?",
+      "description": "Check if the visualization includes proper axis scaling, grid lines, and labels. The graph should adapt to different coefficient values by appropriately adjusting the viewport. Deduct 5 points if the scaling is fixed and doesn't adapt to function behavior, 3 points if axes aren't labeled, and 2 points if grid lines are missing or inconsistent. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Does the implementation include interactive features for better understanding?",
+      "description": "Assess whether the solution includes interactive features like zooming, panning, displaying coordinates on hover, or animating the effect of changing coefficients. Deduct 5 points if no interactive features are implemented, and give full 10 points only if multiple meaningful interactive elements enhance the learning experience.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as non-numeric inputs, extreme coefficient values, browser resizing, 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. Displaying the function formula with proper mathematical notation 2. Showing important points like vertex, x-intercepts, or y-intercept 3. Allowing comparison of multiple functions). 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 graphing functions 2. Function modules unrelated to the quadratic function visualization 3. Fancy effects that affect performance without adding educational 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 calculation logic/view rendering/user interaction), code organization, and maintainability. Deduct 5 points if global state pollution is found or if there's no separation of concerns; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there are no comments explaining complex calculations. 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 (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). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. 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) Graph updates within 100ms after coefficient changes 2) Smooth transitions when the graph changes 3) Clear visual focus on important elements of the function. Deduct 5 points for each operation without feedback, 3 points for jerky graph updates, and 5 points for confusing interface interactions. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/html-rose-chart-housing-prices-chinese-cities.json

@@ -0,0 +1,68 @@
+{
+  "index": 846,
+  "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 demonstration. You are a data analysis expert, please help create an HTML-formatted rose chart for analyzing housing prices across 100 Chinese cities.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the rose chart visualization accurately implemented?",
+      "description": "Review whether the code correctly implements a rose chart (polar area chart) using HTML/JavaScript/SVG or Canvas, with proper polar coordinate system transformation and radial data representation. Check if housing price data for 100 Chinese cities is properly mapped to angular segments and radial distances. Score 0 if basic chart structure is missing, 5 if only simple polar visualization is implemented, and 10 if complete rose chart with accurate data binding and polar geometry is fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the housing price data structure properly designed and processed?",
+      "description": "Evaluate whether the code includes appropriate data structures for storing 100 Chinese cities' housing price information (city name, price, region classification, etc.) and implements proper data preprocessing (normalization, sorting, grouping). Check if data validation and error handling for missing or invalid price data is included. Deduct 5 points if data structure is poorly designed, 3 points if no data validation exists. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are interactive analysis features comprehensively implemented?",
+      "description": "Check whether the rose chart includes essential interactive features: hover tooltips showing detailed city information, click-to-highlight specific cities or regions, zoom/pan capabilities, and filtering options (by price range, region, city tier). Evaluate if smooth transitions and animations are provided during interactions. Deduct 5 points if basic hover interactions are missing, 3 points if no filtering mechanism exists. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the data analysis functionality complete and insightful?",
+      "description": "Assess whether the implementation provides meaningful analytical capabilities: statistical summaries (average, median, quartiles), regional comparisons, trend identification, and data export functionality. Check if the visualization effectively communicates housing price patterns across different city tiers and regions. Deduct 5 points if no statistical analysis is provided, 3 points if regional grouping is missing. Give 10 points if comprehensive analysis features are implemented.",
+      "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 price values, browser compatibility issues, large dataset rendering performance) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle these edge cases, giving 10 points. If 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 analysis experience (e.g., 1. Real-time price comparison with national average 2. Animated timeline showing price trends 3. Geographic clustering visualization 4. Price prediction indicators). 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 chart types (e.g., multiple rose chart libraries coexisting) 2. Function modules unrelated to housing price analysis (e.g., built-in weather widgets) 3. Fancy effects that affect chart readability (e.g., excessive 3D transforms, distracting particle effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if core visualization 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), reusable component structure, and proper documentation. Deduct 5 points if global state pollution is found or no separation of concerns exists; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if no proper commenting or documentation exists. 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 data visualization principles: 1) Harmonious color scheme suitable for data analysis (proper contrast ratios, colorblind-friendly palette) 2) Appropriate chart proportions and spacing (legend placement, axis labeling) 3) Professional typography system (readable font sizes ≥ 12px for labels, clear hierarchy). Deduct 3 points for each poorly designed visual element, 5 points for inappropriate color choices that hinder data interpretation, and 5 points for cluttered layout. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the chart interactions conform to data visualization best practices: 1) Hover feedback delay ≤ 100ms with smooth tooltip positioning 2) Transition animations for data updates controlled between 300-800ms 3) Clear visual feedback for all interactive elements 4) Smooth performance when handling 100 data points simultaneously. Deduct 5 points for each interaction without proper feedback, 3 points for laggy animations during data transitions, and 5 points for unclear interactive affordances. Full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/html-tool-generate-trend-chart-from-table-data.json

@@ -0,0 +1,68 @@
+{
+  "index": 951,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the generated code is executable when possible. Help me create an HTML tool with an input box for tables on the interface. Users can paste table content into this input box, and there's a button to generate a chart. The button will create a trend chart based on the table data organized by date. Please provide sample data for demonstration.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the HTML table input functionality properly implemented?",
+      "description": "Verify if the code provides a clear, user-friendly input box for pasting tabular data. Check if it handles various table formats (tab-separated, CSV, space-aligned) and provides clear instructions to users on expected input format. Score 0 if no input mechanism exists, 5 if basic input is implemented but lacks format flexibility, 10 if the implementation handles multiple formats with clear user guidance.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the table data parsing mechanism robust?",
+      "description": "Evaluate the code's ability to parse and validate table data, especially date recognition. Check if it correctly identifies headers, data types (dates, numbers), and handles malformed data with appropriate error messages. Deduct 5 points if date parsing is inconsistent, 3 points if it can't detect column types automatically, and 2 points if it fails with irregular spacing/formatting. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the trend chart generation complete and accurate?",
+      "description": "Assess if the code properly generates a visualization based on the date-organized data. Check if it correctly identifies time series data, plots appropriate trend lines, and includes necessary chart elements (axes, legends, titles). Deduct 5 points if date sequencing is incorrect, 3 points if numerical data scaling is inappropriate, and 2 points if the chart type doesn't match the data characteristics. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there sample data included for demonstration?",
+      "description": "Verify if the solution includes realistic, diverse sample data that demonstrates the tool's capabilities. The sample should include multiple data points over various dates, potentially with some edge cases. Give 3 points for basic sample data, 7 points for comprehensive examples that showcase different chart scenarios, and 10 points for example data with multiple variables and date ranges that thoroughly test the system.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as malformed input data, non-date columns, missing values, extremely large datasets) 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. Multiple chart type options 2. Interactive tooltips/zooming 3. Data filtering capabilities 4. Export functionality). 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 parsing methods that do the same thing) 2. Function modules unrelated to chart generation (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., heavy rendering processes). 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 parsing/visualization/UI components), error handling patterns, and code organization. Deduct 5 points if global variables are excessively used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there's no separation between data processing and visualization logic. 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 (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). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic text-image layout. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive?",
+      "description": "Judge whether the chart rendering and user interactions are performant: 1) Chart generation completes within 500ms for standard datasets 2) Interaction features (if any) respond within 100ms 3) Visual feedback is provided during processing of large datasets. Deduct 5 points for noticeable lag when generating charts, 3 points for missing loading indicators during processing, and 5 points for browser freezing with larger inputs. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/html-word-cloud-generator.json

@@ -0,0 +1,68 @@
+{
+  "index": 1636,
+  "question": "You are a code expert. Please utilize your professional knowledge to generate accurate and professional responses. Make sure the code you generate is executable for demonstration purposes. Generate a word cloud presented in HTML.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the word cloud generation algorithm properly implemented?",
+      "description": "Check whether the code implements a proper word cloud layout algorithm (e.g., spiraling placement, force-directed layout, or D3.js-based implementation). Full score requires handling of word frequency calculation, size scaling based on frequency, and collision detection between words. Score 0 if no proper algorithm is implemented, 5 if basic functionality is present but with limitations, and 10 if a robust algorithm with optimized placement is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is text input and processing implemented correctly?",
+      "description": "Evaluate text processing capabilities including tokenization, stopword removal, and frequency counting. The implementation should support various input methods (direct text entry, file upload, or API integration). Deduct 5 points if stopwords are not handled, 3 points if only basic tokenization is present. Give 10 points if advanced text processing with language detection and appropriate stemming/lemmatization is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are customization options for the word cloud provided?",
+      "description": "Check for user customization features such as color schemes, font options, layout shapes, minimum/maximum font size, rotation options, and word filtering. Deduct 2 points for each missing core customization option. Award full 10 points only if at least 5 customization options are available with real-time preview functionality.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the word cloud responsive and interactive?",
+      "description": "Assess whether the word cloud includes interactive features (hover effects, click actions, zooming) and responsiveness across different screen sizes. Deduct 5 points if the visualization breaks on mobile devices, 3 points if hover/click interactions are missing. Full score requires fluid responsiveness and meaningful interactions (e.g., displaying frequency data on hover, filtering on click).",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle edge cases (empty input, extremely large texts, single word inputs, special characters, etc.) and provides appropriate error handling with user-friendly messages. Code with strong robustness should gracefully handle these conditions without crashing. Give 10 points for comprehensive error handling, 5 points for basic error checking, and 0 points if errors cause the visualization to fail.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check for surprise features that enhance the experience (e.g., 1. Animation of word cloud formation 2. Theme-based color schemes 3. Ability to export as SVG/PNG 4. Integration with sentiment analysis). 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 text processing methods) 2. Function modules unrelated to word cloud visualization (e.g., unnecessary media players) 3. Fancy effects that affect performance (e.g., excessive animations that slow 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 (separation of text processing, layout algorithm, and rendering), code reusability, and performance optimization. Deduct 5 points if global variables are overused; deduct 5 points if the code has high complexity with no documentation; deduct 5 points if memory management is poor for large texts. 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 in the word cloud (no more than 3 primary colors unless justified by theme) 2) Proper use of white space around the visualization 3) Professional font selection that ensures readability. Deduct 3 points for poor color contrast, 5 points for cluttered layout, and 5 points for illegible text due to size or font choices. 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) Rendering performance with large word sets (should complete in under 3 seconds) 2) Smooth transitions when applying filters or changing visualization options 3) Clear visual feedback for interactive elements. Deduct 5 points for each interaction that causes visible lag, 3 points for abrupt transitions, and 5 points for unresponsive UI elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/implement-3d-charts-maps-vue2-echarts.json

@@ -0,0 +1,68 @@
+{
+  "index": 1500,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Take care to ensure that the code you generate is executable for demonstration. Implement 3D charts and maps using Vue2 and ECharts.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the 3D chart implementation complete?",
+      "description": "Review whether the code accurately implements 3D visualization features using ECharts GL. Check for proper configuration of coordinate systems (grid3D, globe, geo3D), camera positioning, and light sources. Score 0 if no 3D charts are implemented, 5 if only basic 3D bar/scatter charts are created, and 10 if multiple sophisticated 3D chart types are implemented with customized visual effects.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Are the 3D maps properly implemented?",
+      "description": "Evaluate the implementation of 3D maps using ECharts. Check for correct GeoJSON data loading, proper map projection selection, interactive features (zooming, panning, tooltips), and geographic data visualization (heat maps, scatter points, lines). Deduct 5 points if maps lack interactivity, 3 points if geographic data is not properly bound. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is Vue2 integration with ECharts properly implemented?",
+      "description": "Examine whether the code follows Vue2 best practices when integrating ECharts. Check for proper component design, reactive data handling, lifecycle hooks management (especially resize events), and Vue props/events integration. Deduct 5 points if ECharts instances aren't properly disposed on component destruction, 3 points if resize listeners are missing, and 5 points if reactive data updates don't reflect in the charts. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is performance optimization incorporated for large datasets?",
+      "description": "Check whether the implementation includes optimizations for handling large datasets in 3D visualizations. Look for techniques such as data downsampling, progressive rendering, WebGL utilization, off-screen rendering, and proper memory management. Deduct 5 points if rendering noticeably lags with >1000 data points, 3 points if no throttling is implemented for intensive operations. 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, invalid configurations, browser compatibility issues, WebGL not supported). Code with strong robustness should provide graceful fallbacks and helpful error messages. Give 10 points for comprehensive error handling with fallbacks, 5 points for basic error checking, and 0 points if exceptions are not handled at all.",
+      "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 visualization experience (e.g., 1. Custom shader effects 2. Interactive data exploration tools 3. Animation sequences that reveal data insights 4. Cross-chart linking/brushing). 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. Duplicate visualization components showing the same data 2. Excessive decorative elements that don't convey information 3. Heavy effects that degrade performance without adding analytical value. Deduct 3 points for each redundancy found, and directly deduct 10 points if core visualization functionality is compromised by superfluous code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review component architecture (separation of data processing/visualization logic), reusability of chart components, and maintainability. Deduct 5 points if chart options are hardcoded instead of parameterized; deduct 5 points if there's significant code duplication across chart components; deduct 5 points if there's no abstraction for common functionality. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the visualization design follows data visualization principles: 1) Appropriate color schemes for data types (sequential, diverging, categorical) 2) Clear visual hierarchy with proper emphasis on important data 3) Intuitive legends and axes that aid interpretation. Deduct 3 points for poor color choices that hinder data interpretation, 5 points for cluttered visualizations, and 5 points for misleading visual encodings. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the interactive experience smooth and intuitive?",
+      "description": "Judge whether the interactive features enhance data exploration: 1) Responsive rotation/zoom/pan controls for 3D visualization 2) Tooltips appear within 100ms of hovering 3) Selection states clearly indicated 4) Smooth transitions between data views (300-500ms). Deduct 5 points for laggy 3D interactions, 3 points for missing visual feedback during interactions, and 5 points for confusing or unintuitive control schemes. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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

@@ -0,0 +1,68 @@
+{
+  "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"
+}