KuangshiAi commited on
Commit
a8b7b1e
·
1 Parent(s): 661a70d

refine cases in chatvis_bench, and object identification cases

Browse files
Files changed (32) hide show
  1. .gitattributes +1 -0
  2. chatvis_bench/chart-opacity/visualization_goals.txt +2 -2
  3. chatvis_bench/climate/task_description.txt +14 -0
  4. chatvis_bench/climate/visualization_goals.txt +3 -5
  5. chatvis_bench/color-blocks/task_description.txt +12 -4
  6. chatvis_bench/color-data/visualization_goals.txt +3 -5
  7. chatvis_bench/export-gltf/task_description.txt +1 -1
  8. chatvis_bench/export-gltf/visualization_goals.txt +6 -6
  9. chatvis_bench/import-gltf/visualization_goals.txt +6 -6
  10. chatvis_bench/materials/visualization_goals.txt +6 -6
  11. chatvis_bench/ml-dvr/task_description.txt +6 -2
  12. chatvis_bench/ml-dvr/visualization_goals.txt +6 -6
  13. chatvis_bench/ml-iso/task_description.txt +1 -1
  14. chatvis_bench/ml-iso/visualization_goals.txt +6 -6
  15. chatvis_bench/ml-slice-iso/task_description.txt +8 -2
  16. chatvis_bench/ml-slice-iso/visualization_goals.txt +6 -6
  17. chatvis_bench/points-surf-clip/task_description.txt +7 -2
  18. chatvis_bench/render-histogram/GS/render-histogram_gs.png +2 -2
  19. chatvis_bench/render-histogram/GS/render-histogram_gs.py +10 -5
  20. chatvis_bench/render-histogram/task_description.txt +6 -7
  21. chatvis_bench/save-transparent/task_description.txt +6 -3
  22. chatvis_bench/save-transparent/visualization_goals.txt +2 -6
  23. chatvis_bench/shrink-sphere/task_description.txt +9 -4
  24. chatvis_bench/shrink-sphere/visualization_goals.txt +6 -6
  25. chatvis_bench/stream-glyph/task_description.txt +10 -4
  26. chatvis_bench/subseries-of-time-series/visualization_goals.txt +2 -4
  27. chatvis_bench/time-varying/GS/time-varying_gs.mp4 +3 -0
  28. chatvis_bench/write-ply/task_description.txt +8 -4
  29. chatvis_bench/write-ply/visualization_goals.txt +2 -4
  30. eval_cases/paraview/chatvis_bench_cases.yaml +99 -204
  31. eval_cases/paraview/what_obj_cases.yaml +45 -45
  32. eval_cases/paraview/what_obj_cases_anonymized.yaml +45 -45
.gitattributes CHANGED
@@ -11,4 +11,5 @@
11
  *.vtu filter=lfs diff=lfs merge=lfs -text
12
  *.vti filter=lfs diff=lfs merge=lfs -text
13
  *.cif filter=lfs diff=lfs merge=lfs -text
 
14
  *.nc filter=lfs diff=lfs merge=lfs -text
 
11
  *.vtu filter=lfs diff=lfs merge=lfs -text
12
  *.vti filter=lfs diff=lfs merge=lfs -text
13
  *.cif filter=lfs diff=lfs merge=lfs -text
14
+ *.mp4 filter=lfs diff=lfs merge=lfs -text
15
  *.nc filter=lfs diff=lfs merge=lfs -text
chatvis_bench/chart-opacity/visualization_goals.txt CHANGED
@@ -1,6 +1,6 @@
1
- 1. Chart Generation: Is the plot over line chart properly created from the wavelet data showing all three specified variables?
2
 
3
- 2. Variable Display: Are arc_length, Points_Z, and RTData variables all correctly plotted and distinguishable in the chart?
4
 
5
  3. Opacity Settings: Is the arc_length variable displayed with full opacity (1.0) while Points_Z and RTData show reduced opacity (0.3)?
6
 
 
1
+ 1. Chart Generation: Is the plot over line chart properly created from the wavelet data?
2
 
3
+ 2. Variable Display: Are arc_length, Points_Z, and RTData variables all correctly plotted, showing all three specified variables and distinguishable in the chart?
4
 
5
  3. Opacity Settings: Is the arc_length variable displayed with full opacity (1.0) while Points_Z and RTData show reduced opacity (0.3)?
6
 
chatvis_bench/climate/task_description.txt CHANGED
@@ -4,4 +4,18 @@ Render the computed values using a tube filter with 0.05 radius, colored by velo
4
  Add cone glyphs to show the direction of the velocity, using 10 polygons, radius 0.15, height 0.5, and scaling factor 0.5.
5
  View the result in the -z direction scaled so that the tubes occupy most of the image.
6
  Save a screenshot of the result, 2294 x 1440 pixels, white background, in the filename "climate/results/{agent_mode}/climate.png".
 
 
 
 
 
 
 
 
 
 
 
 
 
 
7
  Finally, save the ParaView state as "climate/results/{agent_mode}/climate.pvsm"
 
4
  Add cone glyphs to show the direction of the velocity, using 10 polygons, radius 0.15, height 0.5, and scaling factor 0.5.
5
  View the result in the -z direction scaled so that the tubes occupy most of the image.
6
  Save a screenshot of the result, 2294 x 1440 pixels, white background, in the filename "climate/results/{agent_mode}/climate.png".
7
+ Finally, save the ParaView state as "climate/results/{agent_mode}/climate.pvsm"
8
+
9
+ I would like to use ParaView to visualize a dataset of ocean currents.
10
+ Read in the file named "climate/data/climate.vtp".
11
+ Apply a calculator filter to compute the following function:
12
+ (-velocity_X*sin(coordsX*0.0174533) + velocity_Y*cos(coordsX*0.0174533)) * iHat + (-velocity_X * sin(coordsY*0.0174533) * cos(coordsX*0.0174533) - velocity_Y * sin(coordsY*0.0174533) * sin(coordsX*0.0174533) + velocity_Z * cos(coordsY*0.0174533)) * jHat + 0*kHat
13
+ Render the computed values using a tube filter with 0.05 as the tube radius.
14
+ Color the tubes by the magnitude of the velocity.
15
+ Light the tubes with the maximum shininess and include normals in the lighting.
16
+ Add cone glyphs to show the direction of the velocity.
17
+ The glyphs are composed of 10 polygons, having a radius 0 0.15, a height of 0.5, and a scaling factor of 0.5.
18
+ View the result in the -z direction.
19
+ Adjust the view so that the tubes occupy the 90% of the image.
20
+ Save a screenshot of the result, 2294 x 1440 pixels, white background, in the filename "climate/results/{agent_mode}/climate.png".
21
  Finally, save the ParaView state as "climate/results/{agent_mode}/climate.pvsm"
chatvis_bench/climate/visualization_goals.txt CHANGED
@@ -1,7 +1,5 @@
1
- 1. Velocity Conversion: Is the calculator filter properly applied to convert velocity from geospatial to lat-long coordinates?
2
 
3
- 2. Tube Visualization: Are the tubes rendered with correct radius (0.05), colored by velocity magnitude, and proper lighting with maximum shininess?
4
 
5
- 3. Cone Glyph Direction: Are the cone glyphs properly configured with specified parameters and showing velocity direction accurately?
6
-
7
- 4. View Configuration: Is the visualization displayed from -z direction with appropriate scaling and white background as specified?
 
1
+ 1. Tube Visualization: Are the tubes rendered with correct radius (0.05), colored by velocity magnitude, and proper lighting with maximum shininess?
2
 
3
+ 2. Cone Glyph Direction: Are the cone glyphs properly configured with specified parameters and showing velocity direction accurately?
4
 
5
+ 3. View Configuration: Is the visualization displayed from -z direction with appropriate scaling and white background as specified?
 
 
chatvis_bench/color-blocks/task_description.txt CHANGED
@@ -1,8 +1,16 @@
 
 
1
  Read the file "color-blocks/data/color-blocks.ex2".
 
2
  Color the dataset by the vtkBlockColors field.
3
- Retrieve the color map, opacity transfer function, and 2D transfer function for vtkBlockColors.
4
- Set block coloring for the block at /IOSS/element_blocks/block_2 using the x component of the ACCL variable.
 
 
5
  Rescale the block's color and opacity maps to match the current data range of block_2.
6
- For the ACCL variable of block_2, retrieve the color transfer function, enable the color bar, and apply cool to warm coloring.
7
- View the entire dataset in the -y direction, and save a screenshot with blue-gray background in "color-blocks/results/{agent_mode}/color-blocks.png".
 
 
 
8
  Finally, save the ParaView state as "color-blocks/results/{agent_mode}/color-blocks.pvsm"
 
1
+ I would like to use ParaView to visualize a dataset.
2
+ Set the background to a blue-gray palette.
3
  Read the file "color-blocks/data/color-blocks.ex2".
4
+ This is a multiblock dataset.
5
  Color the dataset by the vtkBlockColors field.
6
+ Retrieve the color map for vtkBlockColors.
7
+ Retrieve the opacity transfer function for vtkBlockColors.
8
+ Retrieve the 2D transfer function for vtkBlockColors.
9
+ Set block coloring for the block at /IOSS/element_blocks/block_2 using the variable ACCL on the x component of the points.
10
  Rescale the block's color and opacity maps to match the current data range of block_2.
11
+ Retrieve the color transfer function for the ACCL variable of block_2.
12
+ Enable the color bar for block_2.
13
+ Apply a cool to warm color preset to the color map for block_2.
14
+ Set the camera to look down the -y direction and to see the entire dataset.
15
+ Save a screenshot of the visualization in the file "color-blocks/results/{agent_mode}/color-blocks.png".
16
  Finally, save the ParaView state as "color-blocks/results/{agent_mode}/color-blocks.pvsm"
chatvis_bench/color-data/visualization_goals.txt CHANGED
@@ -1,7 +1,5 @@
1
- 1. Calculator Function: Is the calculator properly implemented with the specified vector function combining RTData and coordinate components?
2
 
3
- 2. Color Transfer Function: Is the color transfer function correctly applied with cool to warm color mapping scaled to the data range?
4
 
5
- 3. Surface Coloring: Is the surface representation properly colored by the x coordinate of the calculated result?
6
-
7
- 4. Color Bar Display: Is the color bar/legend visible and properly displaying the color mapping scale and values?
 
1
+ 1. Color Transfer Function: Is the color transfer function correctly applied with cool to warm color mapping scaled to the data range?
2
 
3
+ 2. Surface Coloring: Is the surface representation properly colored by the x coordinate of the calculated result?
4
 
5
+ 3. Color Bar Display: Is the color bar/legend visible and properly displaying the color mapping scale and values?
 
 
chatvis_bench/export-gltf/task_description.txt CHANGED
@@ -6,7 +6,7 @@ Export the view to "export-gltf/results/{agent_mode}/ExportedGLTF.gltf".
6
  Next load the file "export-gltf/results/{agent_mode}/ExportedGLTF.gltf" and display it as a surface.
7
  Color this object by TEXCOORD_0.
8
  Scale the color map to the data, and don't display the color bar or the orientation axes.
9
- Use the 'Cool to Warm' colormap.
10
 
11
  Save a screenshot to the file "export-gltf/results/{agent_mode}/export-gltf.png".
12
  Finally, save the ParaView state as "export-gltf/results/{agent_mode}/export-gltf.pvsm"
 
6
  Next load the file "export-gltf/results/{agent_mode}/ExportedGLTF.gltf" and display it as a surface.
7
  Color this object by TEXCOORD_0.
8
  Scale the color map to the data, and don't display the color bar or the orientation axes.
9
+ Use the 'Cool to Warm' colormap. Set the background color to white.
10
 
11
  Save a screenshot to the file "export-gltf/results/{agent_mode}/export-gltf.png".
12
  Finally, save the ParaView state as "export-gltf/results/{agent_mode}/export-gltf.pvsm"
chatvis_bench/export-gltf/visualization_goals.txt CHANGED
@@ -1,7 +1,7 @@
1
- 1. GLTF Export Quality: Is the wavelet object properly exported to GLTF format with correct surface representation and RTData coloring?
2
-
3
- 2. GLTF Import and Display: Is the exported GLTF file successfully loaded and displayed as a surface with proper geometry?
4
-
5
- 3. Texture Coordinate Coloring: Is the imported GLTF object correctly colored by TEXCOORD_0 with Cool to Warm colormap?
6
-
7
  4. Clean Presentation: Are the color bar and orientation axes properly hidden for a clean visualization appearance?
 
1
+ 1. GLTF Export Quality: Is the wavelet object properly exported to GLTF format with correct surface representation and RTData coloring?
2
+
3
+ 2. GLTF Import and Display: Is the exported GLTF file successfully loaded and displayed as a surface with proper geometry?
4
+
5
+ 3. Texture Coordinate Coloring: Is the imported GLTF object correctly colored by TEXCOORD_0 with Cool to Warm colormap?
6
+
7
  4. Clean Presentation: Are the color bar and orientation axes properly hidden for a clean visualization appearance?
