Space Research Laboratory

User Tools

Site Tools

Trace: • ged_examples
ged_examples

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
ged_examples [2023/10/10 15:43] – adminged_examples [2023/10/11 14:49] (current) – admin
Line 4: Line 4:
  
 When using ged to read ERNE data, the type of data and the associated reader function is determined based on the data file name (or the name of the first file in a file name array). Some reader functions can process the data based on keywords. The set of acknowledged keywords are typically specific to the reader function in question, so in order to find what options are available, the user should consult the documentation of the reader function associated with the desired data type. The functions for each data type can be found in the quick reference tables on the [[ged_docs|main page]]. When using ged to read ERNE data, the type of data and the associated reader function is determined based on the data file name (or the name of the first file in a file name array). Some reader functions can process the data based on keywords. The set of acknowledged keywords are typically specific to the reader function in question, so in order to find what options are available, the user should consult the documentation of the reader function associated with the desired data type. The functions for each data type can be found in the quick reference tables on the [[ged_docs|main page]].
 +
 +(hr)
  
 ==== Empty keyword list ==== ==== Empty keyword list ====
Line 17: Line 19:
 If FILENAMES keyword is not set, [[GEDfunction|ged]] will call [[Datafilename|datafilename]] function which will open a Graphical User Interface (GUI) window to let user interactively select the desired files. The result **mydata** will be an array of file records. Level-2 pulse height data are exceptions, as the reader output record structure is slightly modified from the one used in the input disk files (see the quick reference table on the [[ged_docs|main page]]). If FILENAMES keyword is not set, [[GEDfunction|ged]] will call [[Datafilename|datafilename]] function which will open a Graphical User Interface (GUI) window to let user interactively select the desired files. The result **mydata** will be an array of file records. Level-2 pulse height data are exceptions, as the reader output record structure is slightly modified from the one used in the input disk files (see the quick reference table on the [[ged_docs|main page]]).
  
 +
 +(hr)
  
 ==== Keywords for DATAFILENAME ==== ==== Keywords for DATAFILENAME ====
Line 59: Line 63:
  
 will silently read ten days of onboard spectra records (structure type 'TobSpectra_a') into **mydata** array. will silently read ten days of onboard spectra records (structure type 'TobSpectra_a') into **mydata** array.
 +
 +(hr)
  
 ==== Keywords for GED ==== ==== Keywords for GED ====
Line 74: Line 80:
  
 The other **ged** keywords are more or less technical, and are intended to be used in some special situations.  The other **ged** keywords are more or less technical, and are intended to be used in some special situations. 
 +
 +(hr)
  
 ==== Onboard Spectra ==== ==== Onboard Spectra ====
Line 90: Line 98:
  
 === Example-7 === === Example-7 ===
 +
 +Let's assume we have prepared an energy channel selector table chsel using the guidelines for the appropriate filter function (which as discussed above, depends on the data format).
  
 <code> <code>
 +IDL> mydata = ged(G3SPE_DT=15*60.0, G3SPE_ECUST=chsel, G3SPE_EINFO=info)
 </code> </code>
  
 This will call [[Datafilename|datafilename]] for interactive file selection and assuming we select level-3 spectra as the data type, we will get an time integrated spectra with 15 minute binning and custom energy channels. The behaviour is unpredictable if we happened to choose some other data type for which the keywords have no meaning (in some cases the keywords are ignored in other cases the call will fail). This will call [[Datafilename|datafilename]] for interactive file selection and assuming we select level-3 spectra as the data type, we will get an time integrated spectra with 15 minute binning and custom energy channels. The behaviour is unpredictable if we happened to choose some other data type for which the keywords have no meaning (in some cases the keywords are ignored in other cases the call will fail).
 +
 +(hr)
  
 ==== Pulse Height Data ==== ==== Pulse Height Data ====
Line 123: Line 136:
 The record type of **mydata** array will be [[ThedPartData_a]] and the structure of **amps** will be [[ThedAmpParams_a]].  The record type of **mydata** array will be [[ThedPartData_a]] and the structure of **amps** will be [[ThedAmpParams_a]]. 
  
 +
 +(hr)
  
 ==== LED Direction Spectra ==== ==== LED Direction Spectra ====
ged_examples.1696941820.txt.gz · Last modified: 2023/10/10 15:43 by admin