LHC@home

Ok, so I am new to LHC and have probably missed this, but why does the newest result I have received have a reporting deadline sooner than the one before?

---

Ok, so I am new to LHC and have probably missed this, but why does the newest result I have received have a reporting deadline sooner than the one before?

wnov1B_v6s4hvnom_mqx__2__64.274_59.294__8_10__6__15_1_sixvf_boinc58857
versus
wnov1A_v6s4hvnom_mqx__15__64.255_59.275__10_12__6__35_1_sixvf_boinc48950

I think in the boinc wiki, or in the FAQ, there's explanations as to what the different studies are.
http://boinc-doc.net/boinc-wiki/index.php?title=LHC%40Home_FAQ

Someone probably wanted the model to look at a certain set of parameters based on initial results of their study... so maybe the 1B study has a higher priority for the designers.

---

I'm not the LHC Alex. Just a number cruncher like everyone else here.

Ok, so I am new to LHC and have probably missed this, but why does the newest result I have received have a reporting deadline sooner than the one before?

The LHC scheduler has an optimiser built in that estimates the best deadline to get the studies done in the shortest overall time. The optimiser calculates deadlines on the fly based on return times, the number of computers available, and the size of the study (amongst other things).

It is quite possibe that the deadlines have shortened between downloads such that later units finish earlier than earlier ones.

---

Gaspode the UnDressed
http://www.littlevale.co.uk

Ok, so I am new to LHC and have probably missed this, but why does the newest result I have received have a reporting deadline sooner than the one before?

The LHC scheduler has an optimiser built in that estimates the best deadline to get the studies done in the shortest overall time. The optimiser calculates deadlines on the fly based on return times, the number of computers available, and the size of the study (amongst other things).

It is quite possibe that the deadlines have shortened between downloads such that later units finish earlier than earlier ones.

That's all well and good however i am getting 4 and 5 day deadines to complete WU's and the scheduler is downloading far too many WU's to get them completed in time. The LHC@home scheduler does not seem to take in account the LHC@home project share of cpu time or the fact that I have 4 other Boinc projects running on my PC.

It looks like LHC@home will be getting suspended on my PC until we return to something even approaching a sensible deadline for complettion.

---

Ok, so I am new to LHC and have probably missed this, but why does the newest result I have received have a reporting deadline sooner than the one before?

The LHC scheduler has an optimiser built in that estimates the best deadline to get the studies done in the shortest overall time. The optimiser calculates deadlines on the fly based on return times, the number of computers available, and the size of the study (amongst other things).

It is quite possibe that the deadlines have shortened between downloads such that later units finish earlier than earlier ones.

That's all well and good however i am getting 4 and 5 day deadines to complete WU's and the scheduler is downloading far too many WU's to get them completed in time. The LHC@home scheduler does not seem to take in account the LHC@home project share of cpu time or the fact that I have 4 other Boinc projects running on my PC.

It looks like LHC@home will be getting suspended on my PC until we return to something even approaching a sensible deadline for complettion.

Of course if you are using a fairly recent (4.43 or later) version of BOINC, the CPU scheduler will ensure that the deadlines will be met if at all possible, and the project that needs the extra CPU time will not get to download work for a while, so it evens out in the long run.

---

BOINC WIKI