ged_progs
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| ged_progs [2023/10/10 15:22] – admin | ged_progs [2023/10/12 10:34] (current) – [Other functions] admin | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| In principle there is only one ged program user needs to know: **ged**, an IDL function that acts as a front end for the other ged programs. The other functions are called automatically as needed based on the requested data type and prosessing parameter (IDL keyword) settings. However, an effective use of the system at its current state requires also some knowledge of what happens ' | In principle there is only one ged program user needs to know: **ged**, an IDL function that acts as a front end for the other ged programs. The other functions are called automatically as needed based on the requested data type and prosessing parameter (IDL keyword) settings. However, an effective use of the system at its current state requires also some knowledge of what happens ' | ||
| - | Edit Section | ||
| - | Top level function | ||
| * [[GEDfunction|ged]] | * [[GEDfunction|ged]] | ||
| Line 34: | Line 32: | ||
| * Energy integration of LED direction spectra: [[Eint_leddir]] | * Energy integration of LED direction spectra: [[Eint_leddir]] | ||
| - | * Date-time to LOBT (TAI): [[date2lobt]] | + | * Date-time to LOBT (TAI, integer): [[date2lobt]] |
| + | * Date-time to LOBT (TAI, double): [[date2lobt2]] | ||
| * LOBT (TAI) to date-time: [[lobt2date]] | * LOBT (TAI) to date-time: [[lobt2date]] | ||
ged_progs.1696940542.txt.gz · Last modified: 2023/10/10 15:22 by admin