When that happens, IDL will attempt to make an informed guess as to which float number yourĭata should have been, but doing so is not technically part of the IEEE standard, so it raises the Program caused arithmetic error: Floating illegal operand error. If you inadvertently encounter the end of theįile, there's a high chance that some of the data read from the file won't fit nicely into a float32. Not all 32-bit series of 1s and 0s make a valid IEEE float32 (the "float" values used in IDL and most other languages). IDL is expecting to read in 41 32-bit float values, but some or all of the values it reads in are not The illegal floating point operation is probably not from not(eof(1)) but from readf, 1, line or carried over from another portion of the code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |