3D printer

EVENTS

SOLO

PUZZLES CODE GOLF OPTIMIZATION

MULTI

LEADERBOARDS CLASH OF CODE BOT PROGRAMMING CODING ESCAPE

COMMUNITY

CONTRIBUTIONS LEARN DISCORD FORUM LIVE STREAMS

3D printer

Statement

Goal

You get 3 pictures made by # in sizes width*height, length*height and width*length. The first one is the front view, the second one is the view from the right side and the third one is the view from the top. You need to print the 3D model based on the pictures you get; one by one layer separated by two dashes from bottom to the top layer and two dashes at the end.

Example Input

2    // width
5    // height
1    // length
##   // start of front view, always height number of lines
##
##
##
##
#    // start of right side view, always height number of lines
#
#
#
#
##    // start of top view, always length number of lines

So from these inputs, your code should guess what is the 3D model. In the example it's a block 2x5x1.
Example Solution

##    // the lowest layer
--
##
--
##
--
##
--
##    // the highest layer
--

If the three pictures cannot define some parts of the model as solid or hollow, assume these parts are solid, so that output '#' to fill-in.

Input

Line 1: An integer width of the 3D model
Line 2: An integer height of the 3D model
Line 3: An integer length of the 3D model
Next height lines: Strings - part of the front view
Next height lines: Strings - part of the view from the right
Next length lines: Strings - part of the view from the top

NOTE There is no trailing space in the input.

Output

Layers of the 3D model separated by two dashes and two dashes at the end.
Write no trailing space in output.
If the three pictures cannot define some parts of the model as solid or hollow, assume these parts are solid, so that output '#' to fill-in.

Constraints

0 < width, height, length ≤ 20

Example

Input

2
5
1
##
##
##
##
##
#
#
#
#
#
##

Output

##
--
##
--
##
--
##
--
##
--

Tags

Strings, String manipulation, 3D

Difficulty

Medium

Test cases

example Test

Input

2 5 1 ## ## ## ## ## # # # # # ##

Output

## -- ## -- ## -- ## -- ## --

block Validator

Input

2 2 5 ## ## ##### ##### ## ## ## ## ##

Output

## ## ## ## ## -- ## ## ## ## ## --

weird shape Test

Input

5 5 2 ##### ## #### # ##### ## ## ## ## ## ##### #####

Output

##### ##### -- # # -- #### #### -- ## ## -- ##### ##### --

weird shape Validator

Input

5 5 1 ##### ### # ### ##### # # # # # #####

Output

##### -- ### -- # -- ### -- ##### --

WHAT THE... Test

Input

20 20 1 ##### ###### ######### ## ######## ############ #### #### ############### # ################# ####### ####### ########## # ################ ########### # ###### ######### # # # # # # # # # # # # # # # # # # # # ####################

Output

######### -- ###### -- # -- ########### -- ################ -- # -- ########## -- ####### -- ####### -- ################# -- # -- ############### -- #### -- #### -- ############ -- ######## -- ## -- ######### -- ###### -- ##### --

WHAT? Validator

Input

5 10 1 ##### # ##### # ##### ### ### ## #### ## # # # # # # # # # # #####

Output

## -- #### -- ## -- ### -- ### -- ##### -- # -- ##### -- # -- ##### --

Hole Test

Input

4 2 4 #### #### #### #### #### # # # # ####

Output

#### # # # # #### -- #### # # # # #### --

Hole Validator

Input

4 1 4 #### #### #### # ## # ## ###

Output

#### # ## # ## ### --

Cube with a hole Test

Input

6 6 6 ###### # # # # # # # # ###### ###### # # # # # # # # ###### ###### # # # # # # # # ######

Output

###### # # # # # # # # ###### -- # # # # -- # # # # -- # # # # -- # # # # -- ###### # # # # # # # # ###### --

Cube with a hole Validator

Input

4 4 4 #### # # # # #### #### # # # # #### #### # # # # ####

Output

#### # # # # #### -- # # # # -- # # # # -- #### # # # # #### --

A mug??? Test

Input

8 8 5 ##### ###### ####### ##### ## ##### ## ####### ###### ##### ##### ##### ##### ##### ##### ##### ##### ##### ### ##### ######## ##### ###

Output

### ##### ##### ##### ### -- ### ##### ###### ##### ### -- ### ##### ####### ##### ### -- ### ##### ##### ## ##### ### -- ### ##### ##### ## ##### ### -- ### ##### ####### ##### ### -- ### ##### ###### ##### ### -- ### ##### ##### ##### ### --

Another mug Validator

Input

7 8 5 ##### ##### ####### ##### # ##### # ####### ##### ##### ##### ##### ##### ##### ##### ##### ##### ##### ### ##### ####### ##### ###

Output

### ##### ##### ##### ### -- ### ##### ##### ##### ### -- ### ##### ####### ##### ### -- ### ##### ##### # ##### ### -- ### ##### ##### # ##### ### -- ### ##### ####### ##### ### -- ### ##### ##### ##### ### -- ### ##### ##### ##### ### --

