Student Guide

​

Getting Started

​

Logging In

1. Navigate to your Wecode installation URL
2. Enter your username and password
3. Click “Login”

​

First Time Login

• Update your display name
• Set your email address
• Change your password (optional but recommended)

1. Click your username in the top navigation
2. Click “Edit Profile”
3. Update your information
4. Click “Save”

​

Enrolling in Classes

​

Viewing Available Classes

​

Enrolling in a Class

​

Leaving a Class

1. Navigate to the class page
2. Click “Leave” or “Unenroll”
3. Confirm - you’ll lose access to class assignments

​

Viewing Assignments

​

Assignments List

• Assignment name
• Number of problems
• Start and finish times
• Current coefficient (late penalty multiplier)
• Status (not started, active, or finished)
• Your progress

• 🟢 Green: You can submit now
• 🟡 Yellow: Assignment hasn’t started yet
• 🔴 Red: Assignment finished or closed

​

Opening an Assignment

• Read problem descriptions
• Submit solutions
• View your submissions
• See the scoreboard (if enabled)

​

Understanding Problem Descriptions

​

Problem View

• Description of what the program should do
• Input format specification
• Output format specification
• Sample inputs and outputs
• Constraints (time limit, memory limit)

• Points available
• Allowed languages
• Time and memory limits
• Your previous submissions

​

Sample Input/Output

• Understand the problem format
• Test your solution locally
• Debug before submitting

​

PDF Descriptions

1. Click “View PDF” button
2. Download or view the full problem statement
3. Return to the problem page to submit

​

Downloading Test Cases

1. Look for “Download Input” and “Download Output” buttons
2. Click to download ZIP files
3. Extract and use for local testing

​

Submitting Your Solution

​

Submission Methods

• Write code in your IDE
• Save to a file
• Upload through the interface

• Write or paste code directly in the browser
• Use the built-in code editor
• Submit without saving a file

​

Step-by-Step Submission

​

Submission Requirements

• Maximum size varies by installation (typically 64KB)
• Excessively large files will be rejected

• Must match assignment requirements
• Use correct file extension
• Code must compile without errors

• Read from standard input (stdin)
• Write to standard output (stdout)
• Match exact format in problem description
• No extra output (debugging statements)

​

Common Submission Mistakes

• Extra spaces, wrong number of decimal places
• Missing newlines
• Debugging print statements

• Not reading all input
• Wrong order of inputs
• Assuming specific input size

• Empty input
• Maximum values
• Minimum values
• Special cases mentioned in problem

• Inefficient algorithm
• Infinite loops
• Not optimized for large inputs

​

Viewing Submission Results

​

Submissions List

1. Click “Submissions” in the navigation
2. Or click “My Submissions” on the problem page

• Submission ID and time
• Problem name
• Language used
• Status/Verdict
• Score
• Time and memory used

​

Understanding Verdicts

• Your solution is correct!
• Passed all test cases
• Score: 100%
• This is what you want to see

• Output doesn’t match expected output
• Check:
  • Output format (spaces, newlines)
  • Edge cases
  • Logic errors
• Score: Partial credit based on passed test cases

• Your program took too long
• Fix:
  • Use more efficient algorithm
  • Optimize your code
  • Remove unnecessary operations
  • Check for infinite loops

• Your program used too much memory
• Fix:
  • Use less memory in data structures
  • Don’t allocate huge arrays
  • Free unused memory

• Your program crashed during execution
• Common causes:
  • Array index out of bounds
  • Division by zero
  • Null pointer
  • Stack overflow (deep recursion)
  • Segmentation fault

• Your code didn’t compile
• Check:
  • Syntax errors
  • Missing includes/imports
  • Correct language selected
  • File extension matches language

• Submission is queued for judging
• Usually processes in seconds
• If stuck for minutes, contact instructor

​

Viewing Detailed Results

• Your submitted source code
• Syntax highlighted
• Exactly what was judged

• Verdict for each test case
• Time and memory per test case
• Which cases passed/failed
• Percentage score

• Compilation output
• Runtime errors
• Debugging information

​

Selecting Your Final Submission

​

What is a Final Submission?

​

Automatic Selection

1. Best score (highest points)
2. Earliest ACCEPTED (if multiple 100% solutions)

​

Manual Selection

​

Why Manual Selection?

• You prefer an earlier submission with the same score
• A partial solution is acceptable for your strategy
• You want to demonstrate a specific approach

​

Late Penalty Application

Final Score = Problem Score × (Pre-Score / 100) × (Coefficient / 100)

• Problem Score: Points assigned by instructor
• Pre-Score: Percentage of test cases passed
• Coefficient: Late penalty multiplier (100 = no penalty)