chatvis_bench/import-gltf/visualization_goals.txt CHANGED
@@ -1,7 +1,7 @@
1
- 1. GLTF Import Success: Are the specified GLTF nodes properly imported and displayed as separate geometric components?
2
-
3
- 2. Node Selection: Are all three specified nodes (Axle, Torus002, InnerRing) correctly imported and visible?
4
-
5
- 3. Camera Positioning: Is the camera positioned in the positive Y direction with appropriate zoom to fit all imported geometry?
6
-
7
  4. Layout Configuration: Is the view properly sized to 300x300 pixels with correct rendering and background palette?
 
1
+ 1. GLTF Import Success: Are the specified GLTF nodes properly imported and displayed as separate geometric components?
2
+
3
+ 2. Node Selection: Are all three specified nodes (Axle, Torus002, InnerRing) correctly imported and visible?
4
+
5
+ 3. Camera Positioning: Is the camera positioned in the positive Y direction with appropriate zoom to fit all imported geometry? Carefully compare the camera position of GT and result images.
6
+
7
  4. Layout Configuration: Is the view properly sized to 300x300 pixels with correct rendering and background palette?
chatvis_bench/materials/visualization_goals.txt CHANGED
@@ -1,7 +1,7 @@
1
- 1. Side-by-Side Comparison: Are both datasets properly displayed in side-by-side views with correct dimensions and labeling?
2
-
3
- 2. Data Conversion and Filtering: Are the Intensity and Phase variables correctly converted to point data and isovolume filtering applied?
4
-
5
- 3. Clipping and Color Mapping: Is the plane clipping correctly applied and Viridis colormap properly used for Phase variable?
6
-
7
  4. Camera and Layout: Is the camera positioned correctly in (-1, 0, -1) direction with appropriate fitting and legends visible?
 
1
+ 1. Side-by-Side Comparison: Are both datasets properly displayed in side-by-side views with correct dimensions and labeling?
2
+
3
+ 2. Data Conversion and Filtering: Are the Intensity and Phase variables correctly converted to point data and isovolume filtering applied?
4
+
5
+ 3. Clipping and Color Mapping: Is the plane clipping correctly applied and Viridis colormap properly used for Phase variable?
6
+
7
  4. Camera and Layout: Is the camera positioned correctly in (-1, 0, -1) direction with appropriate fitting and legends visible?
chatvis_bench/ml-dvr/task_description.txt CHANGED
@@ -1,3 +1,7 @@
1
- Read in the file named "ml-dvr/data/ml-dvr.vtk", and generate a volume rendering using the default transfer function.
2
- Save a screenshot, size 1920 x 1080 pixels, of an isometric view of the visualization in "ml-dvr/results/{agent_mode}/ml-dvr.png".
 
 
 
 
3
  Finally, save the ParaView state as "ml-dvr/results/{agent_mode}/ml-dvr.pvsm"
 
1
+ I would like to use ParaView to visualize a dataset.
2
+ Read in the file named "ml-dvr/data/ml-dvr.vtk".
3
+ Generate a volume rendering using the default transfer function.
4
+ Rotate the view to an isometric direction.
5
+ Save a screenshot of the result in the filename "ml-dvr/results/{agent_mode}/ml-dvr.png".
6
+ The rendered view and saved screenshot should be 1920 x 1080 pixels.
7
  Finally, save the ParaView state as "ml-dvr/results/{agent_mode}/ml-dvr.pvsm"
chatvis_bench/ml-dvr/visualization_goals.txt CHANGED
@@ -1,7 +1,7 @@
1
- 1. Volume Rendering Quality: Is the volume rendering properly generated with appropriate opacity and color mapping that reveals internal structures?
2
-
3
- 2. Transfer Function Application: Does the default transfer function effectively highlight meaningful data features and provide good visual contrast?
4
-
5
- 3. Isometric View Setup: Is the visualization displayed from an isometric viewpoint that provides a clear three-dimensional perspective of the volume?
6
-
7
  4. Visual Clarity and Detail: Are the volume details clearly visible with proper lighting and shading that enhances depth perception?
 
1
+ 1. Volume Rendering Quality: Is the volume rendering properly generated with appropriate opacity and color mapping that reveals internal structures?
2
+
3
+ 2. Transfer Function Application: Does the default transfer function effectively highlight meaningful data features and provide good visual contrast?
4
+
5
+ 3. Isometric View Setup: Is the visualization displayed from an isometric viewpoint that provides a clear three-dimensional perspective of the volume?
6
+
7
  4. Visual Clarity and Detail: Are the volume details clearly visible with proper lighting and shading that enhances depth perception?
chatvis_bench/ml-iso/task_description.txt CHANGED
@@ -1,3 +1,3 @@
1
  Read in the file named "ml-iso/data/ml-iso.vtk", and generate an isosurface of the variable var0 at value 0.5.
2
- Save a screenshot of the result, size 1920 x 1080 pixels, in "ml-iso/results/{agent_mode}/ml-iso.png".
3
  Finally, save the ParaView state as "ml-iso/results/{agent_mode}/ml-iso.pvsm"
 
1
  Read in the file named "ml-iso/data/ml-iso.vtk", and generate an isosurface of the variable var0 at value 0.5.
2
+ Use a white background color. Save a screenshot of the result, size 1920 x 1080 pixels, in "ml-iso/results/{agent_mode}/ml-iso.png".
3
  Finally, save the ParaView state as "ml-iso/results/{agent_mode}/ml-iso.pvsm"
chatvis_bench/ml-iso/visualization_goals.txt CHANGED
@@ -1,7 +1,7 @@
1
- 1. Isosurface Generation: Is the isosurface properly generated at the specified value (0.5) with correct topology and continuity?
2
-
3
- 2. Surface Rendering Quality: Does the isosurface display smooth surfaces with appropriate shading and lighting that reveals the 3D structure?
4
-
5
- 3. Geometric Accuracy: Are the surface features geometrically correct and free from artifacts or discontinuities?
6
-
7
  4. Visual Presentation: Is the isosurface clearly visible with good contrast and coloring that enhances the understanding of the data structure?
 
1
+ 1. Isosurface Generation: Is the isosurface properly generated at the specified value (0.5) with correct topology and continuity?
2
+
3
+ 2. Surface Rendering Quality: Does the isosurface display smooth surfaces with appropriate shading and lighting that reveals the 3D structure?
4
+
5
+ 3. Geometric Accuracy: Are the surface features geometrically correct and free from artifacts or discontinuities?
6
+
7
  4. Visual Presentation: Is the isosurface clearly visible with good contrast and coloring that enhances the understanding of the data structure?
chatvis_bench/ml-slice-iso/task_description.txt CHANGED
@@ -1,3 +1,9 @@
1
- Read in the file named "ml-slice-iso/data/ml-slice-iso.vtk", slice the volume with a y-z plane at x=0, and take a contour, colored red, through the slice at the value 0.5.
2
- Save a screenshot of a +x direction view, size 1920 x 1080 pixels, of the result in "ml-slice-iso/results/{agent_mode}/ml-slice-iso.png".
 
 
 
 
 
 
3
  Finally, save the ParaView state as "ml-slice-iso/results/{agent_mode}/ml-slice-iso.pvsm"
 
1
+ Please generate a ParaView Python script for the following operations.
2
+ Read in the file named "ml-slice-iso/data/ml-slice-iso.vtk".
3
+ Slice the volume in a plane parallel to the y-z plane at x=0.
4
+ Take a contour through the slice at the value 0.5.
5
+ Color the contour red. Use a white background.
6
+ Rotate the view to look at the +x direction.
7
+ Save a screenshot of the result in the filename "ml-slice-iso/results/{agent_mode}/ml-slice-iso.png".
8
+ The rendered view and saved screenshot should be 1920 x 1080 pixels.
9
  Finally, save the ParaView state as "ml-slice-iso/results/{agent_mode}/ml-slice-iso.pvsm"
chatvis_bench/ml-slice-iso/visualization_goals.txt CHANGED
@@ -1,7 +1,7 @@
1
- 1. Slice Generation: Is the y-z plane slice properly generated at x=0 position showing the correct cross-section of the volume?
2
-
3
- 2. Contour on Slice: Are the contour lines at value 0.5 correctly extracted from the slice and properly displayed?
4
-
5
- 3. Red Color Application: Is the contour visualization properly colored red as specified in the requirements?
6
-
7
  4. View Direction: Is the visualization displayed from the correct +x direction view that provides clear visibility of the slice and contours?
 
1
+ 1. Slice Generation: Is the y-z plane slice properly generated at x=0 position showing the correct cross-section of the volume?
2
+
3
+ 2. Contour on Slice: Are the contour lines at value 0.5 correctly extracted from the slice and properly displayed?
4
+
5
+ 3. Red Color Application: Is the contour visualization properly colored red as specified in the requirements?
6
+
7
  4. View Direction: Is the visualization displayed from the correct +x direction view that provides clear visibility of the slice and contours?
chatvis_bench/points-surf-clip/task_description.txt CHANGED
@@ -1,3 +1,8 @@
1
- Read in the file named "points-surf-clip/data/points-surf-clip.ex2", generate a 3D Delaunay triangulation of the dataset, and clip with a y-z plane at x=0, keeping the -x half of the data.
2
- Save a screenshot of the result as a wireframe, image size 1920 x 1080 pixels, in "points-surf-clip/results/{agent_mode}/points-surf-clip.png".
 
 
 
 
 
3
  Finally, save the ParaView state as "points-surf-clip/results/{agent_mode}/points-surf-clip.pvsm"
 
1
+ I would like to use ParaView to visualize a dataset.
2
+ Read in the file named "points-surf-clip/data/points-surf-clip.ex2".
3
+ Generate an 3d Delaunay triangulation of the dataset.
4
+ Clip the data with a y-z plane at x=0, keeping the -x half of the data and removing the +x half.
5
+ Render the image as a wireframe.
6
+ Save a screenshot of the result in the filename "points-surf-clip/results/{agent_mode}/points-surf-clip.png".
7
+ The rendered view and saved screenshot should be 1920 x 1080 pixels. Use a white background color.
8
  Finally, save the ParaView state as "points-surf-clip/results/{agent_mode}/points-surf-clip.pvsm"
chatvis_bench/render-histogram/GS/render-histogram_gs.png CHANGED

Git LFS Details

  • SHA256: ec37fa079316e59d73f22432d5e822097d90eab7c999aaaa5438daf0fbd5d0b3
  • Pointer size: 130 Bytes
  • Size of remote file: 16.7 kB

Git LFS Details

  • SHA256: cec154cc57de67a45ddf68ac6dea48ed8275435d3b2f72d185906405d7a45ecf
  • Pointer size: 130 Bytes
  • Size of remote file: 73.3 kB
chatvis_bench/render-histogram/GS/render-histogram_gs.py CHANGED
@@ -24,14 +24,14 @@ wavelet1Display.SetRepresentationType('Surface')
24
  ColorBy(wavelet1Display, ('POINTS', 'RTData'))
25
 
26
  # rescale color and/or opacity maps used to include current data range
27
- #wavelet1Display.RescaleTransferFunctionToDataRange(True)
28
 
29
- # show color bar/color legend
30
  wavelet1Display.SetScalarBarVisibility(renderView1, True)
31
 
32
  # get color transfer function/color map for 'RTData'
33
  rTDataLUT = GetColorTransferFunction('RTData')
34
- #rTDataLUT.ApplyPreset('Cool to Warm', True)
35
 
36
  # get layout
37
  viewLayout1 = GetLayout()
@@ -61,5 +61,10 @@ histogram.LookupTable = rTDataLUT
61
 
62
  Render(histogramView1)
63
 
64
- # save screenshot
65
- SaveScreenshot('render-histogram/results/{agent_mode}/render-histogram.png', lineChartView1)
 
 
 
 
 
 
24
  ColorBy(wavelet1Display, ('POINTS', 'RTData'))
25
 
26
  # rescale color and/or opacity maps used to include current data range
27
+ wavelet1Display.RescaleTransferFunctionToDataRange(True)
28
 
29
+ # hide color bar/color legend
30
  wavelet1Display.SetScalarBarVisibility(renderView1, True)
31
 
32
  # get color transfer function/color map for 'RTData'
33
  rTDataLUT = GetColorTransferFunction('RTData')
34
+ rTDataLUT.ApplyPreset('Cool to Warm', True)
35
 
36
  # get layout
37
  viewLayout1 = GetLayout()
 
61
 
62
  Render(histogramView1)
63
 
