Gamma-ray pulsar search #5 longer computing time

B.I.G
B.I.G
Joined: 26 Oct 07
Posts: 111
Credit: 990,424,445
RAC: 913,668
Topic 230966

On my old Xeon machine ( https://einsteinathome.org/host/3426951 )  the Gamma-ray pulsar search #5 v1.11 () x86_64-apple-darwin tasks suddenly take 20.000 instead of 10.000 seconds for the same credits. Was there a change in the work units. Or is there something wrong with my machine?

GWGeorge007
GWGeorge007
Joined: 8 Jan 18
Posts: 2,850
Credit: 4,720,611,869
RAC: 3,283,246

B.I.G wrote: On my old Xeon

B.I.G wrote:

On my old Xeon machine ( https://einsteinathome.org/host/3426951 )  the Gamma-ray pulsar search #5 v1.11 () x86_64-apple-darwin tasks suddenly take 20.000 instead of 10.000 seconds for the same credits. Was there a change in the work units. Or is there something wrong with my machine?

Best as I can tell, it is the Task I.D. "LATeah2011F" vs "LATeah2014F" with the former taking ~10,000 secs.  Nothing that you can do about it.  Sorry.

George

Proud member of the Old Farts Association

Pavel_Kirpichenko
Pavel_Kirpichenko
Joined: 28 Aug 12
Posts: 6
Credit: 42,634,440
RAC: 111,656

Do 2011 and 2014 mean the

Do 2011 and 2014 mean the year when the data was received?

GWGeorge007
GWGeorge007
Joined: 8 Jan 18
Posts: 2,850
Credit: 4,720,611,869
RAC: 3,283,246

Pavel_Kirpichenko wrote: Do

Pavel_Kirpichenko wrote:

Do 2011 and 2014 mean the year when the data was received?

No, they were both built in the same year:  Jul 26 2017. You can find this information in the 'Stderr output' file of the task in question on the 4th line.  It's really easy.

George

Proud member of the Old Farts Association

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 4,779
Credit: 17,805,306,131
RAC: 3,978,201

No George, he was asking

No George, he was asking about the data sets, not the date the science application was built.

The naming of the data sets COULD be the year the data was acquired, OR it could just be sequential numbering of the data set the tasks are part of.

Likely to be the year the data was acquired but just a guess.  A scientist would have to chime in with the truth here.

 

Scrooge McDuck
Scrooge McDuck
Joined: 2 May 07
Posts: 872
Credit: 16,314,111
RAC: 5,136

B.I.G schrieb: On my old

B.I.G wrote:

On my old Xeon machine ( https://einsteinathome.org/host/3426951 )  the Gamma-ray pulsar search #5 v1.11 () x86_64-apple-darwin tasks suddenly take 20.000 instead of 10.000 seconds for the same credits. Was there a change in the work units. Or is there something wrong with my machine?

These tasks analyze different raw data files (Keith explained it already). The analysis configuration changes with different raw data. Even within the same science run (crunching same LATeah20xxF file) different tasks apply different analysis configuration, that is, e.g. the number of skypoints differ and thus the specific calculations (see task descriptions in client_state.xml or command line printout in stderr.txt. There are lots of parameters). From my observations: The recent FGRP5 tasks with only four skypoints require significantly less CPU time compared to current ones with 40...44 skypoints. FGRP5 task with two digit numbers (NN) in task name after prefix "LATeah2014F_", e.g.: "LATeah2014F_72.0_3252_-1.7e-11_0" have few skypoints (four, or six for previous raw data files).

In this regard the credit mechanism for FGRP5 tasks is not perfectly fair. They all get the same credits independent of required computation effort, which differs significantly.

But hey, We're crunchin for science not credits, aren't we?  ;-)

B.I.G
B.I.G
Joined: 26 Oct 07
Posts: 111
Credit: 990,424,445
RAC: 913,668

Scrooge McDuck wrote: But

Scrooge McDuck wrote:

But hey, We're crunchin for science not credits, aren't we?  ;-)

Thank you for the detailed explanation, and yes, it's all about the science, I was more worried there could be something wrong with that old machine than about my credits. Credits are nice and all but science rocks :)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.