|
[Sponsors] |
July 1, 2014, 19:24 |
"Data range too small to render"
|
#1 |
New Member
john m
Join Date: Jun 2014
Posts: 1
Rep Power: 0 |
Hello everyone,
First post here. I'm currently trying to compare two different mesh solution output files in ParaView 4.1.0 Linux64bit. I'm getting an strange error that doesn't make much sense and I think may have something to do with my settings. I have a data range for the following variables to be rendered. File_1: disp_Magnitude: [0,.100] disp_x: [-0.001,0.001] disp_y: [-2e-5, 2e-5] disp_z: [-0.10, 2e-6] File_2: disp_Magnitude: [0,.100] disp_x: [-0.002,0.002] disp_y: [-8e-6,0.001] disp_z: [-0.10,0.0110] File_2 seems to be able to be rendered fine in ParaView but File_1 is giving me troubles. It says "Data range too small to render" in the corner Mapping Data section. I have another program(a simple gui with my solver) that can open these types of files(Exodus II .e format) and all is fine(no errors, the data is there) for both File_1 and File_2. Does anyone know what might be going on here? I'm completely lost. I can share the files if anyone wants to see. EDIT: A couple things I've tried -For File_1 I tried to set a log scale for the color map transfer function and got this error: " Warning: Range [0,0.100038] invalid for log scaling. Changing to [0.0100038,0.100038]." So I know that the program sees the correct data range. -I've also looked in the information tab for my exodus object in ParaView. It says my data ranges for all of the variables are type double [0,0] but this is absolutely wrong since I can open the same file in my gui and view the mesh with the correct data ranges for each of these variables. I also think the error for log scale conflicts this statement. Why does the information tab say [0,0] but log scale reads a range of [0,0.1]? -If I open File_1 and then open File_2 in this order I get the same error for File_2 that I get for File_1. Then if I change my disp_Mag variable to disp_X the problem ceases for File_2 Thanks. Last edited by mangj; July 2, 2014 at 02:58. Reason: Another issue I put in is actually something different. |
|
Tags |
bugs, color map, paraview |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[General] Extracting ParaView Data into Python Arrays | Jeffzda | ParaView | 30 | November 6, 2023 22:00 |
Experimental data for validation of a 2D conv-div nozzle in mach range 0.2-2.0 | DDikeshorn | Main CFD Forum | 0 | January 18, 2017 05:56 |
[OpenFOAM] Paraview doesn't seem to be picking up data generated by icofoam | MikeHersee | ParaView | 2 | January 6, 2015 09:27 |
Problem in running ICEM grid in Openfoam | Tarak | OpenFOAM | 6 | September 9, 2011 18:51 |
[OpenFOAM] Automatic range in paraview animations | arno | ParaView | 1 | August 29, 2006 05:00 |