« Timing | Main | HINTS FOR CHALLENGES 3B and 4B »
October 18, 2005
Prizes for week 2
Sorry we haven't published the prizewinners for week 2. There will be an announcement soon. All the best,
Posted by Harry at October 18, 2005 01:09 AM
Comments
If you wish to leave a comment please act responsibly. No personal or innapropriate comments should be made. Concerns about a comment should be emailed directly to us here. Hints about the challenges may be blocked or held back at our discretion. We reserve the right to refuse to publish comments without entering into a discussion about why, and to censor comments as we see fit. Please be patient if it takes a while for your comments to be approved.
Please decide the timing intervals and publish them! Thanks.
Posted by: cecil at October 20, 2005 01:12 PM
Tom, I think it's only a secret because they haven't decided all of them yet!
Posted by: Jess at October 20, 2005 06:56 AM
Please could you tell us what the timing interval for tomorrow will be?
Would it also be possible to just have a list on the site somewhere of what the interval is for each challenge? I don't see any reason for it being a secret.
Posted by: tom at October 19, 2005 09:01 PM
It would be nice for you maybe but it wouldn't be right. You are responsible for the accuracy of your solution, and any programs you write if this is the case. If you don't check it yourself then you should pay the price of a point to have it checked for you. A bit harsh maybe, but there is no reason you should get a solution wrong if you have found the key.
About morse code, there are only 3 characters you need, so these should be filtered into new text first. You should have no problems then. If like me for some reason you need all cipher text parts to be equal length to fit into an existing program you can fill the morse code out with extra "/"s at the end of each part before deciphering. Not a perfect solution, I know. It's probably better just to write an individual program.
However, morse code is just one small part of the challenge. Why not try writing code to generate tables showing frequencies of neighbouring letters or of letters before/after another specified letter? This proves useful for finding vowels (since they are more "friendly" with other letters), finding double letters (don't see "aa" and "ii" much do you?) and relationships like "he" and "qu" in all monoalphabetic ciphers. This is no trouble to write if you are familiar with the language.
Posted by: Jason at October 19, 2005 07:15 PM
3B i think is sneaky, because i got some of the words wrong cos of the formatting of the orginal morse code, and it would be nice to receive a confirmation email b4 the nxt time interval.
Posted by: kols at October 19, 2005 02:38 PM
I think the challenges have been quite easy so far, apart from a few problems We've had with the morse converter we wrote (stupid newlines :P) it's been okay.
Posted by: Jack at October 19, 2005 01:58 PM
Keyword cipher? I thought it might be but just solved it as a random substitution, because I couldn't work out which way round you had to write it. How's everyone else doing?
Posted by: cecil at October 19, 2005 07:04 AM
Harry, what will the timing intervals be for Challenge 4?
Posted by: Jess at October 18, 2005 11:04 PM
How is everyone getting on with the latest challenge? I ask because you all seem to be very quiet, especially for the last few days...
Posted by: wrighty at October 18, 2005 07:28 PM
hurry up then harry plz i want 2 no wether i have won! yeah right is the phrase here!!!
Posted by: mark at October 18, 2005 06:28 PM