[QUOTE=Greebley;178023]It occurred to me that it would be nice to have an option where rather than running ecm forever, you could repeat the ggnfs attempt instead.[/quote]

Sure, should be doable.

It would also be nice to have an option to report new lines to the database automatically once they have calculated. (perhaps -s (lowercase) to report new lines without running further factorizations, and -S (uppercase) to report new lines while running aliqueit factorizations).

[QUOTE=Andi47;178044]It would also be nice to have an option to report new lines to the database automatically once they have calculated. (perhaps -s (lowercase) to report new lines without running further factorizations, and -S (uppercase) to report new lines while running aliqueit factorizations).[/QUOTE]

Roger, something like that is already on The List.

[quote=10metreh;178024]How did ggnfs manage to abort early? Was it that "matrix must have more columns than rows" error?[/quote]
That sounds sort of familiar, but I can't swear to it.

I am running 340 on the computer that got the problem. I was wondering if 360 version was better.

Another item for the list of possible improvements:

If you get a series from the database in text form you get a partial line of what is known so far. However, aliqueit.exe can't handle this partial line and stops. It would be nice if it either used the listed factors or at least realized the list is partial and start computing with the previous entry rather than aborting. I have to go and manually delete this partial line and I always forget to do so ahead of time.

Blank lines can also confuse it, but that is less important.

[QUOTE=Greebley;178231]Another item for the list of possible improvements:

If you get a series from the database in text form you get a partial line of what is known so far. However, aliqueit.exe can't handle this partial line and stops. It would be nice if it either used the listed factors or at least realized the list is partial and start computing with the previous entry rather than aborting. I have to go and manually delete this partial line and I always forget to do so ahead of time.

Blank lines can also confuse it, but that is less important.[/QUOTE]

Which version of aliqueit are you using? I think the issue you describe has been fixed, aliqueit is now saying something like: "Warning: Line xy: partial line. Resuming..."

[QUOTE=Andi47;178238]Which version of aliqueit are you using? I think the issue you describe has been fixed, aliqueit is now saying something like: "Warning: Line xy: partial line. Resuming..."[/QUOTE]

Indeed. If there's still a problem with the latest version, 1.08, could you please post a tiny example that goes wrong?

[QUOTE=mklasson;178253]Indeed. If there's still a problem with the latest version, 1.08, could you please post a tiny example that goes wrong?[/QUOTE]

Talking about versions: How do I see which version I am using (especially if I don't have it in a folder which's name indicates the version number)?

[quote=Andi47;178257]Talking about versions: How do I see which version I am using (especially if I don't have it in a folder which's name indicates the version number)?[/quote]

I don't know if there is an easier way than simply looking in the .ini and testing to see which functions it has.

[QUOTE=10metreh;178259]I don't know if there is an easier way than simply looking in the .ini and testing to see which functions it has.[/QUOTE]

Just run aliqueit without any arguments. That'll print the version number and a brief overview of the args.

I will try it again making sure I have the most recent. I have 2 computers and may have accidentally tried it with an older version.