There are two types of workunits: short and long. The short workunits have XXXX.X less than or equal to 0400.0.
There are also two types of data files: short and long. The short data files (l1_XXXX.X) are from the LIGO Livingston Observatory, and are about 4.5MB in size. The long data files (h1_XXXX.X) are from LIGO Hanford and are about 16MB in size.
Does anyone know the meaning of the second number in the WU's name? And perhaps the ratio long/short? In this thread, it was noticed that under 10M WUs remained. We wonder how many short and long ones that would be.
l1: detector name. L1 is Livingston LA, H1 and H2 are at handford WA.
1391.0: the frequency that the data is being examined at
S5R1: science run 5, revision 1.
738: Subcomponent number for the data at the observatory/frequency. I assume this number is time dependent, adjacent groups of 8 units share the same data file.
S5R1A: Repeat of the science run number,not sure what the repeat is for, or the meaning of the A is.
l1: detector name. L1 is Livingston LA, H1 and H2 are at handford WA.
1391.0: the frequency that the data is being examined at
S5R1: science run 5, revision 1.
738: Subcomponent number for the data at the observatory/frequency. I assume this number is time dependent, adjacent groups of 8 units share the same data file.
S5R1A: Repeat of the science run number,not sure what the repeat is for, or the meaning of the A is.
0: I'm the first person assigned the WU.
S5R1A means: Data from Science run #5, analysis Run #1, issue A.
If we later find that for one reason or another we have to add some WUs (maybe recalculate results we found to be bad), these will get an issue letter B asf. In some sense this string reflects the build of our WU generator.
l1, 1391.0 and S5R1 are the tags that form the name of the datafile "l1_1391.0_S5R1" (which you should find in the project folder on your machine).
The 738 has no obvious relation to the parameters (frequency etc.), it's just the 738th WU generated from WU generator S5R1A referring to this datafile.
Hi Dr. Allen and all crunchers.
Since returning to the project I think I have only received S5 work units. Linux seem to handle Hyper-Threading better then Windblow ever did. I stop processing due to the fact that I starting getting way to many client error.
Anyway just fyi:
"h1_0434.0_S5R1__148_S5RIa_3" and "hi_0638.0_3675_S5RIa_1" are the two work units I have at the moment.
Hi Dr. Allen and all crunchers.
Since returning to the project I think I have only received S5 work units. Linux seem to handle Hyper-Threading better then Windblow ever did. I stop processing due to the fact that I starting getting way to many client error.
Anyway just fyi:
"h1_0434.0_S5R1__148_S5RIa_3" and "hi_0638.0_3675_S5RIa_1" are the two work units I have at the moment.
Am now crunching my first S5R2 workunit and the time to completion has gone up from sbout 16 hours to an estimated 50!!! Sheesh there must be a lot more in these new ones than the old!
In addition to being larger WUs, the new application is brandnew and hasn't been optimized like the s5r1 app so part of the size is due to the expectation of speeding up crunching rates in the medium term future.
RE: Thanks, but I'm down
)
No need to manually install this -- it is now the standard app.
Bruce
Director, Einstein@Home
RE: There are two types
)
Does anyone know the meaning of the second number in the WU's name? And perhaps the ratio long/short? In this thread, it was noticed that under 10M WUs remained. We wonder how many short and long ones that would be.
Regards,
Bert
Somnio ergo sum
l1_1391.0_S5R1__738_S5R1A_0
)
l1_1391.0_S5R1__738_S5R1A_0
l1: detector name. L1 is Livingston LA, H1 and H2 are at handford WA.
1391.0: the frequency that the data is being examined at
S5R1: science run 5, revision 1.
738: Subcomponent number for the data at the observatory/frequency. I assume this number is time dependent, adjacent groups of 8 units share the same data file.
S5R1A: Repeat of the science run number,not sure what the repeat is for, or the meaning of the A is.
0: I'm the first person assigned the WU.
RE: l1_1391.0_S5R1__738_S5R
)
S5R1A means: Data from Science run #5, analysis Run #1, issue A.
If we later find that for one reason or another we have to add some WUs (maybe recalculate results we found to be bad), these will get an issue letter B asf. In some sense this string reflects the build of our WU generator.
l1, 1391.0 and S5R1 are the tags that form the name of the datafile "l1_1391.0_S5R1" (which you should find in the project folder on your machine).
The 738 has no obvious relation to the parameters (frequency etc.), it's just the 738th WU generated from WU generator S5R1A referring to this datafile.
BM
BM
Hi Dr. Allen and all
)
Hi Dr. Allen and all crunchers.
Since returning to the project I think I have only received S5 work units. Linux seem to handle Hyper-Threading better then Windblow ever did. I stop processing due to the fact that I starting getting way to many client error.
Anyway just fyi:
"h1_0434.0_S5R1__148_S5RIa_3" and "hi_0638.0_3675_S5RIa_1" are the two work units I have at the moment.
Greg
RE: Hi Dr. Allen and all
)
Am now crunching my first S5R2 workunit and the time to completion has gone up from sbout 16 hours to an estimated 50!!! Sheesh there must be a lot more in these new ones than the old!
Mrs Miggins - A lady of uncommon refinement
In addition to being larger
)
In addition to being larger WUs, the new application is brandnew and hasn't been optimized like the s5r1 app so part of the size is due to the expectation of speeding up crunching rates in the medium term future.
Just finished my first S5R2
)
Just finished my first S5R2 workunit @ 49 hours. Pages and pages of printout about checkpoints etc. Is this to be expected?
Mrs Miggins - A lady of uncommon refinement
RE: Just finished my first
)
I think this is normal. One of my PCs ned 55 hours..
The debug output, too.
)
The debug output, too. Everyone gets that atm.