10344 - 23 out of 5

[misof]

A correction.

The input file format is correct (I verified it using a bunch of asserts). All numbers are positive integers between 1 and 50. I don't really know what your phrase "value may be long" wanted to say... but all intermediate results will surely fit into a int.

The only change I had to make in my (previously correct and AC, currently WA) code to get it accepted is to change
"output whether 23 can be reached"
to
"output whether 23 or -23 can be reached".

Oh boy, I wonder why they bothered to "rejudge" the problem

[TISARKER]

but all intermediate results will surely fit into a int.

Suppose a1=50,a2=50,a3=50,a4=50,a5=50

If u use normal backtracking then
intermediate result will be a1*a2*a3*a4*a5 which will not fit into int.

[mf]

50^5 is only 312500000, which quite well fits in an 'int' (32-bit, of course)

[TISARKER]

50^5 is only 312500000, which quite well fits in an 'int' (32-bit, of course)

mf,
I am really sorry for not clarifying my statement.
I only wanted to say that use long type variable(32 bit) instead of int type variable (16 bit).
Thnk for Advance.

[misof]

50^5 is only 312500000, which quite well fits in an 'int' (32-bit, of course)

mf,
I am really sorry for not clarifying my statement.
I only wanted to say that use long type variable(32 bit) instead of int type variable (16 bit).
Thnk for Advance.

gcc/g++ used by the judge is a 32-bit compiler, i.e., ints are 32-bit signed integers. If you still use a compiler that has 16-bit ints, you really should upgrade to a newer one. (Take a look at http://www.bloodshed.net/devcpp.html and/or http://www.delorie.com/djgpp/ )

[TISARKER]

mf, A lot of thanks.

[Abednego]

I'm very confused. Why do we care about -23? After the rejudging, my AC solution turned into a WA solution. Like misof, I changed the 'if' statement from

Code: Select all

if( r == 23 )

to

Code: Select all

if( r == 23 || r == -23 )

and got AC.

Why? Could anyone explain it please?

[Dominik Michniewski]

I think too that such change is "strange".
I have the same problem - I modified one if and got Acc again ...

But I think, that description of problem hould change too -> I can't read any word about them. If I read "you must reach 23", it means for me +23, not -23

Best regards
DM

[mamun]

I got WA after the latest rejudgement in Jan,'06.
I did it only about a month ago. So my program takes care of both 23 and -23, I believe. Can somebody post some tricky I/O?

[mamun]

my program takes care of both 23 and -23

You know the fun? After I stopped my program to take care of -23, I got it accepted

[windows2k]

Sorry, I got WA all the time after rejudge.
I have passed all the input/ouput on the board.
Could someone give me some tricky input/output?
Thx

[mamun]

Here are some I/O
Input

Code: Select all

42 8 2 32 37 
10 43 21 46 5 
44 2 27 30 29 
10 20 20 2 36 
28 3 34 42 2
22 6 6 5 37
34 3 31 18 12
25 46 28 13 2
12 4 19 2 50
1 12 2 1 49
48 48 42 2 11
1 2 43 26 33
0 0 0 0 0

Output

Code: Select all

Possible
Possible
Impossible
Impossible
Impossible
Impossible
Impossible
Impossible
Impossible
Impossible
Impossible
Impossible

[misof]

Here are some I/O

Thanks. In all that rewriting and resubmitting each time the problem was rejudged I made a silly mistake and your I/O helped me to find it. Now (finally) everything seems OK, the test data used by the judge is correct, and I have AC

[Abednego]

Miaof, can you explain why you think that the test data used by the judge is correct? I still have no idea why we care about -23.

[misof]

Miaof, can you explain why you think that the test data used by the judge is correct? I still have no idea why we care about -23.

We don't. My solution that's currently AC only checks whether 23 can be achieved.

Previously, the judge used a wrong set where you had to check also whether -23 can be achieved. It looks that this bug has been fixed.