ACM reminders October 30 -- HMC Mock contest 9:00 - 12:30 November 10 -- regional contest This is the next ACM meeting !! Contest-like problems dynamic programming graph algorithms search and heuristic search geometric problems simulation problems & Algorithm s BFS, DFS, branch and bound shortest paths, (max flow) knapsack problem
52
Embed
ACM reminders October 30 -- HMC Mock contest 9:00 - 12:30 November 10 -- regional contest This is the next ACM meeting !! Contest-like problems dynamic.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
ACM reminders
October 30 -- HMC Mock contest 9:00 - 12:30
November 10 -- regional contest
This is the next ACM meeting !!
Contest-like problems
dynamic programming
graph algorithms
search and heuristic search
geometric problemssimulation problems
& AlgorithmsBFS, DFS, branch and bound
shortest paths, (max flow)
knapsack problem
HMC contest
When: 9:00 pm - 12:30 am on Tuesday, October 30
Where: here (the graphics lab or in the terminal room)
What: 6 problems
Rules: • only one terminal/keyboard may be used by a team
• written material and references permitted, but electronic resources or computer files aren’t allowed
• teams may have 1-4 people & will be graded equally(first three teams of <= 3 students ACM)
Next time: contest
The following commands will be available in /cs/ACM/bin
Submission/Information:
• acm_submit <filename> -- submits a file for testing• acm_standings -- gets the current standings + time remaining• acm_answers -- prints out written answers & corrections to problems
Ask any questions directly. (The reg. contest has a program for this.)
When a problem is submitted, we will check it by hand and return one of the following messages
• Problem correct!• Presentation error• Wrong output• Run-time error• Did not compile
increasing severity
Strategy
Look over the problems and decide a rough order of difficulty.
When possible, code with someone looking over your shoulder.
Trade off the job of writing code to the person most familiar with the problem.
You can reuse any code written from the time the contest starts.- you may want to immediately code an I/O skeleton or other routines
Scoring
• a team’s score is two numbers: - solved problems - amount of time
• rankings are based on the # of solved problems- ties are broken by time (less time is better)
• time = sum of the # of minutes from the contest start to the solution of each solved problem
• each incorrect submission of a problem incurs a 20 minute time penalty if that problem is solved
Scoring:
for example...
2 problems
5 hrs. 35 min.
submit problem 1 -- incorrect @ 45 min.
submit problem 2 -- correct @ 55 min.
submit problem 1 -- correct @ 1hr. 15 min.
Simulation Problems
Problem 1 - faa.cc Basic idea: use radar data to determine how close planes are to one another and print warnings
1 revolution / 4 seconds0º
75º
270º
planeA planeB
planeC
Radar sweep:
Simulation Problems
Problem 1 - faa.cc Basic idea: use radar data to determine how close planes are to one another and print warnings
1 revolution / 4 seconds0º
75º
270º
planeA planeB
planeC
Radar sweep:
Input Data
0 planeA 1 10000 0 0 0.2
bearing angle from 0 to 360
plane namehorizontal distance (feet)
elevation (feet)
heading angle from 0 to 360
horizontal velocity (ft/s)
ascent velocity (in ft/s)
Simulation Problems
Problem 1 - faa.cc Basic idea: use radar data to determine how close planes are to one another and print warnings
1 revolution / 4 seconds0º
75º
270º
planeA planeB
planeC
Radar sweep:
Input Data
0 planeA 1 10000 0 0 0.2
75 planeB 5.79 10000 270 0 1
270 planeC 2500 10000 0 0 0.2
END OF INPUT
Simulation Problems
Problem 1 - faa.cc Basic idea: use radar data to determine how close planes are to one another and print warnings
1 revolution / 4 seconds0º
75º
270º
planeA planeB
planeC
Radar sweep:
Input Data
0 planeA 1 10000 0 0 0.2
75 planeB 5.79 10000 270 0 1
270 planeC 2500 10000 0 0 0.2
END OF INPUT
Pairs of planes that will travel within 2500 feet of each other in the next 10 seconds.
Output
planeB planeA
planeC planeB
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
Input Data
top: +1
right: +2
bottom: +4
left: +8
WHEN OPEN
8+2 = A
4 3 A C 4 4 7 D 7 D 1 1 3 A
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
Input Data
top: +1
right: +2
bottom: +4
left: +8
WHEN OPEN
8+2 = A
4 3 A C 4 4 7 D 7 D 1 1 3 A
Output
3 7 C 4 2 E A E C 5 3 E 9 6 9 1 3 A B 8 3 A A
5 4 A E C 4 4 5 1 5 3 B A B 6 C 6 9 1 3 B A
0 0
Maze 1: The robots do not meet.
Maze 2: The robots meet in row 1, column 4.
Maze 3: The robots do not meet.
ACM reminders
October 30 -- HMC Mock contest 9:00 - 12:30
November 10 -- regional contest
This is the next ACM meeting !!
Contest-like problems
dynamic programming
graph algorithms
search and heuristic search
geometric problemssimulation problems
& AlgorithmsBFS, DFS, branch and bound
shortest paths, (max flow)
knapsack problem
HMC contest
When: 9:00 pm - 12:30 am on Tuesday, October 30
Where: here (the graphics lab or in the terminal room)
What: 6 problems
Rules: • only one terminal/keyboard may be used by a team
• written material and references permitted, but electronic resources or computer files aren’t allowed
• teams may have 1-4 people & will be graded equally(first three teams of <= 3 students ACM)
Next time: contest
The following commands will be available in /cs/ACM/bin
Submission/Information:
• acm_submit <filename> -- submits a file for testing• acm_standings -- gets the current standings + time remaining• acm_answers -- prints out written answers & corrections to problems
Ask any questions directly. (The reg. contest has a program for this.)
When a problem is submitted, we will check it by hand and return one of the following messages
• Problem correct!• Presentation error• Wrong output• Run-time error• Did not compile
increasing severity
Strategy
Look over the problems and decide a rough order of difficulty.
When possible, code with someone looking over your shoulder.
Trade off the job of writing code to the person most familiar with the problem.
You can reuse any code written from the time the contest starts.- you may want to immediately code an I/O skeleton or other routines
Scoring
• a team’s score is two numbers: - solved problems - amount of time
• rankings are based on the # of solved problems- ties are broken by time (less time is better)
• time = sum of the # of minutes from the contest start to the solution of each solved problem
• each incorrect submission of a problem incurs a 20 minute time penalty if that problem is solved
Scoring:
for example...
2 problems
5 hrs. 35 min.
submit problem 1 -- incorrect @ 45 min.
submit problem 2 -- correct @ 55 min.
submit problem 1 -- correct @ 1hr. 15 min.
Simulation Problems
Problem 1 - faa.cc Basic idea: use radar data to determine how close planes are to one another and print warnings
1 revolution / 4 seconds0º
75º
270º
planeA planeB
planeC
Radar sweep:
Input Data
0 planeA 1 10000 0 0 0.2
75 planeB 5.79 10000 270 0 1
270 planeC 2500 10000 0 0 0.2
END OF INPUT
Pairs of planes that will travel within 2500 feet of each other in the next 10 seconds.
Output
planeB planeA
planeC planeB
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
“ro” “bot”clockwise counterclockwise
(when there is a choice to be made)
Simulation Problems
Problem 2 - roandbot.cc Basic idea: to see if two robots navigating a maze end up running into each other
Input Data
top: +1
right: +2
bottom: +4
left: +8
WHEN OPEN
8+2 = A
4 3 A C 4 4 7 D 7 D 1 1 3 A
Output
3 7 C 4 2 E A E C 5 3 E 9 6 9 1 3 A B 8 3 A A
5 4 A E C 4 4 5 1 5 3 B A B 6 C 6 9 1 3 B A
0 0
Maze 1: The robots do not meet.
Maze 2: The robots meet in row 1, column 4.
Maze 3: The robots do not meet.
Geometric Problems
Problem 1 - Binary Space Partitions
observerBasic idea: draw objects from far (first) to near (last).