A chair Test

Input

8 13 8 ######## # # ######## # # ######## # # ######## # # # # # # # # # # # # # # # # # # ######## # # # # # # # # # # # # ######## ######## ######## ######## ######## ######## ######## ########

Output

# # # # -- # # # # -- # # # # -- # # # # -- # # # # -- # # # # -- ######## ######## ######## ######## ######## ######## ######## ######## -- # # -- ######## -- # # -- ######## -- # # -- ######## --

Another chair Validator

Input

8 13 8 ######## ######## ######## # # ######## ######## ######## # # # # # # # # # # # # # # # # # # ######## # # # # # # # # # # # # ######## ######## ######## ######## ######## ######## ######## ########

Output

# # # # -- # # # # -- # # # # -- # # # # -- # # # # -- # # # # -- ######## ######## ######## ######## ######## ######## ######## ######## -- ######## -- ######## -- # # -- ######## -- ######## -- ######## --

Solution language

Solution

Stub generator input

Rate this contribution

+16

Make the contribution public (lvl 20+)

Comments

59 Comments

5DN1L Unnamed CodinGamer

about 2 years ago

Added "write answer" to stub generator. Made minor text changes and formatted the Input section and the Constraints section. Edit on 28 February: Amended typo in the name of one of the validators.

Miki09 Unnamed CodinGamer

about 2 years ago

Thanks 😁

Stilgart Unnamed CodinGamer

about 2 years ago

Someone has just fixed a mistake in the statement. Please put a comment when doing so (sometimes, people need to reload their IDE to get the new statement, and we cannot guess this if we do not know about post-validation fixes). Furthermore, I have symmetry issues with Test and Validator 4 (hole). For me, Validator 4 is the only place where a certain asymmetry is introduced. I suggest replacing the test with: 4 1 4 #### #### ### # ## # ## ####

Miki09 Unnamed CodinGamer

about 2 years ago

I think the test is fine.

Wontonimo Unnamed CodinGamer

about 2 years ago

✅ Approved the contribution. Comment: Here is my solution. Nice puzzle. Took about 15 min. Medium is a reasonable difficultly. https://tech.io/...

Miki09 Unnamed CodinGamer

about 2 years ago

Thank you :-)

Wontonimo Unnamed CodinGamer

about 2 years ago

I've made several changes to the formatting of the goal and input section of this contrib.

java_coffee_cup Unnamed CodinGamer

about 2 years ago

✅ Approved the contribution. Comment: The author accepted many advices and made huge improvement in the puzzle design. All discovered bugs are fixed. It should be an interesting puzzle for the public to try out.

Miki09 Unnamed CodinGamer

about 2 years ago

Thank you very much!!

java_coffee_cup Unnamed CodinGamer

about 2 years ago

Well done. A final suggestion is to remove the "Hole" cases because it is the only test case which has a view not left-aligned. It makes an odd exception for no reason and no benefit. The "Cube" cases looks redundant. If you feel there are more than enough cases, this one can be removed with no harm.

Miki09 Unnamed CodinGamer

about 2 years ago

-Hole removed✅️ -cube removed✅️ -another hole renamed to hole✅️

java_coffee_cup Unnamed CodinGamer

about 2 years ago

Would you check the the two chairs cases? Should the back-plate materials be on the top of the layers instead of at the bottom?

Miki09 Unnamed CodinGamer

about 2 years ago

I think theyre fine

java_coffee_cup Unnamed CodinGamer

about 2 years ago

3 2 2 ### ### # ## ### ### With this input, should the answer carry a blank line at the end? But the platform tends to trim off trailing empty chars. ### ### -- ### <blank line?> It will cause confusion. It can be resolved by requiring a layer separator under every layer: ### ### -- ### -- Up to you to decide.

Miki09 Unnamed CodinGamer

about 2 years ago

Allright. Done :-)

jordan_codingame Unnamed CodinGamer

about 2 years ago

✅ Approved the contribution. Comment: Good idea, seems as if problems were resolved.

Miki09 Unnamed CodinGamer

about 2 years ago

Thanks :-)

java_coffee_cup Unnamed CodinGamer

about 2 years ago

is the test case "Hole" impossible to exist? - front and top views are in conflict? You may need to add a function in your program to validate all cases.

Miki09 Unnamed CodinGamer

about 2 years ago

It was just a typo. I've already fixed it. :-)

java_coffee_cup Unnamed CodinGamer

about 2 years ago

I experimented with some more complex models and found that using a blank line as layer separator is sometimes not good looking for human when it mixes with other empty lines of a layer. May be using two dashes "--" for layer separator can help. Up to you to try out and decide.

Miki09 Unnamed CodinGamer

about 2 years ago

Now two dashes :)

java_coffee_cup Unnamed CodinGamer

about 2 years ago

Besides being too uniform in top views in test cases, there are not enough interesting side views as well. A suggestion: consider creating an object showing different Letters or patterns in three different views. There are quite a lot of such models you can download for 3d printing.

