Ignore:
Timestamp:
Jun 8, 2017 1:27:07 PM (5 years ago)
Author:
srkline
Message:

Significant changes to the base READ of individual data fields from data files. Now, if the field requested is from a WORK file, and it does not exist, an error condition is returned (or a null wave). Calling procedures are responsible for handling errors. This prevents a string of open file dialogs if fields are missing from a file if they were never in the file to begin with (like sensor logs, polarization hardware, etc.)

New get/write calls were added for the updated temperature sensor fields.

group_ID is now only in the sample block, not the duplicated in the reduction block, and is correctly a number not a string.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • sans/Dev/trunk/NCNR_User_Procedures/Reduction/VSANS/V_DetectorCorrections.ipf

    r1041 r1044  
    2828// 
    2929// TODO 
    30 // -- verify the direction of the tubes and indexing 
     30// x- verify the direction of the tubes and indexing 
    3131// x- decide on the appropriate functional form for the tubes 
    3232// x- need count time as input 
    33 // -- be sure I'm working in the right data folder 
    34 // -- clean up when done 
    35 // -- calculate + return the error contribution? 
    36 // -- verify the error propagation 
     33// x- be sure I'm working in the right data folder (all waves are passed in) 
     34// x- clean up when done 
     35// x- calculate + return the error contribution? 
     36// x- verify the error propagation 
    3737Function V_DeadTimeCorrectionTubes(dataW,data_errW,dtW,ctTime) 
    3838        Wave dataW,data_errW,dtW 
     
    111111// TODO 
    112112// -- UNITS!!!! currently this is mm, which certainly doesn't match anything else!!! 
    113 // -- verify the direction of the tubes and indexing 
    114 // -- be sure I'm working in the right data folder 
    115 // -- clean up when done 
    116 // -- calculate + return the error contribution? 
    117 // -- do I want this to return a wave? 
    118 // -- do I need to write a separate function that returns the distance wave for later calculations? 
    119 // -- do I want to make the distance array 3D to keep the x and y dims together? Calculate them all right now? 
    120 // -- what else do I need to pass to the function? (fname=folder? detStr?) 
    121 // -- need a separate block or function to handle "B" detector which will be ? different 
     113// x- verify the direction of the tubes and indexing 
     114// x- be sure I'm working in the right data folder (it is passed in, and the full path is used) 
     115// x- clean up when done 
     116// x- calculate + return the error contribution? (there is none for this operation) 
     117// x- do I want this to return a wave? (no, default names are generated) 
     118// x- do I need to write a separate function that returns the distance wave for later calculations? 
     119// x- do I want to make the distance array 3D to keep the x and y dims together? Calculate them all right now? 
     120// x- what else do I need to pass to the function? (fname=folder? detStr?) 
     121// y- (yes,see below) need a separate block or function to handle "B" detector which will be ? different 
    122122// 
    123123// 
     
    269269// -- verify where this needs to be done (if the beam center is changed) 
    270270// -- then the q-calculation needs to be re-done 
    271 // -- the position along the tube length is referenced to tube[0], for no particular reason 
    272 //    It may be better to take an average? but [0] is an ASSUMPTION 
    273 // -- distance along tube is simple interpolation 
    274 // 
    275 // -- distance in the lateral direction is based on tube width, which is well known 
     271// 
     272// -- not much is known about the "B" detector, so this 
     273//    all hinges on the non-linear corrections being done correctly for that detector 
    276274// 
    277275// 
Note: See TracChangeset for help on using the changeset viewer.