@getollie/cli 0.0.5 → 0.2.0

package/library/data_science-predictive_modeling/power-station-trend-prediction-optimization-scheduling.json

@@ -1,68 +0,0 @@
-{
-  "index": 1030,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate, professional responses. Ensure that the generated code is executable for demonstration. Using Java and Angular code, please implement:\n\nTrend prediction and optimization scheduling: Through data modeling, predict the future operational trends of power stations, providing scientific basis for power dispatching and energy allocation.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the data modeling and trend prediction algorithm fully implemented?",
-      "description": "Review whether the Java backend accurately implements time series analysis algorithms (such as ARIMA, LSTM, or Prophet models) for power station operational trend prediction. Check if the code includes data preprocessing, feature engineering, model training, and prediction validation. Score 0 if no prediction algorithm is implemented, 5 if only basic linear regression is used, and 10 if advanced machine learning models with proper validation metrics (MAE, RMSE, MAPE) are fully implemented.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the optimization scheduling system properly designed?",
-      "description": "Evaluate whether the Java implementation includes sophisticated optimization algorithms for power dispatching (such as genetic algorithms, particle swarm optimization, or linear programming). Check if the system considers constraints like power demand, generation capacity, transmission limits, and cost optimization. Deduct 5 points if only basic rule-based scheduling is implemented, and 3 points if real-time constraint handling is missing. Full score requires multi-objective optimization with constraint satisfaction.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Angular frontend data visualization comprehensive and accurate?",
-      "description": "Check whether the Angular application provides comprehensive dashboards with real-time charts showing power generation trends, prediction accuracy, scheduling optimization results, and key performance indicators. Evaluate if interactive charts (using libraries like Chart.js, D3.js, or Highcharts) allow users to drill down into historical data and future predictions. Deduct 5 points if visualizations are static, and 3 points if real-time data updates are not implemented. Full score requires interactive, responsive charts with proper data binding.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the system integration between Java backend and Angular frontend robust?",
-      "description": "Assess whether the Java Spring Boot backend provides RESTful APIs with proper data serialization/deserialization for trend prediction results and scheduling recommendations. Check if Angular services properly consume these APIs with error handling, loading states, and real-time updates. Deduct 5 points if API documentation is missing, and 3 points if no proper error handling between frontend and backend. Full score requires complete API integration with proper authentication and data validation.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data points, network interruptions, invalid input parameters, model prediction failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should include proper exception handling, data validation, and graceful degradation. Give 10 points if fully implemented, 5 points if robustness is average, and 0 points if no exceptions are handled.",
-      "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 anomaly detection alerts 2. What-if scenario analysis for different scheduling strategies 3. AI-powered recommendations for energy optimization 4. Integration with weather data for better predictions). 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 prediction models (e.g., multiple forecasting algorithms without proper comparison) 2. Function modules unrelated to power management (e.g., built-in social features) 3. Overly complex visualizations that affect performance (e.g., 3D animations without functional purpose). Deduct 3 points for each redundancy found, and directly deduct 10 points if core prediction/scheduling functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (separating prediction models, scheduling algorithms, data access layers, and Angular components/services), unit test coverage for critical algorithms, and proper build configuration. Deduct 5 points if global state pollution is found or design patterns are not used; deduct 5 points if code duplication rate is too high (over 30%); deduct 5 points if no automated testing or build pipeline is implemented. Full score requires clean architecture with proper separation of concerns.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the Angular dashboard follows modern design principles: 1) Professional color scheme suitable for industrial applications (no more than 3 primary colors) 2) Proper grid layout with consistent spacing (following 8px grid system) 3) Professional typography with readable fonts (body text ≥ 14px, line height ≥ 1.5). Deduct 3 points for each cluttered visual element, 5 points for inappropriate color combinations that hinder data interpretation, and 5 points for poor information hierarchy. Full score requires clean, professional industrial UI design.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and seamless?",
-      "description": "Judge whether the Angular application's dynamic effects conform to user experience standards: 1) Data loading feedback ≤ 100ms 2) Chart transitions and animations between 300-500ms 3) Clear visual indicators for prediction confidence and scheduling status. Deduct 5 points for each operation without proper loading states, 3 points for choppy chart animations during data updates, and 5 points if critical prediction/scheduling controls are hard to locate. Full score requires smooth, responsive interactions with proper visual feedback.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Predictive Modeling",
-  "difficulty": "hard"
-}

package/library/data_science-predictive_modeling/program-for-market-software-buy-sell-signals.json

@@ -1,68 +0,0 @@
-{
-  "index": 1503,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Take care to ensure that the code you produce is executable for demonstration. You should create a program that connects to market software to provide buy and sell signals based on individually provided indicator requirements.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the market data connection implementation complete?",
-      "description": "Review whether the code properly implements connection to market software with authentication, error handling, and reconnection mechanisms. Check if it handles different API protocols (REST, WebSocket, FIX) and includes rate limiting compliance. Score 0 if no connection is implemented, 5 if basic connection exists but lacks error handling, and 10 if a robust connection system with failover is provided.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the technical indicators correctly implemented?",
-      "description": "Evaluate whether common technical indicators (e.g., moving averages, RSI, MACD, Bollinger Bands) are accurately calculated with proper mathematical formulas and optimized algorithms. Verify indicator parameterization for customization. Deduct 5 points for calculation errors, 3 points for inefficient implementations that would cause performance issues with large datasets. Full score requires at least 5 properly implemented indicators with customizable parameters.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the signal generation logic comprehensive?",
-      "description": "Check if buy/sell signal generation follows clear rules based on indicator combinations. Verify presence of signal strength categorization, false signal filtering, and confirmation logic. Assess if the system handles conflicting signals appropriately. Deduct 5 points if signals are based on single indicators only, 3 points if there's no noise filtering. Give 10 points only if the system includes multiple timeframe analysis and signal confirmation strategies.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the program include backtesting capability?",
-      "description": "Evaluate whether the code includes historical backtesting functionality with performance metrics (win rate, profit factor, maximum drawdown, Sharpe ratio). Check if it handles different market conditions and allows parameter optimization. Score 0 if no backtesting exists, 5 if basic backtesting without performance metrics is implemented, and 10 if comprehensive backtesting with optimization capabilities is provided.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as API disconnections, market data gaps, extreme volatility events, etc.) and provide appropriate error handling and recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Machine learning signal validation 2. Sentiment analysis integration 3. Risk management with position sizing algorithms). 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 indicators or signals 2. Function modules unrelated to trading decision making 3. Unnecessary complex calculations that add little value to signal generation. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data fetching/signal generation/notification layers), unit test coverage, and logging mechanisms. 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's no appropriate error logging system. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the visualization interface meet professional standards?",
-      "description": "Evaluate whether the trading interface (if applicable) follows professional design principles: 1) Clear presentation of indicators and signals 2) Proper use of colors for buy/sell signals (e.g., green/red) 3) Legible charts with appropriate time scaling. Deduct 3 points for cluttered visualizations, 5 points for misleading visual representations of data, and 5 points for charts lacking essential information (price, volume, time). The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the alert and notification system effective?",
-      "description": "Judge whether the signal notification system is well-designed: 1) Timely alerts within 1 second of signal generation 2) Multiple notification channels (email, SMS, push notifications) 3) Clear differentiation between signal types and urgency levels. Deduct 5 points for delayed notifications, 3 points for limited notification options, and 5 points for ambiguous alert messages that don't clearly indicate action required. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Predictive Modeling",
-  "difficulty": "hard"
-}

package/library/data_science-predictive_modeling/real-time-trading-signals-high-accuracy.json

