.:chronfiles:home: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Chronological Files (*.chron)= ==Creating== fix_times.py") |
No edit summary |
||
| Line 1: | Line 1: | ||
=Chronological Files (*.chron)= | =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== | ==Creating== | ||
fix_times.py | The fix_times.py script can be used to create a chronological file. 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 can be ignored and/or deleted. | |||
Revision as of 20:05, 2 June 2017
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. 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 can be ignored and/or deleted.