Travelling with Style Feedback Thread

Hello Alex,

I just submitted my 4th Solver version for Beyond3D's C++ AMP Contest!

I also hard-coded the timeout limits accordingly so they would match with Veikko's running times from the latest rankings chart. Now, if he submits another version those running times may change.
For that reason I have added support for setting the timeout value in ms via command line option.
Just add "-timeout ms" to the command line before the tsp file name.

I am willing to accept any comparison based on the timeout that Veikko chooses!

Hey Veikko, you are a tough sparring partner. Not sure whether I can keep up with you.
I am running out of steam...

Cheers,

- Bernd

 

@Alex: when is exactly the deadline?
Sun, 10/28/2012, 11:59 PM PST?

Or GMT?

This might get important...

 

Hey Niels, have fun in El Salvador!

- Bernd

 

@Alex: x32 is fine with me!

 

A new submission is in

Hi!

I made the timeout window parameters slightly larger, so it should calculate more. No idea how it effects the results on test machine, though.

 

I too have such a switch.

This is nearing a bit of a draw in the sense both of us can "target" the other one. Unless something happens, of course, say, with your latest submission.

Likewise. My hat goes off to you!

Perhaps so. I'd love to tweak some parameters and "clean places", but I'm so out of time and days for "wee hours". A bit annoying to know I have a few so clear places to boost performance noticeably.

 

Hmm, where are the rankings?

 

Oops, I forgot to refresh the browser and I didn't see Alex's post.
I didn't mean to be pushy!

 

I see, the new rankings are out!
Do you guys agree that I am still leading the TSP category?
What happened to ATSP?
Did my solver fail for 400-500?
Were the tours incorrect?

 

ok, I'll work on it.
But what really surprised me is the 23% for ATSP 100,200 nodes.
This doesn't make sense to me:
TSP 200,300 yields 5.51% in 3secs
But ATSP 100,200 yields 23% in 15ms.
This is really suspicious. Are you sure those numbers are correct?

Is there any chance to get the data sets (if Veikko agrees) so I can debug the mess?
My ATSP data sets work.

- Bernd

 

I submitted another version.

This is kind of a shot in the dark in order to fix ATSP.
I also adjusted my timeout values to Veikko's except for the 7300,7500 TSP data sets.
I think 7% for 180 secs is better than 14% for 102 secs.

Cheers,

- Bernd

 

Ah, thanks so much. Now I have something to work on!

- Bernd

 

Oh man, this is tight. I would say I still lead TSP because of better results for the 5000 and above sets.
ATSP is a total disaster.

- Bernd

 

Oh no, this is going to get difficult. So close and so on. I'll see if I can do something... Pass midnight wasn't a problem then? Oh, so difficult now make a decision on normalizing on these time settings if I'm in the losing end, but on the other hand, the results are within error marginals as far as I can judge from the results I have on my computer.

Such is life.

 

Couldn't accomondate daily routines for this, but I'll give a shot if I can make up something quick (during the evening/midnight).