@@ -1,68 +0,0 @@
-{
-  "index": 1563,
-  "question": "You are a code expert. Please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate can be executed and displayed. Integrate real-time market data to show buy and sell signals with 90% accuracy and 30% return rate. After generating the code, conduct practical testing.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the market data integration system fully implemented?",
-      "description": "Review whether the code properly integrates with market data APIs (like Yahoo Finance, Alpha Vantage, or IEX Cloud), implements proper error handling for API limits/failures, and correctly parses the returned data. Score 0 if no real market data integration is implemented, 5 if basic integration exists but lacks error handling, and 10 if comprehensive data fetching with fallback mechanisms and caching strategies is included.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Are the buy/sell signal algorithms properly implemented with verification?",
-      "description": "Evaluate whether the code implements substantiated technical analysis algorithms (such as MACD, RSI, Bollinger Bands) or machine learning models with proper backtesting framework. Check if the claimed 90% accuracy is verified with proper statistical testing (precision, recall, F1 score) on out-of-sample data. Score 0 if algorithms are merely referenced without implementation, 5 if basic indicators are implemented but lack validation, and 10 if comprehensive signal generation with statistical validation is provided.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is a performance backtesting system implemented to verify the 30% return rate?",
-      "description": "Check whether the code includes a proper backtesting framework that accounts for transaction costs, slippage, and market impact. Verify that the claimed 30% return is tested against historical data with proper risk-adjusted metrics (Sharpe ratio, maximum drawdown, Sortino ratio). Deduct 5 points if backtesting doesn't include transaction costs, and 3 points if risk metrics are missing. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the visualization of market data and signals well-implemented?",
-      "description": "Review whether the code implements interactive charts (using libraries like D3.js, Highcharts, or Plotly) that clearly mark buy/sell signals on price data, with proper tooltips, zoom functionality, and time period selection. Score 0 if no visualization is implemented, 5 if basic static charts are provided, and 10 if fully interactive visualizations with clear signal indicators and performance metrics are included.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data points, API failures, market holidays, extreme volatility, 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 alerts via email/SMS 2. Portfolio optimization suggestions 3. Market sentiment analysis integration). 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 technical indicators 2. Function modules unrelated to trading (e.g., unnecessary social media integration) 3. Fancy effects that affect performance (e.g., excessive animations that slow down market data 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 data fetching/analysis/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 financial dashboard standards?",
-      "description": "Evaluate whether the design follows professional financial interface principles: 1) Appropriate color schemes for market data (red/green for price changes, muted colors for background) 2) Clear data hierarchy with proper emphasis on key metrics 3) Professional typography with high readability for numbers. Deduct 3 points for each misleading visual element, 5 points for inappropriate color schemes that hinder data interpretation, and 5 points for cluttered dashboards that obscure critical information. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the dynamic interaction smooth and responsive for real-time market updates?",
-      "description": "Judge whether the dynamic effects support effective market monitoring: 1) Real-time data updates without page refresh 2) Smooth transitions when new data points arrive 3) Responsive interface that maintains performance even with high-frequency data. Deduct 5 points for each second of lag in data updates, 3 points for jumpy/disruptive transitions during data refreshes, and 5 points for performance degradation during market hours. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Predictive Modeling",
-  "difficulty": "hard"
-}

package/library/data_science-predictive_modeling/sales-forecasts-in-tabular-format.json

@@ -1,68 +0,0 @@
-{
-  "index": 965,
-  "question": "You are a coding expert. Please use your professional knowledge to generate accurate and professional responses. Make sure that the code you generate is executable for demonstration. Generate sales forecasts in a tabular format.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the forecasting algorithm properly implemented?",
-      "description": "Evaluate whether the code implements a statistically sound forecasting method (e.g., time series analysis, regression, exponential smoothing, ARIMA). Check if the algorithm handles seasonality, trends, and cyclical patterns. Score 0 if no forecasting logic exists, 5 if only basic linear projection is implemented, and 10 if multiple sophisticated forecasting methods are available with accuracy metrics.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data processing pipeline robust?",
-      "description": "Review whether the code includes proper data cleaning, normalization, and transformation steps. Check for handling of missing values, outliers, and data type conversions. Verify if the code can process different input data formats (CSV, Excel, JSON, etc.). Deduct 5 points if missing value handling is omitted, 3 points if outlier detection is absent. Full score for comprehensive preprocessing with validation steps.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the tabular output format well-implemented?",
-      "description": "Assess if the table has proper headers, consistent formatting of numbers (decimal places, thousands separators), appropriate column widths, and clear labeling. Check if the table includes important metrics like forecast values, confidence intervals, and percentage changes. Deduct 5 points if the table lacks proper formatting, 3 points if it's missing essential sales metrics.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Are visualization components included to complement tabular data?",
-      "description": "Check if the code generates complementary visual representations (charts, graphs) that enhance understanding of the forecasts. Evaluate whether appropriate chart types are used (line charts for trends, bar charts for comparisons). Deduct 5 points if no visualizations are provided, 3 points if visualizations lack interactivity or legends.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as malformed input data, unexpected data types, edge cases) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should 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 of forecast periods 2. Auto-recommendation of best forecasting method based on data characteristics 3. Exportable reports with findings). 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 forecasting algorithms 2. Function modules unrelated to sales forecasting (e.g., unnecessary marketing analysis) 3. Complex visualizations that don't add analytical value. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data processing/modeling/visualization layers), documentation quality, and maintainability. Deduct 5 points if global variables are overused; deduct 5 points if the code lacks comments or documentation; deduct 5 points if the code structure makes it difficult to extend or modify. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the table design meet professional standards?",
-      "description": "Evaluate whether the table follows professional design principles: 1) Consistent typography (font size, weight for different data categories) 2) Proper use of borders, spacing, and alignment 3) Clear visual hierarchy between headers, data, and totals. Deduct 3 points for inconsistent formatting, 5 points for poor information hierarchy, and 5 points for cluttered layout. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction intuitive and responsive?",
-      "description": "Judge whether the interface provides intuitive controls for adjusting forecast parameters and viewing results: 1) Clear input mechanisms for date ranges and variables 2) Responsive updates when parameters change 3) Informative tooltips or context information. Deduct 5 points if parameters cannot be adjusted, 3 points for slow response times, and 5 points if the interaction flow is confusing. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Predictive Modeling",
-  "difficulty": "medium"
-}