Miki09 Unnamed CodinGamer

about 2 years ago

I'll add more testcases tomorrow.

java_coffee_cup Unnamed CodinGamer

about 2 years ago

The first example test case has a trailing space.

Miki09 Unnamed CodinGamer

about 2 years ago

Thanks. Now fixed

java_coffee_cup Unnamed CodinGamer

about 2 years ago

Checking the cases... I am not immediately convinced about the "top view" representation by reading the statement alone. If a top view is # ## Does it mean the object has a front of two blocks, and has a back surface of 1 block width with a recessed face? Or reversed? It could be better if the statement can clarify it because it is also the expected convention to use in output. And there are not enough test cases about irregular shapes in top view. (Currently most top views in test cases are 1 block thick or regular rectangles with the same front and back)

java_coffee_cup Unnamed CodinGamer

about 2 years ago

It looks better now. Will find time to try out the test cases. "There are no trailing spaces in the input." - this line belongs to input description, not in constraint. "If you don't know if there should be free space or a character, there is a character." - it should better be rephrased to avoid "if you don't know" because there are many irrelevant reasons to not knowing something. A suggestion (improve it if you think fit): "If the three pictures cannot define some parts of the model as solid or hollow, assume these parts are solid, so that output '#' to fill-in." This given assumption should be in the statement or in output, not in constraint.

Miki09 Unnamed CodinGamer

about 2 years ago

Thank you very much for the feedback. I've editted as you said and added your suggestion :-)

Elphin Unnamed CodinGamer

about 2 years ago

I really like this idea! Great work! I also think it would be cool to have different versions of this at different difficulty levels, where less input is provided at the start. In either case, way to go, I hope you get published soon!

Miki09 Unnamed CodinGamer

about 2 years ago

Thank you very much :). I hope too 😜

moustave Unnamed CodinGamer

over 2 years ago

oooo that's a good idea

Miki09 Unnamed CodinGamer

over 2 years ago

Thanks :)

CodinBot Unnamed CodinGamer

over 2 years ago

Hey CodinGamer! Your contribution has unfortunately not been moderated on time and will temporarily be removed from the system... But no worries! You can republish it anytime to give it another chance! :)

CyberHD1811 Unnamed CodinGamer

over 2 years ago

I really like this puzzle and i think it's a good idea but there are two things i would change: First: In your example output in the last line it is "# #(the highest layer)" but i think it should be "## (the highest layer)" Second: The Contraints Section: In most puzzles i've seen, the min and max values for the inputs are not written as a sentence, but instead written like this: " 0< width, height, length <= 20

Miki09 Unnamed CodinGamer

over 2 years ago

Now fixed :)

jlfc Unnamed CodinGamer

over 2 years ago

Interesting. Maybe it's more a medium difficulty.

Miki09 Unnamed CodinGamer

over 2 years ago

Now medium 😃.

snoyes Unnamed CodinGamer

over 2 years ago

"lenght" is spelled length In the example, how can the top view be a single #? Surely it must be ##.

Miki09 Unnamed CodinGamer

over 2 years ago

Thanks for the feedback. You were right, I had mistake in my example. It is now fixed 😀. I also changed the english spelling :)

TabulaRasa Unnamed CodinGamer

over 2 years ago

For me this reads a bit weird "one by one layer separated by space" - I would reword this and also be more specific on what layers do you mean (I guess these are layers from the bottom to the top layer). In example I would change "the picture you get is" with "front view", "right side view", "top view". I also second what @Bartholomewlll suggested - example should be a bit more fancy, maybe a block 2x5x1?

Miki09 Unnamed CodinGamer

over 2 years ago

Thanks, nice suggestions. I will edit the statement soon.

BartholomewIII Unnamed CodinGamer

over 2 years ago

This is neat but needs some work: - I would use a 3x3x3 for your example in the goal statement. The 1x5x1 didn't help my understanding at all. - Instead of w1, w2, w3, h1, h2, h3, please use only width, length, and height. And then specify that the front view is width X height, right view is length X height, and top view is width X length. It's less confusing and also helps correctly orient the top view. - It's frustrating when a line has fewer characters than what you would expect because the line is supposed to end with spaces, e.g. " ##" instead of " ## ". Please use periods as padding or guarantee consistent line width for each view. - Also dividing each layer, I would just print a newline with no space, i.e. "\n" instead of " \n". Or better yet, separate them with three equal signs or something: "===\n". - Finally, the statement is a bit hard to read, and it really needs some markup. If you don't know had to add that, click the question mark next to "Goal Statement" when you are editing. Besides that, it's not bad! :)

Miki09 Unnamed CodinGamer

over 2 years ago

Thank you very much for the feedback. I will edit the contribution as soon as possible. Edit: Updated :)

ABOUT US CAREERS PRIVACY FAQ BLOG

ABOUT US CAREERS PRIVACY FAQ BLOG

The #1 tech hiring platform

SCREENING INTERVIEWING