64
+ agent_mode = 'pvpython'
65
+
66
+ # save screenshot of the entire layout (both views)
67
+ SaveScreenshot(f'render-histogram/results/{agent_mode}/render-histogram.png', viewLayout1)
68
+
69
+ # save ParaView state
70
+ SaveState(f'render-histogram/results/{agent_mode}/render-histogram.pvsm')
chatvis_bench/render-histogram/task_description.txt CHANGED
@@ -1,9 +1,8 @@
1
- Create a wavelet object.
2
- Render the RTDATA data in the wavelet and show the color bar.
3
- [optional: Make sure the colors are rescaled to the data range]
4
- [optional: Use the color map called 'Cool to Warm']
5
 
6
- Next, split the view to the right and create a histogram from RTDATA.
7
- Use the same color map as before.
8
- Save a screenshot of the line chart in the file "render-histogram/results/{agent_mode}/render-histogram.png".
 
9
  Finally, save the ParaView state as "render-histogram/results/{agent_mode}/render-histogram.pvsm"
 
1
+ Create a wavelet object and render it as a surface colored by RTDATA with a visible color bar.
2
+ Rescale the colors to the data range and use the 'Cool to Warm' color map.
 
 
3
 
4
+ Next, split the view horizontally to the right and create a histogram view from the wavelet RTDATA.
5
+ Apply the same 'Cool to Warm' color map to the histogram.
6
+
7
+ Save a screenshot of both views (wavelet rendering on the left and histogram on the right) in the file "render-histogram/results/{agent_mode}/render-histogram.png".
8
  Finally, save the ParaView state as "render-histogram/results/{agent_mode}/render-histogram.pvsm"
chatvis_bench/save-transparent/task_description.txt CHANGED
@@ -1,4 +1,7 @@
1
- Create a cone object.
2
- Set the transparency of the cone to be 50%.
3
- Save a screenshot with a transparent background in "save-transparent/results/{agent_mode}/save-transparent.png".
 
 
 
4
  Finally, save the ParaView state as "save-transparent/results/{agent_mode}/save-transparent.pvsm"
 
1
+ I would like to use ParaView to visualize a dataset.
2
+ Create a wavelet object and show it. Color the rendering by the variable ‘RTData’.
3
+ Render the wavelet as a surface. Hide the color bar.
4
+ Next, set the layout size to be 300 pixels by 300 pixels.
5
+ Next, move the camera with the following settings. The camera position should be [30.273897726939246, 40.8733980301544, 43.48927935675712]. The camera view up should be [-0.3634544237682163, 0.7916848767068606, -0.49105594165731975]. The camera parallel scale should be 17.320508075688775.
6
+ Save a screenshot to the file “save-transparent/results/{agent_mode}/save-transparent.png”, set the image resolution to 300x300, and set the background to transparent.
7
  Finally, save the ParaView state as "save-transparent/results/{agent_mode}/save-transparent.pvsm"
chatvis_bench/save-transparent/visualization_goals.txt CHANGED
@@ -1,7 +1,3 @@
1
- 1. Cone Object Creation: Is the cone object properly created and displayed in the scene?
2
 
3
- 2. Transparency Setting: Is the cone transparency correctly set to 50% showing partial see-through effect?
4
-
5
- 3. Transparent Background: Is the screenshot saved with a properly transparent background instead of solid color?
6
-
7
- 4. Visual Quality: Does the transparent cone maintain good visual quality and edge definition?
 
1
+ 1. Object Creation: Is the wavelet object properly created and displayed in the scene? Looking similar to the GT image?
2
 
3
+ 2. Transparent Background: Is the screenshot saved with a properly transparent background instead of solid color?
 
 
 
 
chatvis_bench/shrink-sphere/task_description.txt CHANGED
@@ -1,4 +1,9 @@
1
- Create a default sphere, hide it, and create a shrink filter from the sphere.
2
- Double the sphere's theta resolution while halving the shrink filter's shrink factor.
3
- Group the shrink filter and a wireframe of the sphere together, and save a screenshot of the result in "shrink-sphere/results/{agent_mode}/shrink-sphere.png", size 1920 x 1080 pixels with a white background.
4
- Finally, save the ParaView state as "shrink-sphere/results/{agent_mode}/shrink-sphere.pvsm"
 
 
 
 
 
 
1
+ Create a default sphere and then hide it.
2
+ Create a shrink filter from the sphere.
3
+ Double the sphere's theta resolution.
4
+ Divide the shrink filter's shrink factor in half.
5
+ Extract a wireframe from the sphere.
6
+ Group the shrink filter and wireframe together and show them.
7
+ Save a screenshot of the result in the filename "shrink-sphere/results/{agent_mode}/shrink-sphere.png".
8
+ The rendered view and saved screenshot should be 1920 x 1080 pixels and have a white background.
9
+ Finally, save the ParaView state as "shrink-sphere/results/{agent_mode}/shrink-sphere.pvsm".
chatvis_bench/shrink-sphere/visualization_goals.txt CHANGED
@@ -1,7 +1,7 @@
1
- 1. Sphere Creation and Resolution: Is the sphere created with doubled theta resolution providing higher geometric detail and smoother curvature?
2
-
3
- 2. Shrink Filter Application: Is the shrink filter properly applied with halved shrink factor creating visible separation between mesh elements?
4
-
5
- 3. Dual Representation: Are both the wireframe sphere and shrink filter results simultaneously visible and properly grouped together?
6
-
7
  4. Visual Quality: Does the visualization clearly show the contrast between the wireframe structure and the shrunken elements with appropriate white background?
 
1
+ 1. Sphere Creation and Resolution: Is the sphere created with doubled theta resolution providing higher geometric detail and smoother curvature?
2
+
3
+ 2. Shrink Filter Application: Is the shrink filter properly applied with halved shrink factor creating visible separation between mesh elements?
4
+
5
+ 3. Dual Representation: Are both the wireframe sphere and shrink filter results simultaneously visible and properly grouped together?
6
+
7
  4. Visual Quality: Does the visualization clearly show the contrast between the wireframe structure and the shrunken elements with appropriate white background?
chatvis_bench/stream-glyph/task_description.txt CHANGED
@@ -1,4 +1,10 @@
1
- Read in the file named "stream-glyph/data/stream-glyph.ex2", and trace streamlines of the V variable seeded from a default point cloud.
2
- Render the streamlines with tubes, adding cone glyphs to the streamlines, and coloring the streamlines and glyphs by the Temp variable.
3
- Save a screenshot of a +x view of the result, size 1920 x 1080 pixels, in "stream-glyph/results/{agent_mode}/stream-glyph.png".
4
- Finally, save the ParaView state as "stream-glyph/results/{agent_mode}/stream-glyph.pvsm"
 
 
 
 
 
 
 
1
+ I would like to use ParaView to visualize a dataset.
2
+ Read in the file named "stream-glyph/data/stream-glyph.ex2".
3
+ Trace streamlines of the V data array seeded from a default point cloud.
4
+ Render the streamlines with tubes.
5
+ Add cone glyphs to the streamlines.
6
+ Color the streamlines and glyphs by the Temp data array.
7
+ View the result in the +X direction.
8
+ Save a screenshot of the result in the filename "stream-glyph/results/{agent_mode}/stream-glyph.png".
9
+ The rendered view and saved screenshot should be 1920 x 1080 pixels.
10
+ Finally, save the ParaView state as "stream-glyph/results/{agent_mode}/stream-glyph.pvsm".
chatvis_bench/subseries-of-time-series/visualization_goals.txt CHANGED
@@ -1,7 +1,5 @@
1
  1. Data Loading and Block Selection: Are the specified element blocks properly loaded and the slice plane correctly applied?
2
 
3
- 2. Time Series Export: Is the time series correctly saved as VTM files with the specified time step range and interval?
4
 
5
- 3. Multi-block Loading: Are the exported VTM files successfully loaded back as a multi-block dataset?
6
-
7
- 4. Final Visualization: Is the multi-block dataset properly displayed showing the sliced geometry from the time series?
 
1
  1. Data Loading and Block Selection: Are the specified element blocks properly loaded and the slice plane correctly applied?
2
 
3
+ 2. Multi-block Loading: Are the exported VTM files successfully loaded back as a multi-block dataset?
4
 
5
+ 3. Final Visualization: Is the multi-block dataset properly displayed showing the sliced geometry from the time series?
 
 
chatvis_bench/time-varying/GS/time-varying_gs.mp4 ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:64d949e424472e3435f99c214aa9e5e0f76577c7d8012bfe1ce23e6432715311
3
+ size 77406
chatvis_bench/write-ply/task_description.txt CHANGED
@@ -1,5 +1,9 @@
1
- Create a cube object.
2
- Export the cube to a PLY file named "write-ply/results/{agent_mode}/cube.ply".
3
- Load the PLY file back into ParaView.
4
- Save a screenshot to "write-ply/results/{agent_mode}/write-ply.png".
 
 
 
 
5
  Finally, save the ParaView state as "write-ply/results/{agent_mode}/write-ply.pvsm"
 
1
+ I would like to use ParaView to visualize a dataset.
2
+ Create a wavelet object. Change the view size to 400x400.
3
+ Show the wavelet object and reset the camera to fit the data.
4
+ Next, create a contour of wavelet object from the dataset "RTData".
5
+ The contour should have isosurfaces at the following values: 97.222075, 157.09105, 216.96002500000003, and 276.829.
6
+ Show the contour and color it with the same colormap that is used for coloring "RTData".
7
+ Finally, save the contour in PLY format to the file "write-ply/results/{agent_mode}/PLYWriterData.ply".
8
+ Save a screenshot to the file "write-ply/results/{agent_mode}/write-ply.png".
9
  Finally, save the ParaView state as "write-ply/results/{agent_mode}/write-ply.pvsm"
chatvis_bench/write-ply/visualization_goals.txt CHANGED
@@ -1,7 +1,5 @@
1
  1. Cube Creation: Is the cube object properly created and displayed with correct geometry?
2
 
3
- 2. PLY Export: Is the cube successfully exported to PLY format with proper mesh data preservation?
4
 
5
- 3. PLY Import: Is the exported PLY file correctly loaded back into ParaView maintaining geometric fidelity?
6
-
7
- 4. Visualization Quality: Does the imported cube display properly with correct surface representation and rendering?
 
1
  1. Cube Creation: Is the cube object properly created and displayed with correct geometry?
2
 
3
+ 2. PLY Import: Is the exported PLY file correctly loaded back into ParaView maintaining geometric fidelity?
4
 
5
+ 3. Visualization Quality: Does the imported cube display properly with correct surface representation and rendering?
 
 
eval_cases/paraview/chatvis_bench_cases.yaml CHANGED
@@ -19,18 +19,15 @@
19
 
20
  4. Legend and Readability: Is there a clear legend identifying each variable line with readable labels and proper visual organization?
21
 
22
- - type: code-similarity
23
- subtype: code
24
- gs_file:
25
- - line-plot/GS/line-plot_gs.py
26
- rs_file:
27
- - line-plot/results/{agent_mode}/line-plot.py
28
-
29
  # 2. ml-dvr
30
  - vars:
31
  question: |
32
- Read in the file named "ml-dvr/data/ml-dvr.vtk", and generate a volume rendering using the default transfer function.
33
- Save a screenshot, size 1920 x 1080 pixels, of an isometric view of the visualization in "ml-dvr/results/{agent_mode}/ml-dvr.png".
 
 
 
 
34
  Finally, save the ParaView state as "ml-dvr/results/{agent_mode}/ml-dvr.pvsm"
35
 
36
  assert:
@@ -45,18 +42,11 @@
45
 
46
  4. Visual Clarity and Detail: Are the volume details clearly visible with proper lighting and shading that enhances depth perception?
47
 
48
- - type: code-similarity
49
- subtype: code
50
- gs_file:
51
- - ml-dvr/GS/ml-dvr_gs.py
52
- rs_file:
53
- - ml-dvr/results/{agent_mode}/ml-dvr.py
54
-
55
  # 3. ml-iso
56
  - vars:
57
  question: |
58
  Read in the file named "ml-iso/data/ml-iso.vtk", and generate an isosurface of the variable var0 at value 0.5.
59
- Save a screenshot of the result, size 1920 x 1080 pixels, in "ml-iso/results/{agent_mode}/ml-iso.png".
60
  Finally, save the ParaView state as "ml-iso/results/{agent_mode}/ml-iso.pvsm"
61
 
62
  assert:
@@ -71,18 +61,17 @@
71
 
72
  4. Visual Presentation: Is the isosurface clearly visible with good contrast and coloring that enhances the understanding of the data structure?
73
 
74
- - type: code-similarity
75
- subtype: code
76
- gs_file:
77
- - ml-iso/GS/ml-iso_gs.py
78
- rs_file:
79
- - ml-iso/results/{agent_mode}/ml-iso.py
80
-
81
  # 4. ml-slice-iso
82
  - vars:
83
  question: |
84
- Read in the file named "ml-slice-iso/data/ml-slice-iso.vtk", slice the volume with a y-z plane at x=0, and take a contour, colored red, through the slice at the value 0.5.
85
- Save a screenshot of a +x direction view, size 1920 x 1080 pixels, of the result in "ml-slice-iso/results/{agent_mode}/ml-slice-iso.png".
 
 
 
 
 
 
86
  Finally, save the ParaView state as "ml-slice-iso/results/{agent_mode}/ml-slice-iso.pvsm"
