The crediting system is simple. The crediting is determined on how many FLOPs your system does. Since each unit given to 2 computers is exactly the same, it gets the same credit, cause the FLOPs will be the same. I think that is very simple, and everyone gets fair credit.
That's how it works at SETI.
Einstein credits are pre-determined by the Server. I don't know what algorithm they use for that though.
The crediting system is simple. The crediting is determined on how many FLOPs your system does. Since each unit given to 2 computers is exactly the same, it gets the same credit, cause the FLOPs will be the same. I think that is very simple, and everyone gets fair credit.
That's how it works at SETI.
Einstein credits are pre-determined by the Server. I don't know what algorithm they use for that though.
If I understood the readings, yes it is predetermind from the server side, but they already precounted the flops, and that's why they assign the numbers.
The crediting system is simple. The crediting is determined on how many FLOPs your system does. Since each unit given to 2 computers is exactly the same, it gets the same credit, cause the FLOPs will be the same. I think that is very simple, and everyone gets fair credit.
That's how it works at SETI.
Einstein credits are pre-determined by the Server. I don't know what algorithm they use for that though.
If I understood the readings, yes it is predetermind from the server side, but they already precounted the flops, and that's why they assign the numbers.
Doesn't sound logical to me. If you pre-count the flops, then you must be crunching it at the same time (otherwise how do you know you're done?).
They may have some algorithm that guestimates the flops, but I doubt they pre-count them.
Is there a quick way to tell that a computer's downloaded it?
I'm doubtful that my machine has downloaded it..
The version gets bound at download time--you can see this in client_state.xml if you like.
You downloaded a bunch of results on August 9, before the new ap was available. If I understand how this works, those are already labelled to be processed by 4.02. When you download new results, they'll get tagged as 4.24, and before your host tries to process them it will download the ap.
Is there a quick way to tell that a computer's downloaded it?
I'm doubtful that my machine has downloaded it..
The version gets bound at download time--you can see this in client_state.xml if you like.
You downloaded a bunch of results on August 9, before the new ap was available. If I understand how this works, those are already labelled to be processed by 4.02. When you download new results, they'll get tagged as 4.24, and before your host tries to process them it will download the ap.
Sometimes a big queue is a disadvantage.
If I got this wrong, please correct me.
Thanks for the answers, and yes a big queue can be a disadvantage at times :(
All my WU's are running on the 4.02 app so it looks like I'll have to wait a while to get the new one...
RE: The crediting system
)
That's how it works at SETI.
Einstein credits are pre-determined by the Server. I don't know what algorithm they use for that though.
Seti Classic Final Total: 11446 WU.
RE: RE: The crediting
)
If I understood the readings, yes it is predetermind from the server side, but they already precounted the flops, and that's why they assign the numbers.
RE: RE: RE: The
)
Doesn't sound logical to me. If you pre-count the flops, then you must be crunching it at the same time (otherwise how do you know you're done?).
They may have some algorithm that guestimates the flops, but I doubt they pre-count them.
Seti Classic Final Total: 11446 WU.
I have a quick question
)
I have a quick question regarding the new app...
Is there a quick way to tell that a computer's downloaded it?
I'm doubtful that my machine has downloaded it..
Human Stupidity Is Infinite...
RE: I have a quick question
)
Keep an eye on the 'Work' tab in BOINC manager.
Look at the 'Application' column - make sure it's wide enough to show the version number at the end.
Wait till Einstein downloads the next workunit. You should see '4.24' at the end of the application name.
Then have a look at the 'Messages' tab.
You should see entries for start/finish download of the .exe and the .pdb files.
RE: I have a quick question
)
The version gets bound at download time--you can see this in client_state.xml if you like.
You downloaded a bunch of results on August 9, before the new ap was available. If I understand how this works, those are already labelled to be processed by 4.02. When you download new results, they'll get tagged as 4.24, and before your host tries to process them it will download the ap.
Sometimes a big queue is a disadvantage.
If I got this wrong, please correct me.
RE: RE: I have a quick
)
Thanks for the answers, and yes a big queue can be a disadvantage at times :(
All my WU's are running on the 4.02 app so it looks like I'll have to wait a while to get the new one...
My Einstein debt is way into the negative...
Human Stupidity Is Infinite...
RE: I have a quick question
)
Download the "einstein_S5R1_4.24_windows_intelx86.zip" from here,
Beta Test Page
and follow this description.
Switching Apps half way trough a result
RE: RE: I have a quick
)
Add:
Do not use the "app_info.xml". (only used in Beta Testing phase)
RE: RE: RE: I have a
)
Thanks, but I'm down to only one WU now, so I figure its too much work to manually install it :)
Human Stupidity Is Infinite...