DHF Guide 5: Comprehensive Instructor-Level Troubleshooting

🛠️ Guide 5: Comprehensive Instructor-Level Troubleshooting

This guide helps you understand when a project issue is caused by your work versus when it is a structural problem that needs to be fixed by an instructor. 

1. Identifying "Missing Resource" Scenarios Sometimes, a fellow cannot pass a project because the instructor did not provide enough information. 

• The Task Tab Limitation: Instructors often provide a list of steps in the "Task" tab (e.g., Step 1: Create script, Step 2: Import modules). However, if the instructions are too vague (like not providing the exact name of a folder to create), the automated grader will fail you. 
  
  
• Checking for Template Files: Look at the Resources tab. If this section is empty, it is often impossible for a student to guess the exact technical requirements needed to pass the automated check. In this case, the issue should be escalated as an "Instructor Resource Gap". 
  
  
• AI-Generated Files: Most project templates are generated by an AI backend. If an instructor fails to properly link these AI-generated templates to the Resource tab, the fellow will have no starting point to work from. 
  
  

2. Validating Grading ConsistencyIf you believe your project is correct but you are still failing, use this validation logic: 

• The 100-Student Rule: If you are the only person failing with a specific error, it is likely a mistake in your code or directory structure. If 100 students are all complaining about the exact same score (e.g., everyone is stuck at 40/100), this indicates a "Systemic Grading Bug". 
  
  
• Criterion Over-Tightness: Sometimes instructors set the grading criteria too "tight," meaning the system looks for a very specific word or character that might be missing. 
  
  
• The Escalation Bridge: If you suspect a grading bug, expand your results, take a screenshot of the specific failed criteria (e.g., "Script utilizes a while loop: Fail"), and send it to your track lead. They will use that screenshot to adjust the "Rubric" at the backend to make the grading more fair. 
  
  

3. Special Cases for Animation and 3D LinksFor tracks like 3D Animation, the AI grader performs "Visual Reading" of your video link. 

• Technical Soundness: The AI checks for specific principles like "squash and stretch," "parabolic arcs," and "volume retention" in your animation. 
  
  
• Weight Communication: If a project asks for two different balls (one light, one heavy) and you only animate one, the AI will detect the missing energy decay and timing spacing for the second ball, causing a failure. 
  
  
• Public Access Check: If the AI cannot "read" your video, verify that your YouTube or Drive link is not set to "Private". The grader cannot log in to your personal accounts to view files.