87
 
88
  assert:
@@ -97,18 +86,16 @@
97
 
98
  4. View Direction: Is the visualization displayed from the correct +x direction view that provides clear visibility of the slice and contours?
99
 
100
- - type: code-similarity
101
- subtype: code
102
- gs_file:
103
- - ml-slice-iso/GS/ml-slice-iso_gs.py
104
- rs_file:
105
- - ml-slice-iso/results/{agent_mode}/ml-slice-iso.py
106
-
107
  # 5. points-surf-clip
108
  - vars:
109
  question: |
110
- Read in the file named "points-surf-clip/data/points-surf-clip.ex2", generate a 3D Delaunay triangulation of the dataset, and clip with a y-z plane at x=0, keeping the -x half of the data.
111
- Save a screenshot of the result as a wireframe, image size 1920 x 1080 pixels, in "points-surf-clip/results/{agent_mode}/points-surf-clip.png".
 
 
 
 
 
112
  Finally, save the ParaView state as "points-surf-clip/results/{agent_mode}/points-surf-clip.pvsm"
113
 
114
  assert:
@@ -123,20 +110,18 @@
123
 
124
  4. Geometric Integrity: Does the clipped wireframe maintain proper connectivity and show the expected geometric features without artifacts?
125
 
126
- - type: code-similarity
127
- subtype: code
128
- gs_file:
129
- - points-surf-clip/GS/points-surf-clip_gs.py
130
- rs_file:
131
- - points-surf-clip/results/{agent_mode}/points-surf-clip.py
132
-
133
  # 6. shrink-sphere
134
  - vars:
135
  question: |
136
- Create a default sphere, hide it, and create a shrink filter from the sphere.
137
- Double the sphere's theta resolution while halving the shrink filter's shrink factor.
138
- Group the shrink filter and a wireframe of the sphere together, and save a screenshot of the result in "shrink-sphere/results/{agent_mode}/shrink-sphere.png", size 1920 x 1080 pixels with a white background.
139
- Finally, save the ParaView state as "shrink-sphere/results/{agent_mode}/shrink-sphere.pvsm"
 
 
 
 
 
140
 
141
  assert:
142
  - type: llm-rubric
@@ -150,20 +135,19 @@
150
 
151
  4. Visual Quality: Does the visualization clearly show the contrast between the wireframe structure and the shrunken elements with appropriate white background?
152
 
153
- - type: code-similarity
154
- subtype: code
155
- gs_file:
156
- - shrink-sphere/GS/shrink-sphere_gs.py
157
- rs_file:
158
- - shrink-sphere/results/{agent_mode}/shrink-sphere.py
159
-
160
  # 7. stream-glyph
161
  - vars:
162
  question: |
163
- Read in the file named "stream-glyph/data/stream-glyph.ex2", and trace streamlines of the V variable seeded from a default point cloud.
164
- Render the streamlines with tubes, adding cone glyphs to the streamlines, and coloring the streamlines and glyphs by the Temp variable.
165
- Save a screenshot of a +x view of the result, size 1920 x 1080 pixels, in "stream-glyph/results/{agent_mode}/stream-glyph.png".
166
- Finally, save the ParaView state as "stream-glyph/results/{agent_mode}/stream-glyph.pvsm"
 
 
 
 
 
 
167
 
168
  assert:
169
  - type: llm-rubric
@@ -177,13 +161,6 @@
177
 
178
  4. View Configuration: Is the visualization displayed from the correct +x view direction providing clear visibility of the flow patterns and structures?
179
 
180
- - type: code-similarity
181
- subtype: code
182
- gs_file:
183
- - stream-glyph/GS/stream-glyph_gs.py
184
- rs_file:
185
- - stream-glyph/results/{agent_mode}/stream-glyph.py
186
-
187
  # 8. time-varying
188
  - vars:
189
  question: |
@@ -207,13 +184,6 @@
207
 
208
  4. View Direction and Layout: Is the +y direction view properly set and are both views arranged side-by-side in the correct layout configuration?
209
 
210
- - type: code-similarity
211
- subtype: code
212
- gs_file:
213
- - time-varying/GS/time-varying_gs.py
214
- rs_file:
215
- - time-varying/results/{agent_mode}/time-varying.py
216
-
217
  # 9. chart-opacity
218
  - vars:
219
  question: |
@@ -226,31 +196,32 @@
226
  - type: llm-rubric
227
  subtype: vision
228
  value: |
229
- 1. Chart Generation: Is the plot over line chart properly created from the wavelet data showing all three specified variables?
230
 
231
- 2. Variable Display: Are arc_length, Points_Z, and RTData variables all correctly plotted and distinguishable in the chart?
232
 
233
  3. Opacity Settings: Is the arc_length variable displayed with full opacity (1.0) while Points_Z and RTData show reduced opacity (0.3)?
234
 
235
  4. Chart Clarity: Does the chart provide clear visualization of the data trends with appropriate axis scaling and readable formatting?
236
 
237
- - type: code-similarity
238
- subtype: code
239
- gs_file:
240
- - chart-opacity/GS/chart-opacity_gs.py
241
- rs_file:
242
- - chart-opacity/results/{agent_mode}/chart-opacity.py
243
-
244
  # 10. color-blocks
245
  - vars:
246
  question: |
 
 
247
  Read the file "color-blocks/data/color-blocks.ex2".
 
248
  Color the dataset by the vtkBlockColors field.
249
- Retrieve the color map, opacity transfer function, and 2D transfer function for vtkBlockColors.
250
- Set block coloring for the block at /IOSS/element_blocks/block_2 using the x component of the ACCL variable.
 
 
251
  Rescale the block's color and opacity maps to match the current data range of block_2.
252
- For the ACCL variable of block_2, retrieve the color transfer function, enable the color bar, and apply cool to warm coloring.
253
- View the entire dataset in the -y direction, and save a screenshot with blue-gray background in "color-blocks/results/{agent_mode}/color-blocks.png".
 
 
 
254
  Finally, save the ParaView state as "color-blocks/results/{agent_mode}/color-blocks.pvsm"
255
 
256
  assert:
@@ -265,13 +236,6 @@
265
 
266
  4. View Configuration: Is the dataset displayed from the -y direction with blue-gray background and visible color bar legend?
267
 
268
- - type: code-similarity
269
- subtype: code
270
- gs_file:
271
- - color-blocks/GS/color-blocks_gs.py
272
- rs_file:
273
- - color-blocks/results/{agent_mode}/color-blocks.py
274
-
275
  # 11. color-data
276
  - vars:
277
  question: |
@@ -285,20 +249,11 @@
285
  - type: llm-rubric
286
  subtype: vision
287
  value: |
288
- 1. Calculator Function: Is the calculator properly implemented with the specified vector function combining RTData and coordinate components?
289
-
290
- 2. Color Transfer Function: Is the color transfer function correctly applied with cool to warm color mapping scaled to the data range?
291
 
292
- 3. Surface Coloring: Is the surface representation properly colored by the x coordinate of the calculated result?
293
 
294
- 4. Color Bar Display: Is the color bar/legend visible and properly displaying the color mapping scale and values?
295
-
296
- - type: code-similarity
297
- subtype: code
298
- gs_file:
299
- - color-data/GS/color-data_gs.py
300
- rs_file:
301
- - color-data/results/{agent_mode}/color-data.py
302
 
303
  # 12. export-gltf
304
  - vars:
@@ -311,7 +266,7 @@
311
  Next load the file "export-gltf/results/{agent_mode}/ExportedGLTF.gltf" and display it as a surface.
312
  Color this object by TEXCOORD_0.
313
  Scale the color map to the data, and don't display the color bar or the orientation axes.
314
- Use the 'Cool to Warm' colormap.
315
 
316
  Save a screenshot to the file "export-gltf/results/{agent_mode}/export-gltf.png".
317
  Finally, save the ParaView state as "export-gltf/results/{agent_mode}/export-gltf.pvsm"
@@ -328,13 +283,6 @@
328
 
329
  4. Clean Presentation: Are the color bar and orientation axes properly hidden for a clean visualization appearance?
330
 
331
- - type: code-similarity
332
- subtype: code
333
- gs_file:
334
- - export-gltf/GS/export-gltf_gs.py
335
- rs_file:
336
- - export-gltf/results/{agent_mode}/export-gltf.py
337
-
338
  # 13. import-gltf
339
  - vars:
340
  question: |
@@ -353,28 +301,20 @@
353
 
354
  2. Node Selection: Are all three specified nodes (Axle, Torus002, InnerRing) correctly imported and visible?
355
 
356
- 3. Camera Positioning: Is the camera positioned in the positive Y direction with appropriate zoom to fit all imported geometry?
357
 
358
  4. Layout Configuration: Is the view properly sized to 300x300 pixels with correct rendering and background palette?
359
 
360
- - type: code-similarity
361
- subtype: code
362
- gs_file:
363
- - import-gltf/GS/import-gltf_gs.py
364
- rs_file:
365
- - import-gltf/results/{agent_mode}/import-gltf.py
366
-
367
  # 14. render-histogram
368
  - vars:
369
  question: |
370
- Create a wavelet object.
371
- Render the RTDATA data in the wavelet and show the color bar.
372
- [optional: Make sure the colors are rescaled to the data range]
373
- [optional: Use the color map called 'Cool to Warm']
 
374
 
375
- Next, split the view to the right and create a histogram from RTDATA.
376
- Use the same color map as before.
377
- Save a screenshot of the line chart in the file "render-histogram/results/{agent_mode}/render-histogram.png".
378
  Finally, save the ParaView state as "render-histogram/results/{agent_mode}/render-histogram.pvsm"
379
 
380
  assert:
@@ -389,13 +329,6 @@
389
 
390
  4. Color Map Consistency: Are both the wavelet visualization and histogram using the same Cool to Warm color map?
391
 
392
- - type: code-similarity
393
- subtype: code
394
- gs_file:
395
- - render-histogram/GS/render-histogram_gs.py
396
- rs_file:
397
- - render-histogram/results/{agent_mode}/render-histogram.py
398
-
399
  # 15. reset-camera-direction
400
  - vars:
401
  question: |
@@ -415,39 +348,24 @@
415
 
416
  4. View Quality: Does the visualization provide a clear view of the wavelet structure from the specified camera angle?
417
 
418
- - type: code-similarity
419
- subtype: code
420
- gs_file:
421
- - reset-camera-direction/GS/reset-camera-direction_gs.py
422
- rs_file:
423
- - reset-camera-direction/results/{agent_mode}/reset-camera-direction.py
424
-
425
  # 16. save-transparent
426
  - vars:
427
  question: |
428
- Create a cone object.
429
- Set the transparency of the cone to be 50%.
430
- Save a screenshot with a transparent background in "save-transparent/results/{agent_mode}/save-transparent.png".
 
 
 
431
  Finally, save the ParaView state as "save-transparent/results/{agent_mode}/save-transparent.pvsm"
432
 
433
  assert:
434
  - type: llm-rubric
435
  subtype: vision
436
  value: |
437
- 1. Cone Object Creation: Is the cone object properly created and displayed in the scene?
438
-
439
- 2. Transparency Setting: Is the cone transparency correctly set to 50% showing partial see-through effect?
440
-
441
- 3. Transparent Background: Is the screenshot saved with a properly transparent background instead of solid color?
442
-
443
- 4. Visual Quality: Does the transparent cone maintain good visual quality and edge definition?
444
 
445
- - type: code-similarity
446
- subtype: code
447
- gs_file:
448
- - save-transparent/GS/save-transparent_gs.py
449
- rs_file:
450
- - save-transparent/results/{agent_mode}/save-transparent.py
451
 
452
  # 17. subseries-of-time-series
453
  - vars:
@@ -466,26 +384,21 @@
466
  value: |
467
  1. Data Loading and Block Selection: Are the specified element blocks properly loaded and the slice plane correctly applied?
468
 
469
- 2. Time Series Export: Is the time series correctly saved as VTM files with the specified time step range and interval?
470
 
471
- 3. Multi-block Loading: Are the exported VTM files successfully loaded back as a multi-block dataset?
472
-
473
- 4. Final Visualization: Is the multi-block dataset properly displayed showing the sliced geometry from the time series?
474
-
475
- - type: code-similarity
476
- subtype: code
477
- gs_file:
478
- - subseries-of-time-series/GS/subseries-of-time-series_gs.py
479
- rs_file:
480
- - subseries-of-time-series/results/{agent_mode}/subseries-of-time-series.py
481
 
482
  # 18. write-ply
483
  - vars:
484
  question: |
