I posted this in the triple check Thread.

I checked all the exponents a user tried to assign himself.

Exponents which he could not reserve :

83553139
83554087
83627359
83630863
83633729

Each of them has two expired P-1 assignments but no current reservation...

He was able to reserve the following exponents with only one expired P-1 assignment :

83543501
83562067
83602901

And of course he has able to claim those that have no expired assignment at all : - )

Others have confirmed this observation on other exponents. That unavailability has been discussed earlier...

Indeed something for the managers of PrimeNet.

Jacob

Double assignments?
 

So, something's a bit strange on [URL="https://www.mersenne.org/primenet/"]the Primenet Work Distribution Map[/URL]. Some of the ranges above 110M have more TF assignments listed than there are candidates.

Drilling down, [URL="https://www.mersenne.org/assignments/?exp_lo=119000000&exp_hi=120000000"]this report[/URL] is showing that SRBase has two TF assignments per candidate. I didn't think Primenet supported more than one TF assignment at a time.

Envious? :razz:
You can't get two assignments for the same expo huh? :razz:

Joking apart, I think it is a mistake, "somebody" opened a door for them to be able to get lots of assignments, and forgot to close it properly. Even if you want to do more bitlevels, it makes no sense to do more assignments for the same expo. Either reserve it "from 72 to 77", or just reserve it "from 72 to 73" but do not return the results until you finish with it. Creating one assignment for every bit would be silly. I think it is an error, which will be fixed soon.

We did both ways in the past, and also the other way around, we were looking for work to low bitlevels, like 73, but the server only assigned us 72 to 76 or so, therefore we did the 72 to 73 and reported it, and we have seen that the assignment is gone, therefore we didn't do the rest of the bits. Doing them would be detrimental, as somebody else could get the assignments and then either we or them, will end with "error 40, results not needed, your work is not wanted, you wasted your ticks in vain".

We raised this flag in the past, but it was not heard. (well, we didn't insist hard, because we liked the idea of picking low hanging fruits too, and yes, we just tried, this is still working!)

[QUOTE=LaurV;543790]Joking apart, I think it is a mistake, "somebody" opened a door for them to be able to get lots of assignments, and forgot to close it properly. Even if you want to do more bitlevels, it makes no sense to do more assignments for the same expo. Either reserve it "from 72 to 77", or just reserve it "from 72 to 73" but do not return the results until you finish with it. Creating one assignment for every bit would be silly. I think it is an error, which will be fixed soon.[/QUOTE]

That's why I raised the observation... :razz:

Aaron has said before that the Primenet database doesn't have a bit-map for TF bit-levels. And, therefore, it can cause problems if TF'ing is reported out-of-order. As in, as you said, if you're going to go to 77, go 77 in one step (or multiple, but in order).

Yeah.

Another thing that is still happening (and we used to take advantage of it in the past) is the following: you go to manual assignment for GPU page and take few high-exponent assignments, where you select the last bit to be 72 or 73, and the range over 400M (where there still are assignments available for this low bitlevel). You click the button, and get a list of as many expos you requested, [B]but[/B] they are not to 72, they are "upgraded" by the server to be 75, or 76. Well, nothing wrong with it, gpu72 also does that, if you let "it" decide, the last bit will be raised to the "optimal" level.

But now, you close the manual assignment page, without adding any work to your cards, and go again to account/my assignments and ask for the assignments you have. The server will say "you have these assignments already:" and give you the list.

But... BUT! In the list of assignment you get now [B]they are all to 72 (or how much you requested) and NOT to the "inflated" values[/B]. You can grab and paste [B]THIS[/B] list to your cards, work on them, and NOT to the inflated expos, and you just got low hanging fruits.

As the server is set now (with this "bug/feature") it is in fact recommended to do so! Because, if you use Misfit, for example, and automatically report each bitlevel as soon as you finish it, then the assignment is "gone" after your first report. Then, if you continue, as per the inflated list, i.e. continue to TF to the levels PrimeNet gave you initially, then you [B]WILL[/B] end up doing the higher bitlevel [B]in the same time[/B] somebody else is getting them assigned and working them (you or the other user will get error 40 upon completion of the higher bitlevels). That is because the assignment, as said, is gone when misfit first reports the low bitlevel.

Moral is that after you request assignments from PrimeNet using the manual form, you should every time go to the "my assignments" and check what you really GOT. And work on that. The initial grab list (the inflated one) is not to be trusted. Maybe that's why some users who got manual assignments got "work not needed", and not because of poaching.

Any chance you can properly direct these results?
 

For some reason my first batch of results from a new PC got credited to -Anonymous- even though the results.txt has my userid.

Recent results are properly credited to me.

Here are the offenders.

[CODE][Sat Apr 25 19:07:42 2020]
UID: petrw1/Stinky_Pete, M56694191 completed P-1, B1=1500000, B2=30000000, E=12, Wh8: BB5C3657
UID: petrw1/Stinky_Pete, M56694097 completed P-1, B1=1500000, B2=30000000, E=12, Wh8: BB5B365E
UID: petrw1/Stinky_Pete, M56693999 completed P-1, B1=1500000, B2=30000000, E=12, Wh8: BB563650
UID: petrw1/Stinky_Pete, M56694181 completed P-1, B1=1500000, B2=30000000, E=12, Wh8: BB52365E
UID: petrw1/Stinky_Pete, M56693969 completed P-1, B1=1500000, B2=30000000, E=12, Wh8: BB273654
UID: petrw1/Stinky_Pete, M56694887 completed P-1, B1=1500000, B2=30000000, E=12, Wh8: BB57365D
UID: petrw1/Stinky_Pete, M56696713 completed P-1, B1=1500000, B2=30000000, E=12, Wh8: BB5C3636
[Sat Apr 25 19:14:04 2020]
P-1 found a factor in stage #2, B1=1500000, B2=30000000, E=12.
UID: petrw1/Stinky_Pete, M56670233 has a factor: 184602903967341014096340982753 (P-1, B1=1500000, B2=30000000, E=12)[/CODE]

[QUOTE=petrw1;543865]Recent results are properly credited to me.[/QUOTE]

Fixed.

[QUOTE=Prime95;543901]Fixed.[/QUOTE]

Thanks but they show up in my results page without a Computer Name

[QUOTE=petrw1;543908]Thanks but they show up in my results page without a Computer Name[/QUOTE]

You can't have everything :)

TF assignments accepted for Cat 1 exponents ?
 

It seems that it is possible to reserve an exponent for trial factoring (with the trial factoring expiry rules) when an exponent is in CAT 1. A query on the active assignments between 50M and 52M wil show it.

IMO once an exponent is in CAT 2, but even more in CAT 1 it should not possible to assign it for manual testing and certainly not for trial factoring.

Jacob

[QUOTE=S485122;545035]IMO once an exponent is in CAT 2, but even more in CAT 1 it should not possible to assign it for manual testing and certainly not for trial factoring.[/QUOTE]

Seconded.

Another (IMO more serious) issue is [URL="https://www.mersenne.org/assignments/?exp_lo=91000000&exp_hi=92000000&exdchk=1&exfirst=1&exp1=1"]the 1002 assignments in the "Cat 1" 91M range.[/URL]

The assignee, SRS Technology, has some compute behind him. But these need to be worked in the next few days, or else expired. He's about to hoard from the LL'ers.