.:chronfiles:home: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Shawnwagner (talk | contribs) No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 4: | Line 4: | ||
==Creating== | ==Creating== | ||
The fix_times.py script can be used to create a chronological file. The command syntax is: | The fix_times.py script can be used to create a chronological file (as well as synchronous files). The command syntax is: | ||
fix_times.py in_file | fix_times.py in_file | ||
in_file - any file in UND/NASA ASCII Format | in_file - any file in UND/NASA ASCII Format | ||
| Line 12: | Line 12: | ||
Notes: | Notes: | ||
* This program creates multiple files of which only one is truly necessary. The *.mvc and *.chron files can be ignored and/or deleted. | * This program creates multiple files of which only one is truly necessary. The *.mvc and *.chron files that are created can be ignored and/or deleted since the *.sync file is the only truly necessary file. | ||
Latest revision as of 18:21, 28 August 2018
Chronological Files (*.chron)
Chronological files (*.chron) are the next step up from *.raw files because they are always in chronological order, but gaps in time may still exist in the data. These time gaps may break some processing, especially processing involving the use of more than one data acquisition system.
Creating
The fix_times.py script can be used to create a chronological file (as well as synchronous files). The command syntax is:
fix_times.py in_file in_file - any file in UND/NASA ASCII Format
For example:
fix_times.py 15_07_28_20_19_49.nevzorov.raw
Notes:
- This program creates multiple files of which only one is truly necessary. The *.mvc and *.chron files that are created can be ignored and/or deleted since the *.sync file is the only truly necessary file.