https://www.codingame.com/training/easy/nature-of-triangles
Send your feedback or ask for help here!
Created by @nicola,validated by @eklore,@murrayr and @Faibbus.
If you have any issues, feel free to ping them.
https://www.codingame.com/training/easy/nature-of-triangles
Send your feedback or ask for help here!
Created by @nicola,validated by @eklore,@murrayr and @Faibbus.
If you have any issues, feel free to ping them.
For the first test, I get the following failure:
Found:
ABC is a scalene and an obtuse in B(176\2\1) triangle…
Expected:
ABC is a scalene and an obtuse in A (176\-62\-80) triangle.
All angles of a triangle add up to 180 degrees which my calculations match(minus rounding). I admit my geometry is rusty, how can -62 and -80 degrees fit with a triangle with a 176 degree angle?
Also, when displaying the first testcase, it shows expected results of
ABC is a scalene and an obtuse in A (176°) triangle.
not
ABC is a scalene and an obtuse in A (176\-62\-80) triangle.
For the first test, angles are 176.269° (176°) in A, 2.419° (2°) in B, 1.312° (1°) in C … you probably did a mistake somewhere in your code.
On bad output, \-62\-80 is displayed instead of ° (weird but…it is the same, and it does not match -62° and -80° angles).
I see, the ‘°’ character can be displayed in the console output but not the failure message output…
@Mehdi_Moulati You’re off the mark… I didn’t ask questions, I was answering someone… who understood…and it was 10 months ago .
Hello,
Has someone tried solving this puzzle in python recently? I have solved it, but every output line for an obtuse triangle results in an error because of the degrees ° character.
For instance:
Standard Output Stream:
ACD is a scalene and a right in D triangle.
ABC is a scalene and an acute triangle.
COG is an isosceles in O and a right in O triangle.
BCD is an isosceles in C and an acute triangle.
DEF is a scalene and an obtuse in E (162°) triangle.Failure
Found: Nothing
Expected: DEF is a scalene and an obtuse in E (162°) triangle.
The same error appeared when I ran my solution (which had passed 100%). I’ve reported the issue in #bug-report in CG’s Discord chat just now.
Yep, same bug here.