Report deadline: 1 week!
18 Feb 2005 12:18:47 UTC
Topic 187702
(moderation:
When I look at my results in the user profile I see the download date and the deadline. I downloaded several WUs today (Feb. 18th). For all WUs the deadline is Feb. 25th! This must be an error - even for SETI@Home the deadline is 2 weeks.
Report deadline: 1 week!
)
> When I look at my results in the user profile I see the download date and the
> deadline. I downloaded several WUs today (Feb. 18th). For all WUs the deadline
> is Feb. 25th! This must be an error - even for SETI@Home the deadline is 2
> weeks.
>
no, its not an error, einstein@home has shorter deadlines than seti@home....
its planed to extend them when the project finishs the testing phase and goes public
> > When I look at my results
)
> > When I look at my results in the user profile I see the download date and
> the
> > deadline. I downloaded several WUs today (Feb. 18th). For all WUs the
> deadline
> > is Feb. 25th! This must be an error - even for SETI@Home the deadline is
> 2
> > weeks.
> >
>
> no, its not an error, einstein@home has shorter deadlines than seti@home....
> its planed to extend them when the project finishs the testing phase and goes
> public
>
Hi MetalWarrior,
it IS public since yesterday! That's how I registered.
> Hi MetalWarrior, > > it IS
)
> Hi MetalWarrior,
>
> it IS public since yesterday! That's how I registered.
>
>
Feb 14, 2005
For testing purposes, in anticipation of our public launch, we will be enabling account creation for some unannounced periods this week. If you are interested in joining Einstein@Home, please try the Create Account link.
no, its not really public... this also belongs to the testing phase. i think they want to get more users to test if the System can handle it, so its still in testing
> > Hi MetalWarrior, > > > >
)
> > Hi MetalWarrior,
> >
> > it IS public since yesterday! That's how I registered.
> >
> >
>
> Feb 14, 2005
>
> For testing purposes, in anticipation of our public launch, we will be
> enabling account creation for some unannounced periods this week. If you are
> interested in joining Einstein@Home, please try the Create Account link.
>
>
> no, its not really public... this also belongs to the testing phase. i think
> they want to get more users to test if the System can handle it, so its still
> in testing
>
O.K., thanks for the information. I was one of the lucky-ones then!
> > > Hi MetalWarrior, > > >
)
> > > Hi MetalWarrior,
> > >
> > > it IS public since yesterday! That's how I registered.
> > >
> > >
> >
> > Feb 14, 2005
> >
> > For testing purposes, in anticipation of our public launch, we will be
> > enabling account creation for some unannounced periods this week. If you
> are
> > interested in joining Einstein@Home, please try the Create Account link.
> >
> >
> > no, its not really public... this also belongs to the testing phase. i
> think
> > they want to get more users to test if the System can handle it, so its
> still
> > in testing
> >
>
>
> O.K., thanks for the information. I was one of the lucky-ones then!
Note: At least in the short term, I am not planning to extend the report deadlines. The size of the database grows directly in proportion to these deadlines, so keeping the deadlines shorter reduces the strain on the server and allows more people to participate.
A single E@H workunit should take 7 or 8 hours on a modern machine, and perhaps 24-36 CPU hours on an old machine. Provided that the machine is available for BOINC at least 10% of the time, most machines should be able to complete the workunit by the deadline.
Bruce
Director, Einstein@Home
> Note: At least in the short
)
> Note: At least in the short term, I am not planning to extend the report
> deadlines. The size of the database grows directly in proportion to these
> deadlines, so keeping the deadlines shorter reduces the strain on the server
> and allows more people to participate.
>
> A single E@H workunit should take 7 or 8 hours on a modern machine, and
> perhaps 24-36 CPU hours on an old machine. Provided that the machine is
> available for BOINC at least 10% of the time, most machines should be able to
> complete the workunit by the deadline.
>
> Bruce
FWIW, one of the machines I have dedicated to the project is a Compaq Proliant Quad Xeon P3-500 with 1.8 Gig of ram running Win2k Server. With E@H being the only project each of the processors is running, typical WU times hover around 20 to 24 hours to complete. :)
"Chance is irrelevant. We will succeed."
- Seven of Nine
> > > Feb 14, 2005 > > > > >
)
> > > Feb 14, 2005
> > >
> > > For testing purposes, in anticipation of our public launch, we will
> be
> > > enabling account creation for some unannounced periods this week. If
> you
> > are
> > > interested in joining Einstein@Home, please try the Create Account
> link.
> > >
> > >
> > > no, its not really public... this also belongs to the testing phase.
> i
> > think
> > > they want to get more users to test if the System can handle it, so
> its
> > still
> > > in testing
> > >
> >
> >
> > O.K., thanks for the information. I was one of the lucky-ones then!
>
> Note: At least in the short term, I am not planning to extend the report
> deadlines. The size of the database grows directly in proportion to these
> deadlines, so keeping the deadlines shorter reduces the strain on the server
> and allows more people to participate.
>
> A single E@H workunit should take 7 or 8 hours on a modern machine, and
> perhaps 24-36 CPU hours on an old machine. Provided that the machine is
> available for BOINC at least 10% of the time, most machines should be able to
> complete the workunit by the deadline.
>
> Bruce
>
hm... sorry, i dont know where i got my wrong information from :)
p.s. i think its great that you yourself participate that much in this board
and answer the questions of the users ! @bruce allen
greetings, MetalWarrior
> > Note: At least in the
)
>
> Note: At least in the short term, I am not planning to extend the report
> deadlines. The size of the database grows directly in proportion to these
> deadlines, so keeping the deadlines shorter reduces the strain on the server
> and allows more people to participate.
>
> A single E@H workunit should take 7 or 8 hours on a modern machine, and
> perhaps 24-36 CPU hours on an old machine. Provided that the machine is
> available for BOINC at least 10% of the time, most machines should be able to
> complete the workunit by the deadline.
>
> Bruce
Even a extension of the report deadlines to eight days in the future would be appreciated.
Are you considering to give out work to computers grouped bye average turnaround time?
Then the scheduler have to resend a WU, is it sent to the first available computer or do you have preferences for who gets whose?
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
For whats it's worth Pro
)
For whats it's worth Pro Predictor is at a 7 day Deadline also. Personally I think all the Projects should adopt the 7 Day Deadline & stick with it. It might alleviate some of the complaining about delays in getting credit.
The People would just have to adjust their Resources and Cache size accordingly ...
> Are you considering to give
)
> Are you considering to give out work to computers grouped bye average
> turnaround time?
Yes -- in fact I made some modifications to the scheduler to do this. But then David Anderson (chief BOINC architect) persuaded me that what I had done was not a good idea. So I backed it out. I'll probably come back to it in the future.
> Then the scheduler have to resend a WU, is it sent to the first available
> computer or do you have preferences for who gets whose?
During 3.5 days after creation, the WU goes to the first machine which has the right data file, that needs work. During the next 3.5 days, it also has some probability of being picked up by a machine that has NO data files. Finally, after 7 days, it goes to the first machine that requests work, which has a broadband (>100 kB/sec) network connection.
Bruce
Director, Einstein@Home