| View Issue Details [ Jump to Notes ] | [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0009870 | ParaView | Bug | public | 2009-11-09 11:22 | 2011-01-13 17:00 |
|
| Reporter | Ken Moreland | |
| Assigned To | Ken Moreland | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | 3.8 | Fixed in Version | | |
|
| Summary | 0009870: CSV reader does not detect columns with non-finite numbers as numeric |
| Description | When reading in CSV files, columns with integers and floating point numbers are automatically detected and converted to numeric values so that they may be processed. However, this detection breaks down if the column has non-finite values like NaN (not a number) or INF (infinity). These numbers should be considered floating point values and read in as such. |
| Additional Information | This problem has recently become much more serious as the ParaView probe filter now writes out nan's whenever sampling a point outside the mesh or whenever a field is not available. The easiest way to replicate the problem is to use the Plot Over Line filter when the line extends outside of the mesh (which is usually done by simply hitting one of the Axis buttons. (This is how the attached example file was created.) Save out the CSV and note that nan values are written out in the field columns. Read the CSV file back in and see that the field values are now stored in strings. |
| Tags | No tags attached. |
|
| Project | |
| Topic Name | |
| Type | |
|
| Attached Files |  nancolumn.csv [^] (2,492 bytes) 2009-11-09 11:22 |
|