TOBIN User's Guide |
Table of ContentsTOBIN User's Guide Abstract Summary Particulars Examples Note about DAF and DAS Run-Time Binary File Format Translation Appendix A --- Revision History 2017 MAR 23 by N. J. Bachman 2002 DEC 06 by B. V. Semenov. TOBIN User's Guide
Abstract
Summary
Particulars
If only the name of the input transfer file is provided on the command line, TOBIN will generate a name for the output binary kernel file that has the same base name as the input transfer file and an appropriate filename extension, based on the filename extension of the transfer file. If TOBIN does not recognize the filename extension of the input transfer file, or there is no filename extension on the input transfer file, a filename extension of '.bin' will be used as the filename extension of the output binary file. If a file having the same name as the output file already exists, TOBIN signals an error and stops. We assume that it is bad form to overwrite or replace an existing file. TOBIN recognizes the transfer filename extensions ``.xc'', ``.xee'', ``.xpc'', and ``.xsp'' associated with transfer files for SPICE data products. These are converted to the SPICE binary kernel filename extensions ``.bc'', ``.bee'', ``.bpc'', and ``.bsp,'' respectively. Also recognized are the old transfer file extensions ``.tc'', ``.tee'', ``.tpc'', and ``.tsp,'' which are converted into the appropriate filename extensions for a binary kernel file. Examples
prompt > tobin thisfile.xspand
prompt > tobin thisfile.xsp thisfile.bspwould both produce the file `thisfile.bsp' in the current directory. In the first example, the name for the binary file produced is derived from the name of the transfer file, using the full base name and replacing the letter `x' in the file name extension with the letter `b', to indicate that the file is a binary file. In the second example, the name for the binary file produced is taken directly from the command line.
> tobin ephem.xsp
> tobin ephem.xsp myephem.bsp
> tobin mydata.ttt
Note about DAF and DAS Run-Time Binary File Format Translation
Starting with the N0066 release of the SPICE Toolkit (April, 2017), SPICE performs run-time translation of non-native binary DAS files. Both DAF and DAS files having big-endian IEEE format can be read on platforms using the little-endian IEEE format, and vice versa. Refer to the Convert User's Guide (convert.ug) to see if using transfer format files is indeed necessary in your data exchange path. Appendix A --- Revision History2017 MAR 23 by N. J. Bachman
2002 DEC 06 by B. V. Semenov.
|