First check and double check llrnet servers.

opyrt · 2008-12-31, 13:17

What happens if a first check result is submitted to the double check llrnet server?

I have some computers running first check now, and I wonder if changing the port to the double check port and restarting the clients will be enough to switch to double check without the running first check WU (and one cached) being wasted. I know I can start llrnet with different params to only crunch one WU and not reserve another one, but that seems like alot more work.

mdettweiler · 2008-12-31, 17:39

Quote:

Originally Posted by opyrt

What happens if a first check result is submitted to the double check llrnet server?

I have some computers running first check now, and I wonder if changing the port to the double check port and restarting the clients will be enough to switch to double check without the running first check WU (and one cached) being wasted. I know I can start llrnet with different params to only crunch one WU and not reserve another one, but that seems like alot more work.

From what I've observed of the PSP LLRnet setup, your results should in fact be accepted, and credited as first-pass tests. I'm not sure, however, as to whether the first-pass server will think you've abandoned them, and re-hand them out to first-pass clients...and then they will be submitted a second time for an early doublecheck to the first-pass server (and credited as a doublecheck). Even if it did do that, though, it shouldn't be too bad.

Of course, I could be dead wrong on this so someone please correct me if that's the case.

ltd · 2009-01-01, 10:55

At the moment first pass tests returned to the second pass server are not used as first or second pass results. They are used for third pass only. The reason for that is that I did not imagine that there would be a change from the first pass server to the second pass server while the result is still running. And so I did not implement the necessary routines in by backend programms.

So at the moment the best thing you can do is to finish the first pass test before changing. Yes I know that means the most work for you but I have no short term solution for the backend.

I will but the isssue on my agenda for future implementation.

To describe the internal handling a little bit more here are the rules used when importing data from the llr server.

First pass server:

If a result comes in that was handed out by this server it is checked if there is no first pass result. In that case the result is used as first pass. If there is already a first pass result it is checked if the new result comes from the same user. If this is the case the result is discarded. If it comes from a different user the result is used as second pass. This rule is implemented due to the fact that in case of a communication disturbance between llr server and llr client there is a chance that the client send the result twice.
If the received result is not in the working queue of the llrnet server the result can only be counted as second pass but again only if it comes from a different user.

Same goes for the second pass server only replcae first/second pass with second/third pass.

Hope this makes everything a little bit clearer.

opyrt · 2009-01-02, 01:50

Quote:

Originally Posted by ltd

Hope this makes everything a little bit clearer.

It makes everything alot clearer, thanks!

2008-12-31, 13:17	#1
opyrt Apr 2008 Oslo, Norway 7×31 Posts	First check and double check llrnet servers. What happens if a first check result is submitted to the double check llrnet server? I have some computers running first check now, and I wonder if changing the port to the double check port and restarting the clients will be enough to switch to double check without the running first check WU (and one cached) being wasted. I know I can start llrnet with different params to only crunch one WU and not reserve another one, but that seems like alot more work.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Double-Check	wombatman	Conjectures 'R Us	3	2016-08-29 20:46
Double Check	Unregistered	Information & Answers	3	2011-10-01 04:38
Double-check check?	M0CZY	Software	15	2008-10-30 14:20
Here's why we double-check...	gd_barnes	No Prime Left Behind	0	2008-02-11 19:23
Double Check P-1	PhilF	PrimeNet	6	2005-07-03 14:36

2009-01-01, 10:55	#3
ltd Apr 2003 2²·193 Posts	At the moment first pass tests returned to the second pass server are not used as first or second pass results. They are used for third pass only. The reason for that is that I did not imagine that there would be a change from the first pass server to the second pass server while the result is still running. And so I did not implement the necessary routines in by backend programms. So at the moment the best thing you can do is to finish the first pass test before changing. Yes I know that means the most work for you but I have no short term solution for the backend. I will but the isssue on my agenda for future implementation. To describe the internal handling a little bit more here are the rules used when importing data from the llr server. First pass server: If a result comes in that was handed out by this server it is checked if there is no first pass result. In that case the result is used as first pass. If there is already a first pass result it is checked if the new result comes from the same user. If this is the case the result is discarded. If it comes from a different user the result is used as second pass. This rule is implemented due to the fact that in case of a communication disturbance between llr server and llr client there is a chance that the client send the result twice. If the received result is not in the working queue of the llrnet server the result can only be counted as second pass but again only if it comes from a different user. Same goes for the second pass server only replcae first/second pass with second/third pass. Hope this makes everything a little bit clearer.