package/library/data_science-predictive_modeling/stock-k-line-wave-analysis-buy-sell-points.json

@@ -1,68 +0,0 @@
-{
-  "index": 807,
-  "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 the analysis of K-line wave cycles for each stock in Shanghai and Shenzhen markets, combined with the K-line wave analysis of both markets' overall trends, determine the one-week trend direction. Display individual stock price movements with dotted line code, and edit the code to show buy/sell points with alerts based on predicted price movements.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "K-line data structure implementation and retrieval",
-      "description": "Evaluate whether the code properly defines K-line data structures (OHLCV - Open, High, Low, Close, Volume) with proper typing and efficient retrieval mechanisms. Check if the code fetches real-time or historical data from Shanghai/Shenzhen markets through appropriate APIs with error handling. Score 0 if K-line data structure is missing, 5 if basic structures exist but lack error handling, 10 if comprehensive implementation with efficient retrieval and proper error handling.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Wave cycle detection algorithm implementation",
-      "description": "Review the implementation of technical indicators used for wave analysis (e.g., Moving Averages, Bollinger Bands, MACD, KDJ, Fibonacci retracements). Check if the code includes at least three different technical indicators and implements proper pattern recognition algorithms. Deduct 5 points if only basic MA crossover is implemented, 3 points if trend strength validation is missing. The full score requires detection of Elliott Waves or similar complex patterns with accuracy validation mechanisms.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Market-wide trend correlation analysis",
-      "description": "Assess whether the code correlates individual stock movements with market-wide indices to predict trend direction. Check if it includes Shanghai Composite Index and Shenzhen Component Index data with proper weighting algorithms, sector rotation analysis, and market breadth indicators. Deduct 5 points if only one market index is analyzed, 3 points if sector correlation is missing, and 5 points if there's no volatility comparison between individual stocks and the broader market.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Trend prediction and visualization with dotted line",
-      "description": "Evaluate the implementation of trend prediction for the one-week forecast with proper backtesting mechanisms. Review the dotted line visualization that represents predicted price movements, including proper styling, differentiation from historical data, and confidence intervals. Score 0 if prediction visualization is missing, 5 if basic prediction exists without confidence intervals, 10 if comprehensive visualization with multiple scenarios (bullish/bearish/neutral) and probability indicators.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as missing data points, market holidays, sudden volatility spikes, API failures, etc.) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should be able to effectively handle these edge cases, giving 10 points. If the robustness is average, give 5 points, and if no exceptions are handled, give 0 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 5,
-      "title": "Are there any innovative features that are eye-catching?",
-      "description": "Check whether the code includes surprise features that enhance the experience (e.g., 1. Real-time alert notification system 2. Multi-timeframe analysis (daily/weekly/monthly comparisons) 3. Volume profile analysis 4. Sentiment analysis integration from news 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 calculation of similar technical indicators (e.g., multiple moving average calculations with similar periods) 2. Function modules unrelated to stock analysis (e.g., cryptocurrency data) 3. Fancy visual effects that affect performance (e.g., excessive animations or transitions). Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating data fetching/analysis/visualization layers), caching strategies for performance, and proper documentation. 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's no optimization for handling large datasets. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional financial analysis standards?",
-      "description": "Evaluate whether the visualization follows financial charting best practices: 1) Professional color scheme (green/red for price movements, neutrals for background) 2) Clear labeling of axes and indicators 3) Proper scaling that prevents visual distortion of trends 4) Clean, uncluttered layout with information hierarchy. Deduct 3 points for each misleading visual element, 5 points for color schemes that make pattern recognition difficult, and 5 points for overlapping elements that obscure important data. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the buy/sell alert system effective and user-friendly?",
-      "description": "Judge whether the alert system meets these requirements: 1) Clear visual differentiation between buy/sell signals 2) Configurable alert thresholds 3) False positive minimization through confirmation patterns 4) Alert history tracking. Deduct 5 points if alerts don't include confidence levels, 3 points if alert conditions aren't clearly documented, and 5 points if there's no mechanism to validate alert accuracy against actual market movements. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Predictive Modeling",
-  "difficulty": "hard"
-}

