Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 957
|
![]() |
Author |
|
KLiK
Master Cruncher Croatia Joined: Nov 13, 2006 Post Count: 3108 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I like it!!! I personally think batches per unit of time is the most accurate predictor of the end of the KNOWN work. As more more work is KNOWN, the dates moves. Downside, major dependence on information from the techs/scientists.... nuff said. But only if you have a time unit from beginning of the project, that would work...as shown in FA@h graph, some batches go quicker, some less quick...if you take 30 day average, you end up with problems! That's why I suggested on many occasions to techs/admins to use start date of the project...& subtract the days that project has been paused...to use that for a project 6m before ECD statement in Research page... It has been only said that it's a hard to make such a thing... ![]() I do know we had hick ups with OET...but my ECD are for a long runs better than anything else we have here...if only some people would join in the math to their graphs, things would be so much better looking... ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I think that a 30 day average is getting close to being to long. I would probably stick with 7 to 15 day average. IMO, a 30 day average, or longer, will tend to smooth out peaks and valleys in batch flow that are more indicative of the recent batch processing. I would prefer to have the ECD move forward and backward as a result of the peaks and valleys. This makes the ECD more accurate especially as you get close to the end of the project where accuracy matters. If you go all the way back to the beginning of the project, your ECD will be waaaaaaay off. I have to agree with your statement that your ECD is better than anything we have here only because we don't really have anything here. So, in essence, anything is better, no matter how inaccurate. Don't remember seeing your math but if you use the percentages from the research page, your ECD becomes suspect as your input is suspect.
|
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7701 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
IMO, a 30 day average, or longer, will tend to smooth out peaks and valleys in batch flow that are more indicative of the recent batch processing. I do keep track of a 7 day average, but it jumps around too much for my taste. I like the 30 day average precisely because it does smooth out the peaks and valleys. I also experimented with some longer time frames, but settled on the 30 day figure because it seemed to track more closely to a trend line. If the project had exhibited greater volatility in such factors as length of work unit or number of crunchers it would be less likely to follow a trend line, especially in the short run. So far it does look like batch 126500 will be issued either very late on October 4 or very early on October 5, so at least for the last month or so this method seems to come close to the right time. I appreciate your input. Cheers Edit: Looks like it will be October 5 for 126500. Edit 2: MCM1_ 0126500_ 6370_ 0-- In Progress 10/5/16 06:01:06 10/12/16 06:01:06
Sgt. Joe
----------------------------------------*Minnesota Crunchers* [Edit 2 times, last edit by Sgt.Joe at Oct 5, 2016 12:56:53 PM] |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7701 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Can send you a copy of a cleaned book containing just the tab with that chart in it (Office 2013, possibly Office 2010... don't recollect)... PM via Berkeley forums and I'll Dropbox a zipped personal copy for your use. Thank you. In the next day or two I shall proceed to figure out how to PM you from the Berkeley forums. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
@Sgt.Joe
My comments were directed at ECD calculations in general and not at any specific project. Your process seems to work quite well, so I would stick with it. I suspect a lot of it is personal preference and one's desired accuracy at any one point in time. BTW, do appreciate the work you've put into the MCM progress reports. |
||
|
KLiK
Master Cruncher Croatia Joined: Nov 13, 2006 Post Count: 3108 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I think that a 30 day average is getting close to being to long. I would probably stick with 7 to 15 day average. IMO, a 30 day average, or longer, will tend to smooth out peaks and valleys in batch flow that are more indicative of the recent batch processing. I would prefer to have the ECD move forward and backward as a result of the peaks and valleys. This makes the ECD more accurate especially as you get close to the end of the project where accuracy matters. If you go all the way back to the beginning of the project, your ECD will be waaaaaaay off. I have to agree with your statement that your ECD is better than anything we have here only because we don't really have anything here. So, in essence, anything is better, no matter how inaccurate. Don't remember seeing your math but if you use the percentages from the research page, your ECD becomes suspect as your input is suspect. I do agree with you that 7d average would give more precise ECD during the end of the project...but some 30d were also going a way off (which WCG uses), as OET has gone up to 90% or more in June or July this year...while now it has settled back! I do agree also that those percentages vary from time to time...'cause of a 30d averages, which WCG uses & 'cause of work problems which arise on some projects...& that percentages are in truncated numbers, also doesn't help out... But % also vary 'cause of some new database imputed to servers, like on this MCM project...hopefully it will be disclosed what is this new database, why is it important (in cancer terms) & what are the goals with this new database?! Some of us also asked for a disclosure of weight of projects on WCG servers, here: https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,39503 Those data were not disclosed yet...hopefully it will in future?! |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7701 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
The following figures are based on a total number of work units of 530,000,000 from cubes (project scientist) with the addition of Seippel (WCG tech).
----------------------------------------Hello all, We've received an update on the estimate batch count from the researchers that has added another 9000 batches making the new estimate 26,500 batches. However, this is only an estimate (a lot can change in the almost one year it will take to complete these new batches). Also, the progress bar on the webpage has been updated accordingly. Thanks, Seippel Last 30 day average results:507,111 Percentage Complete:??????? The average length of a WU is currently running about 4.08 hours, slightly shorter than last week, and still trending steady around the 4 hour mark. Still have not seen any of the batches from 122278 to 122402. The ovarian units started with 122403 as the lowest number.My latest batch number was 126610 which would give about 163 batches for the week. Therefore, by this measure the project is about ??.??% complete. We are still at about ??? more months (approx. ? days)of additional crunching at the current recent run rate.The projected completion date is now a ?. Production decreased a bit this past week going from about 3.517 million WU's to 3.338 million WU's completed. During this past week the time devoted to MCM1 was just over an average of 224 years per day, compared to 234 years per day the previous week. Remember, the situation can change at any time and these are only estimates. I have left some question marks because there is a lack of information to even speculate.Perhaps one of the techs will be kind enough to chime in with the estimated number of new batches of work. I decided I will not go into a much more speculative projection of the end of project just based on the amount of work done, the percentage listed on the research page and current pace of units being completed. Just too speculative. I wish I could do better, but the lack of information does provide a bit of hurdle. Only one chart this week, as the second one would be meaningless. ![]() Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
Seoulpowergrid
Veteran Cruncher Joined: Apr 12, 2013 Post Count: 818 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Oh! It's that time of week. Thanks Sgt. Joe! I appreciate the question marks instead of randomly filling in numbers. I hope the techs give the information you need. Cheers mate~
----------------------------------------![]() |
||
|
Col323
Senior Cruncher Joined: Nov 4, 2008 Post Count: 372 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Oh! It's that time of week. Thanks Sgt. Joe! I appreciate the question marks instead of randomly filling in numbers. I hope the techs give the information you need. Cheers mate~ +1I come to this thread for analysis not available on the Research page. I appreciate the work you put in here and look forward to having some solid numbers again soon! |
||
|
johncmacalister2010@gmail.com
Veteran Cruncher Canada Joined: Nov 16, 2010 Post Count: 799 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Oh! It's that time of week. Thanks Sgt. Joe! I appreciate the question marks instead of randomly filling in numbers. I hope the techs give the information you need. Cheers mate~ +1I come to this thread for analysis not available on the Research page. I appreciate the work you put in here and look forward to having some solid numbers again soon! +1 ![]() crunching, crunching, crunching. AMD Ryzen 5 2600 6-core Processor with Windows 11 64 Pro. AMD Ryzen 7 3700X 8-Core Processor with Windows 11 64 Pro (part time) ![]() |
||
|
|
![]() |