@getollie/cli 0.0.1

package/library/data_science-data_visualization_dashboards/visitor-flow-analysis-xinzhou-vue-implementation.json

@@ -0,0 +1,68 @@
+{
+  "index": 1024,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for demonstration. The thesis title is \"Visitor Flow Analysis of Xinzhou Ancient City Based on Vue Implementation\".",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Vue.js architecture and component system properly implemented?",
+      "description": "Review whether the code correctly implements Vue.js framework with proper component hierarchy, state management (Vuex/Pinia), and routing (Vue Router). Check if components are properly structured with data flow, props validation, and lifecycle management. Score 0 if basic Vue structure is missing, 5 if only basic components are implemented without state management, and 10 if complete Vue ecosystem with proper architecture is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the visitor flow data visualization comprehensively implemented?",
+      "description": "Evaluate whether the system includes multiple visualization methods for visitor flow analysis such as heat maps, flow direction charts, time-series analysis, and statistical dashboards. Check if data binding is reactive and supports real-time updates. Deduct 5 points if only basic charts are provided, 3 points if interactive filtering is missing. Full score requires comprehensive multi-dimensional visualization with smooth data transitions.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the ancient city geographic mapping and spatial analysis accurately implemented?",
+      "description": "Check whether the code includes accurate geographic mapping of Xinzhou Ancient City with proper coordinate systems, landmark positioning, and spatial relationship analysis. Evaluate if visitor flow paths are correctly mapped to actual geographic locations with proper scaling and orientation. Deduct 5 points if geographic accuracy is poor, 3 points if spatial relationships are not properly represented. Full score requires precise geographic implementation with detailed spatial analysis.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the data processing and analysis algorithm properly implemented?",
+      "description": "Review whether the system includes proper data preprocessing, filtering, aggregation, and statistical analysis algorithms for visitor flow patterns. Check if temporal analysis, peak detection, and trend analysis are implemented. Evaluate data validation and cleansing mechanisms. Deduct 5 points if data processing is superficial, 3 points if statistical analysis is incomplete. Full score requires comprehensive data analysis with multiple algorithmic approaches.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust and handles edge cases effectively?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data, network interruption, invalid coordinates, empty datasets, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle these edge cases and maintain system stability, 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 innovative features that enhance the analysis experience?",
+      "description": "Check whether the code includes valuable features that enhance visitor flow analysis (e.g., 1. Predictive flow modeling 2. Comparative analysis across time periods 3. Interactive 3D visualization 4. Real-time monitoring dashboard 5. Export functionality for reports). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant or unnecessary features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization functions 2. Feature modules unrelated to visitor flow analysis 3. Excessive animations or effects that impact performance and distract from data analysis. Deduct 3 points for each redundancy found, and directly deduct 10 points if core analytical functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code demonstrate high engineering quality?",
+      "description": "Review modular design (separation of data layer/visualization layer/business logic), component reusability, and code organization. Deduct 5 points if global state pollution is found or Vue best practices are not followed; deduct 5 points if code duplication rate exceeds 30%; deduct 5 points if proper build configuration and optimization are missing. Full score requires excellent code structure and maintainability.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface design meet professional academic presentation standards?",
+      "description": "Evaluate whether the design follows academic and professional standards: 1) Clear information hierarchy with proper data visualization principles 2) Consistent color scheme suitable for data analysis (colorblind-friendly palettes) 3) Professional typography with readable font sizes and proper contrast 4) Clean layout without visual clutter. Deduct 3 points for each poorly designed visualization element, 5 points for unprofessional color choices, and 5 points for cluttered or confusing layout.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Are the interactive elements smooth and intuitive for data exploration?",
+      "description": "Judge whether interactions support effective data exploration: 1) Responsive filtering and selection with immediate feedback 2) Smooth transitions between different views and time periods 3) Intuitive navigation and zoom controls 4) Clear visual indicators for interactive elements. Deduct 5 points for each unresponsive interaction, 3 points for confusing navigation, and 5 points for slow rendering that impacts user experience during data exploration.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "hard"
+}

package/library/data_science-data_visualization_dashboards/visualization-dashboard-word-cloud-code-with-npm.json