• Problem worth 100 points
• You passed 90% of test cases (pre-score = 9000/10000)
• Submitted 2 hours late, penalty is 10% (coefficient = 90)
• Final score = 100 × 0.90 × 0.90 = 81 points

​

Practicing Problems

​

Accessing Practice

​

Practice vs Assignment

• No deadlines
• No late penalties
• Doesn’t count toward class grades
• Great for:
  • Learning new algorithms
  • Preparing for assignments
  • Reviewing after assignments close

• Has deadlines
• Counts toward grades
• May have late penalties
• Limited time window

​

Understanding the Scoreboard

​

Accessing Scoreboard

1. Navigate to an assignment
2. Click “Scoreboard” tab or link
3. View rankings and scores

​

Scoreboard Information

• Your rank
• Your username
• Total score
• Score per problem
• Number of submissions per problem

• 🟢 Green: Accepted (100%)
• 🔴 Red: Attempted but not accepted
• ⚪ Gray: Not attempted

• Score: Points earned
• Attempts: Number of submissions
• Time: When first accepted

​

Scoreboard Strategy

​

Tips for Success

​

Before Coding

​

While Coding

• ✅ Use clear variable names for readability
• ✅ Comment complex logic for your future reference
• ✅ Handle edge cases (empty input, maximum values, etc.)
• ✅ Avoid hardcoding specific values
• ✅ Test incrementally as you code

​

Before Submitting

• ✅ Remove debug output (print statements showing variables)
• ✅ Check input reading (read all input, correct order)
• ✅ Verify output format (exact spacing, newlines)
• ✅ Test with sample cases one more time
• ✅ Check language selection matches your code

​

After Submitting

• ✅ Wait for result before resubmitting
• ✅ Read error messages carefully if failed
• ✅ Fix specific issues don’t rewrite everything
• ✅ Test changes locally before resubmitting

​

Common Problems and Solutions

​

”I can’t submit”

• Assignment is open (not closed)
• Assignment has started
• You’re enrolled in a class assigned to this assignment
• You haven’t exceeded the deadline + extra time
• No other submission from you is pending for this problem

​

”My submission is stuck in PENDING”

• Contact your instructor
• There may be a queue issue
• System administrator may need to intervene

​

”I got WRONG ANSWER but it works on my computer”

1. Output format differences
   • Extra spaces or newlines
   • Missing newlines at end
   • Wrong number of decimal places
2. Hidden test cases
   • Sample cases don’t cover all scenarios
   • Edge cases you didn’t consider
3. Uninitialized variables
   • May have different values on different systems
4. Input reading issues
   • Not reading all input
   • Wrong parsing logic

• Review problem output format
• Create more test cases
• Test edge cases (empty, maximum, minimum)

​

“I got TIME LIMIT EXCEEDED”

1. Use more efficient algorithm
2. Optimize loops
3. Use better data structures
4. Remove unnecessary calculations
5. Read about time complexity

• Bubble sort: O(n²) - slow for large n
• Quick sort: O(n log n) - much faster

​

”I got RUNTIME ERROR”

1. Array bounds: Accessing arr[i] where i >= array size
2. Division by zero: Check denominators
3. Null pointers: Initialize before use
4. Stack overflow: Too much recursion or large local arrays
5. Invalid input: Assuming input format

• Add boundary checks
• Validate input
• Limit recursion depth
• Use smaller data structures

​

”I got COMPILATION ERROR”

1. Syntax errors: Missing semicolons, brackets
2. Includes/imports: Add required libraries
3. Language mismatch: Selected C++ but wrote Python?
4. Compiler version: Some features may not be available

​

Academic Integrity

​

Allowed

• ✅ Discussing approaches with classmates
• ✅ Using online resources to learn algorithms
• ✅ Asking for clarification on problem statements
• ✅ Debugging with help from instructors/TAs
• ✅ Referencing documentation and tutorials

​

Not Allowed

• ❌ Copying code from other students
• ❌ Sharing your code with others
• ❌ Using complete solutions found online
• ❌ Having someone else write your code
• ❌ Submitting code you don’t understand

​

Best Practice

1. Write your own code from scratch
2. Understand every line you submit
3. Cite sources if you use algorithms from references
4. Keep your code private don’t share with classmates
5. Ask for help properly explain your approach, ask for guidance

​

Summary

• ✅ Enroll in classes to access assignments
• ✅ Read problem descriptions carefully
• ✅ Submit code via upload or paste
• ✅ View results and learn from errors
• ✅ Select your best submission as final
• ✅ Practice problems to improve skills
• ✅ Track your progress on scoreboards
• ✅ Follow academic integrity guidelines