package/library/data_science-statistical_analysis/ahp-decision-making-program.json

@@ -1,68 +0,0 @@
-{
-  "index": 1580,
-  "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. Help me write a small program using AHP (Analytic Hierarchy Process) for decision-making.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the AHP core algorithm correctly implemented?",
-      "description": "Examine whether the code correctly implements the key components of AHP: criteria matrix creation, normalization, consistency check (CR < 0.1), and final weight calculation. Check for the presence of eigenvector calculation for weights and proper consistency ratio calculation using Random Index (RI) values. Award 10 points for complete implementation, 5 points if only basic matrix operations are present without consistency checking, 0 points if the core algorithm is missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the pairwise comparison functionality complete?",
-      "description": "Verify if the code includes mechanisms for users to input pairwise comparisons using the standard 1-9 scale. Check if the implementation properly handles reciprocal values (if A is 3 times more important than B, then B must be 1/3 as important as A). Award 10 points for complete implementation with validation, 5 points if only basic input is provided without validation, 0 points if the functionality is missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is a hierarchical structure for criteria and alternatives properly implemented?",
-      "description": "Evaluate whether the code allows for a proper hierarchical structure with main criteria, possible sub-criteria, and alternatives. The program should be able to handle at least one level of sub-criteria. Deduct 5 points if only flat criteria are supported without hierarchy, deduct 3 points if the hierarchy is limited to only two levels. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Does the program provide comprehensive results and sensitivity analysis?",
-      "description": "Check if the program calculates final alternative rankings and provides some form of sensitivity analysis to understand how changes in judgments affect the final decision. Verify if visualization of results is included (bar charts, tables, etc.). Award 10 points if comprehensive results with sensitivity analysis are present, 5 points for basic results without sensitivity analysis, 0 points if results presentation is minimal or missing.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code handles common errors (such as invalid inputs, inconsistent judgments, matrix singularity issues) and provides friendly error prompts or recovery mechanisms. Code with strong robustness should validate all user inputs, handle mathematical edge cases, and prevent program crashes. Give 10 points if comprehensive error handling exists, 5 points if basic error handling is present, and 0 points if no error handling is implemented.",
-      "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 visualization of hierarchy 2. Automated recommendations for inconsistent judgments 3. Export capabilities to PDF/Excel 4. Group decision support). 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 matrix normalization methods) 2. Function modules unrelated to AHP decision-making 3. Unnecessary complexity that could be simplified. Deduct 3 points for each redundancy found, and directly deduct 10 points if the core functions are interfered with by redundant code.",
-      "maxScore": 10
-    },
-    {
-      "id": 7,
-      "title": "Does the code have engineering quality?",
-      "description": "Review modular design (such as separating calculation logic from UI), code organization, documentation, and potential for reuse. 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 documentation is insufficient. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface design meet professional standards?",
-      "description": "Evaluate whether the user interface (if included) follows good design principles: 1) Clear organization of input forms 2) Intuitive flow from criteria definition to results 3) Proper use of tables and input controls. Deduct 3 points for each confusing interface element, 5 points for poor organization of the decision hierarchy, and 5 points for unclear results presentation. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the user interaction intuitive and helpful?",
-      "description": "Judge whether the program provides clear guidance through the AHP process: 1) Clear instructions for pairwise comparisons 2) Helpful feedback on consistency 3) Understandable presentation of results. Deduct 5 points if users must understand AHP deeply before using the program, 3 points if the comparison process is tedious without shortcuts, and 5 points if results interpretation requires external explanation. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Statistical Analysis",
-  "difficulty": "easy"
-}