@@ -0,0 +1,68 @@
+{
+  "index": 416,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Pay attention to ensure the generated code is executable for demonstration. Visualization dashboard word cloud code, created with npm.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the word cloud visualization core functionality implemented correctly?",
+      "description": "Check if the code implements a proper word cloud visualization using appropriate npm packages (e.g., d3-cloud, react-wordcloud). The implementation should handle text processing, word frequency calculation, and visual rendering. Score 0 if no word cloud is generated, 5 if basic functionality exists with flaws, and 10 if the implementation is complete with proper text processing and visualization.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Does the code handle data input and processing appropriately?",
+      "description": "Evaluate how the code handles text input (from files, APIs, or user input), processes it (tokenization, stopword removal, stemming/lemmatization), and calculates word frequencies. Check if it handles different languages, special characters, and case sensitivity. Deduct 3 points if stopwords aren't handled, 3 points if no text preprocessing exists, and 2 points if it only works with English text. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the dashboard integration complete and functional?",
+      "description": "Assess if the word cloud is properly integrated into a dashboard context with appropriate layout structure. The dashboard should include controls for customization, data refresh mechanisms, and possibly other complementary visualizations. Deduct 5 points if the word cloud exists in isolation without dashboard elements, and 3 points if integration exists but with limited functionality. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are word cloud customization options implemented?",
+      "description": "Check if the code allows customization of the word cloud appearance and behavior: font styles/sizes, color schemes, layout options (shape, orientation), minimum/maximum word count, and animation settings. Deduct 2 points for each major customization category missing. The full score is 10 points if comprehensive customization is available with intuitive controls.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty input, extremely large texts, malformed data, browser compatibility issues) 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 hovering effects with additional word information 2. Real-time word cloud updates based on streaming data 3. Exportable word cloud as SVG/PNG with custom branding). 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 functionality (e.g., multiple text processing pipelines) 2. Function modules unrelated to the word cloud dashboard (e.g., unnecessary analytics) 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 (such as separating data processing/visualization/UI components), code organization, dependency management, and build configuration. Deduct 5 points if global state pollution is found; deduct 3 points if npm dependencies are not properly managed; deduct 5 points if the code lacks comments or documentation. Check if the project has a proper structure with clear separation of concerns. 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 dashboard design principles: 1) Harmonious color matching with consistent palette 2) Proper layout with appropriate use of space and grid systems 3) Professional typography with readable fonts and proper contrast ratios. Deduct 3 points for cluttered layout, 5 points for poor color choices affecting readability, and 5 points for inconsistent styling across components. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive?",
+      "description": "Judge whether the word cloud and dashboard interactions are fluid and responsive: 1) Smooth transitions when filtering or updating data 2) Responsive design that works across device sizes 3) Performance optimization for large datasets without UI freezing. Deduct 5 points for laggy rendering with large word sets, 3 points for missing loading states during data processing, and 3 points for non-responsive design on different screen sizes. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "medium"
+}

package/library/data_science-data_visualization_dashboards/visualize-excel-pois-clustering-on-map-html.json

