Written by Wendy Sweet Updated on July 22, 1996 Updated on October 25, 1996 jjg Updated on January 15, 1997 wds Updated on Dec 04,97 kes Updated on June 30, 1998 wds Updated on Nov 23, 1998 ps Updated on Jan 22, 1999 ps How to do process ipf (instrument packet files) How to turn real time raw data into readable packets: ----------------------------------------------------- For uvs and euv binary packets, do the following: (1) First, compile program IDL> .run torus1:[gll_raw.software.ipf_proc]ipf_rt_proc.pro (2) Next, run the program IDL> do_rt Unless specified, these will go to the current directory. It will be easier to set the directory to diskk:[gll_raw.lrsp.(uvs or euv)] before running these programs. NOTE: This program is dependent on predicted packet times. This information is stored the files DISKK:[ORBIT_DESIGN.or.SEF_PRODUCTS](OR)_PKT_TIMES.* where (OR) is the orbit number, i.e. G1,G2,C3,..C10. These files are created by DISKH:[GLLSEQ.SOFTWARE](uvs or euv)_PACKET_TIMES.PRO For aacs binary packets, do the following: (1) First, compile the program IDL> .run torus1:[gll_raw.software.ipf_proc]ifp_aacs_proc.pro (2) Next, run the program IDL> do_aacs How to turn playback raw data into readable packets: ---------------------------------------------------- (1) First, compile program IDL> .run torus1:[gll_raw.software.ipf_proc]ipf_pb_proc.pro (2) Next, run the program IDL> do_pb How to make listing for both real time and playback packets: ------------------------------------------------------------ This list is helpful for knowing when packets start and end. The input file is raw data, not the .dat file. (1) First, compile program IDL> .run torus1:[gll_raw.software.ipf_proc]ipf_list.pro (2) Next, run the program IDL> do_list Both the UVS and EUV list should be put in the notebook with the predict packet times files. How to look at euv and uvs real time data: ------------------------------------------ Note: The rest of the programs use the reformated .dat files. UVS: ---- (1) First, compile program IDL> .run torus1:[gll_raw.software]read_uvs_records.pro (2) Next, run the program IDL> read_uvs (3) The program will give several options. For the notebook, the user should print the plots and the engineering list. (4) For more information on this program, look at the document torus1:[gll_raw.software]read_uvs_records.doc This program will rewrite the data packet file to add several header values. NOTE: This program is dependent on the packet time predicts file, as well as the contents of DISKH:[GLLSEQ.HISTORY]CMD_ARCHIVE.LIS EUV: ---- (1) First, compile the program IDL> .run torus1:[gll_raw.software]read_euv_records.pro (2) Next, run the program IDL> read_euv (3) The program will give several options. For the notebook the user should print the engineering list, euv_plot_phase2.pro plots, and the counts per integration plot. (4) For more information on this program, read the document torus1:[gll_raw.software]read_euv_records.doc How to look at aacs records: ---------------------------- (1) First, compile the program IDL> .run torus1:[gll_raw.software]read_aacs_records.pro (2) Next, run the program IDL> read_aacs (3) The program will print out a list of header values under the name aacs.lis. (4) For more information on this program, read the document torus1:[gll_raw.software]read_aacs_records.doc How to look at uvs playback records: ------------------------------------ The first 4 steps are now obsolete. (1) First, the file must be spliced together, since the same record might be spread out with several headers. (2) Print the plots. First, compile the program. IDL> .run torus1:[gll_raw.software]plot_uvs_pb.pro (3) Next, run the program IDL> plot_uvs_pb (4) The program will make a postscript file of the plots. For more information on this program, read the document torus1:[gll_raw.software]plot_uvs_pb.doc Check the file to make sure that split records are properly aligned so they may be spliced together. If they are not, the do_pb program must be re-run entering different start times at the proper prompt. Start here (5) Now you are ready to splice the file. IDL> .run torus1:[gll_raw.software]patch_uvs_pb.pro IDL> patch_uvs_pb This program will create a new file with the ending ...2pb.dat (6) Next, compile the program to print out the header values IDL> .run torus1:[gll_raw.software]read_uvs_pb.pro (7) Next, run the program IDL> read_uvs_pb Remember to give the program the *2pb.dat file. (8) The program will print out a list of header values under the name uvs_pb.lis. (9) For more information on this program, read the document torus1:[gll_raw.software]read_uvs_pb.doc (10)How to make a graph of the total counts for each channel and graph of the engineering values. First, compile the program. IDL> .run torus1:[gll_raw.software]upb_eng_plot.pro (11) Next, run the program IDL> do_plot How to delete certain packets from PB data (Nov 23, 1998 ps) ------------------------------------------ It may be desired to delete certain packets from a UPB data file. This can occur when the FOV off-planet packets have been intentionally edited out of the observation. In this case, the patch_uvs_pb program will fill in these intentional gaps, and the uvs_pb.lis file will flag the gaps as missing packets. To eliminate these intentional gaps from the data file, run the program TORUS1:[GLL_RAW.SOFTWARE]DELETE_PB_PKTS.PRO which will rewrite the data file excluding the intentional gaps. Then the uvs_pb.lis can be recreated and will no longer flag the intentional gaps. (1) First create the uvs_pb.lis file from the original UPB data file. The line numbers for the packets will be used as input to DELETE_PB_PKTS.PRO. (2) Compile and run DELETE_PB_PKTS.PRO. IDL> .r TORUS1:[GLL_RAW.SOFTWARE]DELETE_PB_PKTS.PRO IDL> DELETE_PKTS The program will prompt you for the UPB data file name, the ending packet number, the total number of packets to delete, and the packet numbers to delete (all packet numbers are referenced as the line numbers on the uvs_pb.lis file). The output will be a new data file that excludes the specified packets. (3) Run the read_uvs_pb program on the new data file as shown previously and check that the right packets were deleted in the uvs_pb.lis file. ====================================== Status Listing files and Tube Exposure (see below for updated information) ===================================== Dec 04,97 - kes In the final file directory, GLLUVS2:[GLL_RAW.UVS_P2], there are two list files: UVS_RTS_(ORBIT)_STATUS.LIS and UVS_PB_(ORBIT)_STATUS.LIS To create those files: The rts file holds the uvs_formated_data.lis files for each observation. It can be made with the program TORUS1:[GLL_RAW.SOFTWARE]CREATE_URT_LIST_FILES.PRO where the parameters are CREATE_URT_LIST_FILES.PRO, orbit, observation.lis. Orbit = XX, i.e. G7 observation.lis = file of the observations in time order. This file can be made with the program TORUS1:[GLL_RAW.SOFTWARE]SORTED_UVS_FINAL.PRO where the parameters are SORTED_UVS_FINAL.PRO, search_string, out_put_file_name. search_string = something like glluvs2:[gll_raw.uvs_p2]g07*_urt_*.dat The pb list file holds the uvs_pb.lis files for each oberservation. There is a similar program CREATE_PB_LIST_FILES.PRO, that works in the same way. --------- Jan 22, 1999 ps The above steps are now obsolete. To create the status files, it is only necessary to run the program TORUS1:[GLL_RAW.SOFTWARE]FINAL_STATUS.PRO The program calls the above described routines automatically (minor modifications were required to the above routines to incorporate them together). The user will be prompted for the desired directory and orbit. There are two directory choices depending upon whether the data files are URT/UPB or EUV. The program must be run twice to create status files for both directories. Once the status files are created, the total tube exposure for the orbit can be determined (the following is taken from the HOW_TO_TRACK_TUBE_EXPOSURE help file): At the end of both the UVS_RTS_(ORBIT)_STATUS.LIS and UVS_PB_(ORBIT)_STATUS.LIS files, there is a section called "Orbit total tube exposure." The outputs from "Orbit total tube exposure" section are manually placed in a file called GLLUVS2:[GLL_RAW.UVS_P2]TOTAL_COUNTS_AT_JUPITER.LIS Then the program TORUS1:[GLL_RAW.SOFTWARE]ADD_ORBIT_TOTALS.PRO can be run on TOTAL_COUNTS_AT_JUPITER.LIS to get the total counts at Jupiter. A section called Total Jupiter Counts to Date is appended to TOTAL_COUNTS_AT_JUPITER.LIS. Remember to delete the old "Total Jupiter Counts to Date" section before running ADD_ORBIT_TOTALS.PRO.