[Frost] What is " RZOUT: current RZ file cannot support > 64K records"
Kijun Park
parkkj at jlab.org
Wed Dec 1 13:51:07 EST 2010
Sungkyun Park wrote:
> Eugene,
>
> My understanding is that we do not have any options to limit the number of events in trk_mon_lite.
> The following is the all options I have known about trk_mon_lite
>
> " trk_mon_lite -S[S] -A[R][u,l][#] -Cbeta.[lt,gt].[#] -Cchisq.[lt,gt].[#] -o[outputfile.hbook] [inputfile.A##.B##] "
>
> ----[S] = Sector number (for calibrating one sector at a time)
> ----[R] = Region number (this is for local angle cuts)
> ----[u,l] = u for upper bound, l for lower bound (local angle cuts)
> ----[#] = value of cut (always must go to the tenths digit. e.g. "10.0")
> ----[lt,gt] = lt for less than, gt for greater than (for Ntuple cuts)
> ----[outputfile.hbook] = the name must contain the run number.
>
> Do you mean that I request to cook the run_062505.A05.B03 with 100K events to Brian?
>
> Sung
>
>
>
>
>
> ----- Original Message -----
> From: Eugene Pasyuk <pasyuk at jlab.org>
> Date: Wednesday, December 1, 2010 1:28 pm
> Subject: Re: [Frost] What is " RZOUT: current RZ file cannot support > 64K records"
> To: Michael Dugger <dugger at jlab.org>
> Cc: Sungkyun Park <sp06k at fsu.edu>, dmr10c at fsu.edu, FROST <frost at jlab.org>
>
>
>> Sung,
>>
>> Indeed, ntuple is too large. Try to limit number of events to
>> precess,
>> maybe 100K events.
>>
>> -Eugene
>>
>> Michael Dugger wrote, On 12/01/10 13:23:
>>
>>> Sung,
>>>
>>> It looks like trk_mon_lite is writing an ntuple that is too
>>>
>> large. There
>>
>>> are several ways to try and fix this. The PAW FAQ at
>>> http://www.jlab.org/~brads/Manuals/pawfaq/
>>> under the heading "How to create very large ntuples (RWN or CWN) ?"
>>> has some suggestions.
>>>
>>> -Michael
>>>
>>>
>>>
>>>
>>> On Wed, 1 Dec 2010, Sungkyun Park wrote:
>>>
>>>
>>>> Hi Eugene,
>>>>
>>>> I found some curious points using the trk_mon_lite.
>>>> Do you know what is the following error?
>>>>
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1001) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>>
>>>> The upper errors are happened after using trk_mon_lite.
>>>> For the double check, I tested my current trk_mon_lite using g9a
>>>>
>> data.>> There are no error massages like the upper.
>>
>>>> I think the upper massage is made as the g9b data.
>>>> Do you know how I solve the upper problem?
>>>>
>>>> Sung
>>>> Florida State University
>>>>
>>>>
>>>>
>>>>
>> #########################################################################################>> ifarml1> trk_mon_lite -odc_calib062505_A05B03nov30.hbook /work/clas/disk8/clasg9/pass0/v1/BOS/cooked_062505.A05.B03
>>
>>>> File
>>>>
>> "/work/clas/disk8/clasg9/pass0/v1/BOS/cooked_062505.A05.B03" opened.
>>
>>>> calib_connect: RunIndex_table = "calib_user.RunIndexg9"
>>>> calib_connect: using server=clasdb.jlab.org (default)
>>>> calib_connect: using latest constants
>>>> calib_connect: connecting as user=clasuser
>>>> DC:Reading DC Map parms for run 62505:
>>>> DC: Sector 1 (maprun 62505)
>>>> DC: Sector 2 (maprun 62505)
>>>> DC: Sector 3 (maprun 62505)
>>>> DC: Sector 4 (maprun 62505)
>>>> DC: Sector 5 (maprun 62505)
>>>> DC: Sector 6 (maprun 62505)
>>>> DC:Filling timewalk table for run 62505 (62505):
>>>> DC: RMS residual values read (53968)
>>>> DC: Filling t2x tables..................Done
>>>> DC: Initialization finished for run 62505
>>>> Opening output file "dc_calib062505_A05B03nov30.hbook"
>>>> Ntuple 1001 booked.
>>>> Ntuple 1002 booked.
>>>> Ntuple 1003 booked.
>>>> Ntuple 1004 booked.
>>>> Ntuple 1005 booked.
>>>> Ntuple 1006 booked.
>>>> 119149 events (9372Hz)
>>>>
>>>> 586050 Ntuple rows written.
>>>> 125098 events processed.
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1001) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1002) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1003) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1004) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1005) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1006) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1001) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1002) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1003) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1004) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1005) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>> RZOUT: current RZ file cannot support> 64K records
>>>> or individual directories> 64K
>>>> RZOUT: previous cycle(s) for this key ( 1006) deleted
>>>> RZOUT: please consult ZEBRA manual for further details
>>>>
>>>>
>> ################################################################################>> _______________________________________________
>>
>>>> Frost mailing list
>>>> Frost at jlab.org
>>>> https://mailman.jlab.org/mailman/listinfo/frost
>>>>
>>>>
>>> _______________________________________________
>>> Frost mailing list
>>> Frost at jlab.org
>>> https://mailman.jlab.org/mailman/listinfo/frost
>>>
>
> Florida State University
> _______________________________________________
> Frost mailing list
> Frost at jlab.org
> https://mailman.jlab.org/mailman/listinfo/frost
>
Hi, Sung
There is alternative way to control the event number in BOS file. You
may try ...
splitbos -o run_data_part_file[1] -skip ${skip3} -n $evt3 -q
./run_data_file.A00
where,
run_data_part_file[1] = output BOS file (part)
-skip ${skip3} = skip the event after event number (=skip3)
-n $evt3 = number of event you want to keep in this part BOS output
run_data_file.A00 = original BOS file.
Kijun
--
---------------------------------------******
Dr. Kijun Park
Jefferson Lab.
Suit 5 Room 12_1/F239
12000 Jefferson Av.
Newport News VA 23606
Phone 757-269-6989
More information about the Frost
mailing list