485
- Create a cube object.
486
- Export the cube to a PLY file named "write-ply/results/{agent_mode}/cube.ply".
487
- Load the PLY file back into ParaView.
488
- Save a screenshot to "write-ply/results/{agent_mode}/write-ply.png".
 
 
 
 
489
  Finally, save the ParaView state as "write-ply/results/{agent_mode}/write-ply.pvsm"
490
 
491
  assert:
@@ -494,27 +407,24 @@
494
  value: |
495
  1. Cube Creation: Is the cube object properly created and displayed with correct geometry?
496
 
497
- 2. PLY Export: Is the cube successfully exported to PLY format with proper mesh data preservation?
498
-
499
- 3. PLY Import: Is the exported PLY file correctly loaded back into ParaView maintaining geometric fidelity?
500
 
501
- 4. Visualization Quality: Does the imported cube display properly with correct surface representation and rendering?
502
-
503
- - type: code-similarity
504
- subtype: code
505
- gs_file:
506
- - write-ply/GS/write-ply_gs.py
507
- rs_file:
508
- - write-ply/results/{agent_mode}/write-ply.py
509
 
510
  # 19. climate
511
  - vars:
512
  question: |
 
513
  Read in the file named "climate/data/climate.vtp".
514
- Apply a calculator filter to convert velocity from geospatial to lat-long coordinates.
515
- Render the computed values using a tube filter with 0.05 radius, colored by velocity magnitude, and lit with maximum shininess and include normals for lighting.
516
- Add cone glyphs to show the direction of the velocity, using 10 polygons, radius 0.15, height 0.5, and scaling factor 0.5.
517
- View the result in the -z direction scaled so that the tubes occupy most of the image.
 
 
 
 
 
518
  Save a screenshot of the result, 2294 x 1440 pixels, white background, in the filename "climate/results/{agent_mode}/climate.png".
519
  Finally, save the ParaView state as "climate/results/{agent_mode}/climate.pvsm"
520
 
@@ -522,20 +432,11 @@
522
  - type: llm-rubric
523
  subtype: vision
524
  value: |
525
- 1. Velocity Conversion: Is the calculator filter properly applied to convert velocity from geospatial to lat-long coordinates?
526
-
527
- 2. Tube Visualization: Are the tubes rendered with correct radius (0.05), colored by velocity magnitude, and proper lighting with maximum shininess?
528
-
529
- 3. Cone Glyph Direction: Are the cone glyphs properly configured with specified parameters and showing velocity direction accurately?
530
 
531
- 4. View Configuration: Is the visualization displayed from -z direction with appropriate scaling and white background as specified?
532
 
533
- - type: code-similarity
534
- subtype: code
535
- gs_file:
536
- - climate/GS/climate_gs.py
537
- rs_file:
538
- - climate/results/{agent_mode}/climate.py
539
 
540
  # 20. materials
541
  - vars:
@@ -562,9 +463,3 @@
562
 
563
  4. Camera and Layout: Is the camera positioned correctly in (-1, 0, -1) direction with appropriate fitting and legends visible?
564
 
565
- - type: code-similarity
566
- subtype: code
567
- gs_file:
568
- - materials/GS/materials_gs.py
569
- rs_file:
570
- - materials/results/{agent_mode}/materials.py
 
19
 
20
  4. Legend and Readability: Is there a clear legend identifying each variable line with readable labels and proper visual organization?
21
 
 
 
 
 
 
 
 
22
  # 2. ml-dvr
23
  - vars:
24
  question: |
25
+ I would like to use ParaView to visualize a dataset.
26
+ Read in the file named "ml-dvr/data/ml-dvr.vtk".
27
+ Generate a volume rendering using the default transfer function.
28
+ Rotate the view to an isometric direction.
29
+ Save a screenshot of the result in the filename "ml-dvr/results/{agent_mode}/ml-dvr.png".
30
+ The rendered view and saved screenshot should be 1920 x 1080 pixels.
31
  Finally, save the ParaView state as "ml-dvr/results/{agent_mode}/ml-dvr.pvsm"
32
 
33
  assert:
 
42
 
43
  4. Visual Clarity and Detail: Are the volume details clearly visible with proper lighting and shading that enhances depth perception?
44
 
 
 
 
 
 
 
 
45
  # 3. ml-iso
46
  - vars:
47
  question: |
48
  Read in the file named "ml-iso/data/ml-iso.vtk", and generate an isosurface of the variable var0 at value 0.5.
49
+ Use a white background color. Save a screenshot of the result, size 1920 x 1080 pixels, in "ml-iso/results/{agent_mode}/ml-iso.png".
50
  Finally, save the ParaView state as "ml-iso/results/{agent_mode}/ml-iso.pvsm"
51
 
52
  assert:
 
61
 
62
  4. Visual Presentation: Is the isosurface clearly visible with good contrast and coloring that enhances the understanding of the data structure?
63
 
 
 
 
 
 
 
 
64
  # 4. ml-slice-iso
65
  - vars:
66
  question: |
67
+ Please generate a ParaView Python script for the following operations.
68
+ Read in the file named "ml-slice-iso/data/ml-slice-iso.vtk".
69
+ Slice the volume in a plane parallel to the y-z plane at x=0.
70
+ Take a contour through the slice at the value 0.5.
71
+ Color the contour red. Use a white background.
72
+ Rotate the view to look at the +x direction.
73
+ Save a screenshot of the result in the filename "ml-slice-iso/results/{agent_mode}/ml-slice-iso.png".
74
+ The rendered view and saved screenshot should be 1920 x 1080 pixels.
75
  Finally, save the ParaView state as "ml-slice-iso/results/{agent_mode}/ml-slice-iso.pvsm"
76
 
77
  assert:
 
86
 
87
  4. View Direction: Is the visualization displayed from the correct +x direction view that provides clear visibility of the slice and contours?
88
 
 
 
 
 
 
 
 
89
  # 5. points-surf-clip
90
  - vars:
91
  question: |
92
+ I would like to use ParaView to visualize a dataset.
93
+ Read in the file named "points-surf-clip/data/points-surf-clip.ex2".
94
+ Generate an 3d Delaunay triangulation of the dataset.
95
+ Clip the data with a y-z plane at x=0, keeping the -x half of the data and removing the +x half.
96
+ Render the image as a wireframe.
97
+ Save a screenshot of the result in the filename "points-surf-clip/results/{agent_mode}/points-surf-clip.png".
98
+ The rendered view and saved screenshot should be 1920 x 1080 pixels. Use a white background color.
99
  Finally, save the ParaView state as "points-surf-clip/results/{agent_mode}/points-surf-clip.pvsm"
100
 
101
  assert:
 
110
 
111
  4. Geometric Integrity: Does the clipped wireframe maintain proper connectivity and show the expected geometric features without artifacts?
112
 
 
 
 
 
 
 
 
113
  # 6. shrink-sphere
114
  - vars:
115
  question: |
116
+ Create a default sphere and then hide it.
117
+ Create a shrink filter from the sphere.
118
+ Double the sphere's theta resolution.
119
+ Divide the shrink filter's shrink factor in half.
120
+ Extract a wireframe from the sphere.
121
+ Group the shrink filter and wireframe together and show them.
122
+ Save a screenshot of the result in the filename "shrink-sphere/results/{agent_mode}/shrink-sphere.png".
123
+ The rendered view and saved screenshot should be 1920 x 1080 pixels and have a white background.
124
+ Finally, save the ParaView state as "shrink-sphere/results/{agent_mode}/shrink-sphere.pvsm".
125
 
126
  assert:
127
  - type: llm-rubric
 
135
 
136
  4. Visual Quality: Does the visualization clearly show the contrast between the wireframe structure and the shrunken elements with appropriate white background?
137
 
 
 
 
 
 
 
 
138
  # 7. stream-glyph
139
  - vars:
140
  question: |
141
+ I would like to use ParaView to visualize a dataset.
142
+ Read in the file named "stream-glyph/data/stream-glyph.ex2".
143
+ Trace streamlines of the V data array seeded from a default point cloud.
144
+ Render the streamlines with tubes.
145
+ Add cone glyphs to the streamlines.
146
+ Color the streamlines and glyphs by the Temp data array.
147
+ View the result in the +X direction.
148
+ Save a screenshot of the result in the filename "stream-glyph/results/{agent_mode}/stream-glyph.png".
149
+ The rendered view and saved screenshot should be 1920 x 1080 pixels.
150
+ Finally, save the ParaView state as "stream-glyph/results/{agent_mode}/stream-glyph.pvsm".
151
 
152
  assert:
153
  - type: llm-rubric
 
161
 
162
  4. View Configuration: Is the visualization displayed from the correct +x view direction providing clear visibility of the flow patterns and structures?
163
 
 
 
 
 
 
 
 
164
  # 8. time-varying
165
  - vars:
166
  question: |
 
184
 
185
  4. View Direction and Layout: Is the +y direction view properly set and are both views arranged side-by-side in the correct layout configuration?
186
 
 
 
 
 
 
 
 
187
  # 9. chart-opacity
188
  - vars:
189
  question: |
 
196
  - type: llm-rubric
197
  subtype: vision
198
  value: |
199
+ 1. Chart Generation: Is the plot over line chart properly created from the wavelet data?
200
 
201
+ 2. Variable Display: Are arc_length, Points_Z, and RTData variables all correctly plotted, showing all three specified variables and distinguishable in the chart?
202
 
203
  3. Opacity Settings: Is the arc_length variable displayed with full opacity (1.0) while Points_Z and RTData show reduced opacity (0.3)?
204
 
205
  4. Chart Clarity: Does the chart provide clear visualization of the data trends with appropriate axis scaling and readable formatting?
206
 
 
 
 
 
 
 
 
207
  # 10. color-blocks
208
  - vars:
209
  question: |
210
+ I would like to use ParaView to visualize a dataset.
211
+ Set the background to a blue-gray palette.
212
  Read the file "color-blocks/data/color-blocks.ex2".
213
+ This is a multiblock dataset.
214
  Color the dataset by the vtkBlockColors field.
215
+ Retrieve the color map for vtkBlockColors.
216
+ Retrieve the opacity transfer function for vtkBlockColors.
217
+ Retrieve the 2D transfer function for vtkBlockColors.
218
+ Set block coloring for the block at /IOSS/element_blocks/block_2 using the variable ACCL on the x component of the points.
219
  Rescale the block's color and opacity maps to match the current data range of block_2.
220
+ Retrieve the color transfer function for the ACCL variable of block_2.
221
+ Enable the color bar for block_2.
222
+ Apply a cool to warm color preset to the color map for block_2.
223
+ Set the camera to look down the -y direction and to see the entire dataset.
224
+ Save a screenshot of the visualization in the file "color-blocks/results/{agent_mode}/color-blocks.png".
225
  Finally, save the ParaView state as "color-blocks/results/{agent_mode}/color-blocks.pvsm"
226
 
227
  assert:
 
236
 
237
  4. View Configuration: Is the dataset displayed from the -y direction with blue-gray background and visible color bar legend?
238
 
 
 
 
 
 
 
 
239
  # 11. color-data
240
  - vars:
241
  question: |
 
249
  - type: llm-rubric
250
  subtype: vision
251
  value: |
252
+ 1. Color Transfer Function: Is the color transfer function correctly applied with cool to warm color mapping scaled to the data range?
 
 
253
 
254
+ 2. Surface Coloring: Is the surface representation properly colored by the x coordinate of the calculated result?
255
 
256
+ 3. Color Bar Display: Is the color bar/legend visible and properly displaying the color mapping scale and values?
 
 
 
 
 
 
 
257
 
258
  # 12. export-gltf
259
  - vars:
 
266
  Next load the file "export-gltf/results/{agent_mode}/ExportedGLTF.gltf" and display it as a surface.
267
  Color this object by TEXCOORD_0.
268
  Scale the color map to the data, and don't display the color bar or the orientation axes.
269
+ Use the 'Cool to Warm' colormap. Set the background color to white.
270
 
271
  Save a screenshot to the file "export-gltf/results/{agent_mode}/export-gltf.png".
272
  Finally, save the ParaView state as "export-gltf/results/{agent_mode}/export-gltf.pvsm"
 
283
 
284
  4. Clean Presentation: Are the color bar and orientation axes properly hidden for a clean visualization appearance?
285
 
 
 
 
 
 
 
 
286
  # 13. import-gltf
287
  - vars:
288
  question: |
 
301
 
302
  2. Node Selection: Are all three specified nodes (Axle, Torus002, InnerRing) correctly imported and visible?
303
 
304
+ 3. Camera Positioning: Is the camera positioned in the positive Y direction with appropriate zoom to fit all imported geometry? Carefully compare the camera position of GT and result images.
305
 
306
  4. Layout Configuration: Is the view properly sized to 300x300 pixels with correct rendering and background palette?
307
 
 
 
 
 
 
 
 
308
  # 14. render-histogram
309
  - vars:
310
  question: |
311
+ Create a wavelet object and render it as a surface colored by RTDATA with a visible color bar.
312
+ Rescale the colors to the data range and use the 'Cool to Warm' color map.
313
+
314
+ Next, split the view horizontally to the right and create a histogram view from the wavelet RTDATA.
315
+ Apply the same 'Cool to Warm' color map to the histogram.
316
 
317
+ Save a screenshot of both views (wavelet rendering on the left and histogram on the right) in the file "render-histogram/results/{agent_mode}/render-histogram.png".
 
 
318
  Finally, save the ParaView state as "render-histogram/results/{agent_mode}/render-histogram.pvsm"
319
 
320
  assert:
 
329
 
330
  4. Color Map Consistency: Are both the wavelet visualization and histogram using the same Cool to Warm color map?
331
 
 
 
 
 
 
 
 
332
  # 15. reset-camera-direction
333
  - vars:
334
  question: |
 
348
 
349
  4. View Quality: Does the visualization provide a clear view of the wavelet structure from the specified camera angle?
350
 
 
 
 
 
 
 
 
351
  # 16. save-transparent
352
  - vars:
353
  question: |
354
+ I would like to use ParaView to visualize a dataset.
355
+ Create a wavelet object and show it. Color the rendering by the variable ‘RTData’.
356
+ Render the wavelet as a surface. Hide the color bar.
357
+ Next, set the layout size to be 300 pixels by 300 pixels.
358
+ Next, move the camera with the following settings. The camera position should be [30.273897726939246, 40.8733980301544, 43.48927935675712]. The camera view up should be [-0.3634544237682163, 0.7916848767068606, -0.49105594165731975]. The camera parallel scale should be 17.320508075688775.
359
+ Save a screenshot to the file “save-transparent/results/{agent_mode}/save-transparent.png”, set the image resolution to 300x300, and set the background to transparent.
360
  Finally, save the ParaView state as "save-transparent/results/{agent_mode}/save-transparent.pvsm"
361
 
362
  assert:
363
  - type: llm-rubric
364
  subtype: vision
365
  value: |
366
+ 1. Object Creation: Is the wavelet object properly created and displayed in the scene? Looking similar to the GT image?
 
 
 
 
 
 
367
 
368
+ 2. Transparent Background: Is the screenshot saved with a properly transparent background instead of solid color?
 
 
 
 
 
369
 
370
  # 17. subseries-of-time-series
371
  - vars:
 
384
  value: |
385
  1. Data Loading and Block Selection: Are the specified element blocks properly loaded and the slice plane correctly applied?
386
 
387
+ 2. Multi-block Loading: Are the exported VTM files successfully loaded back as a multi-block dataset?
388
 
389
+ 3. Final Visualization: Is the multi-block dataset properly displayed showing the sliced geometry from the time series?
 
 
 
 
 
 
 
 
 
390
 
391
  # 18. write-ply
392
  - vars:
393
  question: |
394
+ I would like to use ParaView to visualize a dataset.
395
+ Create a wavelet object. Change the view size to 400x400.
396
+ Show the wavelet object and reset the camera to fit the data.
397
+ Next, create a contour of wavelet object from the dataset "RTData".
398
+ The contour should have isosurfaces at the following values: 97.222075, 157.09105, 216.96002500000003, and 276.829.
399
+ Show the contour and color it with the same colormap that is used for coloring "RTData".
400
+ Finally, save the contour in PLY format to the file "write-ply/results/{agent_mode}/PLYWriterData.ply".
401
+ Save a screenshot to the file "write-ply/results/{agent_mode}/write-ply.png".
402
  Finally, save the ParaView state as "write-ply/results/{agent_mode}/write-ply.pvsm"
403
 
404
  assert:
 
407
  value: |
408
  1. Cube Creation: Is the cube object properly created and displayed with correct geometry?
409
 
410
+ 2. PLY Import: Is the exported PLY file correctly loaded back into ParaView maintaining geometric fidelity?
 
 
411
 
412
+ 3. Visualization Quality: Does the imported cube display properly with correct surface representation and rendering?
 
 
 
 
 
 
 
413
 
414
  # 19. climate
415
  - vars:
416
  question: |
417
+ I would like to use ParaView to visualize a dataset of ocean currents.
418
  Read in the file named "climate/data/climate.vtp".
419
+ Apply a calculator filter to compute the following function:
420
+ (-velocity_X*sin(coordsX*0.0174533) + velocity_Y*cos(coordsX*0.0174533)) * iHat + (-velocity_X * sin(coordsY*0.0174533) * cos(coordsX*0.0174533) - velocity_Y * sin(coordsY*0.0174533) * sin(coordsX*0.0174533) + velocity_Z * cos(coordsY*0.0174533)) * jHat + 0*kHat
421
+ Render the computed values using a tube filter with 0.05 as the tube radius.
422
+ Color the tubes by the magnitude of the velocity.
423
+ Light the tubes with the maximum shininess and include normals in the lighting.
424
+ Add cone glyphs to show the direction of the velocity.
425
+ The glyphs are composed of 10 polygons, having a radius 0 0.15, a height of 0.5, and a scaling factor of 0.5.
426
+ View the result in the -z direction.
427
+ Adjust the view so that the tubes occupy the 90% of the image.
428
  Save a screenshot of the result, 2294 x 1440 pixels, white background, in the filename "climate/results/{agent_mode}/climate.png".
429
  Finally, save the ParaView state as "climate/results/{agent_mode}/climate.pvsm"
430
 
 
432
  - type: llm-rubric
433
  subtype: vision
434
  value: |
435
+ 1. Tube Visualization: Are the tubes rendered with correct radius (0.05), colored by velocity magnitude, and proper lighting with maximum shininess?
 
 
 
 
436
 
437
+ 2. Cone Glyph Direction: Are the cone glyphs properly configured with specified parameters and showing velocity direction accurately?
438
 
439
+ 3. View Configuration: Is the visualization displayed from -z direction with appropriate scaling and white background as specified?
 
 
 
 
 
440
 
441
  # 20. materials
442
  - vars:
 
463
 
464
  4. Camera and Layout: Is the camera positioned correctly in (-1, 0, -1) direction with appropriate fitting and legends visible?
465
 
 
 
 
 
 
 
eval_cases/paraview/what_obj_cases.yaml CHANGED
@@ -16,23 +16,23 @@
16
  - type: llm-rubric
17
  subtype: vision
18
  value: |
19
- The assistant should identify the data shows an aneurism or vascular structure
20
 
21
- # # 2. Backpack Dataset
22
- # - vars:
23
- # question: |
24
- # Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/backpack/data/backpack_512x512x373_uint16.raw".
25
- # Use visualization tools to determine what object is contained in this dataset. Save the paraview state as "../SciVisAgentBench-tasks/sci_volume_data/backpack/results/{agent_mode}/backpack.pvsm"
26
- # Provide a textual report identifying what you observe and save it to "../SciVisAgentBench-tasks/sci_volume_data/backpack/results/{agent_mode}/answers.txt"
27
- # assert:
28
- # - type: llm-rubric
29
- # subtype: text
30
- # value: |
31
- # The assistant should identify that the data shows a backpack
32
- # - type: llm-rubric
33
- # subtype: vision
34
- # value: |
35
- # The assistant should identify that the data shows a backpack
36
 
37
  # 3. Blunt Fin Dataset
38
  - vars:
@@ -48,7 +48,7 @@
48
  - type: llm-rubric
49
  subtype: vision
50
  value: |
51
- The assistant should identify a fin or aerodynamic strcuture or simulation result in the data
52
 
53
  # 4. Bonsai Dataset
54
  - vars:
@@ -64,7 +64,7 @@
64
  - type: llm-rubric
65
  subtype: vision
66
  value: |
67
- Should identify a bonsai tree or botanical structure in the data
68
 
69
  # 5. Boston Teapot Dataset
70
  - vars:
@@ -80,7 +80,7 @@
80
  - type: llm-rubric
81
  subtype: vision
82
  value: |
83
- Should identify a teapot in the visualization
84
 
85
  # 6. Bunny Dataset
86
  - vars:
@@ -96,7 +96,7 @@
96
  - type: llm-rubric
97
  subtype: vision
98
  value: |
99
- Should identify a bunny or rabbit in the 3D scanned data
100
 
101
  # 7. Carp Dataset
102
  - vars:
@@ -112,7 +112,7 @@
112
  - type: llm-rubric
113
  subtype: vision
114
  value: |
115
- Should identify a carp or fish anatomy
116
 
117
  # 8. CSAFE Heptane Dataset
118
  - vars:
@@ -128,7 +128,7 @@
128
  - type: llm-rubric
129
  subtype: vision
130
  value: |
131
- Should recognize combustion or heptane simulation data
132
 
133
  # 9. Duct Dataset
134
  - vars:
@@ -144,7 +144,7 @@
144
  - type: llm-rubric
145
  subtype: vision
146
  value: |
147
- Should identify flow patterns in a duct geometry
148
 
149
  # 10. Engine Dataset
150
  - vars:
@@ -160,7 +160,7 @@
160
  - type: llm-rubric
161
  subtype: vision
162
  value: |
163
- Should identify an engine or mechanical components
164
 
165
  # 11. Foot Dataset
166
  - vars:
@@ -176,7 +176,7 @@
176
  - type: llm-rubric
177
  subtype: vision
178
  value: |
179
- Should identify a foot with bone and tissue structures
180
 
181
  # 12. Frog Dataset
182
  - vars:
@@ -192,7 +192,7 @@
192
  - type: llm-rubric
193
  subtype: vision
194
  value: |
195
- Should identify a frog specimen with internal anatomy
196
 
197
  # 13. Fuel Dataset
198
  - vars:
@@ -208,7 +208,7 @@
208
  - type: llm-rubric
209
  subtype: vision
210
  value: |
211
- Should identify fuel combustion or related simulation
212
 
213
  # 14. Hydrogen Atom Dataset
214
  - vars:
@@ -224,7 +224,7 @@
224
  - type: llm-rubric
225
  subtype: vision
226
  value: |
227
- Should recognize hydrogen atom orbital or probability distribution
228
 
229
  # 15. Lobster Dataset
230
  - vars:
@@ -240,7 +240,7 @@
240
  - type: llm-rubric
241
  subtype: vision
242
  value: |
243
- Should identify a lobster or crustacean anatomy
244
 
245
  # 16. Marschner-Lobb Dataset
246
  - vars:
@@ -256,7 +256,7 @@
256
  - type: llm-rubric
257
  subtype: vision
258
  value: |
259
- Should recognize Marschner-Lobb synthetic test pattern
260
 
261
  # 17. MRI Ventricles Dataset
262
  - vars:
@@ -272,7 +272,7 @@
272
  - type: llm-rubric
273
  subtype: vision
274
  value: |
275
- Should identify brain ventricles or ventricular structures
276
 
277
  # 18. MRI Woman Dataset
278
  - vars:
@@ -288,7 +288,7 @@
288
  - type: llm-rubric
289
  subtype: vision
290
  value: |
291
- Should identify human anatomical structures from MRI scan
292
 
293
  # 19. MRT Angio Dataset
294
  - vars:
@@ -304,7 +304,7 @@
304
  - type: llm-rubric
305
  subtype: vision
306
  value: |
307
- Should identify angiography or vascular structures
308
 
309
  # 20. Neghip Dataset
310
  - vars:
@@ -320,7 +320,7 @@
320
  - type: llm-rubric
321
  subtype: vision
322
  value: |
323
- Should visualize and describe molecule structure
324
 
325
  # 21. Neocortical Layer 1 Axons Dataset
326
  - vars:
@@ -336,7 +336,7 @@
336
  - type: llm-rubric
337
  subtype: vision
338
  value: |
339
- Should identify neural axons or neocortical network structures
340
 
341
  # 22. Nucleon Dataset
342
  - vars:
@@ -352,7 +352,7 @@
352
  - type: llm-rubric
353
  subtype: vision
354
  value: |
355
- Should visualize nucleon or particle physics data
356
 
357
  # 23. Pancreas Dataset
358
  - vars:
@@ -368,7 +368,7 @@
368
  - type: llm-rubric
369
  subtype: vision
370
  value: |
371
- Should identify pancreas or pancreatic anatomy
372
 
373
  # 24. Shockwave Dataset
374
  - vars:
@@ -384,7 +384,7 @@
384
  - type: llm-rubric
385
  subtype: vision
386
  value: |
387
- Should identify shockwave or wave propagation patterns
388
 
389
  # 25. Silicium Dataset
390
  - vars:
@@ -400,7 +400,7 @@
400
  - type: llm-rubric
401
  subtype: vision
402
  value: |
403
- Should identify silicon crystal or material structure
404
 
405
  # 26. Skull Dataset
406
  - vars:
@@ -432,7 +432,7 @@
432
  - type: llm-rubric
433
  subtype: vision
434
  value: |
435
- Should identify a statue leg or sculptural form
436
 
437
  # 28. Stent Dataset
438
  - vars:
@@ -459,7 +459,7 @@
459
  - type: llm-rubric
460
  subtype: vision
461
  value: |
462
- Should identify supernova or astrophysical explosion simulation
463
 
464
  # 30. TACC Turbulence Dataset
465
  - vars:
@@ -475,7 +475,7 @@
475
  - type: llm-rubric
476
  subtype: vision
477
  value: |
478
- Should identify turbulence or vortex flow structures
479
 
480
  # 31. Tooth Dataset
481
  - vars:
@@ -491,7 +491,7 @@
491
  - type: llm-rubric
492
  subtype: vision
493
  value: |
494
- Should identify tooth or dental anatomy
495
 
496
  # 32. Tornado Dataset
497
  - vars:
@@ -507,7 +507,7 @@
507
  - type: llm-rubric
508
  subtype: vision
509
  value: |
510
- Should identify tornado or vortex flow pattern
511
 
512
  # 33. Visible Male Dataset
513
  - vars:
@@ -523,4 +523,4 @@
523
  - type: llm-rubric
524
  subtype: vision
525
  value: |
526
- Should identify human anatomical structures
 
16
  - type: llm-rubric
17
  subtype: vision
18
  value: |
19
+ The visualization image shows an aneurism or vascular structure with a reasonable transfer function, and the object is shown clearly
20
 
21
+ # 2. Backpack Dataset
22
+ - vars:
23
+ question: |
24
+ Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/backpack/data/backpack_512x512x373_uint16.raw".
25
+ Use visualization tools to determine what object is contained in this dataset. Save the paraview state as "../SciVisAgentBench-tasks/sci_volume_data/backpack/results/{agent_mode}/backpack.pvsm"
26
+ Provide a textual report identifying what you observe and save it to "../SciVisAgentBench-tasks/sci_volume_data/backpack/results/{agent_mode}/answers.txt"
27
+ assert:
28
+ - type: llm-rubric
29
+ subtype: text
30
+ value: |
31
+ The assistant should identify that the data shows a backpack
32
+ - type: llm-rubric
33
+ subtype: vision
34
+ value: |
35
+ The visualization image shows a backpack with a reasonable transfer function, and the object is shown clearly
36
 
37
  # 3. Blunt Fin Dataset
38
  - vars:
 
48
  - type: llm-rubric
49
  subtype: vision
50
  value: |
51
+ The visualization image shows a fin or aerodynamic strcuture or simulation result in the data with a reasonable transfer function, and the object is shown clearly
52
 
53
  # 4. Bonsai Dataset
54
  - vars:
 
64
  - type: llm-rubric
65
  subtype: vision
66
  value: |
67
+ The visualization image shows a bonsai tree or botanical structure in the data with a reasonable transfer function, and the object is shown clearly
68
 
69
  # 5. Boston Teapot Dataset
70
  - vars:
 
80
  - type: llm-rubric
81
  subtype: vision
82
  value: |
83
+ The visualization image shows a teapot in the visualization with a reasonable transfer function, and the object is shown clearly
84
 
85
  # 6. Bunny Dataset
86
  - vars:
 
96
  - type: llm-rubric
97
  subtype: vision
98
  value: |
99
+ The visualization image shows a bunny or rabbit in the 3D scanned data with a reasonable transfer function, and the object is shown clearly
100
 
101
  # 7. Carp Dataset
102
  - vars:
 
112
  - type: llm-rubric
113
  subtype: vision
114
  value: |
115
+ The visualization image shows a carp or fish anatomy with a reasonable transfer function, and the object is shown clearly
116
 
117
  # 8. CSAFE Heptane Dataset
118
  - vars:
 
128
  - type: llm-rubric
129
  subtype: vision
130
  value: |
131
+ The visualization image shows combustion or heptane simulation data with a reasonable transfer function, and the object is shown clearly
132
 
133
  # 9. Duct Dataset
134
  - vars:
 
144
  - type: llm-rubric
145
  subtype: vision
146
  value: |
147
+ The visualization image shows flow patterns in a duct geometry with a reasonable transfer function, and the object is shown clearly
148
 
149
  # 10. Engine Dataset
150
  - vars:
 
160
  - type: llm-rubric
161
  subtype: vision
162
  value: |
163
+ The visualization image shows an engine or mechanical components with a reasonable transfer function, and the object is shown clearly
164
 
165
  # 11. Foot Dataset
166
  - vars:
 
176
  - type: llm-rubric
177
  subtype: vision
178
  value: |
179
+ The visualization image shows a foot with bone and tissue structures with a reasonable transfer function, and the object is shown clearly
180
 
181
  # 12. Frog Dataset
182
  - vars:
 
192
  - type: llm-rubric
193
  subtype: vision
194
  value: |
195
+ The visualization image shows a frog specimen with internal anatomy with a reasonable transfer function, and the object is shown clearly
196
 
197
  # 13. Fuel Dataset
198
  - vars:
 
208
  - type: llm-rubric
209
  subtype: vision
210
  value: |
211
+ The visualization image shows fuel combustion or related simulation with a reasonable transfer function, and the object is shown clearly
212
 
213
  # 14. Hydrogen Atom Dataset
214
  - vars:
 
224
  - type: llm-rubric
225
  subtype: vision
226
  value: |
227
+ The visualization image shows hydrogen atom orbital or probability distribution with a reasonable transfer function, and the object is shown clearly
228
 
229
  # 15. Lobster Dataset
230
  - vars:
 
240
  - type: llm-rubric
241
  subtype: vision
242
  value: |
243
+ The visualization image shows a lobster or crustacean anatomy with a reasonable transfer function, and the object is shown clearly
244
 
245
  # 16. Marschner-Lobb Dataset
246
  - vars:
 
256
  - type: llm-rubric
257
  subtype: vision
258
  value: |
259
+ The visualization image shows Marschner-Lobb synthetic test pattern with a reasonable transfer function, and the object is shown clearly
260
 
261
  # 17. MRI Ventricles Dataset
262
  - vars:
 
272
  - type: llm-rubric
273
  subtype: vision
274
  value: |
275
+ The visualization image shows brain ventricles or ventricular structures with a reasonable transfer function, and the object is shown clearly
276
 
277
  # 18. MRI Woman Dataset
278
  - vars:
 
288
  - type: llm-rubric
289
  subtype: vision
290
  value: |
291
+ The visualization image shows human anatomical structures from MRI scan with a reasonable transfer function, and the object is shown clearly
292
 
293
  # 19. MRT Angio Dataset
294
  - vars:
 
304
  - type: llm-rubric
305
  subtype: vision
306
  value: |
307
+ The visualization image shows angiography or vascular structures with a reasonable transfer function, and the object is shown clearly
308
 
309
  # 20. Neghip Dataset
310
  - vars:
 
320
  - type: llm-rubric
321
  subtype: vision
322
  value: |
323
+ The visualization image shows molecule structure with a reasonable transfer function, and the object is shown clearly
324
 
325
  # 21. Neocortical Layer 1 Axons Dataset
326
  - vars:
 
336
  - type: llm-rubric
337
  subtype: vision
338
  value: |
339
+ The visualization image shows neural axons or neocortical network structures with a reasonable transfer function, and the object is shown clearly
340
 
341
  # 22. Nucleon Dataset
342
  - vars:
 
352
  - type: llm-rubric
353
  subtype: vision
354
  value: |
355
+ Should visualize nucleon or particle physics data with a reasonable transfer function, and the object is shown clearly
356
 
357
  # 23. Pancreas Dataset
358
  - vars:
 
368
  - type: llm-rubric
369
  subtype: vision
370
  value: |
371
+ The visualization image shows pancreas or pancreatic anatomy with a reasonable transfer function, and the object is shown clearly
372
 
373
  # 24. Shockwave Dataset
374
  - vars:
 
384
  - type: llm-rubric
385
  subtype: vision
386
  value: |
387
+ The visualization image shows shockwave or wave propagation patterns with a reasonable transfer function, and the object is shown clearly
388
 
389
  # 25. Silicium Dataset
390
  - vars:
 
400
  - type: llm-rubric
401
  subtype: vision
402
  value: |
403
+ The visualization image shows silicon crystal or material structure with a reasonable transfer function, and the object is shown clearly
404
 
405
  # 26. Skull Dataset
406
  - vars:
 
432
  - type: llm-rubric
433
  subtype: vision
434
  value: |
435
+ The visualization image shows a statue leg or sculptural form with a reasonable transfer function, and the object is shown clearly
436
 
437
  # 28. Stent Dataset
438
  - vars:
 
459
  - type: llm-rubric
460
  subtype: vision
461
  value: |
462
+ The visualization image shows supernova or astrophysical explosion simulation with a reasonable transfer function, and the object is shown clearly
463
 
464
  # 30. TACC Turbulence Dataset
465
  - vars:
 
475
  - type: llm-rubric
476
  subtype: vision
477
  value: |
478
+ The visualization image shows turbulence or vortex flow structures with a reasonable transfer function, and the object is shown clearly
479
 
480
  # 31. Tooth Dataset
481
  - vars:
 
491
  - type: llm-rubric
492
  subtype: vision
493
  value: |
494
+ The visualization image shows tooth or dental anatomy with a reasonable transfer function, and the object is shown clearly
495
 
496
  # 32. Tornado Dataset
497
  - vars:
 
507
  - type: llm-rubric
508
  subtype: vision
509
  value: |
510
+ The visualization image shows tornado or vortex flow pattern with a reasonable transfer function, and the object is shown clearly
511
 
512
  # 33. Visible Male Dataset
513
  - vars:
 
523
  - type: llm-rubric
524
  subtype: vision
525
  value: |
526
+ The visualization image shows human anatomical structures with a reasonable transfer function, and the object is shown clearly
eval_cases/paraview/what_obj_cases_anonymized.yaml CHANGED
@@ -16,23 +16,23 @@
16
  - type: llm-rubric
17
  subtype: vision
18
  value: |
19
- The assistant should identify the data shows an aneurism or vascular structure
20
 
21
- # # 2. Backpack Dataset
22
- # - vars:
23
- # question: |
24
- # Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_002/data/data_002_512x512x373_uint16.raw".
25
- # Use visualization tools to determine what object is contained in this dataset. Save the paraview state as "anonymized_datasets/dataset_002/results/{agent_mode}/dataset_002.pvsm"
26
- # Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_002/results/{agent_mode}/answers.txt"
27
- # assert:
28
- # - type: llm-rubric
29
- # subtype: text
30
- # value: |
31
- # The assistant should identify that the data shows a backpack
32
- # - type: llm-rubric
33
- # subtype: vision
34
- # value: |
35
- # The assistant should identify that the data shows a backpack
36
 
37
  # 3. Blunt Fin Dataset
38
  - vars:
@@ -48,7 +48,7 @@
48
  - type: llm-rubric
49
  subtype: vision
50
  value: |
51
- The assistant should identify a fin or aerodynamic strcuture or simulation result in the data
52
 
53
  # 4. Bonsai Dataset
54
  - vars:
@@ -64,7 +64,7 @@
64
  - type: llm-rubric
65
  subtype: vision
66
  value: |
67
- Should identify a bonsai tree or botanical structure in the data
68
 
69
  # 5. Boston Teapot Dataset
70
  - vars:
@@ -80,7 +80,7 @@
80
  - type: llm-rubric
81
  subtype: vision
82
  value: |
83
- Should identify a teapot in the visualization
84
 
85
  # 6. Bunny Dataset
86
  - vars:
@@ -96,7 +96,7 @@
96
  - type: llm-rubric
97
  subtype: vision
98
  value: |
99
- Should identify a bunny or rabbit in the 3D scanned data
100
 
101
  # 7. Carp Dataset
102
  - vars:
@@ -112,7 +112,7 @@
112
  - type: llm-rubric
113
  subtype: vision
114
  value: |
115
- Should identify a carp or fish anatomy
116
 
117
  # 8. CSAFE Heptane Dataset
118
  - vars:
@@ -128,7 +128,7 @@
128
  - type: llm-rubric
129
  subtype: vision
130
  value: |
131
- Should recognize combustion or heptane simulation data
132
 
133
  # 9. Duct Dataset
134
  - vars:
@@ -144,7 +144,7 @@
144
  - type: llm-rubric
145
  subtype: vision
146
  value: |
147
- Should identify flow patterns in a duct geometry
148
 
149
  # 10. Engine Dataset
150
  - vars:
@@ -160,7 +160,7 @@
160
  - type: llm-rubric
161
  subtype: vision
162
  value: |
163
- Should identify an engine or mechanical components
164
 
165
  # 11. Foot Dataset
166
  - vars:
@@ -176,7 +176,7 @@
176
  - type: llm-rubric
177
  subtype: vision
178
  value: |
179
- Should identify a foot with bone and tissue structures
180
 
181
  # 12. Frog Dataset
182
  - vars:
@@ -192,7 +192,7 @@
192
  - type: llm-rubric
193
  subtype: vision
194
  value: |
195
- Should identify a frog specimen with internal anatomy
196
 
