CCC '11 J4 - Boring Business

View as PDF

Submit solution

Points: 7
Time limit: 1.0s
Memory limit: 64M

Problem type
Allowed languages
Ada, Assembly, Awk, Brain****, C, C#, C++, COBOL, CommonLisp, D, Dart, F#, Forth, Fortran, Go, Groovy, Haskell, Intercal, Java, JS, Kotlin, Lisp, Lua, Nim, ObjC, OCaml, Octave, Pascal, Perl, PHP, Pike, Prolog, Python, Racket, Ruby, Rust, Scala, Scheme, Sed, Swift, TCL, Text, Turing, VB, Zig
Canadian Computing Competition: 2011 Stage 1, Junior #4

Boring is a type of drilling, specifically, the drilling of a tunnel, well, or hole in the earth. With some recent events, such as the Deepwater Horizon oil spill and the rescue of Chilean miners, the public became aware of the sophistication of the current boring technology. Using the technique known as geosteering, drill operators can drill wells vertically, horizontally, or even on a slant angle.

A well plan is prepared before drilling, which specifies a sequence of lines, representing a geometrical shape of the future well. However, as new information becomes available during drilling, the model can be updated and the well plan modified.

Your task is to write a program that verifies validity of a well plan by verifying that the borehole will not intersect itself. A two-dimensional well plan is used to represent a vertical cross-section of the borehole, and this well plan includes some drilling that has occurred starting at (0, -1) and moving to (-1, -5). You will encode in your program the current well plan shown in the figure below:


Input Specification

The input consists of a sequence of drilling command pairs. A drilling command pair begins with one of four direction indicators (d for down, u for up, l for left, and r for right) followed by a positive length. There is an additional drilling command indicated by q (quit) followed by any integer, which indicates the program should stop execution. You can assume that the input is such that the drill point will not:

  • rise above the ground, nor
  • be more than 200 units below ground, nor
  • be more than 200 units to the left of the original starting point, nor
  • be more than 200 units to the right of the original starting point

Output Specification

The program should continue to monitor drilling assuming that the well shown in the figure has already been made. As we can see (-1, -5) is the starting position for your program. After each command, the program must output one line with the coordinates of the new position of the drill, and one of the two comments safe, if there has been no intersection with a previous position or DANGER if there has been an intersection with a previous borehole location. After detecting and reporting a self-intersection, your program must stop.

Sample Input 1

l 2
d 2
r 1
q 0

Output for Sample Input 1

-3 -5 safe
-3 -7 safe
-2 -7 safe

Sample Input 2

r 2
d 10
r 4

Output for Sample Input 2

1 -5 safe
1 -15 DANGER


  • -7
    Tony1234  commented on Sept. 30, 2020, 9:59 p.m.

    This comment is hidden due to too much negative feedback. Click here to view it.

  • 7
    faraz123  commented on Sept. 3, 2020, 8:11 p.m.

    Never mine straight down

  • -5
    puppy  commented on June 3, 2020, 4:01 p.m.

    This comment is hidden due to too much negative feedback. Click here to view it.

  • 3
    Neon  commented on Nov. 27, 2019, 9:22 p.m.

    For test case #3, the input given doesn't seem to seem to intersect, but yet there is DANGER on the last step.

  • 0
    pro  commented on Sept. 13, 2017, 2:26 p.m. edited

    How does the second sample input output Danger? They don't seem to intersect?

    • 1
      injust  commented on Sept. 13, 2017, 4:03 p.m.

      You will encode in your program the current well plan shown in the figure

      • 3
        pro  commented on Sept. 13, 2017, 6:24 p.m.

        OH YES TY

  • -1
    bobhob314  commented on Jan. 16, 2015, 8:07 p.m.

    There is no "q 0". Does there not need to be one if the program terminates due with "DANGER"?

    • 3
      Xyene  commented on Feb. 2, 2015, 9:19 p.m.

      Your program must stop when it's in DANGER, so it's implied you are not to read input past that point. So yes, there need not be a q directive if the drill is in DANGER.