---++ The Pipeline Here is the description of the pipeline that can be found at ~ccohalan/wtl_timestream_pipeline. The convention I use below, at my fake IDL prompt (IDL>), is that italics mean input something, and a regular font means just type that in. Of course keywords are always optional, so I justt put them regular font.

• The Main Program, which envokes many of the small bits:
  • standardize_output.pro takes in the .ac, .dc, and .fits file and spits out a .data file which is described at StandardFile.
    • IDL> standardize_output, mbfits_file = inut mbfits file_*.fits*, _ac and dc input file name, no .extension, output file name, standard_array, frac_err= #, sample_size= #, version_no=version #, glitch_flag
    • NOTE :
      • The mbfits file is a keyword, because there may not be one. This may change with Yoshi's rebinning code, but we'll see.
      • The glitch_flag is probably just there temporarily, as I play with the glitches.

• The Programs in the Pipeline:
  • file_io/read_raw_data.pro creates 3 data arrays (ac_array, dc_array, fits_array)
    • IDL> read_raw_data, fits___file_*.fits*, _ac dc file, ac_array, dc_array, fits_array
  • file_io/read_raw_wo_mbfits.pro creates similar arrays when no mbfits is present
    • IDL> read_raw_wo_mbfits, acdc input, ac_array, dc_array, fits_array, version_no = version #
    • NOTE : The nMJD (second column of fits array) is screwed up. The problem is that a double is not big enough. If you want to plot wrt time, I suggest time_sec = lindgen(#lines) * rate (in our case 200Hz)
  • file_io/create_flags.pro simply creates 3 empty flags with the right dimensions.
    • IDL> create_flags, fits_array, squid_demod_flag, telesc_flag, glitch_flag,
  • timestream_processing/calc_velacc.pro calculates the velocity and acceleration of the telescope.
    • IDL> calc_velacc, fits_array, data_array
  • timestream_processing/calc_squid_demod_flag.pro --->*To be modified for efficacity*
    • IDL> calc_squid_demod_flag, data_array, squid_demod_flag, ac_array, dc_array, fits_array
  • timestream_processing/calc_telesc_flag.pro yep, calculates the telescope flags
    • IDL> calc_telesc_flag, data_array, telesc_flag, frac_err = #, sample_size = #
  • file_io/create_standard_array.pro creates an array which you can play around with.
    • IDL> create_standard_array, data_array, telesc_flag, standad_array, bolo_data
  • file_io/write_standard_data.pro
    • IDL> write_standard_data, standard_array, filename out .data

• Other programs not currently used in standardize_data but which are in the directory:
  • timestream_processing/center_on_zero.pro centers each bolometer's signal to zero.
    • IDL> center_on_zero, standard_array, centered_array
  • timestream_plotting/plot_telesc_flag.pro yep...
    • IDL> plot_telesc_flag, telesc_flag, data_array, plot_to_file= name of file .ps
  • timestream_plotting/plot_all_channels.pro plots all of the bolo columns of the file given
    • IDL> plot_all_channels, version_no = #, centered_array, ps_filename
    • NOTE The version number is there until the problem regarding the nMJD for runs with no mbfits file is solved.

• The Glitch Finders: So far, only one type of glitch can more or less be successfully found. It's the type which appears in Run 405, and that rings. The flags raised need to be improved, since they do not cover the full glitch. See ~ccohalan/plots/405-zoom_glitch.ps.
  • timestream_processing/glitch_finder2.pro --> glitch_finder1 was not very succesful. This name will be changed eventually, when other glitch finders come along (looking for other glitches).
  • IDL> glitch_finder2, standard_array, glitch_flag.

-- ClaireCohalan - 02 Jun 2006

---

This topic: Main > TWikiUsers > ClaireCohalan > PipelineElements Topic revision: r1 - 2006-06-02 - ClaireCohalan

---