197
  # 13. Fuel Dataset
198
  - vars:
@@ -208,7 +208,7 @@
208
  - type: llm-rubric
209
  subtype: vision
210
  value: |
211
- Should identify fuel combustion or related simulation
212
 
213
  # 14. Hydrogen Atom Dataset
214
  - vars:
@@ -224,7 +224,7 @@
224
  - type: llm-rubric
225
  subtype: vision
226
  value: |
227
- Should recognize hydrogen atom orbital or probability distribution
228
 
229
  # 15. Lobster Dataset
230
  - vars:
@@ -240,7 +240,7 @@
240
  - type: llm-rubric
241
  subtype: vision
242
  value: |
243
- Should identify a lobster or crustacean anatomy
244
 
245
  # 16. Marschner-Lobb Dataset
246
  - vars:
@@ -256,7 +256,7 @@
256
  - type: llm-rubric
257
  subtype: vision
258
  value: |
259
- Should recognize Marschner-Lobb synthetic test pattern
260
 
261
  # 17. MRI Ventricles Dataset
262
  - vars:
@@ -272,7 +272,7 @@
272
  - type: llm-rubric
273
  subtype: vision
274
  value: |
275
- Should identify brain ventricles or ventricular structures
276
 
277
  # 18. MRI Woman Dataset
278
  - vars:
@@ -288,7 +288,7 @@
288
  - type: llm-rubric
289
  subtype: vision
290
  value: |
291
- Should identify human anatomical structures from MRI scan
292
 
293
  # 19. MRT Angio Dataset
294
  - vars:
@@ -304,7 +304,7 @@
304
  - type: llm-rubric
305
  subtype: vision
306
  value: |
307
- Should identify angiography or vascular structures
308
 
309
  # 20. Neghip Dataset
310
  - vars:
@@ -320,7 +320,7 @@
320
  - type: llm-rubric
321
  subtype: vision
322
  value: |
323
- Should visualize and describe molecule structure
324
 
325
  # 21. Neocortical Layer 1 Axons Dataset
326
  - vars:
@@ -336,7 +336,7 @@
336
  - type: llm-rubric
337
  subtype: vision
338
  value: |
339
- Should identify neural axons or neocortical network structures
340
 
341
  # 22. Nucleon Dataset
342
  - vars:
@@ -352,7 +352,7 @@
352
  - type: llm-rubric
353
  subtype: vision
354
  value: |
355
- Should visualize nucleon or particle physics data
356
 
357
  # 23. Pancreas Dataset
358
  - vars:
@@ -368,7 +368,7 @@
368
  - type: llm-rubric
369
  subtype: vision
370
  value: |
371
- Should identify pancreas or pancreatic anatomy
372
 
373
  # 24. Shockwave Dataset
374
  - vars:
@@ -384,7 +384,7 @@
384
  - type: llm-rubric
385
  subtype: vision
386
  value: |
387
- Should identify shockwave or wave propagation patterns
388
 
389
  # 25. Silicium Dataset
390
  - vars:
@@ -400,7 +400,7 @@
400
  - type: llm-rubric
401
  subtype: vision
402
  value: |
403
- Should identify silicon crystal or material structure
404
 
405
  # 26. Skull Dataset
406
  - vars:
@@ -432,7 +432,7 @@
432
  - type: llm-rubric
433
  subtype: vision
434
  value: |
435
- Should identify a statue leg or sculptural form
436
 
437
  # 28. Stent Dataset
438
  - vars:
@@ -459,7 +459,7 @@
459
  - type: llm-rubric
460
  subtype: vision
461
  value: |
462
- Should identify supernova or astrophysical explosion simulation
463
 
464
  # 30. TACC Turbulence Dataset
465
  - vars:
@@ -475,7 +475,7 @@
475
  - type: llm-rubric
476
  subtype: vision
477
  value: |
478
- Should identify turbulence or vortex flow structures
479
 
480
  # 31. Tooth Dataset
481
  - vars:
@@ -491,7 +491,7 @@
491
  - type: llm-rubric
492
  subtype: vision
493
  value: |
494
- Should identify tooth or dental anatomy
495
 
496
  # 32. Tornado Dataset
497
  - vars:
@@ -507,7 +507,7 @@
507
  - type: llm-rubric
508
  subtype: vision
509
  value: |
510
- Should identify tornado or vortex flow pattern
511
 
512
  # 33. Visible Male Dataset
513
  - vars:
@@ -523,4 +523,4 @@
523
  - type: llm-rubric
524
  subtype: vision
525
  value: |
526
- Should identify human anatomical structures
 
16
  - type: llm-rubric
17
  subtype: vision
18
  value: |
19
+ The visualization image shows an aneurism or vascular structure with a reasonable transfer function, and the object is shown clearly
20
 
21
+ # 2. Backpack Dataset
22
+ - vars:
23
+ question: |
24
+ Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_002/data/data_002_512x512x373_uint16.raw".
25
+ Use visualization tools to determine what object is contained in this dataset. Save the paraview state as "anonymized_datasets/dataset_002/results/{agent_mode}/dataset_002.pvsm"
26
+ Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_002/results/{agent_mode}/answers.txt"
27
+ assert:
28
+ - type: llm-rubric
29
+ subtype: text
30
+ value: |
31
+ The assistant should identify that the data shows a backpack
32
+ - type: llm-rubric
33
+ subtype: vision
34
+ value: |
35
+ The visualization image shows a backpack with a reasonable transfer function, and the object is shown clearly
36
 
37
  # 3. Blunt Fin Dataset
38
  - vars:
 
48
  - type: llm-rubric
49
  subtype: vision
50
  value: |
51
+ The visualization image shows a fin or aerodynamic strcuture or simulation result in the data with a reasonable transfer function, and the object is shown clearly
52
 
53
  # 4. Bonsai Dataset
54
  - vars:
 
64
  - type: llm-rubric
65
  subtype: vision
66
  value: |
67
+ The visualization image shows a bonsai tree or botanical structure in the data with a reasonable transfer function, and the object is shown clearly
68
 
69
  # 5. Boston Teapot Dataset
70
  - vars:
 
80
  - type: llm-rubric
81
  subtype: vision
82
  value: |
83
+ The visualization image shows a teapot in the visualization with a reasonable transfer function, and the object is shown clearly
84
 
85
  # 6. Bunny Dataset
86
  - vars:
 
96
  - type: llm-rubric
97
  subtype: vision
98
  value: |
99
+ The visualization image shows a bunny or rabbit in the 3D scanned data with a reasonable transfer function, and the object is shown clearly
100
 
101
  # 7. Carp Dataset
102
  - vars:
 
112
  - type: llm-rubric
113
  subtype: vision
114
  value: |
115
+ The visualization image shows a carp or fish anatomy with a reasonable transfer function, and the object is shown clearly
116
 
117
  # 8. CSAFE Heptane Dataset
118
  - vars:
 
128
  - type: llm-rubric
129
  subtype: vision
130
  value: |
131
+ The visualization image shows combustion or heptane simulation data with a reasonable transfer function, and the object is shown clearly
132
 
133
  # 9. Duct Dataset
134
  - vars:
 
144
  - type: llm-rubric
145
  subtype: vision
146
  value: |
147
+ The visualization image shows flow patterns in a duct geometry with a reasonable transfer function, and the object is shown clearly
148
 
149
  # 10. Engine Dataset
150
  - vars:
 
160
  - type: llm-rubric
161
  subtype: vision
162
  value: |
163
+ The visualization image shows an engine or mechanical components with a reasonable transfer function, and the object is shown clearly
164
 
165
  # 11. Foot Dataset
166
  - vars:
 
176
  - type: llm-rubric
177
  subtype: vision
178
  value: |
179
+ The visualization image shows a foot with bone and tissue structures with a reasonable transfer function, and the object is shown clearly
180
 
181
  # 12. Frog Dataset
182
  - vars:
 
192
  - type: llm-rubric
193
  subtype: vision
194
  value: |
195
+ The visualization image shows a frog specimen with internal anatomy with a reasonable transfer function, and the object is shown clearly
196
 
197
  # 13. Fuel Dataset
198
  - vars:
 
208
  - type: llm-rubric
209
  subtype: vision
210
  value: |
211
+ The visualization image shows fuel combustion or related simulation with a reasonable transfer function, and the object is shown clearly
212
 
213
  # 14. Hydrogen Atom Dataset
214
  - vars:
 
224
  - type: llm-rubric
225
  subtype: vision
226
  value: |
227
+ The visualization image shows hydrogen atom orbital or probability distribution with a reasonable transfer function, and the object is shown clearly
228
 
229
  # 15. Lobster Dataset
230
  - vars:
 
240
  - type: llm-rubric
241
  subtype: vision
242
  value: |
243
+ The visualization image shows a lobster or crustacean anatomy with a reasonable transfer function, and the object is shown clearly
244
 
245
  # 16. Marschner-Lobb Dataset
246
  - vars:
 
256
  - type: llm-rubric
257
  subtype: vision
258
  value: |
259
+ The visualization image shows Marschner-Lobb synthetic test pattern with a reasonable transfer function, and the object is shown clearly
260
 
261
  # 17. MRI Ventricles Dataset
262
  - vars:
 
272
  - type: llm-rubric
273
  subtype: vision
274
  value: |
275
+ The visualization image shows brain ventricles or ventricular structures with a reasonable transfer function, and the object is shown clearly
276
 
277
  # 18. MRI Woman Dataset
278
  - vars:
 
288
  - type: llm-rubric
289
  subtype: vision
290
  value: |
291
+ The visualization image shows human anatomical structures from MRI scan with a reasonable transfer function, and the object is shown clearly
292
 
293
  # 19. MRT Angio Dataset
294
  - vars:
 
304
  - type: llm-rubric
305
  subtype: vision
306
  value: |
307
+ The visualization image shows angiography or vascular structures with a reasonable transfer function, and the object is shown clearly
308
 
309
  # 20. Neghip Dataset
310
  - vars:
 
320
  - type: llm-rubric
321
  subtype: vision
322
  value: |
323
+ The visualization image shows molecule structure with a reasonable transfer function, and the object is shown clearly
324
 
325
  # 21. Neocortical Layer 1 Axons Dataset
326
  - vars:
 
336
  - type: llm-rubric
337
  subtype: vision
338
  value: |
339
+ The visualization image shows neural axons or neocortical network structures with a reasonable transfer function, and the object is shown clearly
340
 
341
  # 22. Nucleon Dataset
342
  - vars:
 
352
  - type: llm-rubric
353
  subtype: vision
354
  value: |
355
+ Should visualize nucleon or particle physics data with a reasonable transfer function, and the object is shown clearly
356
 
357
  # 23. Pancreas Dataset
358
  - vars:
 
368
  - type: llm-rubric
369
  subtype: vision
370
  value: |
371
+ The visualization image shows pancreas or pancreatic anatomy with a reasonable transfer function, and the object is shown clearly
372
 
373
  # 24. Shockwave Dataset
374
  - vars:
 
384
  - type: llm-rubric
385
  subtype: vision
386
  value: |
387
+ The visualization image shows shockwave or wave propagation patterns with a reasonable transfer function, and the object is shown clearly
388
 
389
  # 25. Silicium Dataset
390
  - vars:
 
400
  - type: llm-rubric
401
  subtype: vision
402
  value: |
403
+ The visualization image shows silicon crystal or material structure with a reasonable transfer function, and the object is shown clearly
404
 
405
  # 26. Skull Dataset
406
  - vars:
 
432
  - type: llm-rubric
433
  subtype: vision
434
  value: |
435
+ The visualization image shows a statue leg or sculptural form with a reasonable transfer function, and the object is shown clearly
436
 
437
  # 28. Stent Dataset
438
  - vars:
 
459
  - type: llm-rubric
460
  subtype: vision
461
  value: |
462
+ The visualization image shows supernova or astrophysical explosion simulation with a reasonable transfer function, and the object is shown clearly
463
 
464
  # 30. TACC Turbulence Dataset
465
  - vars:
 
475
  - type: llm-rubric
476
  subtype: vision
477
  value: |
478
+ The visualization image shows turbulence or vortex flow structures with a reasonable transfer function, and the object is shown clearly
479
 
480
  # 31. Tooth Dataset
481
  - vars:
 
491
  - type: llm-rubric
492
  subtype: vision
493
  value: |
494
+ The visualization image shows tooth or dental anatomy with a reasonable transfer function, and the object is shown clearly
495
 
496
  # 32. Tornado Dataset
497
  - vars:
 
507
  - type: llm-rubric
508
  subtype: vision
509
  value: |
510
+ The visualization image shows tornado or vortex flow pattern with a reasonable transfer function, and the object is shown clearly
511
 
512
  # 33. Visible Male Dataset
513
  - vars:
 
523
  - type: llm-rubric
524
  subtype: vision
525
  value: |
526
+ The visualization image shows human anatomical structures with a reasonable transfer function, and the object is shown clearly