New LLR version produces LLRnet results!

[kar_bon]

hi all,

Jean Penné (many thanks for that work) compiled a new version of LLR V.3.7.1c with the feature of producing LLRnet-compatible resultfiles,
so like this:

user=testuser
[2009-05-18 14:11:15]
432383773965*2^48611-1 is prime!  Time : 35.147 sec.
user=testuser
[2009-05-18 14:20:23]
391*2^263115-1 is not prime.  LLR Res64: B890E505AD7ABFD4  Time : 103.134 sec.

to obtain this output a new entry in the 'llr.ini' with the user has to be inserted, here:

LLRnetuser=testuser

if this line is not present, the output is like the original LLR (one line per result).

the only difference in the output-string is 'LLR Res64' instead of only 'Res64' by LLRnet!
but this in no problem, because the import-script should handle this by a small change (if one needed).

you can download this new LLR-version on Jean's page here http://jpenne.free.fr/index2.html (the MS Windows, GUI version).
for MAC-users there's no new exe available, because Jean got none.

please both David's post here any problems with the (small) different output-format for the import-scripts.

test some outputs before everyone can use this new feature!

thanks!


BTW:
the advantage of this feature is to import manual LLR-resultfiles directly into the NPLB-stats system without any work of conversion!
so you reserve a range for manual testing, complete the tests, and IronBits or AMDave can import them into the stats with all necessary information like it was done with LLRnet!
easy, he?

[gd_barnes]

Great work Karsten and Jean!

Oddly enough, Max and/or I have been converting all of the LLRNet results from "Res64" to "LLR Res64" so that they match manual results. Therefore, that is the way that I would prefer it here.


G

[MyDogBuster]

to obtain this output a new entry in the 'llr.ini' with the user has to be inserted, here:

Code:
LLRnetuser=testuser
if this line is not present, the output is like the original LLR (one line per result).

I'm a little confused about this. The llr.ini file is not created until AFTER the program is executing. What happens to any output that may be created before you get the entry into the ini.file?

[mdettweiler]

Originally Posted by gd_barnes

Oddly enough, Max and/or I have been converting all of the LLRNet results from "Res64" to "LLR Res64" so that they match manual results. Therefore, that is the way that I would prefer it here.

Yes, but that's *after* they've been imported into the DB. The DB feeds in the original results files, which still just say "Res64".

My script for converting manual results to LLRnet results changes it to "Res64", also. I'm not sure if that's crucial for the DB import; Dave, would it make any difference?

[kar_bon]

Originally Posted by MyDogBuster

I'm a little confused about this. The llr.ini file is not created until AFTER the program is executing. What happens to any output that may be created before you get the entry into the ini.file?

- copy an old ini-file in your directory
- insert the line in the ini-file
- start LLR.exe
- choose your input- and output-file and starting line new (menu Test -> Input Data)
- all is ok

[mdettweiler]

Originally Posted by MyDogBuster

I'm a little confused about this. The llr.ini file is not created until AFTER the program is executing. What happens to any output that may be created before you get the entry into the ini.file?

As Karsten said--also, we could provide users with a link to donwnload a specialized version of LLR that includes a premade llr.ini file. That would be quite useful for new users.

[MyDogBuster]

- copy an old ini-file in your directory
- insert the line in the ini-file
- start LLR.exe
- choose your input- and output-file and starting line new (menu Test -> Input Data)
- all is ok

Thanks Karsten. Works just fine.

As Karsten said--also, we could provide users with a link to donwnload a specialized version of LLR that includes a premade llr.ini file. That would be quite useful for new users.

That probably would be helpful because new users wouldn't necessarily have an old ini file.

[kar_bon]

another way:

- just start and stop LLR immediatly -> the ini-file is avaiable and editable

but i think so too: a downloadable example would be best!

[Brucifer]

yes, please. :-)

[AMDave]

Originally Posted by mdettweiler

Yes, but that's *after* they've been imported into the DB. The DB feeds in the original results files, which still just say "Res64".

My script for converting manual results to LLRnet results changes it to "Res64", also. I'm not sure if that's crucial for the DB import; Dave, would it make any difference?

Looking at the code of the stats-db import routine, it does make a difference at the moment.
If Jean wants to keep the format different to the old format or has run out of time to fix that then we can improve the db code so that it should make no difference and the characters "LLR " should be ignored.
I'll run some tests soon.