@@ -0,0 +1,68 @@
+{
+  "index": 1307,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code that can be demonstrated. Read from Excel, display POIs and clustering situations on a map, and visualize through HTML.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the Excel data reading functionality properly implemented?",
+      "description": "Evaluate whether the code correctly reads data from Excel files (XLSX/XLS) including error handling for missing files, incorrect formats, and large datasets. Check if the code uses appropriate libraries (e.g., SheetJS, xlsx, pandas) and maintains data integrity. Score 0 if there's no Excel reading implementation, 5 if basic reading is implemented but with limitations, and 10 if robust Excel processing with error handling is fully implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the POI data extraction and processing properly implemented?",
+      "description": "Review whether the code correctly extracts Point of Interest (POI) data from the Excel file, validates geographic coordinates (latitude/longitude), handles missing or invalid POI data, and transforms data into an appropriate format for mapping. Deduct 5 points if coordinate validation is missing, 3 points if there's no handling for incomplete data, and 2 points if data transformation is inefficient. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the clustering algorithm implementation effective?",
+      "description": "Assess the clustering algorithm implementation (e.g., K-means, DBSCAN, hierarchical clustering) for grouping POIs. Check if the algorithm is appropriate for geospatial data, includes proper parameter selection, and has optimization for performance with larger datasets. Deduct 5 points if the clustering doesn't account for geographic distance properly, 3 points if parameter tuning options are missing, and 2 points if performance issues exist with larger datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the map visualization implementation complete?",
+      "description": "Evaluate whether the map implementation includes proper initialization (using libraries like Leaflet, Google Maps API, or OpenLayers), correct POI placement, appropriate zoom levels, distinguishable cluster visualizations, and interactive elements. Deduct 5 points if the map lacks proper initialization or responsive design, 3 points if POI markers lack clarity or distinction, and 3 points if clustering visualization is not intuitive. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as malformed Excel data, invalid coordinates, 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. Heatmap visualization as an alternative view 2. Time-series animation for temporal POI data 3. Advanced filtering options for clusters 4. Custom cluster inspection tools). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar functions (e.g., multiple mapping libraries used simultaneously) 2. Function modules unrelated to POI visualization (e.g., unnecessary analytics tools) 3. Fancy effects that affect performance (e.g., excessive animations that slow down map 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 data loading/processing/visualization layers), unit test coverage, and build process automation. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not automated. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching for map elements and clusters (distinguishable but not jarring) 2) Proper layout spacing for controls and information panels 3) Professional font system for labels and information displays (readable at various zoom levels). Deduct 3 points for cluttered map controls, 5 points for indistinguishable cluster/POI markers, and 5 points for illegible text elements. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the map interactions conform to user expectations: 1) Responsive zooming and panning without lag 2) Clear visual feedback when selecting POIs or clusters 3) Smooth transitions when switching between cluster views and individual POIs. Deduct 5 points for laggy map rendering, 3 points for unresponsive POI selection, and 5 points for abrupt transitions between clustering levels. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/visualize-temperature-data-from-serial-monitor-web-interface.json

@@ -0,0 +1,68 @@
+{
+  "index": 1305,
+  "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. How can I visualize temperature data from a serial monitor on a web interface, using USB as the communication method?",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the serial communication implementation complete?",
+      "description": "Check whether the code properly implements the Web Serial API or an alternative method for USB communication. Verify that it handles connection setup, disconnection handling, and error recovery. Score 0 if no serial communication code is implemented, 5 if basic connection is established but lacks error handling, and 10 if the implementation includes proper connection management, data buffering, and error handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the temperature data parsing logic robust?",
+      "description": "Evaluate whether the code correctly parses temperature data from the serial stream, handling different formats (JSON, CSV, plain text), corrupted data, and partial messages. Check for validation of reasonable temperature ranges and units conversion if needed. Score 3 if basic parsing is implemented, 7 if validation and error handling are included, and 10 if the parsing is comprehensive with support for multiple formats and robust against transmission errors.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is real-time visualization effectively implemented?",
+      "description": "Assess whether the visualization updates in real-time with minimal latency (< 500ms), uses appropriate charts/graphs (line charts, gauges, etc.) for temperature data, and handles continuous data streams without performance degradation. Score 3 for static visualization, 7 for basic real-time updates, and 10 for smooth visualization with proper time scaling and performance optimization.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is data history and management functionality provided?",
+      "description": "Check if the implementation includes data history storage, allows viewing historical data trends, provides zoom/pan capabilities for exploring the data timeline, and includes options for exporting/saving temperature logs. Score 0 if no history is maintained, 5 if basic history is shown but lacks interaction features, and 10 if comprehensive history management with time navigation controls is implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as device unplugging, buffer overflows, malformed data, browser compatibility issues) 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. Temperature anomaly detection with alerts 2. Multi-sensor comparison visualization 3. Responsive design for mobile/desktop). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
+      "maxScore": 10
+    },
+    {
+      "id": 6,
+      "title": "Are there any redundant features?",
+      "description": "Strictly check three types of redundancy: 1. Redundant data processing steps (e.g., multiple parsing of the same data) 2. Function modules unrelated to temperature visualization (e.g., irrelevant UI components) 3. Fancy effects that affect performance (e.g., excessive animations that slow down real-time updates). 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 communication/data processing/visualization layers), use of appropriate design patterns, error handling, and code maintainability. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if there is no separation of concerns. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the visualization dashboard follows modern design principles: 1) Harmonious color scheme appropriate for data visualization (clear distinction between data series) 2) Proper layout with intuitive organization of components 3) Professional typography with clear legends and axis labels. Deduct 3 points for cluttered visualization, 5 points for poor color choices that make data hard to interpret, and 5 points for missing critical information like units or timestamp. 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 user expectations: 1) Data updates without visual jarring 2) Smooth transitions when new data arrives 3) Intuitive controls for adjusting view parameters (timeframe, scale, etc.). Deduct 5 points for each interaction without visual feedback, 3 points for choppy animations during updates, and 5 points for unintuitive interface controls. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/visualize-trajectories-code-segment.json

@@ -0,0 +1,68 @@
+{
+  "index": 997,
+  "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 purposes. Please create a complete code segment for visualizing trajectories, including the data reading portion, so I can try it out.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the trajectory data reading implementation correct and flexible?",
+      "description": "Check whether the code provides robust methods for reading trajectory data from common formats (CSV, JSON, etc.) and handles different data structures appropriately. Score 0 if no data reading is implemented, 5 if only basic file loading is included, and 10 if it supports multiple data formats with error handling and validation.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the trajectory visualization core rendering complete?",
+      "description": "Evaluate whether the visualization leverages appropriate technology (Canvas, SVG, WebGL, etc.) based on the data scale. Check if it properly implements features like path drawing, data point plotting, and coordinate mapping. Deduct 5 points if the visualization is static only, 3 points if there are rendering artifacts. Score 10 if the visualization is smooth with proper scaling and coordination transformations.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are interactive elements properly implemented?",
+      "description": "Review whether the code includes essential interactive features like zooming, panning, selection of specific trajectories, and time-based filtering/playback. Deduct 5 points if basic interactions are missing, 3 points if interactions have noticeable lag. Give 10 points if all interactions feel responsive and intuitive.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is there appropriate temporal representation in the visualization?",
+      "description": "Assess if the code handles the temporal aspect of trajectory data effectively, including features like timeline controls, color/opacity gradient for time progression, or animation capabilities. Score 0 if time is not represented, 5 if basic time representation exists but isn't interactive, and 10 if comprehensive temporal navigation and visualization are implemented.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as malformed data, empty datasets, browser compatibility issues, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 5,
+      "title": "Are there any innovative features that are eye-catching?",
+      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time statistical analysis of trajectories 2. Pattern recognition for similar paths 3. Heat map overlay of trajectory densities). 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 methods 2. Function modules unrelated to trajectory visualization (e.g., unnecessary UI elements) 3. Fancy effects that affect performance (e.g., excessive animations or effects that obscure the data). Deduct 3 points for each redundancy found, and directly deduct 10 points if the 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), code reusability, and performance optimization. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if no performance considerations are implemented for large datasets. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional data visualization standards?",
+      "description": "Evaluate whether the visualization follows effective data visualization principles: 1) Appropriate color schemes for data clarity 2) Clear visual hierarchy with proper labels and legends 3) Balanced information density without chart junk. Deduct 3 points for poor color choices that hinder data interpretation, 5 points for missing essential contextual elements (axes, legends, etc.), and 5 points for cluttered visuals that obscure the data narrative. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the visualization responsive and performant?",
+      "description": "Judge whether the implementation maintains smooth performance across different data loads: 1) Renders trajectories with minimal latency 2) Efficiently handles large datasets with appropriate optimizations (data sampling, WebWorkers, etc.) 3) Adapts gracefully to different screen sizes. Deduct 5 points for noticeable lag with moderate data sizes, 3 points for poor mobile/responsive behavior, and 5 points if the visualization breaks under larger datasets. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/vue-3-interface-data-list-line-charts.json

@@ -0,0 +1,68 @@
+{
+  "index": 207,
+  "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. For a Vue 3 interface, organize a data list by extracting time as the x-axis and values as the y-axis data, arranging them into three line charts.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the data extraction and organization logic correctly implemented?",
+      "description": "Evaluate whether the code accurately extracts time values for x-axis and corresponding values for y-axis from the provided dataset. Check for proper data validation, formatting (especially time/date parsing using libraries like dayjs or date-fns), and error handling for invalid data points. Score 0 if data extraction is missing, 5 if basic extraction is done but with formatting issues, and 10 if extraction includes robust validation and proper type handling.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Vue 3 implementation following best practices?",
+      "description": "Check whether the code properly uses Vue 3's Composition API (setup(), ref(), computed(), etc.) and follows Vue 3's reactive principles. Evaluate proper component structure, lifecycle hooks usage, and reactivity management. Deduct 5 points if using Options API instead of Composition API without justification, 3 points if reactivity is broken when data changes, and 5 points if Vue 3 specific features are ignored. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are the three line charts properly implemented and configured?",
+      "description": "Verify the implementation of three distinct line charts using a suitable charting library (e.g., ECharts, Chart.js, D3.js). Assess whether each chart is correctly configured with appropriate axes, legends, tooltips, and responsive design. Deduct 5 points if charts don't resize properly, 3 points if interactive features like tooltips are missing, and 5 points if customization options are not utilized. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is the time axis (x-axis) properly formatted and scaled?",
+      "description": "Evaluate time axis implementation including proper time formatting, appropriate time intervals, handling of irregular time data, and time zone considerations. Check for time range selection/filtering capabilities. Deduct 5 points for inappropriate time formatting, 3 points for missing time scale adaptability, and 5 points for incorrect time sorting. Full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as empty datasets, malformed data, asynchronous loading 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 data point highlighting across all charts 2. Dynamic theme switching 3. Animation transitions between data updates). 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 charting libraries used simultaneously) 2. Function modules unrelated to data visualization (e.g., unnecessary UI components) 3. Fancy effects that affect performance (e.g., excessive animations or 3D effects). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating data processing/visualization/UI layers), component reusability, and build process optimization. Deduct 5 points if global state pollution is found or composition functions aren't properly utilized; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if performance optimizations are neglected (like memoization with computed/memo). 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 schemes for the three charts (distinguishable but coordinated) 2) Proper layout spacing and chart proportions 3) Professional typography for labels, legends and tooltips (readable font sizes, appropriate contrast). Deduct 3 points for each crowded visual element, 5 points for clashing colors between charts, and 5 points for poor information hierarchy. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the dynamic effects conform to human perception characteristics: 1) Responsive hover/click feedback on data points ≤ 100ms 2) Smooth transitions between data updates or filtering 3) Intuitive zoom/pan interactions if implemented. Deduct 5 points for laggy chart rendering, 3 points for abrupt transitions between states, and 5 points for confusing interactive elements. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/vue-antv-china-national-map.json

@@ -0,0 +1,68 @@
+{
+  "index": 736,
+  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Be careful to ensure that the generated code is executable for demonstration purposes. Develop a national map of China using Vue and AntV.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Does the code implement a complete China map visualization?",
+      "description": "Check whether the code correctly renders a detailed map of China with proper geographical boundaries using AntV (G2, G2Plot, or L7). Verify that all provinces, autonomous regions, municipalities, and special administrative regions are accurately displayed. Score 0 if only a basic outline is shown, 5 if most regions are present but with inaccuracies, 10 if the map is complete and geographically accurate with proper GeoJSON data.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is the Vue integration properly implemented?",
+      "description": "Evaluate whether Vue's reactivity system is properly utilized for data binding and component architecture. Check for proper Vue lifecycle hooks, computed properties, and watchers when handling map interactions. Deduct 5 points if Vue components are not modular, 3 points if Vue's reactivity is not leveraged, and 2 points if Vue best practices (like single-file components) are not followed. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Are map interactions and user controls implemented?",
+      "description": "Verify the implementation of essential map interactions: zooming, panning, region selection, hover effects, and tooltip information. Check whether the map responds to user interactions with appropriate visual feedback. Award 10 points for comprehensive interactions with smooth transitions, 5 points for basic interactions, and 0 points if interactions are missing or non-functional.",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Is data visualization and thematic mapping functionality implemented?",
+      "description": "Assess whether the code supports thematic mapping capabilities with dynamic data binding (e.g., choropleth maps showing population density, economic indicators, etc.). Check if the visualization includes a legend and supports data updates. Award 10 points for complete implementation with multiple visualization options, 5 points for basic implementation, and 0 points if absent.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as missing GeoJSON data, API errors, malformed data, slow network connections, 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. Animation showing historical changes in regions 2. 3D terrain visualization 3. Interactive drill-down from national to province to city level). 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 map rendering logic (e.g., multiple renderers for the same area) 2. Function modules unrelated to the China map visualization (e.g., irrelevant charts) 3. Fancy effects that affect performance (e.g., excessive animations or unnecessary 3D effects). 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), component reusability, and build process configuration. Deduct 5 points if global state pollution is found or Vue design patterns are not used correctly; deduct 5 points if the code duplication rate is too high (over 30%); deduct 5 points if the build process is not properly configured for a production environment. 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 for the map, appropriate contrast for data visualization) 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 layout of controls and legends. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and seamless?",
+      "description": "Judge whether the map interactions conform to human perception characteristics: 1) Click/hover feedback delay ≤ 100ms 2) Zoom/pan animations controlled between 300-500ms 3) Clear visual feedback for selected regions. Deduct 5 points for each operation without feedback, 3 points for visual lag during map navigation, and 5 points for hard-to-find key function controls. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "easy"
+}

package/library/data_science-data_visualization_dashboards/vue-d3-github-calendar-heatmap.json

@@ -0,0 +1,68 @@
+{
+  "index": 1075,
+  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code when possible. Help me draw a GitHub calendar heatmap using Vue and D3.js.",
+  "checklist": [
+    {
+      "id": 0,
+      "title": "Is the GitHub calendar heatmap visualization correctly implemented?",
+      "description": "Review whether the code accurately implements the GitHub-style calendar heatmap visualization using D3.js. Check if it includes proper day-by-day grid layout, color intensity mapping based on contribution counts, and correct date handling. Score 0 if the heatmap is not implemented, 5 if basic visualization is present but with structural issues, and 10 if the implementation closely resembles GitHub's calendar appearance with correct date alignment and week/month indicators.",
+      "maxScore": 10
+    },
+    {
+      "id": 1,
+      "title": "Is Vue integration properly implemented?",
+      "description": "Evaluate whether D3.js is correctly integrated with Vue.js framework. Check if the implementation uses Vue's reactivity system for data binding, proper lifecycle hooks for D3 rendering, and component-based architecture. Deduct 5 points if D3 manipulates the DOM directly bypassing Vue's virtual DOM, 3 points if Vue reactivity is not leveraged for data changes. The full score is 10 points if D3 and Vue are seamlessly integrated with proper data flow.",
+      "maxScore": 10
+    },
+    {
+      "id": 2,
+      "title": "Is the data handling functionality complete?",
+      "description": "Check whether the code includes proper data processing for the heatmap, including data format transformation, date parsing, contribution count aggregation, and color scale mapping. Deduct 5 points if data normalization is missing, 3 points if date handling is incorrect. Give 10 points if the implementation includes flexible data input formats and proper edge case handling (sparse data, empty periods, etc.).",
+      "maxScore": 10
+    },
+    {
+      "id": 3,
+      "title": "Are interactive features implemented?",
+      "description": "Assess whether the heatmap includes GitHub-like interactive features such as tooltips showing exact contribution counts and dates on hover, highlighting of selected days/weeks, and possibly filtering options. Score 0 if no interactivity is implemented, 5 if only basic tooltips exist, and 10 if comprehensive interactive features are present with smooth transitions and responsive behavior.",
+      "maxScore": 10
+    },
+    {
+      "id": 4,
+      "title": "Is the code robust?",
+      "description": "Evaluate whether the code can handle common abnormal situations (such as invalid data formats, missing data points, boundary dates, different time zones, etc.) and provide graceful fallbacks. 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. Customizable color schemes 2. Animation of data changes 3. Contribution trend analysis visualization 4. Comparative view between different time periods). 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 functionality 2. Unnecessary dependencies or libraries 3. Over-engineered features that complicate the code without adding value to the heatmap visualization. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functionality is impaired by redundant code.",
+      "maxScore": 10
+    },
+    {
+      "id": 7,
+      "title": "Does the code have engineering quality?",
+      "description": "Review modular design (such as separating visualization logic/data processing/UI components), reusability of the heatmap component, and code maintainability. Deduct 5 points if global state is used inappropriately; deduct 5 points if the code has high coupling between D3 and Vue; deduct 5 points if there's no clear separation of concerns. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 8,
+      "title": "Does the interface vision meet professional design standards?",
+      "description": "Evaluate whether the heatmap design follows modern visualization principles: 1) Appropriate color scale that effectively communicates intensity 2) Proper grid layout with consistent spacing 3) Clear typography for labels and tooltips (month names, day indicators). Deduct 3 points for poor color contrast, 5 points for inconsistent grid sizing, and 5 points for illegible or misaligned labels. The full score is 10 points.",
+      "maxScore": 10
+    },
+    {
+      "id": 9,
+      "title": "Is the dynamic interaction smooth and responsive?",
+      "description": "Judge whether the dynamic effects conform to user expectations: 1) Tooltip appearance within 100ms of hover 2) Smooth transitions when data changes 3) Responsive layout that adapts to different screen sizes. Deduct 5 points for noticeable lag during interactions, 3 points for jarring or missing transitions, and 5 points for broken layouts on window resize. The full score is 10 points.",
+      "maxScore": 10
+    }
+  ],
+  "class": "Data Science-Data Visualization Dashboards",
+  "difficulty": "hard"
+}