11/27/2023 0 Comments Old fashion nasa pcThis file containsįor all usage examples, we will assume an IBM PC or compatibleĬomputer with a CDROM mounted as drive D:Įxtract an ephemeris data file for orbit 291 to the file "mydata.asc" VALID: PULSE, SPIN, EPHEM, LOGISTIC, SEL_ROLL, ATTITUDE,Ĭolfile: An ASCII file containing a list of column (numbers) to beĮxtracted from the "ephemeris" dataset. VALID: sun, SUN, IBM, HP, MSB (MicroSoft DOS), PC (IBM DOS) Host: The type of host system you are working on. Infile: The complete name including path to the input data file.Īscfile: The name of the output file or "-" for output-to-screen. All options to the program are givenĪt run-time in the same command that executes the program. System description text on the CD-ROM for definitions of these coordinate Output the matrix which rotates from Inertial SpacecraftĬoordinates to Venus Solar Orbital coordinates. To the basic 6 files, this program can extract data identical to theĮphemeris dataset submitted by the Magnetometer instrument team or it can The screen or output data to an ASCII file on the local system. This program can extract any of these files and either display the data to Pulse time, spin period, selected roll reference, attitude, and ephemeris). The original PVO SEDR tapes contained 6 files per orbit (logical header, "-traditional" option or the sun C compiler version 3.1. The program is written in the C programming languageĪnd will compile using either the Gnu C Compiler (2.3) with the The sedr2asc program is used to extract data from the PDS Archive CD-ROM'sĬontaining the Pioneer Venus Orbiter (PVO) Supplemental Experimenter Data To run these games, you will need to disable FPU emulation (fpu=false) to force the QBasic/TurboBasic runtime to use software emulation instead. There are such DOS games written that check their file size using a floating point compare that will fail in this manner. It is known at this time that this lack of precision is enough to cause otherwise straightforward comparisons against integers to fail in DOS applications originally written in QBasic or Turbo Basic. This slight loss of precision is perfectly fine considering DOSBox's original goal in supporting DOS games, but may cause problems in other cases that need the full precision. The Intel FPU registers are 80-bit "extended precision" floating point values, not 64-bit double precision, so this is effectively 12 bits of precision loss and 5 bits of range loss (64 to 53 mantissa bits and 16 to 11 exponent bits). Unless using the dynamic core, DOSBox and DOSBox-X emulate the FPU registers using the "double" 64-bit floating point data type.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |