I believe you want to set the following to false in aliqueit ini:
[code]
//Stop if sequence merges with an earlier sequence?
detect_merge = [B]false[/B]
[/code]

But would you really want to? You'd likely be duplicating the efforts of someone else, right?

I don't know, if it's been a long time since you've used it then maybe you're about as rusty as I am. You haven't started aliqueit with the 105-digit number as the sequence number, have you?

i.e. ran "aliqueit N", with N being the c105?

YAFU SIQS Threads
 

Subject change...

I'm running Aliqueit in its normal configuration (without -y**), but with YAFU preferred. When SIQS runs, it only invokes one thread. I do have threads=2 in the yafu.ini file and if I invoke YAFU (SIQS) manually, it runs both threads. I've tried adding -threads 2 in various fashions to the yafu_cmd line, with no luck. I have not tried changing any source code.

Suggestions?

Thanks for all...

**The reason I'm not using the -y option is because I have other machines adding in relations, so I'm relying on factmsieve.py via Aliqueit to create the necessary files used to trigger the other systems.

[QUOTE=EdH;338664]Subject change...

I'm running Aliqueit in its normal configuration (without -y**), but with YAFU preferred. When SIQS runs, it only invokes one thread. I do have threads=2 in the yafu.ini file and if I invoke YAFU (SIQS) manually, it runs both threads. I've tried adding -threads 2 in various fashions to the yafu_cmd line, with no luck. I have not tried changing any source code.

Suggestions?[/QUOTE]

Might it be a case of yafu not using the right yafu.ini? I've got both yafu.exe och yafu.ini in the same dir as aliqueit.exe, but I can imagine there's room for confusion if executables are in different locations. I don't know whether yafu reads yafu.ini from the CWD or from the yafu.exe dir.

[QUOTE=mklasson;338666]Might it be a case of yafu not using the right yafu.ini? I've got both yafu.exe och yafu.ini in the same dir as aliqueit.exe, but I can imagine there's room for confusion if executables are in different locations. I don't know whether yafu reads yafu.ini from the CWD or from the yafu.exe dir.[/QUOTE]
Thanks! You provided a solution:

My YAFU is located in a separate directory, but Aliqueit isn't retrieving the yafu.ini file from there. I copied the yafu.ini file into the Aliqueit directory and it is working now.

Although this works, would it be difficult to have Aliqueit read the original yafu.ini, instead of needing a copy?

Thanks for all.

[QUOTE=EdH;338671]Thanks! You provided a solution:

My YAFU is located in a separate directory, but Aliqueit isn't retrieving the yafu.ini file from there. I copied the yafu.ini file into the Aliqueit directory and it is working now.

Although this works, would it be difficult to have Aliqueit read the original yafu.ini, instead of needing a copy?

Thanks for all.[/QUOTE]

Well, it's not aliqueit that's reading yafu.ini but rather yafu itself. It would appear that yafu reads the ini file from the current working directory and not from the directory yafu.exe is in. I don't see a good way of solving that from within aliqueit.

Yafu's docfile.txt says "These same flags can be specified in a file named yafu.ini in the same directory as the executable." so perhaps you've found some kind of bug? Maybe ask Ben about it and see what he says?

[QUOTE=mklasson;338674]Well, it's not aliqueit that's reading yafu.ini but rather yafu itself. It would appear that yafu reads the ini file from the current working directory and not from the directory yafu.exe is in. I don't see a good way of solving that from within aliqueit.

Yafu's docfile.txt says "These same flags can be specified in a file named yafu.ini in the same directory as the executable." so perhaps you've found some kind of bug? Maybe ask Ben about it and see what he says?[/QUOTE]
Yeah, I started realizing the same thing a little while ago and was going to post it myself.

OTOH, is there a way to pass the -threads switch with the YAFU call. I really thought I should have been able to do so in aliqueit.ini, but most of my attempts triggered Aliqueit to run msieve's SIQS routine.

For now, the copy of yafu.ini in the Aliqueit directory is a simple effort.

Thanks again.

[QUOTE=EdH;338677]OTOH, is there a way to pass the -threads switch with the YAFU call. I really thought I should have been able to do so in aliqueit.ini, but most of my attempts triggered Aliqueit to run msieve's SIQS routine.[/quote]

Yafu seems very particular about the order of cmdline arguments, in that switches need to come _after_ the main command ("factor(nnnnn)"). Adding the switches to yafu_cmd in aliqueit.ini puts the switches before the main command which doesn't seem to work.

Running
"yafu.exe factor(1111111111111111111111) -threads 2"
works fine.

Running
"yafu.exe -threads 2 factor(1111111111111111111111)"
just says "no switch detected" and quits.

[quote]For now, the copy of yafu.ini in the Aliqueit directory is a simple effort.

Thanks again.[/QUOTE]

:tu:

[QUOTE=mklasson;338682]Adding the switches to yafu_cmd [/QUOTE]
You can use yafu.ini for (almost) all switches. No need to put them in command line. For example, instead of -R in cmd line, you can use R=1 in the ini file.

[QUOTE=LaurV;338804]You can use yafu.ini for (almost) all switches. No need to put them in command line. For example, instead of -R in cmd line, you can use R=1 in the ini file.[/QUOTE]

In this case he had problems with yafu.ini specifically and wanted another solution though :)

[QUOTE=LaurV;338804]You can use yafu.ini for (almost) all switches. No need to put them in command line. For example, instead of -R in cmd line, you can use R=1 in the ini file.[/QUOTE]
This was realized. The problem is that yafu (and yafu.ini) is in a separate directory from Aliqueit (they're in the yafu directory), so yafu.ini was never read by YAFU when called from Aliqueit. The solution is that a second yafu.ini is needed in the Aliqueit directory.