QuantumChecker 0.3.2__tar.gz → 0.3.4__tar.gz

{quantumchecker-0.3.2 → quantumchecker-0.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: QuantumChecker
-Version: 0.3.2
+Version: 0.3.4
 Summary: A package to evaluate homework submissions in Python, SQL, PowerBI, and SSIS.
 Author: Qobiljon
 Author-email: qobiljonkhayrullayev@gmail.com

{quantumchecker-0.3.2 → quantumchecker-0.3.4}/QuantumCheck/powerbi_evaluator.py

@@ -17,22 +17,37 @@ import base64
 
 def prompt_text_powerbi(combined_content: str) -> str:
     return f"""
-    Evaluate the following Power BI DAX question-answer pairs for correctness, clarity, and appropriateness.
-    Provide an overall score out of 100 and concise feedback. Focus on DAX logic and structure.
-    Structure the response as:
-    OVERALL SCORE: [SCORE]/100
-    [FEEDBACK]
+            You are an expert Power BI instructor evaluating beginner-level DAX question-answer pairs.
+            
+            Each answer contains a data model (in JSON format) extracted from a submitted .pbit file. Evaluate the technical correctness, relevance, and clarity of the DAX elements provided.
+            
+            Use the following criteria to give a fair and supportive evaluation:
+            - Measures (40 points): Are calculated measures meaningful, syntactically valid, and aligned with the question?
+            - Relationships (20 points): Are key relationships between tables defined logically?
+            - Tables & Columns (20 points): Are relevant tables/columns present? Are naming conventions clear?
+            - Expressions (10 points): Are query partitions or expressions present and understandable?
+            - Overall structure (10 points): Does the model appear coherent and purposeful?
+            
+            **Scoring Tolerance**:
+            - Be kind to beginners. Do not give extremely low scores unless the model is completely missing or incorrect.
+            - If measures exist and make some sense, award partial credit (e.g., 20–30 out of 40).
+            - A score below 30/100 should only be given if there’s little to no relevant content.
+            
+            Structure your response exactly like this:
+            OVERALL SCORE: [SCORE]/100  
+            [Brief feedback here — 3–5 sentences focused on strengths + areas to improve.]
+{combined_content}
+"""
 
-    {combined_content}
-    """
 
 
 load_dotenv()
 logger = logging.getLogger(__name__)
+
 logging.basicConfig(
     level=logging.INFO,
     format="%(asctime)s - %(name)s - %(levelname)s - %(message)s",
-    handlers=[logging.FileHandler("../powerbi_evaluator.log"), logging.StreamHandler()]
+    handlers=[logging.StreamHandler()]
 )
 
 

{quantumchecker-0.3.2 → quantumchecker-0.3.4}/QuantumCheck/ssis_evaluator.py

@@ -10,7 +10,7 @@ from pprint import pprint
 import json
 import re
 
-from .prompts import prompt_text_ssis  # Assumes this is defined in .prompts
+from .prompts import prompt_text_ssis
 
 logger = logging.getLogger(__name__)
 
@@ -90,7 +90,7 @@ class SSISAnswerParser:
                 "issues": []
             }
 
-            # Parse package info
+
             package_info = {
                 "Package Name": root.attrib.get("{www.microsoft.com/SqlServer/Dts}ObjectName", "Unknown"),
                 "Creation Date": root.attrib.get("{www.microsoft.com/SqlServer/Dts}CreationDate", "Unknown"),
@@ -101,7 +101,7 @@ class SSISAnswerParser:
             structured_data["package_info"] = package_info
             summary.append(f"Package: {package_info['Package Name']} (Created: {package_info['Creation Date']})")
 
-            # Parse package description from comments
+
             package_description = "No description found"
             comment_pattern = re.compile(r'<!--\s*Package Description:\s*(.*?)\s*-->', re.DOTALL)
             match = comment_pattern.search(content)
@@ -109,7 +109,7 @@ class SSISAnswerParser:
                 package_description = match.group(1).strip()
                 summary.append(f"Description: {package_description}")
 
-            # Parse connection managers
+
             for conn in root.findall(".//DTS:ConnectionManager", namespace):
                 try:
                     conn_name = conn.attrib.get("{www.microsoft.com/SqlServer/Dts}ObjectName", "Unnamed Connection")
@@ -133,14 +133,14 @@ class SSISAnswerParser:
                     summary.append(
                         f"Connection: {conn_name} ({conn_type}, ConnectionString: {conn_details['ConnectionString']})")
                     structured_data["connections"].append(conn_details)
-                    # Validate connection
+
                     if conn_type == "OLEDB" and "Initial Catalog" not in conn_details["ConnectionString"]:
                         structured_data["issues"].append(f"OLEDB Connection {conn_name} missing database specification")
                 except AttributeError as e:
                     structured_data["issues"].append(f"Error parsing connection {conn_name}: {str(e)}")
                     logger.error("Error parsing connection %s: %s", conn_name, str(e))
 
-            # Parse variables
+
             for var in root.findall(".//DTS:Variable", namespace):
                 try:
                     var_name = var.attrib.get("{www.microsoft.com/SqlServer/Dts}ObjectName", "Unnamed Variable")
@@ -155,7 +155,7 @@ class SSISAnswerParser:
                     structured_data["issues"].append(f"Error parsing variable {var_name}: {str(e)}")
                     logger.error("Error parsing variable %s: %s", var_name, str(e))
 
-            # Parse data flow components
+
             component_ids = set()
             for component in root.findall(".//DTS:Executables//component", namespace):
                 try:
@@ -168,7 +168,7 @@ class SSISAnswerParser:
                     structured_data["issues"].append(f"Error parsing component {comp_name}: {str(e)}")
                     logger.error("Error parsing component %s: %s", comp_name, str(e))
 
-            # Parse data flow paths
+
             for path in root.findall(".//DTS:Executables//path", namespace):
                 try:
                     start_id = path.attrib.get("startId", "Unknown Start")
@@ -183,14 +183,14 @@ class SSISAnswerParser:
                     structured_data["issues"].append(f"Error parsing path {path_name}: {str(e)}")
                     logger.error("Error parsing path %s: %s", path_name, str(e))
 
-            # Additional validations
+
             if not structured_data["connections"]:
                 structured_data["issues"].append("No connections configured in the package")
             if not structured_data["data_flow_paths"]:
                 structured_data["issues"].append("No data flow paths configured in the package")
 
             combined_summary = "\n".join(summary)[:2000] or "No components found in SSIS package"
-            # Split summary into logical sections for multiple questions
+
             answers = []
             sections = ["Package", "Description", "Connection", "Variable", "Component", "Data Flow Path"]
             current_section = []
@@ -207,7 +207,7 @@ class SSISAnswerParser:
                 logger.warning("No valid answers found in single SSIS file")
                 answers = [combined_summary]
 
-            # Save structured data for debugging
+
             with open("parsed_ssis_summary.json", "w", encoding="utf-8") as f:
                 json.dump(structured_data, f, indent=2)
             logger.info("Saved structured SSIS summary to 'parsed_ssis_summary.json'")
@@ -337,7 +337,7 @@ class SSISEvaluator:
         """
         try:
             if answer_path.lower().endswith(".zip"):
-                # Use provided temp_dir or generate a default one
+
                 temp_dir = temp_dir or f"temp_ssis_extract_{os.getpid()}"
                 parsed_data = SSISAnswerParser.parse_zip_file(answer_path, temp_dir)
             elif answer_path.lower().endswith('.dtsx'):
@@ -361,17 +361,17 @@ class SSISEvaluator:
             logger.info("Processing %d questions and %d answers", len(questions), len(answers))
             pprint(f"Processing {len(questions)} questions and {len(answers)} answers")
 
-            # Map answers to questions
+
             if not answers:
                 logger.warning("No answers parsed from SSIS file")
                 answers = ["No valid SSIS components found"] * len(questions)
             elif len(answers) < len(questions):
-                # Cycle through answers to match question count
+
                 answers = [answers[i % len(answers)] for i in range(len(questions))]
                 logger.debug("Expanded %d answers to %d for %d questions", len(parsed_data["text_answers"]),
                              len(answers), len(questions))
             elif len(answers) > len(questions):
-                # Truncate to match question count
+
                 answers = answers[:len(questions)]
                 logger.debug("Truncated %d answers to %d for %d questions", len(parsed_data["text_answers"]),
                              len(answers), len(questions))

{quantumchecker-0.3.2 → quantumchecker-0.3.4}/QuantumChecker.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: QuantumChecker
-Version: 0.3.2
+Version: 0.3.4
 Summary: A package to evaluate homework submissions in Python, SQL, PowerBI, and SSIS.
 Author: Qobiljon
 Author-email: qobiljonkhayrullayev@gmail.com

{quantumchecker-0.3.2 → quantumchecker-0.3.4}/setup.py

@@ -2,7 +2,7 @@ from setuptools import setup, find_packages
 
 setup(
     name="QuantumChecker",
-    version="0.3.2",
+    version="0.3.4",
     author="Qobiljon",
     author_email="qobiljonkhayrullayev@gmail.com",
     description="A package to evaluate homework submissions in Python, SQL, PowerBI, and SSIS.",