package/library/data_science-statistical_analysis/browser-data-post-processing-software.json

@@ -1,68 +0,0 @@
-{
-  "index": 1047,
-  "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. Help me complete a program, a browser-based data post-processing software, with functions including data import, data processing, data statistics, and speed-based statistics.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the data import functionality comprehensively implemented?",
-      "description": "Review whether the code supports multiple data formats (CSV, JSON, XML, Excel) with proper file validation and parsing. Check if drag-and-drop upload, batch import, and large file chunked processing are implemented. Score 0 if only basic file reading is present, 5 if single format import works, and 10 if multiple formats with validation and error handling are fully supported.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the data processing engine robust and feature-complete?",
-      "description": "Evaluate whether the processing capabilities include data cleaning (null value handling, duplicate removal), transformation (filtering, sorting, grouping), and computation (aggregation, mathematical operations). Check for undo/redo functionality and processing history. Deduct 5 points if no data validation is present, 3 points if processing operations cannot be chained. Full score requires comprehensive processing pipeline with preview capabilities.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Are comprehensive data statistics features implemented?",
-      "description": "Check whether statistical analysis includes descriptive statistics (mean, median, mode, standard deviation), correlation analysis, and trend analysis. Verify if results are exportable and visualized through charts/graphs. Deduct 5 points if only basic calculations are present, 3 points if no visualization is provided. Full score requires advanced statistical functions with interactive charts.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is speed-based statistics functionality properly designed and implemented?",
-      "description": "Evaluate whether the system can measure and analyze processing speeds, performance metrics, and throughput statistics. Check for real-time performance monitoring, benchmark comparisons, and performance optimization suggestions. Deduct 5 points if only basic timing is implemented, 3 points if no performance analytics dashboard is present. Full score requires comprehensive speed analysis with actionable insights.",
-      "maxScore": 10
-    },
-    {
-      "id": 4,
-      "title": "Is the code robust?",
-      "description": "Evaluate whether the code can handle common abnormal situations (such as corrupted files, invalid data formats, memory limitations, browser compatibility issues) and provide friendly error prompts or recovery mechanisms. Code with strong robustness should effectively handle edge cases including large dataset processing without crashes. Give 10 points if fully robust, 5 points if average, and 0 points if no exception handling.",
-      "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 data preview during processing 2. Smart data type detection and suggestions 3. Collaborative data sharing capabilities 4. Advanced visualization templates). 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 data parsing logics coexisting) 2. Function modules unrelated to data processing (e.g., built-in games or social features) 3. Fancy effects that affect performance (e.g., excessive animations during data processing). Deduct 3 points for each redundancy found, and directly deduct 10 points if 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/UI/storage layers), error handling coverage, and code organization. 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 proper data validation or sanitization is implemented. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional font system (body font size ≥ 14px, line height over 1.5 times) 4) Clear data table presentation with proper contrast ratios. Deduct 3 points for each crowded visual element, 5 points for glaring color combinations, and 5 points for chaotic data 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) File upload feedback delay ≤ 100ms 2) Data processing progress indicators with smooth animations 3) Transition effects controlled between 300-500ms 4) Clear visual focus guidance during multi-step workflows. Deduct 5 points for each operation without feedback, 3 points for laggy data table scrolling, and 5 points for hard-to-find key function buttons. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Statistical Analysis",
-  "difficulty": "hard"
-}

package/library/data_science-statistical_analysis/data-analysis-tool-with-excel-support.json

@@ -1,68 +0,0 @@
-{
-  "index": 738,
-  "question": "You are a code expert, please use your professional knowledge to generate accurate and professional responses. Make sure the code you generate is functional for demonstration purposes.\n\nData Collection Form: Used to record field survey data, such as facility conditions, questionnaire results, observation records, etc.\n\nQuestionnaire Statistics Table: Organizes questionnaire responses, including basic information, satisfaction ratings, and open-ended questions.\n\nIssue Coding Table: Categorizes and codes observed problems for subsequent statistical analysis.\n\nStatistical Analysis Table: Performs descriptive statistics, such as facility coverage rate, problem frequency, etc.\n\nVisualization Chart Templates: Guides users on how to generate bar charts, radar charts, etc. using Excel's built-in charting functions.\n\nPlace all the above table contents into a single HTML tool file, with support for Excel import and export functionality on the page.",
-  "checklist": [
-    {
-      "id": 0,
-      "title": "Is the Data Collection Form fully implemented?",
-      "description": "Evaluate whether the HTML form properly implements fields for recording field survey data (facility conditions, questionnaire results, observation records). Check for form validation, field types appropriateness (text, number, dropdown, date), and conditional logic. Score 0 if missing entirely, 5 if basic fields exist without validation, and 10 if comprehensively implemented with proper validation and field dependencies.",
-      "maxScore": 10
-    },
-    {
-      "id": 1,
-      "title": "Is the Questionnaire Statistics Table properly structured?",
-      "description": "Review the implementation of the questionnaire responses organization system, including sections for basic information, satisfaction ratings, and open-ended questions. Check for proper data typing, sorting capabilities, filtering options, and aggregation functions. Deduct 3 points if missing search functionality, 3 points if lacking data validation, and 4 points if aggregation functions are absent. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 2,
-      "title": "Is the Issue Coding Table implementation complete?",
-      "description": "Assess whether the code includes a robust system for categorizing and coding observed problems with hierarchical categories, subcategories, and unique identifiers. Check for code search functionality, code relationship mapping, and frequency tracking. Deduct 5 points if hierarchical categorization is missing, and 5 points if no code relationship visualization exists. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 3,
-      "title": "Is the Statistical Analysis Table functionality comprehensive?",
-      "description": "Evaluate whether the implementation includes proper descriptive statistics calculations (mean, median, mode, standard deviation), facility coverage rate calculation, problem frequency analysis, and cross-tabulation capabilities. Check for formula correctness and automatic recalculation. Deduct 3 points for each missing statistical function, and 5 points if calculations contain errors. 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 data input, file import/export errors, 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. Auto-save functionality 2. Dark/light mode toggle 3. Responsive design for mobile devices 4. Data visualization previews). 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 data export methods with identical functionality) 2. Function modules unrelated to data collection and analysis (e.g., unnecessary animations) 3. Features that affect performance (e.g., heavy DOM operations or excessive event listeners). 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/view/controller layers), code organization, and 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's no error handling for Excel import/export operations. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 8,
-      "title": "Does the interface vision meet professional design standards?",
-      "description": "Evaluate whether the overall design follows modern design principles: 1) Harmonious color matching (no more than 3 primary colors) 2) Proper layout spacing (element spacing follows the 8px multiple principle) 3) Professional form layout (clear sections, aligned inputs, consistent styling). Deduct 3 points for each crowded visual element, 5 points for a glaring color combination, and 5 points for chaotic table layouts. The full score is 10 points.",
-      "maxScore": 10
-    },
-    {
-      "id": 9,
-      "title": "Is the Excel import/export functionality properly implemented?",
-      "description": "Judge whether the Excel import/export functionality works as expected: 1) Supports standard Excel formats (.xlsx, .xls) 2) Maintains data integrity during import/export 3) Provides proper progress indication and error handling 4) Preserves formatting and formulas where appropriate. Deduct 5 points if only one direction (import or export) is implemented, 3 points for data loss during transfer, and 5 points if the operation is not user-friendly. The full score is 10 points.",
-      "maxScore": 10
-    }
-  ],
-  "class": "Data Science-Statistical Analysis",
-  "difficulty": "hard"
-}