![]() Subroutine output_vtk_rectilinear(KT,KFILE) !M140625a If you search online for "VTK file format", you should find some more information about this, although testing this might be easier. I can't test this right now, but as I mentioned a few lines above, you can also try using "double" or "float64" instead of "float" for the arrays in the VTK file. that's sounds like an issue related to numerical precision, probably related to using "float" instead of "double" or "float64" in the VTK file format.Īlthough it's a bit strange, because the smallest value for float should be 10e-38, if I'm not mistaken. I wonder if there are any local setting in Paraview that can change the data range limits? ![]() This fixed the issue, with the solution being displayed at all times without error messages. I put a check in my code for underflow conditions and rounded them off to 0. I had a feeling that the underflow conditions maybe be triggering problems while reading. However, I noticed that some of the stored solution values were as small as 10.e-34. If it's the situation #2, then you might try the trick that works on Linux, by running ParaView like this: If the files are in ASCII, then try opening them with a text editor and look for one or more of the occurrences above. For example, if a value "1.0002" is stored as "1,0002" or even perhaps "1.0002ES 000" (just a possibility).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |