You mean stuff like "h1_0535.15_S5R4__2_S5R5a_1" ?
As you might know, E@H is crunching data that is generated by teh LIGO gravitational wave observatories in the US, the first part of the task name:
h1_0535.15_S5R4
is the name of the first data file that the task is reading to crunch (each task uses a couple of data files but for the sake of naming the task, only the name of one of the files is used). Within this name: "h1" designates the observatory that generated the data (h1:LIGO Hanfort, L1: LIGO Livingston).
Here 535.15 is the frequency is Hz that is at the low end of a 0.05 Hz frequency band. Each datafile covers a 0.05 Hz band of the whole observation data.
S5R4 is the name of the "run" (experiment name) that the datafile was first generated for. The first two characters S5 means "Science run #5" and designates the latest data-recording period at LIGO at design sensitivity. "R4" is the run number of Einstein At Home.
So, we are here now:
h1_0535.15_S5R4__**2**_S5R5a_1
For each search frequency, an "all-sky" search is performed, that is the PCs are looking for a gravitational wave source with a frequency within a small frequency band and at a certain set of sky-position. Here the 2nd patch in the sky is contained in the task, all patches of all tasks for the frequency together will cover the whole sky.
The next component , "S5R5a" is a version designation for the work unit generator, here it's the first ("a") version within the S5R5 analysis run.
The final number (here 1) signifies an index of the task as for each workunit, at least 2 copies are generated and sent to different crunchers. The results are compared, and if they don't match (or a cruncher fails to meet the deadline), a new copy has to be generated, and that's why you'll occasionally see tasks ending in "_2" or higher.
Yes... Thank you very much. That helps in seeing what the elements are in the file name... Also, if you don't mind, what are the list of 'c'? I have 1 through 80 something, it varies, with 'c' ...
I am still interested in information in reading/understanding what I am see in "TASKS FOR USERS" ...task ID and after you open a success task.. what is listed... Is there any information for this? I haven't seen anything.
I am still interested in information in reading/understanding what I am see in "TASKS FOR USERS" ...task ID and after you open a success task.. what is listed... Is there any information for this? I haven't seen anything.
Thanks in advance.
I'm still not quite sure what it is exactly you are looking for. Is it the debugging output from the app, like this stuff:
5.8.16
Detected CPU type 1
2009-04-28 16:41:58.6578 [normal]: This program is published under the GNU General Public License, version 2
2009-04-28 16:41:58.6580 [normal]: For details see http://einstein.phys.uwm.edu/license.php
2009-04-28 16:41:58.6580 [normal]: This Einstein@home App was built at: Dec 2 2008 15:07:40
2009-04-28 16:41:58.6581 [normal]: Start of BOINC application '../../projects/einstein.phys.uwm.edu/einstein_S5R5_1.01_i686-pc-linux-gnu_1'.
command line: ../../projects/einstein.phys.uwm.edu/einstein_S5R5_1.01_i686-pc-linux-gnu_1 --method=0 --Freq=836.582511244 --FreqBand=0.0207926846095 --dFreq=6.71056161393e-06 --f1dot=-1.98186199899e-09 --f1dotBand=2.18004819888e-09 --df1dot=1.22837955198e-10 --skyGridFile=skygrid_0840Hz_S5R5.dat --numSkyPartitions=475 --partitionIndex=203 --tStack=90000 --nStacksMax=121 --pixelFactor=0.500 --nf1dotRes=1 --ephemE=../../projects/einstein.phys.uwm.edu/earth_05_09 --ephemS=../../projects/einstein.phys.uwm.edu/sun_05_09 --nCand1=10000 -o ../../projects/einstein.phys.uwm.edu/h1_0836.40_S5R4__1153_S5R5a_0_0 --gridType=3 --useWeights=1 --printCand1 --semiCohToplist --semiCohPatchX=0.014768 --semiCohPatchY=0.014768 -d1 --DataFiles1=../../projects/einstein.phys.uwm.edu/h1_0836.40_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.40_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.45_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.45_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.50_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.50_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.55_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.55_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.60_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.60_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.65_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.65_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.70_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.70_S5R4
2009-04-28 16:41:58.7299 [debug]: Set up communication with graphics process.
2009-04-28 16:41:58.9601 [debug]: Reading SFTs and setting up stacks ... done
2009-04-28 16:42:16.9066 [normal]: INFO: Couldn't open checkpoint h1_0836.40_S5R4__1153_S5R5a_0_0.cpt
2009-04-28 16:42:16.9069 [debug]: Total skypoints = 122. Progress: 0,
$Revision: 1.131 $ REV:$Revision, OPT:6, SCVAR:9, SCTRIM:2, HOTVAR:4, HOTDIV:0, HGHPRE:7, HGHBAT:2
c
1, c
2, c
3, c
One could write a little essay on the command line stuff alone....
I am still interested in information in reading/understanding what I am see in "TASKS FOR USERS" ...task ID and after you open a success task.. what is listed... Is there any information for this? I haven't seen anything.
Thanks in advance.
I'm still not quite sure what it is exactly you are looking for. Is it the debugging output from the app, like this stuff:
5.8.16
Detected CPU type 1
2009-04-28 16:41:58.6578 [normal]: This program is published under the GNU General Public License, version 2
2009-04-28 16:41:58.6580 [normal]: For details see http://einstein.phys.uwm.edu/license.php
2009-04-28 16:41:58.6580 [normal]: This Einstein@home App was built at: Dec 2 2008 15:07:40
2009-04-28 16:41:58.6581 [normal]: Start of BOINC application '../../projects/einstein.phys.uwm.edu/einstein_S5R5_1.01_i686-pc-linux-gnu_1'.
command line: ../../projects/einstein.phys.uwm.edu/einstein_S5R5_1.01_i686-pc-linux-gnu_1 --method=0 --Freq=836.582511244 --FreqBand=0.0207926846095 --dFreq=6.71056161393e-06 --f1dot=-1.98186199899e-09 --f1dotBand=2.18004819888e-09 --df1dot=1.22837955198e-10 --skyGridFile=skygrid_0840Hz_S5R5.dat --numSkyPartitions=475 --partitionIndex=203 --tStack=90000 --nStacksMax=121 --pixelFactor=0.500 --nf1dotRes=1 --ephemE=../../projects/einstein.phys.uwm.edu/earth_05_09 --ephemS=../../projects/einstein.phys.uwm.edu/sun_05_09 --nCand1=10000 -o ../../projects/einstein.phys.uwm.edu/h1_0836.40_S5R4__1153_S5R5a_0_0 --gridType=3 --useWeights=1 --printCand1 --semiCohToplist --semiCohPatchX=0.014768 --semiCohPatchY=0.014768 -d1 --DataFiles1=../../projects/einstein.phys.uwm.edu/h1_0836.40_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.40_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.45_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.45_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.50_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.50_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.55_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.55_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.60_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.60_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.65_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.65_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.70_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.70_S5R4
2009-04-28 16:41:58.7299 [debug]: Set up communication with graphics process.
2009-04-28 16:41:58.9601 [debug]: Reading SFTs and setting up stacks ... done
2009-04-28 16:42:16.9066 [normal]: INFO: Couldn't open checkpoint h1_0836.40_S5R4__1153_S5R5a_0_0.cpt
2009-04-28 16:42:16.9069 [debug]: Total skypoints = 122. Progress: 0,
$Revision: 1.131 $ REV:$Revision, OPT:6, SCVAR:9, SCTRIM:2, HOTVAR:4, HOTDIV:0, HGHPRE:7, HGHBAT:2
c
1, c
2, c
3, c
One could write a little essay on the command line stuff alone....
CU
Bikeman
Yes, that's it. I'm don't want you to go to all that trouble, but I thought there may be information over what we're looking at. For example, part of the interesting aspect of participating is being able to ... well, learn what its all about. The pc's and codes are doing all the work, what part do we do other than simply watch... You know what I mean? We loan our cpu time participating in searching for GWs, it will, for me and possibly others who participate to watch and understand the "code" (and I don't mean, looking at coding or open source) but astronomically speaking.... So, I'm simply looking for interpreting ... I guess this code. Isn't that the 'fun' part, the hobby part of what we're doing? I hope so. This is interesting to me.
The longer I think about it, the more I like the idea of writing up a text that would explain and illustrate *accurately* what is actually going on in the science app, where the challenge is to avoid boring math or programming jargon but visualize the computation and explain it in terms that are understood by everyone. I'm not a physicist so I don't know much of the jargon in the first place :-), so I might as well try to write this, possibly in three or four parts. Stay tuned.
The longer I think about it, the more I like the idea of writing up a text that would explain and illustrate *accurately* what is actually going on in the science app, where the challenge is to avoid boring math or programming jargon but visualize the computation and explain it in terms that are understood by everyone. I'm not a physicist so I don't know much of the jargon in the first place :-), so I might as well try to write this, possibly in three or four parts. Stay tuned.
CU
Bikeman
Thank you. I am actually surprise that someone long before me ever asked. I really thought there would have been something available. I looked around and am finding all this fasinating. I have read a couple of the papers at arxiv; they are the results, not what's happening right here in the pc. Its apparent you will put a lot of effort in this explaination... I hope others who are interested will benefit from this as well. I appreciate sharing what you learned.
As I'm getting my feet wet, (just turned 20K credits) my previous questions are being satisfied slowly by reading past posts... Interestingly are the posts on Cruncher's Corner as suggested but especially the Visualization post using Topcat: A graphical presentation of the data...
But mostly in conclusion to that post, I am looking forward to the results Bikeman mentioned and it could possibly be in association to message 97241.
So I appreciate being part of this interesting group of people looking for something that is obviously elusive and special...
reading or interpreting the Task IDs....
)
More specificially, the details listed within our task IDs tab...
I am interested in learning what I'm looking at...
I would visit the
)
I would visit the "Crunchers´corner". I bet you might get faster response over there.
Here I can invite you to a cup of coffee!!
Cheers!
You mean stuff like
)
You mean stuff like "h1_0535.15_S5R4__2_S5R5a_1" ?
As you might know, E@H is crunching data that is generated by teh LIGO gravitational wave observatories in the US, the first part of the task name:
h1_0535.15_S5R4
is the name of the first data file that the task is reading to crunch (each task uses a couple of data files but for the sake of naming the task, only the name of one of the files is used). Within this name: "h1" designates the observatory that generated the data (h1:LIGO Hanfort, L1: LIGO Livingston).
Here 535.15 is the frequency is Hz that is at the low end of a 0.05 Hz frequency band. Each datafile covers a 0.05 Hz band of the whole observation data.
S5R4 is the name of the "run" (experiment name) that the datafile was first generated for. The first two characters S5 means "Science run #5" and designates the latest data-recording period at LIGO at design sensitivity. "R4" is the run number of Einstein At Home.
So, we are here now:
h1_0535.15_S5R4__**2**_S5R5a_1
For each search frequency, an "all-sky" search is performed, that is the PCs are looking for a gravitational wave source with a frequency within a small frequency band and at a certain set of sky-position. Here the 2nd patch in the sky is contained in the task, all patches of all tasks for the frequency together will cover the whole sky.
The next component , "S5R5a" is a version designation for the work unit generator, here it's the first ("a") version within the S5R5 analysis run.
The final number (here 1) signifies an index of the task as for each workunit, at least 2 copies are generated and sent to different crunchers. The results are compared, and if they don't match (or a cruncher fails to meet the deadline), a new copy has to be generated, and that's why you'll occasionally see tasks ending in "_2" or higher.
CU
Bikeman
Yes... Thank you very much.
)
Yes... Thank you very much. That helps in seeing what the elements are in the file name... Also, if you don't mind, what are the list of 'c'? I have 1 through 80 something, it varies, with 'c' ...
I am still interested in
)
I am still interested in information in reading/understanding what I am see in "TASKS FOR USERS" ...task ID and after you open a success task.. what is listed... Is there any information for this? I haven't seen anything.
Thanks in advance.
RE: I am still interested
)
I'm still not quite sure what it is exactly you are looking for. Is it the debugging output from the app, like this stuff:
Detected CPU type 1
2009-04-28 16:41:58.6578 [normal]: This program is published under the GNU General Public License, version 2
2009-04-28 16:41:58.6580 [normal]: For details see http://einstein.phys.uwm.edu/license.php
2009-04-28 16:41:58.6580 [normal]: This Einstein@home App was built at: Dec 2 2008 15:07:40
2009-04-28 16:41:58.6581 [normal]: Start of BOINC application '../../projects/einstein.phys.uwm.edu/einstein_S5R5_1.01_i686-pc-linux-gnu_1'.
command line: ../../projects/einstein.phys.uwm.edu/einstein_S5R5_1.01_i686-pc-linux-gnu_1 --method=0 --Freq=836.582511244 --FreqBand=0.0207926846095 --dFreq=6.71056161393e-06 --f1dot=-1.98186199899e-09 --f1dotBand=2.18004819888e-09 --df1dot=1.22837955198e-10 --skyGridFile=skygrid_0840Hz_S5R5.dat --numSkyPartitions=475 --partitionIndex=203 --tStack=90000 --nStacksMax=121 --pixelFactor=0.500 --nf1dotRes=1 --ephemE=../../projects/einstein.phys.uwm.edu/earth_05_09 --ephemS=../../projects/einstein.phys.uwm.edu/sun_05_09 --nCand1=10000 -o ../../projects/einstein.phys.uwm.edu/h1_0836.40_S5R4__1153_S5R5a_0_0 --gridType=3 --useWeights=1 --printCand1 --semiCohToplist --semiCohPatchX=0.014768 --semiCohPatchY=0.014768 -d1 --DataFiles1=../../projects/einstein.phys.uwm.edu/h1_0836.40_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.40_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.45_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.45_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.50_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.50_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.55_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.55_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.60_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.60_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.65_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.65_S5R4;../../projects/einstein.phys.uwm.edu/h1_0836.70_S5R4;../../projects/einstein.phys.uwm.edu/l1_0836.70_S5R4
2009-04-28 16:41:58.7299 [debug]: Set up communication with graphics process.
2009-04-28 16:41:58.9601 [debug]: Reading SFTs and setting up stacks ... done
2009-04-28 16:42:16.9066 [normal]: INFO: Couldn't open checkpoint h1_0836.40_S5R4__1153_S5R5a_0_0.cpt
2009-04-28 16:42:16.9069 [debug]: Total skypoints = 122. Progress: 0,
$Revision: 1.131 $ REV:$Revision, OPT:6, SCVAR:9, SCTRIM:2, HOTVAR:4, HOTDIV:0, HGHPRE:7, HGHBAT:2
c
1, c
2, c
3, c
One could write a little essay on the command line stuff alone....
CU
Bikeman
RE: RE: I am still
)
Yes, that's it. I'm don't want you to go to all that trouble, but I thought there may be information over what we're looking at. For example, part of the interesting aspect of participating is being able to ... well, learn what its all about. The pc's and codes are doing all the work, what part do we do other than simply watch... You know what I mean? We loan our cpu time participating in searching for GWs, it will, for me and possibly others who participate to watch and understand the "code" (and I don't mean, looking at coding or open source) but astronomically speaking.... So, I'm simply looking for interpreting ... I guess this code. Isn't that the 'fun' part, the hobby part of what we're doing? I hope so. This is interesting to me.
The longer I think about it,
)
The longer I think about it, the more I like the idea of writing up a text that would explain and illustrate *accurately* what is actually going on in the science app, where the challenge is to avoid boring math or programming jargon but visualize the computation and explain it in terms that are understood by everyone. I'm not a physicist so I don't know much of the jargon in the first place :-), so I might as well try to write this, possibly in three or four parts. Stay tuned.
CU
Bikeman
RE: The longer I think
)
Thank you. I am actually surprise that someone long before me ever asked. I really thought there would have been something available. I looked around and am finding all this fasinating. I have read a couple of the papers at arxiv; they are the results, not what's happening right here in the pc. Its apparent you will put a lot of effort in this explaination... I hope others who are interested will benefit from this as well. I appreciate sharing what you learned.
As I'm getting my feet wet,
)
As I'm getting my feet wet, (just turned 20K credits) my previous questions are being satisfied slowly by reading past posts... Interestingly are the posts on Cruncher's Corner as suggested but especially the Visualization post using Topcat: A graphical presentation of the data...
But mostly in conclusion to that post, I am looking forward to the results Bikeman mentioned and it could possibly be in association to message 97241.
So I appreciate being part of this interesting group of people looking for something that is obviously elusive and special...