OJ Board

Tell ya what... you post some input, and I'll run it through my newly AC program and share the output with you. Deal?

Okay you know what's even weirder? I just got AC (well, PE) after making the following change. At the beginning of my init() method I call a method called crazy_kill_all(void), which goes as follows:

[cpp]
/* Should do nothing; might make my program work */
void crazy_kill_all(void)
{
last_row = 0 ...

Heh... that's weird alright. Guess that's why they call you Guru. ;)

For my reference, could you let me know what AC output looks like for that input? I'm still a little unclear on a few things. For instance, it's my understanding that for the black ones, you leave them blank if there's a direct ...

I, too, think I should have AC but don't.

Here's my input:


8 7
1 1 1 1 1 1 1
1 0 1 0 0 1 1
0 0 1 0 0 0 0
0 0 1 0 1 0 0
1 1 1 1 1 1 1
0 0 0 1 0 0 0
1 0 0 0 0 0 1
1 1 1 1 1 1 1
6 7
1 0 0 0 0 1 1
0 0 1 0 0 0 0
0 0 1 0 1 0 0
0 1 0 1 1 1 1
0 0 0 1 0 0 0
1 0 0 0 0 0 1
6 7
1 0 0 0 0 1 1
0 0 1 0 0 0 0
1 ...

My WA code gives nearly the same as you, Red Scorpion. I just don't know what the problem is! The only difference is as follows:


gpi@grassi 10283 $ diff test foutput
7c7
< 304.5417046668 280844359.6055448021 4178000.5214741933
---
> 304.5417046668 280844359.6055448100 4178000.5214742422


This ...

Hi Robert,

I get the same output as you with one discrepancy. When it shows the number for black and for white, you leave a space and then print the integer, whereas I leave a space and print the integer right-justified in a field of width 2. To show what I mean, here's an excerpt from the diff I ...

Brilliant! It worked first try!

That had really been bugging me, because I knew there couldn't have been anything wrong with my logic. It was too simple! Now I know the problem was with my understanding of the language, and I can rest easy. Thanks again!

Yet another program that should be correct, handles all test output found on the forums without a hitch (even the input that doesn't correspond to the problem description) and still gets WA. What's up with this problem?

[cpp]
#include <iostream>
#include <string>

#define MAX 10000
#define LONGEST ...

I believe there is an error in the output as presented in the description for 211. In the first problem instance, the first column is lined up under the 'o' in 'Layout': column 4. However, in the second, it falls under the 'u', which is column 5. I cannot conceive how this could have been output by ...

Andrew Neitsch wrote:I blame that fact that it is open source software, which we all know is crap.10265 time out.

Heh, flamebait

Boy, sure helps to read that problem description eh? That really changed things for the better. Now, I've coded it all up and it does the test data perfectly. For all floating point operations I use an epsilon value of 10^(-7), just as it says. But I still got WA.

Here are some of the relevant ...

I tried to code up the calculation of the bearings, and I'm getting some weird answers compared to the provided output. Problem is, I think my output is right and the supplied output is wrong!

Consider: If I'm at 0,0 facing 90 degrees, and there's a ship at 10,10 then the bearing should be 315 ...

Well, my program passes all test cases in this thread, and still I get WA. Any ideas for other test cases? Should I post my code?

Sure, I'll spell it out for you. The following is a complete, ready-to-go program which will generate an input file. Copy-paste the code into a file called generate.cpp

[cpp]
#include <iostream>

using namespace std;

/* Globals */
string months[] = {"pop", "no", "zip", "zotz", "tzec", "xul ...

Hah! That was quick! :)

Helps if you copy-paste all the months, not just the ones you like. Turns out I'd missed the twentieth holy month. MAY THE GODS BE MERCIFUL UNTO ME!

Here's a very useful debugging tool: write a program to generate an input file which prints out the first 2 years of creation ...