Difference between revisions of "File talk:KNN.jar"
(→File format: Eclipse project format) |
(→Percentage: better code for progress display) |
||
| Line 6: | Line 6: | ||
The current version uploaded already lists the repetition number, and well... I personally don't think it is realistic to do tests so large that a repetition takes longer than a couple minutes. 40 dimensions? That would take an extremely long time unless the number of points is fairly tiny I'm pretty sure, it probably hasn't locked up. --[[User:Rednaxela|Rednaxela]] 14:51, 11 March 2010 (UTC) | The current version uploaded already lists the repetition number, and well... I personally don't think it is realistic to do tests so large that a repetition takes longer than a couple minutes. 40 dimensions? That would take an extremely long time unless the number of points is fairly tiny I'm pretty sure, it probably hasn't locked up. --[[User:Rednaxela|Rednaxela]] 14:51, 11 March 2010 (UTC) | ||
| + | |||
| + | Normally I use: | ||
| + | <pre> | ||
| + | |||
| + | System.out.printf("Running repetition %d of %d; %d%% completed.\r", i+1, numReps, (i+1)/numReps); | ||
| + | |||
| + | </pre> | ||
| + | |||
| + | So it didn't waste the screen when I run 100+ repetitions. Note that I haven't test this code yet (I'm not sure about %% in Java's printf, but that is what I have done in C). --[[User:Nat|<span style="color:#099;">Nat</span>]] [[User talk:Nat|<span style="color:#0a5;">Pavasant</span>]] 15:26, 11 March 2010 (UTC) | ||
== File format == | == File format == | ||
Revision as of 17:26, 11 March 2010
Percentage
I don't suppose you can add something that will give an an idea about how far along it is? Since some times it takes so long for doing say, 40 dimensions, I wonder if it has locked up. --Chase 14:38, 11 March 2010 (UTC)
Well, there is a way, but I suppose it will make the whole running longer. I'll try to update it. --Nat Pavasant 14:45, 11 March 2010 (UTC)
The current version uploaded already lists the repetition number, and well... I personally don't think it is realistic to do tests so large that a repetition takes longer than a couple minutes. 40 dimensions? That would take an extremely long time unless the number of points is fairly tiny I'm pretty sure, it probably hasn't locked up. --Rednaxela 14:51, 11 March 2010 (UTC)
Normally I use:
System.out.printf("Running repetition %d of %d; %d%% completed.\r", i+1, numReps, (i+1)/numReps);
So it didn't waste the screen when I run 100+ repetitions. Note that I haven't test this code yet (I'm not sure about %% in Java's printf, but that is what I have done in C). --Nat Pavasant 15:26, 11 March 2010 (UTC)
File format
Red, is there any problems with my build file? I am now having a lot of problems merging your change into my modified code. If you don't mind I'd like you to re-package it with my build file... --Nat Pavasant 14:54, 11 March 2010 (UTC)
I'd think the largish amount of refactoring I did would be more likely to cause issues merging. Anyway, I wasn't using the build file because I found it just creates a big hassle to use and slowed down the process of testing things. I could use it probably, but may I ask, why do you have it set up like that anyway? It seems awkward to have a source jar inside the binary jar in that manner. --Rednaxela 15:03, 11 March 2010 (UTC)
Because if you are using Eclipse, the src.jar's content is exactly in Eclipse Project Format. I can guess you didn't use Eclipse then? I found that if I package it normal way, I'll have problem merging it into my workspace after I publish it. Perhaps we need central RoboWiki SVN repository or something like that... (I prefer Mercurial, though) --Nat Pavasant 15:14, 11 March 2010 (UTC)
