@getollie/cli 0.0.5 → 0.2.0

package/library/data_science-data_visualization_dashboards/construction-task-gantt-chart-generator.json

@@ -1,68 +0,0 @@
-{
-  "index": 1357,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to ensure the generated code is executable for display. \n\nNumber | Construction Task | Start Date | End Date | Duration (Days)\n--- | --- | --- | --- | ---\n1 | Site Leveling and Enclosure Setup | XXXX/XX/XX | XXXX/XX/XX | XX\n2 | Foundation Excavation and Pouring | XXXX/XX/XX | XXXX/XX/XX | XX\n3 | Main Structure Construction | XXXX/XX/XX | XXXX/XX/XX | XX\n4 | Roof and Wall Construction | XXXX/XX/XX | XXXX/XX/XX | XX\n5 | Interior Finishing and Decoration | XXXX/XX/XX | XXXX/XX/XX | XX\n6 | Exterior Engineering and Landscaping | XXXX/XX/XX | XXXX/XX/XX | XX\n\nPlease provide me with the code to output a Gantt chart.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the basic Gantt chart structure correctly implemented?",
-      "description": "Evaluate whether the code properly creates a visual timeline representation with horizontal bars for each construction task. Check if the chart includes a timeline axis, task labels, and proper date formatting. Score 0 if the basic structure is missing, 5 points if the structure is present but with deficiencies, and 10 points for a complete and properly structured Gantt chart.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the tasks and date ranges accurately displayed?",
-      "description": "Verify that all 6 construction tasks are correctly represented with their respective start and end dates. The bars should be proportionally sized according to the duration and correctly positioned on the timeline. Deduct 2 points for each incorrectly displayed task or date conversion error. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the time axis implementation complete and accurate?",
-      "description": "Check if the time axis is properly scaled, with clear interval markings, appropriate date labels, and consistent spacing. The axis should accommodate the full project timeline from the earliest start date to the latest end date. Deduct 5 points if the time scale is inconsistent or if date calculations are incorrect, and 3 points if the axis lacks proper labeling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the Gantt chart include visual indicators for progress tracking or milestones?",
-      "description": "Assess whether the implementation includes features for tracking progress (like percent complete indicators, today's date marker) or milestone markers. Give 3 points for basic progress indicators, 3 points for milestone visualization, and 4 points for interactive progress updating capabilities. 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 dates, missing data, browser compatibility issues) and provide appropriate error handling. Code with strong robustness should validate inputs and gracefully handle edge cases, giving 10 points. If the robustness is average, give 5 points, and if no error handling is implemented, 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. Task dependency visualization 2. Critical path highlighting 3. Interactive tooltips with detailed information 4. Zoom and pan capabilities). Add 2.5 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 date parsing methods) 2. Function modules unrelated to Gantt charts (e.g., unnecessary animations) 3. Fancy effects that affect performance (e.g., excessive animations or renderings). 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/rendering/interaction layers), reusability, and maintainability. Deduct 5 points if global variables are excessively used; deduct 3 points if the code is not properly commented; deduct 3 points if there's significant code duplication. Check if the implementation follows modern development practices. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the chart follows data visualization best practices: 1) Clear visual hierarchy with task labels aligned properly 2) Appropriate color coding (consistent, accessible, meaningful) 3) Sufficient contrast between elements and background. Deduct 3 points for poor alignment, 3 points for inappropriate color choices, and 4 points for cluttered or hard-to-read visual presentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether the chart provides appropriate interaction capabilities: 1) Hovering effects for additional information 2) Smooth transitions when updating data or filtering 3) Responsive design that adapts to different screen sizes. Deduct 3 points for lack of hover states, 4 points for jarring transitions or no transitions, and 3 points for poor responsiveness across devices. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/consumption-willingness-by-city-type-bar-chart.json

@@ -1,68 +0,0 @@
-{
-  "index": 812,
-  "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. Create a bar chart where the x-axis represents consumption willingness, including \"Very willing\", \"Somewhat willing\", \"Somewhat unwilling\", and \"Very unwilling\", and the y-axis represents city types, including \"First-tier cities\", \"New first-tier cities\", \"Second-tier cities\", \"Third-tier cities\", and \"Others\" (each x-coordinate corresponds to five bars).",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the bar chart correctly implemented with the specified axes?",
-      "description": "Check whether the code correctly implements a bar chart with consumption willingness on the x-axis ('Very willing', 'Somewhat willing', 'Somewhat unwilling', 'Very unwilling') and city types on the y-axis ('First-tier cities', 'New first-tier cities', 'Second-tier cities', 'Third-tier cities', 'Others'). Verify that each x-coordinate has 5 bars representing different city types. Score 0 if axes are reversed or missing, 5 if partially implemented, 10 if fully and correctly implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data structure appropriate for the visualization?",
-      "description": "Evaluate if the data structure efficiently organizes the relationship between consumption willingness categories and city types. Check if the data format allows for easy updating and scaling. Deduct 5 points if the structure requires complex transformations before visualization, 3 points if it's not optimized for performance with larger datasets. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are appropriate visual differentiation techniques used?",
-      "description": "Assess whether the visualization uses appropriate techniques (colors, patterns, spacing) to differentiate between the 5 city types within each consumption willingness category. Check if a legend is included to identify each city type. Deduct 5 points if bars are not visually distinguishable, 3 points if the legend is missing or unclear. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the chart include proper labels and annotations?",
-      "description": "Verify if the chart includes clear axis titles, value labels, and a meaningful chart title. Check whether tooltips or data labels show exact values when hovering/clicking. Deduct 3 points for missing axis titles, 3 points for missing value labels, and 4 points for missing tooltips/interactive elements. 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, different data scales, browser resizing, etc.) and provide graceful fallbacks or error handling. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive filtering options 2. Animation when loading data or hovering 3. Responsive design that works on mobile devices). Add 3 points for each practical innovative feature implemented (maximum 10 points).",
-      "maxScore": 10
-    },
-    {
-      "id": 6,
-      "title": "Are there any redundant features?",
-      "description": "Strictly check three types of redundancy: 1. Redundant implementation of similar visualization functions 2. Function modules unrelated to the bar chart (e.g., unnecessary widgets) 3. Fancy effects that affect performance (e.g., excessive animations). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data processing/visualization/interaction layers), reusability, and code organization. Deduct 5 points if global namespace 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 code is not organized in logical sections with comments. 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 data visualization principles: 1) Harmonious color matching (color-blind friendly, consistent palette) 2) Proper layout spacing (sufficient margin around the chart, appropriate bar width and spacing) 3) Professional typography (readable font sizes, proper text alignment). 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) Hover/click feedback delay ≤ 100ms 2) Transition animation duration controlled between 300-500ms 3) Clear visual feedback on interaction. Deduct 5 points for each operation without feedback, 3 points for laggy transitions, and 5 points for confusing interaction patterns. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Data Visualization Dashboards",
-  "difficulty": "easy"
-}

package/library/data_science-data_visualization_dashboards/create-pie-chart-from-table-data-html.json

@@ -1,68 +0,0 @@
-{
-  "index": 720,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Be sure to provide executable code whenever possible. I have a table - could you help me create a pie chart based on the data in the table and generate an HTML file?",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the data extraction and processing logic properly implemented?",
-      "description": "Evaluate if the code correctly extracts data from the table input and processes it for chart visualization. Check if the code handles various table formats (HTML tables, CSV strings, JSON data) and applies appropriate data transformations. Deduct 5 points if the code only handles one specific format, deduct 10 points if data extraction fails for complex tables.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the pie chart visualization correctly implemented with proper layout?",
-      "description": "Verify that the pie chart is correctly rendered with properly calculated sectors based on data values. Check that the chart uses appropriate angles, radii, and center points. Deduct 5 points if the chart has incorrect proportions, 3 points for minor rendering issues, and 10 points if the chart fails to represent data accurately.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the chart enhanced with proper labeling and legend?",
-      "description": "Check if the pie chart includes clear labels for each sector, a comprehensive legend, and meaningful title. Labels should show category names and values/percentages. Deduct 3 points for missing labels, 3 points for missing legend, and 4 points for poor placement that obstructs readability.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are appropriate visualization libraries utilized effectively?",
-      "description": "Evaluate if the implementation makes appropriate use of chart libraries (like Chart.js, D3.js, or Google Charts) or implements custom SVG/Canvas rendering when needed. Check correct configuration of library-specific options. Deduct 5 points for inappropriate library choice, 3 points for inefficient implementation, and 10 points for library misuse.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as empty data, single-value datasets, very large or small values, text values mixed with numbers, etc.) and provide friendly error prompts or graceful fallbacks. Deduct 3 points for each unhandled edge case, and 10 points if the chart breaks completely on atypical inputs.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Interactive tooltips showing more details 2. Animation on hover/load 3. Ability to toggle between pie and donut chart 4. Export to image 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 visualization methods 2. Function modules unrelated to chart visualization 3. Fancy effects that affect performance (e.g., excessive animations). 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 maintainability. Deduct 5 points if global state pollution is found; deduct 3 points if the code is not organized into logical functions; deduct 2 points if there's no error handling. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the chart design follows visualization best practices: 1) Harmonious color scheme with good contrast 2) Proper proportions and layout 3) Professional typography (legible fonts, proper sizing). Deduct 3 points for poor color choices that hinder data perception, 4 points for cluttered design, and 3 points for illegible labels or text. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive?",
-      "description": "Judge whether the chart provides appropriate interactive elements: 1) Responsive design that works across device sizes 2) Smooth transitions when data changes 3) Clear interactive elements (e.g., hover effects, clickable segments). Deduct 3 points for lack of responsiveness, 3 points for missing hover states, and 4 points for jerky transitions or poor performance with 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/create-visualizations-from-code-expert.json

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

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

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

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

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

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

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

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

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