KuangshiAi commited on
Commit ·
77dc289
1
Parent(s): be772b8
merge chatvis bench and main
Browse filesThis view is limited to 50 files because it contains too many changes.
See raw diff
- .gitignore +1 -1
- eval_cases/paraview/category_specific_cases.yaml +0 -218
- eval_cases/paraview/chatvis_bench_cases.yaml +0 -465
- eval_cases/paraview/{main_cases.yaml → paraview_cases.yaml} +507 -0
- eval_cases/paraview/what_obj_cases.yaml +20 -116
- eval_cases/paraview/what_obj_cases_anonymized.yaml +0 -526
- main/bonsai/.DS_Store +0 -0
- main/bonsai/GS/.DS_Store +0 -0
- {main → paraview}/ABC/GS/ABC_gs.png +0 -0
- {main → paraview}/ABC/GS/ABC_gs.pvsm +0 -0
- {main → paraview}/ABC/GS/ABC_gs.py +0 -0
- {main → paraview}/ABC/data/ABC.txt +0 -0
- {main → paraview}/ABC/data/ABC_128x128x128_float32_scalar3.raw +0 -0
- {main → paraview}/ABC/task_description.txt +0 -0
- {main → paraview}/ABC/visualization_goals.txt +0 -0
- {main → paraview}/Bernard/GS/Bernard_gs.png +0 -0
- {main → paraview}/Bernard/GS/Bernard_gs.pvsm +0 -0
- {main → paraview}/Bernard/GS/Bernard_gs.py +0 -0
- {main → paraview}/Bernard/data/Bernard.txt +0 -0
- {main → paraview}/Bernard/data/Bernard_128x32x64_float32_scalar3.raw +0 -0
- {main → paraview}/Bernard/task_description.txt +0 -0
- {main → paraview}/Bernard/visualization_goals.txt +0 -0
- {chatvis_bench → paraview}/README.md +0 -0
- {main → paraview}/argon-bubble/GS/CMakeLists.txt +0 -0
- {main → paraview}/argon-bubble/GS/argon-bubble_gs.cxx +0 -0
- {main → paraview}/argon-bubble/GS/argon-bubble_gs.png +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeCache.txt +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CMakeCCompiler.cmake +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CMakeCXXCompiler.cmake +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CMakeDetermineCompilerABI_C.bin +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CMakeDetermineCompilerABI_CXX.bin +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CMakeSystem.cmake +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdC/CMakeCCompilerId.c +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdC/a.out +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdC/apple-sdk.c +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdCXX/CMakeCXXCompilerId.cpp +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdCXX/a.out +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdCXX/apple-sdk.cpp +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/CMakeConfigureLog.yaml +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/CMakeDirectoryInformation.cmake +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/InstallScripts.json +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/Makefile.cmake +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/Makefile2 +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/TargetDirectories.txt +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/DependInfo.cmake +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/argon-bubble_gs.cxx.o +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/argon-bubble_gs.cxx.o.d +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/build.make +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/cmake_clean.cmake +0 -0
- {main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/compiler_depend.make +0 -0
.gitignore
CHANGED
|
@@ -7,4 +7,4 @@ statistics/
|
|
| 7 |
.cache/
|
| 8 |
.claude/
|
| 9 |
.vscode/
|
| 10 |
-
|
|
|
|
| 7 |
.cache/
|
| 8 |
.claude/
|
| 9 |
.vscode/
|
| 10 |
+
backup/
|
eval_cases/paraview/category_specific_cases.yaml
DELETED
|
@@ -1,218 +0,0 @@
|
|
| 1 |
-
# Medical/Anatomical Data Visualization Test Cases for SciVisAgentBench
|
| 2 |
-
# Tests scalar volume visualization capabilities for medical imaging data
|
| 3 |
-
|
| 4 |
-
# Test 1: Basic Volume Rendering and Tissue Identification
|
| 5 |
-
- vars:
|
| 6 |
-
question: |
|
| 7 |
-
Clear the ParaView pipeline and load the data file "foot/data/foot_256x256x256_uint8.raw".
|
| 8 |
-
1. Enable volume rendering to visualize the internal structures
|
| 9 |
-
2. Adjust the opacity transfer function to reveal both bone and soft tissue (bone should be more opaque, soft tissue semi-transparent)
|
| 10 |
-
3. Set an appropriate color map to differentiate tissue types (e.g., white/beige for bone, reddish for soft tissue)
|
| 11 |
-
Finally, save the paraview state as "foot/results/{agent_mode}/foot.pvsm"
|
| 12 |
-
assert:
|
| 13 |
-
- type: llm-rubric
|
| 14 |
-
value: |
|
| 15 |
-
- Successfully load the foot dataset
|
| 16 |
-
- Enable volume rendering
|
| 17 |
-
- Adjust opacity to show both bone and soft tissue structures
|
| 18 |
-
- Apply appropriate color mapping for tissue differentiation
|
| 19 |
-
- Use screenshot to verify foot bones (metatarsals, phalanges) and soft tissue are visible
|
| 20 |
-
- Verify the colors match the instruction (white/beige for bone, reddish for soft tissue)
|
| 21 |
-
|
| 22 |
-
# # Test 2: Multi-Isosurface Segmentation
|
| 23 |
-
# - vars:
|
| 24 |
-
# question: |
|
| 25 |
-
# Clear the ParaView pipeline and load the data file "mri_ventricles/data/mri_ventricles_256x256x124_uint8.raw".
|
| 26 |
-
# 1. Create at least 3 different isosurfaces at different threshold values to segment different tissue types
|
| 27 |
-
# 2. Color each isosurface differently to distinguish structures
|
| 28 |
-
# 3. Make appropriate surfaces semi-transparent if needed to show internal structures
|
| 29 |
-
# Finally, save the paraview state as "mri_ventricles/results/{agent_mode}/mri_ventricles.pvsm"
|
| 30 |
-
# assert:
|
| 31 |
-
# - type: llm-rubric
|
| 32 |
-
# value: |
|
| 33 |
-
# - Create multiple isosurfaces (at least 3) at different threshold values
|
| 34 |
-
# - Apply different colors to each isosurface for clear distinction
|
| 35 |
-
# - Use screenshot to verify brain ventricles are successfully segmented and visible
|
| 36 |
-
# - Verify transparency is applied where needed to show nested structures
|
| 37 |
-
# - Report identification of brain structures (ventricles, grey/white matter boundaries)
|
| 38 |
-
|
| 39 |
-
# # Test 3: Cross-Sectional Analysis
|
| 40 |
-
# - vars:
|
| 41 |
-
# question: |
|
| 42 |
-
# Clear the ParaView pipeline and load the data file "skull/data/skull_256x256x256_uint8.raw".
|
| 43 |
-
# 1. Create three orthogonal slices (axial, sagittal, and coronal planes)
|
| 44 |
-
# 2. Position the slices to show key anatomical features of the skull
|
| 45 |
-
# 3. Apply an appropriate color map to the slices
|
| 46 |
-
# Finally, save the paraview state as "skull/results/{agent_mode}/skull.pvsm"
|
| 47 |
-
# assert:
|
| 48 |
-
# - type: llm-rubric
|
| 49 |
-
# value: |
|
| 50 |
-
|
| 51 |
-
# - Create exactly three orthogonal slices (axial, sagittal, coronal)
|
| 52 |
-
# - Use screenshot to verify all three slice planes are visible simultaneously
|
| 53 |
-
# - Verify slices show key features: cranial cavity, eye sockets, nasal cavity
|
| 54 |
-
# - Report which anatomical features are visible in each specific plane
|
| 55 |
-
|
| 56 |
-
# # Test 4: Vascular Structure Visualization
|
| 57 |
-
# - vars:
|
| 58 |
-
# question: |
|
| 59 |
-
# Clear the ParaView pipeline and load the data file "aneurism/data/aneurism_256x256x256_uint8.raw".
|
| 60 |
-
# 1. Use appropriate visualization technique to isolate and display the vascular structure
|
| 61 |
-
# 2. Create an isosurface that clearly shows the aneurysm and blood vessels
|
| 62 |
-
# 3. Apply a red or red-gradient color map appropriate for vascular visualization
|
| 63 |
-
# 4. Compute and report the surface area of the vascular structure
|
| 64 |
-
# Finally, save the paraview state as "aneurism/results/{agent_mode}/aneurism.pvsm"
|
| 65 |
-
# assert:
|
| 66 |
-
# - type: llm-rubric
|
| 67 |
-
# value: |
|
| 68 |
-
|
| 69 |
-
# - Successfully isolate vascular structure using isosurface
|
| 70 |
-
# - Use screenshot to verify aneurysm bulge is clearly visible
|
| 71 |
-
# - Verify red/red-gradient coloring is applied to vessels
|
| 72 |
-
# - Successfully compute and report numerical surface area value
|
| 73 |
-
|
| 74 |
-
# # Test 5: Histogram Analysis and Tissue Classification
|
| 75 |
-
# - vars:
|
| 76 |
-
# question: |
|
| 77 |
-
# Clear the ParaView pipeline and load the data file "pancreas/data/pancreas_240x512x512_int16.raw".
|
| 78 |
-
# 1. Generate a histogram of the intensity values with 256 bins
|
| 79 |
-
# 2. Based on the histogram, identify distinct peaks corresponding to different tissue types
|
| 80 |
-
# 3. Create threshold filters to isolate pancreatic tissue based on the histogram analysis
|
| 81 |
-
# 4. Apply volume rendering with opacity settings based on your histogram findings
|
| 82 |
-
# Finally, save the paraview state as "pancreas/results/{agent_mode}/pancreas.pvsm"
|
| 83 |
-
# assert:
|
| 84 |
-
# - type: llm-rubric
|
| 85 |
-
# value: |
|
| 86 |
-
|
| 87 |
-
# - Successfully generate histogram with 256 bins
|
| 88 |
-
# - Report specific intensity values for identified peaks
|
| 89 |
-
# - Create threshold filters using values derived from histogram peaks
|
| 90 |
-
# - Apply volume rendering with opacity based on histogram analysis
|
| 91 |
-
# - Use screenshot to verify pancreatic tissue is properly isolated
|
| 92 |
-
|
| 93 |
-
# # Test 6: Complex Organ System Visualization
|
| 94 |
-
# - vars:
|
| 95 |
-
# question: |
|
| 96 |
-
# Clear the ParaView pipeline and load the data file "mri_woman/data/mri_woman_256x256x109_uint16.raw".
|
| 97 |
-
# 1. Enable volume rendering to show internal anatomy
|
| 98 |
-
# 2. Adjust the transfer functions to visualize multiple organ systems simultaneously
|
| 99 |
-
# 3. Create a clip plane to show a sagittal cross-section while maintaining volume rendering
|
| 100 |
-
# 4. Use appropriate color and opacity settings to distinguish between organs
|
| 101 |
-
# Finally, save the paraview state as "mri_woman/results/{agent_mode}/mri_woman.pvsm"
|
| 102 |
-
# assert:
|
| 103 |
-
# - type: llm-rubric
|
| 104 |
-
# value: |
|
| 105 |
-
|
| 106 |
-
# - Enable volume rendering successfully
|
| 107 |
-
# - Adjust transfer functions to reveal multiple organ systems
|
| 108 |
-
# - Create clip plane in sagittal orientation
|
| 109 |
-
# - Use screenshots from anterior and lateral views to verify organ visibility
|
| 110 |
-
# - List identified organs (e.g., heart, lungs, liver, spine)
|
| 111 |
-
# - Verify clip plane and volume rendering work together
|
| 112 |
-
|
| 113 |
-
# # Test 7: Small Animal Specimen Analysis
|
| 114 |
-
# - vars:
|
| 115 |
-
# question: |
|
| 116 |
-
# Clear the ParaView pipeline and load the data file "frog/data/frog_256x256x44_uint8.raw".
|
| 117 |
-
# 1. Create visualization showing both skeletal and soft tissue structures
|
| 118 |
-
# 2. Use either multiple isosurfaces or volume rendering with careful transfer functions
|
| 119 |
-
# 3. Generate a plot-over-line measurement through the specimen (dorsal to ventral)
|
| 120 |
-
# Finally, save the paraview state as "frog/results/{agent_mode}/frog.pvsm"
|
| 121 |
-
# assert:
|
| 122 |
-
# - type: llm-rubric
|
| 123 |
-
# value: |
|
| 124 |
-
|
| 125 |
-
# - Choose appropriate technique (isosurfaces or volume rendering)
|
| 126 |
-
# - Use screenshot to verify both skeleton and soft tissue are visible
|
| 127 |
-
# - Successfully create plot-over-line from dorsal to ventral
|
| 128 |
-
# - Report numerical values from plot-over-line measurement
|
| 129 |
-
# - Verify measurement traverses through the specimen correctly
|
| 130 |
-
|
| 131 |
-
# # Test 8: Dental Structure Analysis
|
| 132 |
-
# - vars:
|
| 133 |
-
# question: |
|
| 134 |
-
# Clear the ParaView pipeline and load the data file "tooth/data/tooth_103x94x161_uint8.raw".
|
| 135 |
-
# 1. Create isosurface to show the tooth enamel (outer layer)
|
| 136 |
-
# 2. Use volume rendering or additional isosurface to show internal structures (dentin, pulp cavity)
|
| 137 |
-
# 3. Apply appropriate colors (white for enamel, yellow for dentin)
|
| 138 |
-
# Finally, save the paraview state as "tooth/results/{agent_mode}/tooth.pvsm"
|
| 139 |
-
# assert:
|
| 140 |
-
# - type: llm-rubric
|
| 141 |
-
# value: |
|
| 142 |
-
|
| 143 |
-
# - Create isosurface at appropriate threshold for enamel
|
| 144 |
-
# - Use screenshot to verify white color on enamel and yellow/amber color on dentin
|
| 145 |
-
# - Identify enamel, dentin, and pulp cavity structures
|
| 146 |
-
|
| 147 |
-
# # Test 9: Abdominal CT with Vascular Stent Visualization
|
| 148 |
-
# - vars:
|
| 149 |
-
# question: |
|
| 150 |
-
# Clear the ParaView pipeline and load the data file "stent/data/stent_512x512x174_uint16.raw".
|
| 151 |
-
# This is an abdominal/pelvic CT scan containing a stent in the abdominal aorta (no contrast agent used).
|
| 152 |
-
# 1. Create a volume rendering to show the overall abdominal anatomy
|
| 153 |
-
# 2. Adjust the opacity transfer function to visualize bones (spine, pelvis) and soft tissue
|
| 154 |
-
# 3. Create an isosurface at a high threshold value to isolate and highlight the metallic stent
|
| 155 |
-
# 4. Apply appropriate colors - bone white/beige, soft tissue reddish, metallic grey for the stent
|
| 156 |
-
# Finally, save the paraview state as "stent/results/{agent_mode}/stent.pvsm"
|
| 157 |
-
|
| 158 |
-
# assert:
|
| 159 |
-
# - type: llm-rubric
|
| 160 |
-
# value: |
|
| 161 |
-
|
| 162 |
-
# - Create volume rendering of full abdomen/pelvis
|
| 163 |
-
# - Use screenshot to verify spine and pelvis are visible
|
| 164 |
-
# - Create high-threshold isosurface to isolate metallic stent
|
| 165 |
-
# - Verify stent appears with metallic/grey coloring
|
| 166 |
-
|
| 167 |
-
# # # Test 10: Comparative Analysis with State Saving
|
| 168 |
-
# # - vars:
|
| 169 |
-
# # question: |
|
| 170 |
-
# # Clear the ParaView pipeline and load the data file "vis_male/data/vis_male_128x256x256_uint8.raw".
|
| 171 |
-
# # 1. Create two different visualization approaches:
|
| 172 |
-
# # a) Volume rendering optimized for soft tissue
|
| 173 |
-
# # b) Isosurface extraction for skeletal system
|
| 174 |
-
# # 2. Save the ParaView state file to preserve your visualization setup
|
| 175 |
-
# # 3. Create a text report comparing the effectiveness of both techniques
|
| 176 |
-
# # assert:
|
| 177 |
-
# # - type: llm-rubric
|
| 178 |
-
# # value: |
|
| 179 |
-
# #
|
| 180 |
-
# # - Create volume rendering with soft tissue emphasis
|
| 181 |
-
# # - Create separate isosurface for skeletal system
|
| 182 |
-
# # - Use screenshots to document both approaches
|
| 183 |
-
# # - Successfully save .pvsm state file
|
| 184 |
-
# # - Write and save comparative analysis as text file
|
| 185 |
-
# # - Report specific advantages/disadvantages of each technique
|
| 186 |
-
# # - Verify both visualizations show distinct anatomical features
|
| 187 |
-
|
| 188 |
-
# # Test 11: Marine Biology Specimen
|
| 189 |
-
# - vars:
|
| 190 |
-
# question: |
|
| 191 |
-
# Clear the ParaView pipeline and load the data file "lobster/data/lobster_301x324x56_uint8.raw".
|
| 192 |
-
# 1. Create visualization showing the exoskeleton and internal anatomy
|
| 193 |
-
# 2. Adjust the visualization to show the prominent structure
|
| 194 |
-
# Finally, save the paraview state as "lobster/results/{agent_mode}/lobster.pvsm"
|
| 195 |
-
# assert:
|
| 196 |
-
# - type: llm-rubric
|
| 197 |
-
# value: |
|
| 198 |
-
|
| 199 |
-
# - Choose appropriate visualization for exoskeleton (isosurface or volume)
|
| 200 |
-
# - Use screenshot to verify whether specific features can be identified: claws, abdomen, tail fan
|
| 201 |
-
|
| 202 |
-
# # Test 12: Fish Anatomy Visualization
|
| 203 |
-
# - vars:
|
| 204 |
-
# question: |
|
| 205 |
-
# Clear the ParaView pipeline and load the data file "carp/data/carp_256x256x512_uint16.raw".
|
| 206 |
-
# 1. Enable volume rendering to show internal fish anatomy
|
| 207 |
-
# 2. Adjust transfer functions to reveal skeletal structure and organs
|
| 208 |
-
# 3. Create a sagittal slice through the fish body
|
| 209 |
-
# 4. Use color mapping that differentiates tissue types
|
| 210 |
-
# 5. Reset camera with appropriate padding to frame the entire fish
|
| 211 |
-
# Finally, save the paraview state as "carp/results/{agent_mode}/carp.pvsm"
|
| 212 |
-
# assert:
|
| 213 |
-
# - type: llm-rubric
|
| 214 |
-
# value: |
|
| 215 |
-
|
| 216 |
-
# - The volume rendering show both skeleton and organs
|
| 217 |
-
# - Create sagittal slice along fish body length
|
| 218 |
-
# - Verify sagittal slice shows internal structure along body axis
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
eval_cases/paraview/chatvis_bench_cases.yaml
DELETED
|
@@ -1,465 +0,0 @@
|
|
| 1 |
-
# 1. line-plot
|
| 2 |
-
- vars:
|
| 3 |
-
question: |
|
| 4 |
-
Read the dataset in the file "line-plot/data/line-plot.ex2", and print the number of components and the range of all the variables.
|
| 5 |
-
Show a default view of the dataset, colored by the variable Pres.
|
| 6 |
-
Create a line plot over all the variables in the dataset, from (0,0,0) to (0,0,10).
|
| 7 |
-
Write the values of the line plot in the file "line-plot/results/{agent_mode}/line-plot.csv", and save a screenshot of the line plot in "line-plot/results/{agent_mode}/line-plot.png".
|
| 8 |
-
Finally, save the ParaView state as "line-plot/results/{agent_mode}/line-plot.pvsm"
|
| 9 |
-
|
| 10 |
-
assert:
|
| 11 |
-
- type: llm-rubric
|
| 12 |
-
subtype: vision
|
| 13 |
-
value: |
|
| 14 |
-
1. Line Visualization Quality: Are multiple distinct lines clearly visible and properly rendered showing the evolution of different variables along the specified path?
|
| 15 |
-
|
| 16 |
-
2. Variable Differentiation: Are all dataset variables visually distinguishable through distinct colors or line styles with clear separation between curves?
|
| 17 |
-
|
| 18 |
-
3. Axis and Scale Appropriateness: Do the plot axes display appropriate ranges and scaling that effectively show the data trends and variations?
|
| 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:
|
| 34 |
-
- type: llm-rubric
|
| 35 |
-
subtype: vision
|
| 36 |
-
value: |
|
| 37 |
-
1. Volume Rendering Quality: Is the volume rendering properly generated with appropriate opacity and color mapping that reveals internal structures?
|
| 38 |
-
|
| 39 |
-
2. Transfer Function Application: Does the default transfer function effectively highlight meaningful data features and provide good visual contrast?
|
| 40 |
-
|
| 41 |
-
3. Isometric View Setup: Is the visualization displayed from an isometric viewpoint that provides a clear three-dimensional perspective of the volume?
|
| 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:
|
| 53 |
-
- type: llm-rubric
|
| 54 |
-
subtype: vision
|
| 55 |
-
value: |
|
| 56 |
-
1. Isosurface Generation: Is the isosurface properly generated at the specified value (0.5) with correct topology and continuity?
|
| 57 |
-
|
| 58 |
-
2. Surface Rendering Quality: Does the isosurface display smooth surfaces with appropriate shading and lighting that reveals the 3D structure?
|
| 59 |
-
|
| 60 |
-
3. Geometric Accuracy: Are the surface features geometrically correct and free from artifacts or discontinuities?
|
| 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:
|
| 78 |
-
- type: llm-rubric
|
| 79 |
-
subtype: vision
|
| 80 |
-
value: |
|
| 81 |
-
1. Slice Generation: Is the y-z plane slice properly generated at x=0 position showing the correct cross-section of the volume?
|
| 82 |
-
|
| 83 |
-
2. Contour on Slice: Are the contour lines at value 0.5 correctly extracted from the slice and properly displayed?
|
| 84 |
-
|
| 85 |
-
3. Red Color Application: Is the contour visualization properly colored red as specified in the requirements?
|
| 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:
|
| 102 |
-
- type: llm-rubric
|
| 103 |
-
subtype: vision
|
| 104 |
-
value: |
|
| 105 |
-
1. Delaunay Triangulation Quality: Is the 3D Delaunay triangulation properly generated creating a valid mesh structure from the point data?
|
| 106 |
-
|
| 107 |
-
2. Clipping Accuracy: Is the mesh correctly clipped by the y-z plane at x=0, with only the -x half of the data remaining visible?
|
| 108 |
-
|
| 109 |
-
3. Wireframe Representation: Is the result displayed as a clear wireframe showing the triangulated mesh structure with visible edges?
|
| 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
|
| 128 |
-
subtype: vision
|
| 129 |
-
value: |
|
| 130 |
-
1. Sphere Creation and Resolution: Is the sphere created with doubled theta resolution providing higher geometric detail and smoother curvature?
|
| 131 |
-
|
| 132 |
-
2. Shrink Filter Application: Is the shrink filter properly applied with halved shrink factor creating visible separation between mesh elements?
|
| 133 |
-
|
| 134 |
-
3. Dual Representation: Are both the wireframe sphere and shrink filter results simultaneously visible and properly grouped together?
|
| 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
|
| 154 |
-
subtype: vision
|
| 155 |
-
value: |
|
| 156 |
-
1. Streamline Generation: Are streamlines properly traced following the V variable flow field with appropriate seeding from the point cloud?
|
| 157 |
-
|
| 158 |
-
2. Tube and Glyph Rendering: Are streamlines rendered as tubes with cone glyphs properly attached showing flow direction and magnitude?
|
| 159 |
-
|
| 160 |
-
3. Temperature Color Mapping: Are both streamlines and glyphs correctly colored by the Temp variable with appropriate color scaling?
|
| 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: |
|
| 167 |
-
Read the dataset in the file "time-varying/data/time-varying.ex2", and color the data by the EQPS variable.
|
| 168 |
-
Viewing in the +y direction, play an animation through the time steps, with visible color bar legend.
|
| 169 |
-
Rescale the data range to last time step, and play the animation again.
|
| 170 |
-
Create a second linked render view to the right of the first, applying a temporal interpolator to the second view.
|
| 171 |
-
Play the animation simultaneously in both views, and save the animation of both views in "time-varying/results/{agent_mode}/time-varying.avi".
|
| 172 |
-
Print the following statistics: average value of EQPS over all locations and all time steps, average value of EQPS over all locations in the first half of the time steps, average value of EQPS over all locations in the even numbered time steps, and variance of EQPS over all locations and all the time steps.
|
| 173 |
-
Finally, save the ParaView state as "time-varying/results/{agent_mode}/time-varying.pvsm"
|
| 174 |
-
|
| 175 |
-
assert:
|
| 176 |
-
- type: llm-rubric
|
| 177 |
-
subtype: vision
|
| 178 |
-
value: |
|
| 179 |
-
1. Temporal Animation Quality: Does the animation smoothly progress through all time steps showing the evolution of the EQPS variable over time?
|
| 180 |
-
|
| 181 |
-
2. Dual View Configuration: Are both render views properly configured with the second view showing temporal interpolation effects compared to the first?
|
| 182 |
-
|
| 183 |
-
3. Color Mapping and Legend: Is the EQPS variable properly color-mapped with an appropriate color bar legend visible throughout the animation?
|
| 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: |
|
| 190 |
-
Create a wavelet object.
|
| 191 |
-
Create a plot over line chart from the wavelet with three paths: arc_length, Points_Z, and RTData variables with opacity for arc_length 1 and opacity for Points_Z and RTData 0.3.
|
| 192 |
-
Save a screenshot in "chart-opacity/results/{agent_mode}/chart-opacity.png".
|
| 193 |
-
Finally, save the ParaView state as "chart-opacity/results/{agent_mode}/chart-opacity.pvsm"
|
| 194 |
-
|
| 195 |
-
assert:
|
| 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:
|
| 228 |
-
- type: llm-rubric
|
| 229 |
-
subtype: vision
|
| 230 |
-
value: |
|
| 231 |
-
1. Block Color Mapping: Is the dataset properly colored by vtkBlockColors field with distinct block visualization?
|
| 232 |
-
|
| 233 |
-
2. Individual Block Coloring: Is block_2 correctly colored using the x component of the ACCL variable with appropriate scaling?
|
| 234 |
-
|
| 235 |
-
3. Color Transfer Functions: Are the color transfer functions properly applied with cool to warm coloring for the ACCL variable?
|
| 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: |
|
| 242 |
-
Create a wavelet object.
|
| 243 |
-
Create a new calculator with the function 'RTData*iHat + ln(RTData)*jHat + coordsZ*kHat'.
|
| 244 |
-
Get a color transfer function/color map and opacity transfer function/opacity map for the result of the calculation, scaling the color and/or opacity maps to the data range.
|
| 245 |
-
For a surface representation, color by the x coordinate of the result using a cool to warm color map, show the color bar/color legend, and save a screenshot of size 1158 x 833 pixels in "color-data/results/{agent_mode}/color-data.png".
|
| 246 |
-
Finally, save the ParaView state as "color-data/results/{agent_mode}/color-data.pvsm"
|
| 247 |
-
|
| 248 |
-
assert:
|
| 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:
|
| 260 |
-
question: |
|
| 261 |
-
Create a wavelet object.
|
| 262 |
-
Create a surface rendering of the wavelet object and color by RTData.
|
| 263 |
-
Scale the color map to the data, and don't display the color bar or the orientation axes.
|
| 264 |
-
Export the view to "export-gltf/results/{agent_mode}/ExportedGLTF.gltf".
|
| 265 |
-
|
| 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"
|
| 273 |
-
|
| 274 |
-
assert:
|
| 275 |
-
- type: llm-rubric
|
| 276 |
-
subtype: vision
|
| 277 |
-
value: |
|
| 278 |
-
1. GLTF Export Quality: Is the wavelet object properly exported to GLTF format with correct surface representation and RTData coloring?
|
| 279 |
-
|
| 280 |
-
2. GLTF Import and Display: Is the exported GLTF file successfully loaded and displayed as a surface with proper geometry?
|
| 281 |
-
|
| 282 |
-
3. Texture Coordinate Coloring: Is the imported GLTF object correctly colored by TEXCOORD_0 with Cool to Warm colormap?
|
| 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: |
|
| 289 |
-
Load the "BlueGrayBackground" palette.
|
| 290 |
-
Read the file "import-gltf/data/import-gltf.glb" and import the nodes "/assembly/Axle", "assembly/OuterRing/Torus002", and "assembly/OuterRing/MiddleRing/InnerRing".
|
| 291 |
-
Set the layout size to 300x300 pixels.
|
| 292 |
-
Point the camera in the positive Y direction and zoom to fit.
|
| 293 |
-
Make sure all views are rendered, then save a screenshot to "import-gltf/results/{agent_mode}/import-gltf.png".
|
| 294 |
-
Finally, save the ParaView state as "import-gltf/results/{agent_mode}/import-gltf.pvsm"
|
| 295 |
-
|
| 296 |
-
assert:
|
| 297 |
-
- type: llm-rubric
|
| 298 |
-
subtype: vision
|
| 299 |
-
value: |
|
| 300 |
-
1. GLTF Import Success: Are the specified GLTF nodes properly imported and displayed as separate geometric components?
|
| 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:
|
| 321 |
-
- type: llm-rubric
|
| 322 |
-
subtype: vision
|
| 323 |
-
value: |
|
| 324 |
-
1. Wavelet Visualization: Is the wavelet object properly rendered with RTDATA coloring and visible color bar?
|
| 325 |
-
|
| 326 |
-
2. Split View Layout: Is the view correctly split with the wavelet visualization on the left and histogram on the right?
|
| 327 |
-
|
| 328 |
-
3. Histogram Generation: Is the histogram properly generated from RTDATA showing the data distribution?
|
| 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: |
|
| 335 |
-
Create a Wavelet object, set its representation to "Surface with Edges", and set the camera direction to [0.5, 1, 0.5].
|
| 336 |
-
Save a screenshot to the file "reset-camera-direction/results/{agent_mode}/reset-camera-direction.png".
|
| 337 |
-
Finally, save the ParaView state as "reset-camera-direction/results/{agent_mode}/reset-camera-direction.pvsm"
|
| 338 |
-
|
| 339 |
-
assert:
|
| 340 |
-
- type: llm-rubric
|
| 341 |
-
subtype: vision
|
| 342 |
-
value: |
|
| 343 |
-
1. Wavelet Creation: Is the Wavelet object properly created and displayed in the scene?
|
| 344 |
-
|
| 345 |
-
2. Surface with Edges Representation: Is the wavelet correctly displayed with "Surface with Edges" representation showing both surface and wireframe?
|
| 346 |
-
|
| 347 |
-
3. Camera Direction: Is the camera positioned according to the specified direction vector [0.5, 1, 0.5]?
|
| 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:
|
| 372 |
-
question: |
|
| 373 |
-
Read the file "subseries-of-time-series/data/subseries-of-time-series.ex2". Load two element blocks: the first is called 'Unnamed block ID: 1 Type: HEX', the second is called 'Unnamed block ID: 2 Type: HEX'.
|
| 374 |
-
Next, slice this object with a plane with origin at [0.21706008911132812, 4.0, -5.110947132110596] and normal direction [1.0, 0.0, 0.0]. The plane should have no offset.
|
| 375 |
-
Next, save this time series to a collection of .vtm files. The base file name for the time series is "subseries-of-time-series/results/{agent_mode}/canslices.vtm" and the suffix is '_%d'. Only save time steps with index between 10 and 20 inclusive, counting by 3.
|
| 376 |
-
Next, load the files "subseries-of-time-series/results/{agent_mode}/canslices_10.vtm", "subseries-of-time-series/results/{agent_mode}/canslices_13.vtm", "subseries-of-time-series/results/{agent_mode}/canslices_16.vtm", and "subseries-of-time-series/results/{agent_mode}/canslices_19.vtm" in multi-block format.
|
| 377 |
-
Finally, show the multi-block data set you just loaded.
|
| 378 |
-
Save a screenshot to the file "subseries-of-time-series/results/{agent_mode}/subseries-of-time-series.png".
|
| 379 |
-
Finally, save the ParaView state as "subseries-of-time-series/results/{agent_mode}/subseries-of-time-series.pvsm"
|
| 380 |
-
|
| 381 |
-
assert:
|
| 382 |
-
- type: llm-rubric
|
| 383 |
-
subtype: vision
|
| 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:
|
| 405 |
-
- type: llm-rubric
|
| 406 |
-
subtype: vision
|
| 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 |
-
|
| 431 |
-
assert:
|
| 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:
|
| 443 |
-
question: |
|
| 444 |
-
Compare two datasets in two views side by side each 900 pixels wide x 1400 pixels high.
|
| 445 |
-
Read the dataset "materials/data/materials_prediction.vtr" in the left view and "materials/data/materials_ground_truth.vtr" in the right view.
|
| 446 |
-
In both views, convert the "Intensity" and "Phase" variables from cell to point data.
|
| 447 |
-
In both views, take an isovolume of the "Intensity" variable in the range of [0.2, 1.0], clipped with a plane at (32.0, 32.0, 32.0) and +x normal direction.
|
| 448 |
-
Color both views with the Viridis (matplotlib) color map for the "Phase" variable, scaled to the data range, including a colormap legend in both views.
|
| 449 |
-
Label the left view "NN Prediction" and the right view "Ground Truth".
|
| 450 |
-
Orient the camera to look in the (-1, 0, -1) direction, with the datasets fitting in the views.
|
| 451 |
-
Save a screenshot of both views in "materials/results/{agent_mode}/materials.png".
|
| 452 |
-
Finally, save the ParaView state as "materials/results/{agent_mode}/materials.pvsm"
|
| 453 |
-
|
| 454 |
-
assert:
|
| 455 |
-
- type: llm-rubric
|
| 456 |
-
subtype: vision
|
| 457 |
-
value: |
|
| 458 |
-
1. Side-by-Side Comparison: Are both datasets properly displayed in side-by-side views with correct dimensions and labeling?
|
| 459 |
-
|
| 460 |
-
2. Data Conversion and Filtering: Are the Intensity and Phase variables correctly converted to point data and isovolume filtering applied?
|
| 461 |
-
|
| 462 |
-
3. Clipping and Color Mapping: Is the plane clipping correctly applied and Viridis colormap properly used for Phase variable?
|
| 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/{main_cases.yaml → paraview_cases.yaml}
RENAMED
|
@@ -937,3 +937,510 @@
|
|
| 937 |
3. Surface Appearance: Does the surface color and shading appear similar to the ground truth?
|
| 938 |
|
| 939 |
4. Visualization Clarity: Are the vortex features clearly visible and comparable to the ground truth?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 937 |
3. Surface Appearance: Does the surface color and shading appear similar to the ground truth?
|
| 938 |
|
| 939 |
4. Visualization Clarity: Are the vortex features clearly visible and comparable to the ground truth?
|
| 940 |
+
|
| 941 |
+
# Case 29: line-plot
|
| 942 |
+
- vars:
|
| 943 |
+
question: |
|
| 944 |
+
Read the dataset in the file "line-plot/data/line-plot.ex2", and print the number of components and the range of all the variables.
|
| 945 |
+
Show a default view of the dataset, colored by the variable Pres.
|
| 946 |
+
Create a line plot over all the variables in the dataset, from (0,0,0) to (0,0,10).
|
| 947 |
+
Write the values of the line plot in the file "line-plot/results/{agent_mode}/line-plot.csv", and save a screenshot of the line plot in "line-plot/results/{agent_mode}/line-plot.png".
|
| 948 |
+
(Optional, but must save if use paraview) Save the paraview state as "line-plot/results/{agent_mode}/line-plot.pvsm".
|
| 949 |
+
(Optional, but must save if use python script) Save the python script as "line-plot/results/{agent_mode}/line-plot.py".
|
| 950 |
+
Do not save any other files, and always save the visualization image.
|
| 951 |
+
|
| 952 |
+
assert:
|
| 953 |
+
- type: llm-rubric
|
| 954 |
+
subtype: vision
|
| 955 |
+
value: |
|
| 956 |
+
1. Line Visualization Quality: Are multiple distinct lines clearly visible and properly rendered showing the evolution of different variables along the specified path?
|
| 957 |
+
|
| 958 |
+
2. Variable Differentiation: Are all dataset variables visually distinguishable through distinct colors or line styles with clear separation between curves?
|
| 959 |
+
|
| 960 |
+
3. Axis and Scale Appropriateness: Do the plot axes display appropriate ranges and scaling that effectively show the data trends and variations?
|
| 961 |
+
|
| 962 |
+
4. Legend and Readability: Is there a clear legend identifying each variable line with readable labels and proper visual organization?
|
| 963 |
+
|
| 964 |
+
# Case 30: ml-dvr
|
| 965 |
+
- vars:
|
| 966 |
+
question: |
|
| 967 |
+
I would like to use ParaView to visualize a dataset.
|
| 968 |
+
Read in the file named "ml-dvr/data/ml-dvr.vtk".
|
| 969 |
+
Generate a volume rendering using the default transfer function.
|
| 970 |
+
Rotate the view to an isometric direction.
|
| 971 |
+
Save a screenshot of the result in the filename "ml-dvr/results/{agent_mode}/ml-dvr.png".
|
| 972 |
+
The rendered view and saved screenshot should be 1920 x 1080 pixels.
|
| 973 |
+
(Optional, but must save if use paraview) Save the paraview state as "ml-dvr/results/{agent_mode}/ml-dvr.pvsm".
|
| 974 |
+
(Optional, but must save if use python script) Save the python script as "ml-dvr/results/{agent_mode}/ml-dvr.py".
|
| 975 |
+
Do not save any other files, and always save the visualization image.
|
| 976 |
+
|
| 977 |
+
assert:
|
| 978 |
+
- type: llm-rubric
|
| 979 |
+
subtype: vision
|
| 980 |
+
value: |
|
| 981 |
+
1. Volume Rendering Quality: Is the volume rendering properly generated with appropriate opacity and color mapping that reveals internal structures?
|
| 982 |
+
|
| 983 |
+
2. Transfer Function Application: Does the default transfer function effectively highlight meaningful data features and provide good visual contrast?
|
| 984 |
+
|
| 985 |
+
3. Isometric View Setup: Is the visualization displayed from an isometric viewpoint that provides a clear three-dimensional perspective of the volume?
|
| 986 |
+
|
| 987 |
+
4. Visual Clarity and Detail: Are the volume details clearly visible with proper lighting and shading that enhances depth perception?
|
| 988 |
+
|
| 989 |
+
# Case 31: ml-iso
|
| 990 |
+
- vars:
|
| 991 |
+
question: |
|
| 992 |
+
Read in the file named "ml-iso/data/ml-iso.vtk", and generate an isosurface of the variable var0 at value 0.5.
|
| 993 |
+
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".
|
| 994 |
+
(Optional, but must save if use paraview) Save the paraview state as "ml-iso/results/{agent_mode}/ml-iso.pvsm".
|
| 995 |
+
(Optional, but must save if use python script) Save the python script as "ml-iso/results/{agent_mode}/ml-iso.py".
|
| 996 |
+
Do not save any other files, and always save the visualization image.
|
| 997 |
+
|
| 998 |
+
assert:
|
| 999 |
+
- type: llm-rubric
|
| 1000 |
+
subtype: vision
|
| 1001 |
+
value: |
|
| 1002 |
+
1. Isosurface Generation: Is the isosurface properly generated at the specified value (0.5) with correct topology and continuity?
|
| 1003 |
+
|
| 1004 |
+
2. Surface Rendering Quality: Does the isosurface display smooth surfaces with appropriate shading and lighting that reveals the 3D structure?
|
| 1005 |
+
|
| 1006 |
+
3. Geometric Accuracy: Are the surface features geometrically correct and free from artifacts or discontinuities?
|
| 1007 |
+
|
| 1008 |
+
4. Visual Presentation: Is the isosurface clearly visible with good contrast and coloring that enhances the understanding of the data structure?
|
| 1009 |
+
|
| 1010 |
+
# Case 32: ml-slice-iso
|
| 1011 |
+
- vars:
|
| 1012 |
+
question: |
|
| 1013 |
+
Please generate a ParaView Python script for the following operations.
|
| 1014 |
+
Read in the file named "ml-slice-iso/data/ml-slice-iso.vtk".
|
| 1015 |
+
Slice the volume in a plane parallel to the y-z plane at x=0.
|
| 1016 |
+
Take a contour through the slice at the value 0.5.
|
| 1017 |
+
Color the contour red. Use a white background.
|
| 1018 |
+
Rotate the view to look at the +x direction.
|
| 1019 |
+
Save a screenshot of the result in the filename "ml-slice-iso/results/{agent_mode}/ml-slice-iso.png".
|
| 1020 |
+
The rendered view and saved screenshot should be 1920 x 1080 pixels.
|
| 1021 |
+
(Optional, but must save if use paraview) Save the paraview state as "ml-slice-iso/results/{agent_mode}/ml-slice-iso.pvsm".
|
| 1022 |
+
(Optional, but must save if use python script) Save the python script as "ml-slice-iso/results/{agent_mode}/ml-slice-iso.py".
|
| 1023 |
+
Do not save any other files, and always save the visualization image.
|
| 1024 |
+
|
| 1025 |
+
assert:
|
| 1026 |
+
- type: llm-rubric
|
| 1027 |
+
subtype: vision
|
| 1028 |
+
value: |
|
| 1029 |
+
1. Slice Generation: Is the y-z plane slice properly generated at x=0 position showing the correct cross-section of the volume?
|
| 1030 |
+
|
| 1031 |
+
2. Contour on Slice: Are the contour lines at value 0.5 correctly extracted from the slice and properly displayed?
|
| 1032 |
+
|
| 1033 |
+
3. Red Color Application: Is the contour visualization properly colored red as specified in the requirements?
|
| 1034 |
+
|
| 1035 |
+
4. View Direction: Is the visualization displayed from the correct +x direction view that provides clear visibility of the slice and contours?
|
| 1036 |
+
|
| 1037 |
+
# Case 33: points-surf-clip
|
| 1038 |
+
- vars:
|
| 1039 |
+
question: |
|
| 1040 |
+
I would like to use ParaView to visualize a dataset.
|
| 1041 |
+
Read in the file named "points-surf-clip/data/points-surf-clip.ex2".
|
| 1042 |
+
Generate an 3d Delaunay triangulation of the dataset.
|
| 1043 |
+
Clip the data with a y-z plane at x=0, keeping the -x half of the data and removing the +x half.
|
| 1044 |
+
Render the image as a wireframe.
|
| 1045 |
+
Save a screenshot of the result in the filename "points-surf-clip/results/{agent_mode}/points-surf-clip.png".
|
| 1046 |
+
The rendered view and saved screenshot should be 1920 x 1080 pixels. Use a white background color.
|
| 1047 |
+
(Optional, but must save if use paraview) Save the paraview state as "points-surf-clip/results/{agent_mode}/points-surf-clip.pvsm".
|
| 1048 |
+
(Optional, but must save if use python script) Save the python script as "points-surf-clip/results/{agent_mode}/points-surf-clip.py".
|
| 1049 |
+
Do not save any other files, and always save the visualization image.
|
| 1050 |
+
|
| 1051 |
+
assert:
|
| 1052 |
+
- type: llm-rubric
|
| 1053 |
+
subtype: vision
|
| 1054 |
+
value: |
|
| 1055 |
+
1. Delaunay Triangulation Quality: Is the 3D Delaunay triangulation properly generated creating a valid mesh structure from the point data?
|
| 1056 |
+
|
| 1057 |
+
2. Clipping Accuracy: Is the mesh correctly clipped by the y-z plane at x=0, with only the -x half of the data remaining visible?
|
| 1058 |
+
|
| 1059 |
+
3. Wireframe Representation: Is the result displayed as a clear wireframe showing the triangulated mesh structure with visible edges?
|
| 1060 |
+
|
| 1061 |
+
4. Geometric Integrity: Does the clipped wireframe maintain proper connectivity and show the expected geometric features without artifacts?
|
| 1062 |
+
|
| 1063 |
+
# Case 34: shrink-sphere
|
| 1064 |
+
- vars:
|
| 1065 |
+
question: |
|
| 1066 |
+
Create a default sphere and then hide it.
|
| 1067 |
+
Create a shrink filter from the sphere.
|
| 1068 |
+
Double the sphere's theta resolution.
|
| 1069 |
+
Divide the shrink filter's shrink factor in half.
|
| 1070 |
+
Extract a wireframe from the sphere.
|
| 1071 |
+
Group the shrink filter and wireframe together and show them.
|
| 1072 |
+
Save a screenshot of the result in the filename "shrink-sphere/results/{agent_mode}/shrink-sphere.png".
|
| 1073 |
+
The rendered view and saved screenshot should be 1920 x 1080 pixels and have a white background.
|
| 1074 |
+
(Optional, but must save if use paraview) Save the paraview state as "shrink-sphere/results/{agent_mode}/shrink-sphere.pvsm".
|
| 1075 |
+
(Optional, but must save if use python script) Save the python script as "shrink-sphere/results/{agent_mode}/shrink-sphere.py".
|
| 1076 |
+
Do not save any other files, and always save the visualization image.
|
| 1077 |
+
|
| 1078 |
+
assert:
|
| 1079 |
+
- type: llm-rubric
|
| 1080 |
+
subtype: vision
|
| 1081 |
+
value: |
|
| 1082 |
+
1. Sphere Creation and Resolution: Is the sphere created with doubled theta resolution providing higher geometric detail and smoother curvature?
|
| 1083 |
+
|
| 1084 |
+
2. Shrink Filter Application: Is the shrink filter properly applied with halved shrink factor creating visible separation between mesh elements?
|
| 1085 |
+
|
| 1086 |
+
3. Dual Representation: Are both the wireframe sphere and shrink filter results simultaneously visible and properly grouped together?
|
| 1087 |
+
|
| 1088 |
+
4. Visual Quality: Does the visualization clearly show the contrast between the wireframe structure and the shrunken elements with appropriate white background?
|
| 1089 |
+
|
| 1090 |
+
# Case 35: stream-glyph
|
| 1091 |
+
- vars:
|
| 1092 |
+
question: |
|
| 1093 |
+
I would like to use ParaView to visualize a dataset.
|
| 1094 |
+
Read in the file named "stream-glyph/data/stream-glyph.ex2".
|
| 1095 |
+
Trace streamlines of the V data array seeded from a default point cloud.
|
| 1096 |
+
Render the streamlines with tubes.
|
| 1097 |
+
Add cone glyphs to the streamlines.
|
| 1098 |
+
Color the streamlines and glyphs by the Temp data array.
|
| 1099 |
+
View the result in the +X direction.
|
| 1100 |
+
Save a screenshot of the result in the filename "stream-glyph/results/{agent_mode}/stream-glyph.png".
|
| 1101 |
+
The rendered view and saved screenshot should be 1920 x 1080 pixels.
|
| 1102 |
+
(Optional, but must save if use paraview) Save the paraview state as "stream-glyph/results/{agent_mode}/stream-glyph.pvsm".
|
| 1103 |
+
(Optional, but must save if use python script) Save the python script as "stream-glyph/results/{agent_mode}/stream-glyph.py".
|
| 1104 |
+
Do not save any other files, and always save the visualization image.
|
| 1105 |
+
|
| 1106 |
+
assert:
|
| 1107 |
+
- type: llm-rubric
|
| 1108 |
+
subtype: vision
|
| 1109 |
+
value: |
|
| 1110 |
+
1. Streamline Generation: Are streamlines properly traced following the V variable flow field with appropriate seeding from the point cloud?
|
| 1111 |
+
|
| 1112 |
+
2. Tube and Glyph Rendering: Are streamlines rendered as tubes with cone glyphs properly attached showing flow direction and magnitude?
|
| 1113 |
+
|
| 1114 |
+
3. Temperature Color Mapping: Are both streamlines and glyphs correctly colored by the Temp variable with appropriate color scaling?
|
| 1115 |
+
|
| 1116 |
+
4. View Configuration: Is the visualization displayed from the correct +x view direction providing clear visibility of the flow patterns and structures?
|
| 1117 |
+
|
| 1118 |
+
# Case 36: time-varying
|
| 1119 |
+
- vars:
|
| 1120 |
+
question: |
|
| 1121 |
+
Read the dataset in the file "time-varying/data/time-varying.ex2", and color the data by the EQPS variable.
|
| 1122 |
+
Viewing in the +y direction, play an animation through the time steps, with visible color bar legend.
|
| 1123 |
+
Rescale the data range to last time step, and play the animation again.
|
| 1124 |
+
Create a second linked render view to the right of the first, applying a temporal interpolator to the second view.
|
| 1125 |
+
Play the animation simultaneously in both views, and save the animation of both views in "time-varying/results/{agent_mode}/time-varying.avi".
|
| 1126 |
+
Print the following statistics: average value of EQPS over all locations and all time steps, average value of EQPS over all locations in the first half of the time steps, average value of EQPS over all locations in the even numbered time steps, and variance of EQPS over all locations and all the time steps.
|
| 1127 |
+
Save the last frame of the visualization image as "time-varying/results/{agent_mode}/time-varying.png".
|
| 1128 |
+
(Optional, but must save if use paraview) Save the paraview state as "time-varying/results/{agent_mode}/time-varying.pvsm".
|
| 1129 |
+
(Optional, but must save if use python script) Save the python script as "time-varying/results/{agent_mode}/time-varying.py".
|
| 1130 |
+
Do not save any other files, and always save the visualization image.
|
| 1131 |
+
|
| 1132 |
+
assert:
|
| 1133 |
+
- type: llm-rubric
|
| 1134 |
+
subtype: vision
|
| 1135 |
+
value: |
|
| 1136 |
+
1. Temporal Animation Quality: Does the animation smoothly progress through all time steps showing the evolution of the EQPS variable over time?
|
| 1137 |
+
|
| 1138 |
+
2. Dual View Configuration: Are both render views properly configured with the second view showing temporal interpolation effects compared to the first?
|
| 1139 |
+
|
| 1140 |
+
3. Color Mapping and Legend: Is the EQPS variable properly color-mapped with an appropriate color bar legend visible throughout the animation?
|
| 1141 |
+
|
| 1142 |
+
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?
|
| 1143 |
+
|
| 1144 |
+
# Case 37: chart-opacity
|
| 1145 |
+
- vars:
|
| 1146 |
+
question: |
|
| 1147 |
+
Create a wavelet object.
|
| 1148 |
+
Create a plot over line chart from the wavelet with three paths: arc_length, Points_Z, and RTData variables with opacity for arc_length 1 and opacity for Points_Z and RTData 0.3.
|
| 1149 |
+
|
| 1150 |
+
Save the visualization image as "chart-opacity/results/{agent_mode}/chart-opacity.png".
|
| 1151 |
+
(Optional, but must save if use paraview) Save the paraview state as "chart-opacity/results/{agent_mode}/chart-opacity.pvsm".
|
| 1152 |
+
(Optional, but must save if use python script) Save the python script as "chart-opacity/results/{agent_mode}/chart-opacity.py".
|
| 1153 |
+
Do not save any other files, and always save the visualization image.
|
| 1154 |
+
|
| 1155 |
+
assert:
|
| 1156 |
+
- type: llm-rubric
|
| 1157 |
+
subtype: vision
|
| 1158 |
+
value: |
|
| 1159 |
+
1. Chart Generation: Is the plot over line chart properly created from the wavelet data?
|
| 1160 |
+
|
| 1161 |
+
2. Variable Display: Are arc_length, Points_Z, and RTData variables all correctly plotted, showing all three specified variables and distinguishable in the chart?
|
| 1162 |
+
|
| 1163 |
+
3. Opacity Settings: Is the arc_length variable displayed with full opacity (1.0) while Points_Z and RTData show reduced opacity (0.3)?
|
| 1164 |
+
|
| 1165 |
+
4. Chart Clarity: Does the chart provide clear visualization of the data trends with appropriate axis scaling and readable formatting?
|
| 1166 |
+
|
| 1167 |
+
# Case 38: color-blocks
|
| 1168 |
+
- vars:
|
| 1169 |
+
question: |
|
| 1170 |
+
I would like to use ParaView to visualize a dataset.
|
| 1171 |
+
Set the background to a blue-gray palette.
|
| 1172 |
+
Read the file "color-blocks/data/color-blocks.ex2".
|
| 1173 |
+
This is a multiblock dataset.
|
| 1174 |
+
Color the dataset by the vtkBlockColors field.
|
| 1175 |
+
Retrieve the color map for vtkBlockColors.
|
| 1176 |
+
Retrieve the opacity transfer function for vtkBlockColors.
|
| 1177 |
+
Retrieve the 2D transfer function for vtkBlockColors.
|
| 1178 |
+
Set block coloring for the block at /IOSS/element_blocks/block_2 using the variable ACCL on the x component of the points.
|
| 1179 |
+
Rescale the block's color and opacity maps to match the current data range of block_2.
|
| 1180 |
+
Retrieve the color transfer function for the ACCL variable of block_2.
|
| 1181 |
+
Enable the color bar for block_2.
|
| 1182 |
+
Apply a cool to warm color preset to the color map for block_2.
|
| 1183 |
+
Set the camera to look down the -y direction and to see the entire dataset.
|
| 1184 |
+
Save the visualization image as "color-blocks/results/{agent_mode}/color-blocks.png".
|
| 1185 |
+
(Optional, but must save if use paraview) Save the paraview state as "color-blocks/results/{agent_mode}/color-blocks.pvsm".
|
| 1186 |
+
(Optional, but must save if use python script) Save the python script as "color-blocks/results/{agent_mode}/color-blocks.py".
|
| 1187 |
+
Do not save any other files, and always save the visualization image.
|
| 1188 |
+
|
| 1189 |
+
assert:
|
| 1190 |
+
- type: llm-rubric
|
| 1191 |
+
subtype: vision
|
| 1192 |
+
value: |
|
| 1193 |
+
1. Block Color Mapping: Is the dataset properly colored by vtkBlockColors field with distinct block visualization?
|
| 1194 |
+
|
| 1195 |
+
2. Individual Block Coloring: Is block_2 correctly colored using the x component of the ACCL variable with appropriate scaling?
|
| 1196 |
+
|
| 1197 |
+
3. Color Transfer Functions: Are the color transfer functions properly applied with cool to warm coloring for the ACCL variable?
|
| 1198 |
+
|
| 1199 |
+
4. View Configuration: Is the dataset displayed from the -y direction with blue-gray background and visible color bar legend?
|
| 1200 |
+
|
| 1201 |
+
# Case 39: color-data
|
| 1202 |
+
- vars:
|
| 1203 |
+
question: |
|
| 1204 |
+
Create a wavelet object.
|
| 1205 |
+
Create a new calculator with the function 'RTData*iHat + ln(RTData)*jHat + coordsZ*kHat'.
|
| 1206 |
+
Get a color transfer function/color map and opacity transfer function/opacity map for the result of the calculation, scaling the color and/or opacity maps to the data range.
|
| 1207 |
+
For a surface representation, color by the x coordinate of the result using a cool to warm color map, show the color bar/color legend, and save a screenshot of size 1158 x 833 pixels in "color-data/results/{agent_mode}/color-data.png".
|
| 1208 |
+
(Optional, but must save if use paraview) Save the paraview state as "color-data/results/{agent_mode}/color-data.pvsm".
|
| 1209 |
+
(Optional, but must save if use python script) Save the python script as "color-data/results/{agent_mode}/color-data.py".
|
| 1210 |
+
Do not save any other files, and always save the visualization image.
|
| 1211 |
+
|
| 1212 |
+
assert:
|
| 1213 |
+
- type: llm-rubric
|
| 1214 |
+
subtype: vision
|
| 1215 |
+
value: |
|
| 1216 |
+
1. Color Transfer Function: Is the color transfer function correctly applied with cool to warm color mapping scaled to the data range?
|
| 1217 |
+
|
| 1218 |
+
2. Surface Coloring: Is the surface representation properly colored by the x coordinate of the calculated result?
|
| 1219 |
+
|
| 1220 |
+
3. Color Bar Display: Is the color bar/legend visible and properly displaying the color mapping scale and values?
|
| 1221 |
+
|
| 1222 |
+
# Case 40: export-gltf
|
| 1223 |
+
- vars:
|
| 1224 |
+
question: |
|
| 1225 |
+
Create a wavelet object.
|
| 1226 |
+
Create a surface rendering of the wavelet object and color by RTData.
|
| 1227 |
+
Scale the color map to the data, and don't display the color bar or the orientation axes.
|
| 1228 |
+
Export the view to "export-gltf/results/{agent_mode}/ExportedGLTF.gltf".
|
| 1229 |
+
|
| 1230 |
+
Next load the file "export-gltf/results/{agent_mode}/ExportedGLTF.gltf" and display it as a surface.
|
| 1231 |
+
Color this object by TEXCOORD_0.
|
| 1232 |
+
Scale the color map to the data, and don't display the color bar or the orientation axes.
|
| 1233 |
+
Use the 'Cool to Warm' colormap. Set the background color to white.
|
| 1234 |
+
|
| 1235 |
+
Save the visualization image as "export-gltf/results/{agent_mode}/export-gltf.png".
|
| 1236 |
+
(Optional, but must save if use paraview) Save the paraview state as "export-gltf/results/{agent_mode}/export-gltf.pvsm".
|
| 1237 |
+
(Optional, but must save if use python script) Save the python script as "export-gltf/results/{agent_mode}/export-gltf.py".
|
| 1238 |
+
Do not save any other files, and always save the visualization image.
|
| 1239 |
+
|
| 1240 |
+
assert:
|
| 1241 |
+
- type: llm-rubric
|
| 1242 |
+
subtype: vision
|
| 1243 |
+
value: |
|
| 1244 |
+
1. GLTF Export Quality: Is the wavelet object properly exported to GLTF format with correct surface representation and RTData coloring?
|
| 1245 |
+
|
| 1246 |
+
2. GLTF Import and Display: Is the exported GLTF file successfully loaded and displayed as a surface with proper geometry?
|
| 1247 |
+
|
| 1248 |
+
3. Texture Coordinate Coloring: Is the imported GLTF object correctly colored by TEXCOORD_0 with Cool to Warm colormap?
|
| 1249 |
+
|
| 1250 |
+
4. Clean Presentation: Are the color bar and orientation axes properly hidden for a clean visualization appearance?
|
| 1251 |
+
|
| 1252 |
+
# Case 41: import-gltf
|
| 1253 |
+
- vars:
|
| 1254 |
+
question: |
|
| 1255 |
+
Load the "BlueGrayBackground" palette.
|
| 1256 |
+
Read the file "import-gltf/data/import-gltf.glb" and import the nodes "/assembly/Axle", "assembly/OuterRing/Torus002", and "assembly/OuterRing/MiddleRing/InnerRing".
|
| 1257 |
+
Set the layout size to 300x300 pixels.
|
| 1258 |
+
Point the camera in the positive Y direction and zoom to fit.
|
| 1259 |
+
Make sure all views are rendered, then save a screenshot to "import-gltf/results/{agent_mode}/import-gltf.png".
|
| 1260 |
+
(Optional, but must save if use paraview) Save the paraview state as "import-gltf/results/{agent_mode}/import-gltf.pvsm".
|
| 1261 |
+
(Optional, but must save if use python script) Save the python script as "import-gltf/results/{agent_mode}/import-gltf.py".
|
| 1262 |
+
Do not save any other files, and always save the visualization image.
|
| 1263 |
+
|
| 1264 |
+
assert:
|
| 1265 |
+
- type: llm-rubric
|
| 1266 |
+
subtype: vision
|
| 1267 |
+
value: |
|
| 1268 |
+
1. GLTF Import Success: Are the specified GLTF nodes properly imported and displayed as separate geometric components?
|
| 1269 |
+
|
| 1270 |
+
2. Node Selection: Are all three specified nodes (Axle, Torus002, InnerRing) correctly imported and visible?
|
| 1271 |
+
|
| 1272 |
+
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.
|
| 1273 |
+
|
| 1274 |
+
4. Layout Configuration: Is the view properly sized to 300x300 pixels with correct rendering and background palette?
|
| 1275 |
+
|
| 1276 |
+
# Case 42: render-histogram
|
| 1277 |
+
- vars:
|
| 1278 |
+
question: |
|
| 1279 |
+
Create a wavelet object and render it as a surface colored by RTDATA with a visible color bar.
|
| 1280 |
+
Rescale the colors to the data range and use the 'Cool to Warm' color map.
|
| 1281 |
+
|
| 1282 |
+
Next, split the view horizontally to the right and create a histogram view from the wavelet RTDATA.
|
| 1283 |
+
Apply the same 'Cool to Warm' color map to the histogram.
|
| 1284 |
+
|
| 1285 |
+
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".
|
| 1286 |
+
(Optional, but must save if use paraview) Save the paraview state as "render-histogram/results/{agent_mode}/render-histogram.pvsm".
|
| 1287 |
+
(Optional, but must save if use python script) Save the python script as "render-histogram/results/{agent_mode}/render-histogram.py".
|
| 1288 |
+
Do not save any other files, and always save the visualization image.
|
| 1289 |
+
|
| 1290 |
+
assert:
|
| 1291 |
+
- type: llm-rubric
|
| 1292 |
+
subtype: vision
|
| 1293 |
+
value: |
|
| 1294 |
+
1. Wavelet Visualization: Is the wavelet object properly rendered with RTDATA coloring and visible color bar?
|
| 1295 |
+
|
| 1296 |
+
2. Split View Layout: Is the view correctly split with the wavelet visualization on the left and histogram on the right?
|
| 1297 |
+
|
| 1298 |
+
3. Histogram Generation: Is the histogram properly generated from RTDATA showing the data distribution?
|
| 1299 |
+
|
| 1300 |
+
4. Color Map Consistency: Are both the wavelet visualization and histogram using the same Cool to Warm color map?
|
| 1301 |
+
|
| 1302 |
+
# Case 43: reset-camera-direction
|
| 1303 |
+
- vars:
|
| 1304 |
+
question: |
|
| 1305 |
+
Create a Wavelet object, set its representation to "Surface with Edges", and set the camera direction to [0.5, 1, 0.5].
|
| 1306 |
+
Save a screenshot to the file "reset-camera-direction/results/{agent_mode}/reset-camera-direction.png".
|
| 1307 |
+
(Optional, but must save if use paraview) Save the paraview state as "reset-camera-direction/results/{agent_mode}/reset-camera-direction.pvsm".
|
| 1308 |
+
(Optional, but must save if use python script) Save the python script as "reset-camera-direction/results/{agent_mode}/reset-camera-direction.py".
|
| 1309 |
+
Do not save any other files, and always save the visualization image.
|
| 1310 |
+
|
| 1311 |
+
assert:
|
| 1312 |
+
- type: llm-rubric
|
| 1313 |
+
subtype: vision
|
| 1314 |
+
value: |
|
| 1315 |
+
1. Wavelet Creation: Is the Wavelet object properly created and displayed in the scene?
|
| 1316 |
+
|
| 1317 |
+
2. Surface with Edges Representation: Is the wavelet correctly displayed with "Surface with Edges" representation showing both surface and wireframe?
|
| 1318 |
+
|
| 1319 |
+
3. Camera Direction: Is the camera positioned according to the specified direction vector [0.5, 1, 0.5]?
|
| 1320 |
+
|
| 1321 |
+
4. View Quality: Does the visualization provide a clear view of the wavelet structure from the specified camera angle?
|
| 1322 |
+
|
| 1323 |
+
# Case 44: save-transparent
|
| 1324 |
+
- vars:
|
| 1325 |
+
question: |
|
| 1326 |
+
I would like to use ParaView to visualize a dataset.
|
| 1327 |
+
Create a wavelet object and show it. Color the rendering by the variable ‘RTData’.
|
| 1328 |
+
Render the wavelet as a surface. Hide the color bar.
|
| 1329 |
+
Next, set the layout size to be 300 pixels by 300 pixels.
|
| 1330 |
+
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.
|
| 1331 |
+
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.
|
| 1332 |
+
(Optional, but must save if use paraview) Save the paraview state as “save-transparent/results/{agent_mode}/save-transparent.pvsm”.
|
| 1333 |
+
(Optional, but must save if use python script) Save the python script as “save-transparent/results/{agent_mode}/save-transparent.py”.
|
| 1334 |
+
Do not save any other files, and always save the visualization image.
|
| 1335 |
+
|
| 1336 |
+
assert:
|
| 1337 |
+
- type: llm-rubric
|
| 1338 |
+
subtype: vision
|
| 1339 |
+
value: |
|
| 1340 |
+
1. Object Creation: Is the wavelet object properly created and displayed in the scene? Looking similar to the GT image?
|
| 1341 |
+
|
| 1342 |
+
2. Transparent Background: Is the screenshot saved with a properly transparent background instead of solid color?
|
| 1343 |
+
|
| 1344 |
+
# Case 45: subseries-of-time-series
|
| 1345 |
+
- vars:
|
| 1346 |
+
question: |
|
| 1347 |
+
Read the file "subseries-of-time-series/data/subseries-of-time-series.ex2". Load two element blocks: the first is called 'Unnamed block ID: 1 Type: HEX', the second is called 'Unnamed block ID: 2 Type: HEX'.
|
| 1348 |
+
Next, slice this object with a plane with origin at [0.21706008911132812, 4.0, -5.110947132110596] and normal direction [1.0, 0.0, 0.0]. The plane should have no offset.
|
| 1349 |
+
Next, save this time series to a collection of .vtm files. The base file name for the time series is "subseries-of-time-series/results/{agent_mode}/canslices.vtm" and the suffix is '_%d'. Only save time steps with index between 10 and 20 inclusive, counting by 3.
|
| 1350 |
+
Next, load the files "subseries-of-time-series/results/{agent_mode}/canslices_10.vtm", "subseries-of-time-series/results/{agent_mode}/canslices_13.vtm", "subseries-of-time-series/results/{agent_mode}/canslices_16.vtm", and "subseries-of-time-series/results/{agent_mode}/canslices_19.vtm" in multi-block format.
|
| 1351 |
+
Finally, show the multi-block data set you just loaded.
|
| 1352 |
+
Save a screenshot to the file "subseries-of-time-series/results/{agent_mode}/subseries-of-time-series.png".
|
| 1353 |
+
(Optional, but must save if use paraview) Save the paraview state as "subseries-of-time-series/results/{agent_mode}/subseries-of-time-series.pvsm".
|
| 1354 |
+
(Optional, but must save if use python script) Save the python script as "subseries-of-time-series/results/{agent_mode}/subseries-of-time-series.py".
|
| 1355 |
+
Do not save any other files, and always save the visualization image.
|
| 1356 |
+
|
| 1357 |
+
assert:
|
| 1358 |
+
- type: llm-rubric
|
| 1359 |
+
subtype: vision
|
| 1360 |
+
value: |
|
| 1361 |
+
1. Data Loading and Block Selection: Are the specified element blocks properly loaded and the slice plane correctly applied?
|
| 1362 |
+
|
| 1363 |
+
2. Multi-block Loading: Are the exported VTM files successfully loaded back as a multi-block dataset?
|
| 1364 |
+
|
| 1365 |
+
3. Final Visualization: Is the multi-block dataset properly displayed showing the sliced geometry from the time series?
|
| 1366 |
+
|
| 1367 |
+
# Case 46: write-ply
|
| 1368 |
+
- vars:
|
| 1369 |
+
question: |
|
| 1370 |
+
I would like to use ParaView to visualize a dataset.
|
| 1371 |
+
Create a wavelet object. Change the view size to 400x400.
|
| 1372 |
+
Show the wavelet object and reset the camera to fit the data.
|
| 1373 |
+
Next, create a contour of wavelet object from the dataset "RTData".
|
| 1374 |
+
The contour should have isosurfaces at the following values: 97.222075, 157.09105, 216.96002500000003, and 276.829.
|
| 1375 |
+
Show the contour and color it with the same colormap that is used for coloring "RTData".
|
| 1376 |
+
Finally, save the contour in PLY format to the file "write-ply/results/{agent_mode}/PLYWriterData.ply".
|
| 1377 |
+
Save the visualization image as "write-ply/results/{agent_mode}/write-ply.png".
|
| 1378 |
+
(Optional, but must save if use paraview) Save the paraview state as "write-ply/results/{agent_mode}/write-ply.pvsm".
|
| 1379 |
+
(Optional, but must save if use python script) Save the python script as "write-ply/results/{agent_mode}/write-ply.py".
|
| 1380 |
+
Do not save any other files, and always save the visualization image.
|
| 1381 |
+
|
| 1382 |
+
assert:
|
| 1383 |
+
- type: llm-rubric
|
| 1384 |
+
subtype: vision
|
| 1385 |
+
value: |
|
| 1386 |
+
1. Cube Creation: Is the cube object properly created and displayed with correct geometry?
|
| 1387 |
+
|
| 1388 |
+
2. PLY Import: Is the exported PLY file correctly loaded back into ParaView maintaining geometric fidelity?
|
| 1389 |
+
|
| 1390 |
+
3. Visualization Quality: Does the imported cube display properly with correct surface representation and rendering?
|
| 1391 |
+
|
| 1392 |
+
# Case 47: climate
|
| 1393 |
+
- vars:
|
| 1394 |
+
question: |
|
| 1395 |
+
I would like to use ParaView to visualize a dataset of ocean currents.
|
| 1396 |
+
Read in the file named "climate/data/climate.vtp".
|
| 1397 |
+
Apply a calculator filter to compute the following function:
|
| 1398 |
+
(-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
|
| 1399 |
+
Render the computed values using a tube filter with 0.05 as the tube radius.
|
| 1400 |
+
Color the tubes by the magnitude of the velocity.
|
| 1401 |
+
Light the tubes with the maximum shininess and include normals in the lighting.
|
| 1402 |
+
Add cone glyphs to show the direction of the velocity.
|
| 1403 |
+
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.
|
| 1404 |
+
View the result in the -z direction.
|
| 1405 |
+
Adjust the view so that the tubes occupy the 90% of the image.
|
| 1406 |
+
Save a screenshot of the result, 2294 x 1440 pixels, white background, in the filename "climate/results/{agent_mode}/climate.png".
|
| 1407 |
+
(Optional, but must save if use paraview) Save the paraview state as "climate/results/{agent_mode}/climate.pvsm".
|
| 1408 |
+
(Optional, but must save if use python script) Save the python script as "climate/results/{agent_mode}/climate.py".
|
| 1409 |
+
Do not save any other files, and always save the visualization image.
|
| 1410 |
+
|
| 1411 |
+
assert:
|
| 1412 |
+
- type: llm-rubric
|
| 1413 |
+
subtype: vision
|
| 1414 |
+
value: |
|
| 1415 |
+
1. Tube Visualization: Are the tubes rendered with correct radius (0.05), colored by velocity magnitude, and proper lighting with maximum shininess?
|
| 1416 |
+
|
| 1417 |
+
2. Cone Glyph Direction: Are the cone glyphs properly configured with specified parameters and showing velocity direction accurately?
|
| 1418 |
+
|
| 1419 |
+
3. View Configuration: Is the visualization displayed from -z direction with appropriate scaling and white background as specified?
|
| 1420 |
+
|
| 1421 |
+
# Case 48: materials
|
| 1422 |
+
- vars:
|
| 1423 |
+
question: |
|
| 1424 |
+
Compare two datasets in two views side by side each 900 pixels wide x 1400 pixels high.
|
| 1425 |
+
Read the dataset "materials/data/materials_prediction.vtr" in the left view and "materials/data/materials_ground_truth.vtr" in the right view.
|
| 1426 |
+
In both views, convert the "Intensity" and "Phase" variables from cell to point data.
|
| 1427 |
+
In both views, take an isovolume of the "Intensity" variable in the range of [0.2, 1.0], clipped with a plane at (32.0, 32.0, 32.0) and +x normal direction.
|
| 1428 |
+
Color both views with the Viridis (matplotlib) color map for the "Phase" variable, scaled to the data range, including a colormap legend in both views.
|
| 1429 |
+
Label the left view "NN Prediction" and the right view "Ground Truth".
|
| 1430 |
+
Orient the camera to look in the (-1, 0, -1) direction, with the datasets fitting in the views.
|
| 1431 |
+
Save the visualization image as "materials/results/{agent_mode}/materials.png".
|
| 1432 |
+
(Optional, but must save if use paraview) Save the paraview state as "materials/results/{agent_mode}/materials.pvsm".
|
| 1433 |
+
(Optional, but must save if use python script) Save the python script as "materials/results/{agent_mode}/materials.py".
|
| 1434 |
+
Do not save any other files, and always save the visualization image.
|
| 1435 |
+
|
| 1436 |
+
assert:
|
| 1437 |
+
- type: llm-rubric
|
| 1438 |
+
subtype: vision
|
| 1439 |
+
value: |
|
| 1440 |
+
1. Side-by-Side Comparison: Are both datasets properly displayed in side-by-side views with correct dimensions and labeling?
|
| 1441 |
+
|
| 1442 |
+
2. Data Conversion and Filtering: Are the Intensity and Phase variables correctly converted to point data and isovolume filtering applied?
|
| 1443 |
+
|
| 1444 |
+
3. Clipping and Color Mapping: Is the plane clipping correctly applied and Viridis colormap properly used for Phase variable?
|
| 1445 |
+
|
| 1446 |
+
4. Camera and Layout: Is the camera positioned correctly in (-1, 0, -1) direction with appropriate fitting and legends visible?
|
eval_cases/paraview/what_obj_cases.yaml
CHANGED
|
@@ -114,39 +114,7 @@
|
|
| 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.
|
| 118 |
-
- vars:
|
| 119 |
-
question: |
|
| 120 |
-
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/csafe_heptane/data/csafe_heptane_302x302x302_uint8.raw".
|
| 121 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "../SciVisAgentBench-tasks/sci_volume_data/csafe_heptane/results/{agent_mode}/csafe_heptane.pvsm"
|
| 122 |
-
Provide a textual report identifying what you observe and save it to "../SciVisAgentBench-tasks/sci_volume_data/csafe_heptane/results/{agent_mode}/answers.txt"
|
| 123 |
-
assert:
|
| 124 |
-
- type: llm-rubric
|
| 125 |
-
subtype: text
|
| 126 |
-
value: |
|
| 127 |
-
Should recognize combustion or heptane simulation data
|
| 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:
|
| 135 |
-
question: |
|
| 136 |
-
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/duct/data/duct_193x194x1000_float32.raw".
|
| 137 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "../SciVisAgentBench-tasks/sci_volume_data/duct/results/{agent_mode}/duct.pvsm"
|
| 138 |
-
Take a screenshot and provide a textual report describing what you observe and save it to "../SciVisAgentBench-tasks/sci_volume_data/duct/results/{agent_mode}/answers.txt"
|
| 139 |
-
assert:
|
| 140 |
-
- type: llm-rubric
|
| 141 |
-
subtype: text
|
| 142 |
-
value: |
|
| 143 |
-
Should identify flow patterns in a duct geometry
|
| 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:
|
| 151 |
question: |
|
| 152 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/engine/data/engine_256x256x128_uint8.raw".
|
|
@@ -162,7 +130,7 @@
|
|
| 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 |
-
#
|
| 166 |
- vars:
|
| 167 |
question: |
|
| 168 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/foot/data/foot_256x256x256_uint8.raw".
|
|
@@ -178,7 +146,7 @@
|
|
| 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 |
-
#
|
| 182 |
- vars:
|
| 183 |
question: |
|
| 184 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/frog/data/frog_256x256x44_uint8.raw".
|
|
@@ -194,7 +162,7 @@
|
|
| 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 |
-
#
|
| 198 |
- vars:
|
| 199 |
question: |
|
| 200 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/fuel/data/fuel_64x64x64_uint8.raw".
|
|
@@ -210,7 +178,7 @@
|
|
| 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 |
-
#
|
| 214 |
- vars:
|
| 215 |
question: |
|
| 216 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/hydrogen_atom/data/hydrogen_atom_128x128x128_uint8.raw".
|
|
@@ -226,7 +194,7 @@
|
|
| 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 |
-
#
|
| 230 |
- vars:
|
| 231 |
question: |
|
| 232 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/lobster/data/lobster_301x324x56_uint8.raw".
|
|
@@ -242,23 +210,7 @@
|
|
| 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 |
-
#
|
| 246 |
-
- vars:
|
| 247 |
-
question: |
|
| 248 |
-
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/marschner_lobb/data/marschner_lobb_41x41x41_uint8.raw".
|
| 249 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "../SciVisAgentBench-tasks/sci_volume_data/marschner_lobb/results/{agent_mode}/marschner_lobb.pvsm"
|
| 250 |
-
Provide a textual report identifying what you observe and save it to "../SciVisAgentBench-tasks/sci_volume_data/marschner_lobb/results/{agent_mode}/answers.txt"
|
| 251 |
-
assert:
|
| 252 |
-
- type: llm-rubric
|
| 253 |
-
subtype: text
|
| 254 |
-
value: |
|
| 255 |
-
Should recognize Marschner-Lobb synthetic test pattern
|
| 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:
|
| 263 |
question: |
|
| 264 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/mri_ventricles/data/mri_ventricles_256x256x124_uint8.raw".
|
|
@@ -274,7 +226,7 @@
|
|
| 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 |
-
#
|
| 278 |
- vars:
|
| 279 |
question: |
|
| 280 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/mri_woman/data/mri_woman_256x256x109_uint16.raw".
|
|
@@ -290,7 +242,7 @@
|
|
| 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 |
-
#
|
| 294 |
- vars:
|
| 295 |
question: |
|
| 296 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/mrt_angio/data/mrt_angio_416x512x112_uint16.raw".
|
|
@@ -306,23 +258,7 @@
|
|
| 306 |
value: |
|
| 307 |
The visualization image shows angiography or vascular structures with a reasonable transfer function, and the object is shown clearly
|
| 308 |
|
| 309 |
-
#
|
| 310 |
-
- vars:
|
| 311 |
-
question: |
|
| 312 |
-
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/neghip/data/neghip_64x64x64_uint8.raw".
|
| 313 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "../SciVisAgentBench-tasks/sci_volume_data/neghip/results/{agent_mode}/neghip.pvsm"
|
| 314 |
-
Provide a textual report identifying what you observe and save it to "../SciVisAgentBench-tasks/sci_volume_data/neghip/results/{agent_mode}/answers.txt"
|
| 315 |
-
assert:
|
| 316 |
-
- type: llm-rubric
|
| 317 |
-
subtype: text
|
| 318 |
-
value: |
|
| 319 |
-
Should visualize and describe molecule structure
|
| 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:
|
| 327 |
question: |
|
| 328 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/neocortical_layer_1_axons/data/neocortical_layer_1_axons_1464x1033x76_uint8.raw".
|
|
@@ -338,7 +274,7 @@
|
|
| 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 |
-
#
|
| 342 |
- vars:
|
| 343 |
question: |
|
| 344 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/nucleon/data/nucleon_41x41x41_uint8.raw".
|
|
@@ -354,7 +290,7 @@
|
|
| 354 |
value: |
|
| 355 |
Should visualize nucleon or particle physics data with a reasonable transfer function, and the object is shown clearly
|
| 356 |
|
| 357 |
-
#
|
| 358 |
- vars:
|
| 359 |
question: |
|
| 360 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/pancreas/data/pancreas_240x512x512_int16.raw".
|
|
@@ -370,23 +306,7 @@
|
|
| 370 |
value: |
|
| 371 |
The visualization image shows pancreas or pancreatic anatomy with a reasonable transfer function, and the object is shown clearly
|
| 372 |
|
| 373 |
-
#
|
| 374 |
-
- vars:
|
| 375 |
-
question: |
|
| 376 |
-
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/shockwave/data/shockwave_64x64x512_uint8.raw".
|
| 377 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "../SciVisAgentBench-tasks/sci_volume_data/shockwave/results/{agent_mode}/shockwave.pvsm"
|
| 378 |
-
Provide a textual report identifying what you observe and save it to "../SciVisAgentBench-tasks/sci_volume_data/shockwave/results/{agent_mode}/answers.txt"
|
| 379 |
-
assert:
|
| 380 |
-
- type: llm-rubric
|
| 381 |
-
subtype: text
|
| 382 |
-
value: |
|
| 383 |
-
Should identify shockwave or wave propagation patterns
|
| 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:
|
| 391 |
question: |
|
| 392 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/silicium/data/silicium_98x34x34_uint8.raw".
|
|
@@ -402,7 +322,7 @@
|
|
| 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 |
-
#
|
| 406 |
- vars:
|
| 407 |
question: |
|
| 408 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/skull/data/skull_256x256x256_uint8.raw".
|
|
@@ -418,7 +338,7 @@
|
|
| 418 |
value: |
|
| 419 |
1. Should identify skull or cranial bone structures
|
| 420 |
|
| 421 |
-
#
|
| 422 |
- vars:
|
| 423 |
question: |
|
| 424 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/statue_leg/data/statue_leg_341x341x93_uint8.raw".
|
|
@@ -434,7 +354,7 @@
|
|
| 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 |
-
#
|
| 438 |
- vars:
|
| 439 |
question: |
|
| 440 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/stent/data/stent_512x512x174_uint16.raw".
|
|
@@ -445,7 +365,7 @@
|
|
| 445 |
value: |
|
| 446 |
Should identify a stent or medical device mesh structure
|
| 447 |
|
| 448 |
-
#
|
| 449 |
- vars:
|
| 450 |
question: |
|
| 451 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/supernova/data/supernova_256x256x256_float32.raw".
|
|
@@ -461,23 +381,7 @@
|
|
| 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 |
-
#
|
| 465 |
-
- vars:
|
| 466 |
-
question: |
|
| 467 |
-
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/tacc_turbulence/data/tacc_turbulence_256x256x256_float32.raw".
|
| 468 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "../SciVisAgentBench-tasks/sci_volume_data/tacc_turbulence/results/{agent_mode}/tacc_turbulence.pvsm"
|
| 469 |
-
Provide a textual report identifying what you observe and save it to "../SciVisAgentBench-tasks/sci_volume_data/tacc_turbulence/results/{agent_mode}/answers.txt"
|
| 470 |
-
assert:
|
| 471 |
-
- type: llm-rubric
|
| 472 |
-
subtype: text
|
| 473 |
-
value: |
|
| 474 |
-
Should identify turbulence or vortex flow structures
|
| 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:
|
| 482 |
question: |
|
| 483 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/tooth/data/tooth_103x94x161_uint8.raw".
|
|
@@ -493,7 +397,7 @@
|
|
| 493 |
value: |
|
| 494 |
The visualization image shows tooth or dental anatomy with a reasonable transfer function, and the object is shown clearly
|
| 495 |
|
| 496 |
-
#
|
| 497 |
- vars:
|
| 498 |
question: |
|
| 499 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/tornado/data/tornado_64x64x64_float32_scalar3.raw".
|
|
@@ -509,7 +413,7 @@
|
|
| 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 |
-
#
|
| 513 |
- vars:
|
| 514 |
question: |
|
| 515 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/vis_male/data/vis_male_128x256x256_uint8.raw".
|
|
|
|
| 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. Engine Dataset
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 118 |
- vars:
|
| 119 |
question: |
|
| 120 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/engine/data/engine_256x256x128_uint8.raw".
|
|
|
|
| 130 |
value: |
|
| 131 |
The visualization image shows an engine or mechanical components with a reasonable transfer function, and the object is shown clearly
|
| 132 |
|
| 133 |
+
# 9. Foot Dataset
|
| 134 |
- vars:
|
| 135 |
question: |
|
| 136 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/foot/data/foot_256x256x256_uint8.raw".
|
|
|
|
| 146 |
value: |
|
| 147 |
The visualization image shows a foot with bone and tissue structures with a reasonable transfer function, and the object is shown clearly
|
| 148 |
|
| 149 |
+
# 10. Frog Dataset
|
| 150 |
- vars:
|
| 151 |
question: |
|
| 152 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/frog/data/frog_256x256x44_uint8.raw".
|
|
|
|
| 162 |
value: |
|
| 163 |
The visualization image shows a frog specimen with internal anatomy with a reasonable transfer function, and the object is shown clearly
|
| 164 |
|
| 165 |
+
# 11. Fuel Dataset
|
| 166 |
- vars:
|
| 167 |
question: |
|
| 168 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/fuel/data/fuel_64x64x64_uint8.raw".
|
|
|
|
| 178 |
value: |
|
| 179 |
The visualization image shows fuel combustion or related simulation with a reasonable transfer function, and the object is shown clearly
|
| 180 |
|
| 181 |
+
# 12. Hydrogen Atom Dataset
|
| 182 |
- vars:
|
| 183 |
question: |
|
| 184 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/hydrogen_atom/data/hydrogen_atom_128x128x128_uint8.raw".
|
|
|
|
| 194 |
value: |
|
| 195 |
The visualization image shows hydrogen atom orbital or probability distribution with a reasonable transfer function, and the object is shown clearly
|
| 196 |
|
| 197 |
+
# 13. Lobster Dataset
|
| 198 |
- vars:
|
| 199 |
question: |
|
| 200 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/lobster/data/lobster_301x324x56_uint8.raw".
|
|
|
|
| 210 |
value: |
|
| 211 |
The visualization image shows a lobster or crustacean anatomy with a reasonable transfer function, and the object is shown clearly
|
| 212 |
|
| 213 |
+
# 14. MRI Ventricles Dataset
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 214 |
- vars:
|
| 215 |
question: |
|
| 216 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/mri_ventricles/data/mri_ventricles_256x256x124_uint8.raw".
|
|
|
|
| 226 |
value: |
|
| 227 |
The visualization image shows brain ventricles or ventricular structures with a reasonable transfer function, and the object is shown clearly
|
| 228 |
|
| 229 |
+
# 15. MRI Woman Dataset
|
| 230 |
- vars:
|
| 231 |
question: |
|
| 232 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/mri_woman/data/mri_woman_256x256x109_uint16.raw".
|
|
|
|
| 242 |
value: |
|
| 243 |
The visualization image shows human anatomical structures from MRI scan with a reasonable transfer function, and the object is shown clearly
|
| 244 |
|
| 245 |
+
# 16. MRT Angio Dataset
|
| 246 |
- vars:
|
| 247 |
question: |
|
| 248 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/mrt_angio/data/mrt_angio_416x512x112_uint16.raw".
|
|
|
|
| 258 |
value: |
|
| 259 |
The visualization image shows angiography or vascular structures with a reasonable transfer function, and the object is shown clearly
|
| 260 |
|
| 261 |
+
# 17. Neocortical Layer 1 Axons Dataset
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 262 |
- vars:
|
| 263 |
question: |
|
| 264 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/neocortical_layer_1_axons/data/neocortical_layer_1_axons_1464x1033x76_uint8.raw".
|
|
|
|
| 274 |
value: |
|
| 275 |
The visualization image shows neural axons or neocortical network structures with a reasonable transfer function, and the object is shown clearly
|
| 276 |
|
| 277 |
+
# 18. Nucleon Dataset
|
| 278 |
- vars:
|
| 279 |
question: |
|
| 280 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/nucleon/data/nucleon_41x41x41_uint8.raw".
|
|
|
|
| 290 |
value: |
|
| 291 |
Should visualize nucleon or particle physics data with a reasonable transfer function, and the object is shown clearly
|
| 292 |
|
| 293 |
+
# 19. Pancreas Dataset
|
| 294 |
- vars:
|
| 295 |
question: |
|
| 296 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/pancreas/data/pancreas_240x512x512_int16.raw".
|
|
|
|
| 306 |
value: |
|
| 307 |
The visualization image shows pancreas or pancreatic anatomy with a reasonable transfer function, and the object is shown clearly
|
| 308 |
|
| 309 |
+
# 20. Silicium Dataset
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 310 |
- vars:
|
| 311 |
question: |
|
| 312 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/silicium/data/silicium_98x34x34_uint8.raw".
|
|
|
|
| 322 |
value: |
|
| 323 |
The visualization image shows silicon crystal or material structure with a reasonable transfer function, and the object is shown clearly
|
| 324 |
|
| 325 |
+
# 21. Skull Dataset
|
| 326 |
- vars:
|
| 327 |
question: |
|
| 328 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/skull/data/skull_256x256x256_uint8.raw".
|
|
|
|
| 338 |
value: |
|
| 339 |
1. Should identify skull or cranial bone structures
|
| 340 |
|
| 341 |
+
# 22. Statue Leg Dataset
|
| 342 |
- vars:
|
| 343 |
question: |
|
| 344 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/statue_leg/data/statue_leg_341x341x93_uint8.raw".
|
|
|
|
| 354 |
value: |
|
| 355 |
The visualization image shows a statue leg or sculptural form with a reasonable transfer function, and the object is shown clearly
|
| 356 |
|
| 357 |
+
# 23. Stent Dataset
|
| 358 |
- vars:
|
| 359 |
question: |
|
| 360 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/stent/data/stent_512x512x174_uint16.raw".
|
|
|
|
| 365 |
value: |
|
| 366 |
Should identify a stent or medical device mesh structure
|
| 367 |
|
| 368 |
+
# 24. Supernova Dataset
|
| 369 |
- vars:
|
| 370 |
question: |
|
| 371 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/supernova/data/supernova_256x256x256_float32.raw".
|
|
|
|
| 381 |
value: |
|
| 382 |
The visualization image shows supernova or astrophysical explosion simulation with a reasonable transfer function, and the object is shown clearly
|
| 383 |
|
| 384 |
+
# 25. Tooth Dataset
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 385 |
- vars:
|
| 386 |
question: |
|
| 387 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/tooth/data/tooth_103x94x161_uint8.raw".
|
|
|
|
| 397 |
value: |
|
| 398 |
The visualization image shows tooth or dental anatomy with a reasonable transfer function, and the object is shown clearly
|
| 399 |
|
| 400 |
+
# 26. Tornado Dataset
|
| 401 |
- vars:
|
| 402 |
question: |
|
| 403 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/tornado/data/tornado_64x64x64_float32_scalar3.raw".
|
|
|
|
| 413 |
value: |
|
| 414 |
The visualization image shows tornado or vortex flow pattern with a reasonable transfer function, and the object is shown clearly
|
| 415 |
|
| 416 |
+
# 27. Visible Male Dataset
|
| 417 |
- vars:
|
| 418 |
question: |
|
| 419 |
Clear the ParaView pipeline and load the data file "../SciVisAgentBench-tasks/sci_volume_data/vis_male/data/vis_male_128x256x256_uint8.raw".
|
eval_cases/paraview/what_obj_cases_anonymized.yaml
DELETED
|
@@ -1,526 +0,0 @@
|
|
| 1 |
-
# Comprehensive Data Identification Test Cases for SciVisAgentBench
|
| 2 |
-
# This test evaluates the ability to identify and understand data content
|
| 3 |
-
# without prior knowledge from metadata or naming patterns
|
| 4 |
-
|
| 5 |
-
# 1. Aneurism Dataset
|
| 6 |
-
- vars:
|
| 7 |
-
question: |
|
| 8 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_001/data/data_001_256x256x256_uint8.raw".
|
| 9 |
-
Use visualization tools to determine what object or structure is contained in this dataset. Save the paraview state as "anonymized_datasets/dataset_001/results/{agent_mode}/dataset_001.pvsm"
|
| 10 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_001/results/{agent_mode}/answers.txt"
|
| 11 |
-
assert:
|
| 12 |
-
- type: llm-rubric
|
| 13 |
-
subtype: text
|
| 14 |
-
value: |
|
| 15 |
-
The assistant should identify the data shows an aneurism or vascular structure
|
| 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:
|
| 39 |
-
question: |
|
| 40 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_003/data/data_003_256x128x64_uint8.raw".
|
| 41 |
-
Use visualization tools to determine what object or structure is in this dataset. Save the paraview state as "anonymized_datasets/dataset_003/results/{agent_mode}/dataset_003.pvsm"
|
| 42 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_003/results/{agent_mode}/answers.txt"
|
| 43 |
-
assert:
|
| 44 |
-
- type: llm-rubric
|
| 45 |
-
subtype: text
|
| 46 |
-
value: |
|
| 47 |
-
The assistant should identify a fin or aerodynamic strcuture or simulation result in the data
|
| 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:
|
| 55 |
-
question: |
|
| 56 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_004/data/data_004_256x256x256_uint8.raw".
|
| 57 |
-
Use visualization tools to determine what object is contained in this dataset. Save the paraview state as "anonymized_datasets/dataset_004/results/{agent_mode}/dataset_004.pvsm"
|
| 58 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_004/results/{agent_mode}/answers.txt"
|
| 59 |
-
assert:
|
| 60 |
-
- type: llm-rubric
|
| 61 |
-
subtype: text
|
| 62 |
-
value: |
|
| 63 |
-
Should identify a bonsai tree or botanical structure in the data
|
| 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:
|
| 71 |
-
question: |
|
| 72 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_005/data/data_005_256x256x178_uint8.raw".
|
| 73 |
-
Use visualization tools to determine what object is in this dataset. Save the paraview state as "anonymized_datasets/dataset_005/results/{agent_mode}/dataset_005.pvsm"
|
| 74 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_005/results/{agent_mode}/answers.txt"
|
| 75 |
-
assert:
|
| 76 |
-
- type: llm-rubric
|
| 77 |
-
subtype: text
|
| 78 |
-
value: |
|
| 79 |
-
Should identify a teapot in the visualization
|
| 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:
|
| 87 |
-
question: |
|
| 88 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_006/data/data_006_512x512x361_uint16.raw".
|
| 89 |
-
Use visualization tools to determine what object is in this dataset. Save the paraview state as "anonymized_datasets/dataset_006/results/{agent_mode}/dataset_006.pvsm"
|
| 90 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_006/results/{agent_mode}/answers.txt"
|
| 91 |
-
assert:
|
| 92 |
-
- type: llm-rubric
|
| 93 |
-
subtype: text
|
| 94 |
-
value: |
|
| 95 |
-
Should identify a bunny or rabbit in the 3D scanned data
|
| 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:
|
| 103 |
-
question: |
|
| 104 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_007/data/carp_256x256x512_uint16.raw".
|
| 105 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_007/results/{agent_mode}/dataset_007.pvsm"
|
| 106 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_007/results/{agent_mode}/answers.txt"
|
| 107 |
-
assert:
|
| 108 |
-
- type: llm-rubric
|
| 109 |
-
subtype: text
|
| 110 |
-
value: |
|
| 111 |
-
Should identify a carp or fish anatomy
|
| 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:
|
| 119 |
-
question: |
|
| 120 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_008/data/data_007_302x302x302_uint8.raw".
|
| 121 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_008/results/{agent_mode}/dataset_008.pvsm"
|
| 122 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_008/results/{agent_mode}/answers.txt"
|
| 123 |
-
assert:
|
| 124 |
-
- type: llm-rubric
|
| 125 |
-
subtype: text
|
| 126 |
-
value: |
|
| 127 |
-
Should recognize combustion or heptane simulation data
|
| 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:
|
| 135 |
-
question: |
|
| 136 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_009/data/data_008_193x194x1000_float32.raw".
|
| 137 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_009/results/{agent_mode}/dataset_009.pvsm"
|
| 138 |
-
Take a screenshot and provide a textual report describing what you observe and save it to "anonymized_datasets/dataset_009/results/{agent_mode}/answers.txt"
|
| 139 |
-
assert:
|
| 140 |
-
- type: llm-rubric
|
| 141 |
-
subtype: text
|
| 142 |
-
value: |
|
| 143 |
-
Should identify flow patterns in a duct geometry
|
| 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:
|
| 151 |
-
question: |
|
| 152 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_010/data/data_009_256x256x128_uint8.raw".
|
| 153 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_010/results/{agent_mode}/dataset_010.pvsm"
|
| 154 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_010/results/{agent_mode}/answers.txt"
|
| 155 |
-
assert:
|
| 156 |
-
- type: llm-rubric
|
| 157 |
-
subtype: text
|
| 158 |
-
value: |
|
| 159 |
-
Should identify an engine or mechanical components
|
| 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:
|
| 167 |
-
question: |
|
| 168 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_011/data/data_010_256x256x256_uint8.raw".
|
| 169 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_011/results/{agent_mode}/dataset_011.pvsm"
|
| 170 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_011/results/{agent_mode}/answers.txt"
|
| 171 |
-
assert:
|
| 172 |
-
- type: llm-rubric
|
| 173 |
-
subtype: text
|
| 174 |
-
value: |
|
| 175 |
-
Should identify a foot with bone and tissue structures
|
| 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:
|
| 183 |
-
question: |
|
| 184 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_012/data/data_011_256x256x44_uint8.raw".
|
| 185 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_012/results/{agent_mode}/dataset_012.pvsm"
|
| 186 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_012/results/{agent_mode}/answers.txt"
|
| 187 |
-
assert:
|
| 188 |
-
- type: llm-rubric
|
| 189 |
-
subtype: text
|
| 190 |
-
value: |
|
| 191 |
-
Should identify a frog specimen with internal anatomy
|
| 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:
|
| 199 |
-
question: |
|
| 200 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_013/data/fuel_64x64x64_uint8.raw".
|
| 201 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_013/results/{agent_mode}/dataset_013.pvsm"
|
| 202 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_013/results/{agent_mode}/answers.txt"
|
| 203 |
-
assert:
|
| 204 |
-
- type: llm-rubric
|
| 205 |
-
subtype: text
|
| 206 |
-
value: |
|
| 207 |
-
Should identify fuel combustion or related simulation
|
| 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:
|
| 215 |
-
question: |
|
| 216 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_014/data/data_012_128x128x128_uint8.raw".
|
| 217 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_014/results/{agent_mode}/dataset_014.pvsm"
|
| 218 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_014/results/{agent_mode}/answers.txt"
|
| 219 |
-
assert:
|
| 220 |
-
- type: llm-rubric
|
| 221 |
-
subtype: text
|
| 222 |
-
value: |
|
| 223 |
-
Should recognize hydrogen atom orbital or probability distribution
|
| 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:
|
| 231 |
-
question: |
|
| 232 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_015/data/data_013_301x324x56_uint8.raw".
|
| 233 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_015/results/{agent_mode}/dataset_015.pvsm"
|
| 234 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_015/results/{agent_mode}/answers.txt"
|
| 235 |
-
assert:
|
| 236 |
-
- type: llm-rubric
|
| 237 |
-
subtype: text
|
| 238 |
-
value: |
|
| 239 |
-
Should identify a lobster or crustacean anatomy
|
| 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:
|
| 247 |
-
question: |
|
| 248 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_016/data/marschner_lobb_41x41x41_uint8.raw".
|
| 249 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_016/results/{agent_mode}/dataset_016.pvsm"
|
| 250 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_016/results/{agent_mode}/answers.txt"
|
| 251 |
-
assert:
|
| 252 |
-
- type: llm-rubric
|
| 253 |
-
subtype: text
|
| 254 |
-
value: |
|
| 255 |
-
Should recognize Marschner-Lobb synthetic test pattern
|
| 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:
|
| 263 |
-
question: |
|
| 264 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_017/data/data_014_256x256x124_uint8.raw".
|
| 265 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_017/results/{agent_mode}/dataset_017.pvsm"
|
| 266 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_017/results/{agent_mode}/answers.txt"
|
| 267 |
-
assert:
|
| 268 |
-
- type: llm-rubric
|
| 269 |
-
subtype: text
|
| 270 |
-
value: |
|
| 271 |
-
Should identify brain ventricles or ventricular structures
|
| 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:
|
| 279 |
-
question: |
|
| 280 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_018/data/data_015_256x256x109_uint16.raw".
|
| 281 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_018/results/{agent_mode}/dataset_018.pvsm"
|
| 282 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_018/results/{agent_mode}/answers.txt"
|
| 283 |
-
assert:
|
| 284 |
-
- type: llm-rubric
|
| 285 |
-
subtype: text
|
| 286 |
-
value: |
|
| 287 |
-
Should identify human anatomical structures from MRI scan
|
| 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:
|
| 295 |
-
question: |
|
| 296 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_019/data/data_016_416x512x112_uint16.raw".
|
| 297 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_019/results/{agent_mode}/dataset_019.pvsm"
|
| 298 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_019/results/{agent_mode}/answers.txt"
|
| 299 |
-
assert:
|
| 300 |
-
- type: llm-rubric
|
| 301 |
-
subtype: text
|
| 302 |
-
value: |
|
| 303 |
-
Should identify angiography or vascular structures
|
| 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:
|
| 311 |
-
question: |
|
| 312 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_020/data/data_017_64x64x64_uint8.raw".
|
| 313 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_020/results/{agent_mode}/dataset_020.pvsm"
|
| 314 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_020/results/{agent_mode}/answers.txt"
|
| 315 |
-
assert:
|
| 316 |
-
- type: llm-rubric
|
| 317 |
-
subtype: text
|
| 318 |
-
value: |
|
| 319 |
-
Should visualize and describe molecule structure
|
| 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:
|
| 327 |
-
question: |
|
| 328 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_021/data/neocortical_layer_1_axons_1464x1033x76_uint8.raw".
|
| 329 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_021/results/{agent_mode}/dataset_021.pvsm"
|
| 330 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_021/results/{agent_mode}/answers.txt"
|
| 331 |
-
assert:
|
| 332 |
-
- type: llm-rubric
|
| 333 |
-
subtype: text
|
| 334 |
-
value: |
|
| 335 |
-
Should identify neural axons or neocortical network structures
|
| 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:
|
| 343 |
-
question: |
|
| 344 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_022/data/data_018_41x41x41_uint8.raw".
|
| 345 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_022/results/{agent_mode}/dataset_022.pvsm"
|
| 346 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_022/results/{agent_mode}/answers.txt"
|
| 347 |
-
assert:
|
| 348 |
-
- type: llm-rubric
|
| 349 |
-
subtype: text
|
| 350 |
-
value: |
|
| 351 |
-
Should visualize nucleon or particle physics data
|
| 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:
|
| 359 |
-
question: |
|
| 360 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_023/data/pancreas_240x512x512_int16.raw".
|
| 361 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_023/results/{agent_mode}/dataset_023.pvsm"
|
| 362 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_023/results/{agent_mode}/answers.txt"
|
| 363 |
-
assert:
|
| 364 |
-
- type: llm-rubric
|
| 365 |
-
subtype: text
|
| 366 |
-
value: |
|
| 367 |
-
Should identify pancreas or pancreatic anatomy
|
| 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:
|
| 375 |
-
question: |
|
| 376 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_024/data/shockwave_64x64x512_uint8.raw".
|
| 377 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_024/results/{agent_mode}/dataset_024.pvsm"
|
| 378 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_024/results/{agent_mode}/answers.txt"
|
| 379 |
-
assert:
|
| 380 |
-
- type: llm-rubric
|
| 381 |
-
subtype: text
|
| 382 |
-
value: |
|
| 383 |
-
Should identify shockwave or wave propagation patterns
|
| 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:
|
| 391 |
-
question: |
|
| 392 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_025/data/silicium_98x34x34_uint8.raw".
|
| 393 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_025/results/{agent_mode}/dataset_025.pvsm"
|
| 394 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_025/results/{agent_mode}/answers.txt"
|
| 395 |
-
assert:
|
| 396 |
-
- type: llm-rubric
|
| 397 |
-
subtype: text
|
| 398 |
-
value: |
|
| 399 |
-
Should identify silicon crystal or material structure
|
| 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:
|
| 407 |
-
question: |
|
| 408 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_026/data/skull_256x256x256_uint8.raw".
|
| 409 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_026/results/{agent_mode}/dataset_026.pvsm"
|
| 410 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_026/results/{agent_mode}/answers.txt"
|
| 411 |
-
assert:
|
| 412 |
-
- type: llm-rubric
|
| 413 |
-
subtype: text
|
| 414 |
-
value: |
|
| 415 |
-
1. Should identify skull or cranial bone structures
|
| 416 |
-
- type: llm-rubric
|
| 417 |
-
subtype: vision
|
| 418 |
-
value: |
|
| 419 |
-
1. Should identify skull or cranial bone structures
|
| 420 |
-
|
| 421 |
-
# 27. Statue Leg Dataset
|
| 422 |
-
- vars:
|
| 423 |
-
question: |
|
| 424 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_027/data/data_019_341x341x93_uint8.raw".
|
| 425 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_027/results/{agent_mode}/dataset_027.pvsm"
|
| 426 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_027/results/{agent_mode}/answers.txt"
|
| 427 |
-
assert:
|
| 428 |
-
- type: llm-rubric
|
| 429 |
-
subtype: text
|
| 430 |
-
value: |
|
| 431 |
-
Should identify a statue leg or sculptural form
|
| 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:
|
| 439 |
-
question: |
|
| 440 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_028/data/stent_512x512x174_uint16.raw".
|
| 441 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_028/results/{agent_mode}/dataset_028.pvsm"
|
| 442 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_028/results/{agent_mode}/answers.txt"
|
| 443 |
-
assert:
|
| 444 |
-
- type: llm-rubric
|
| 445 |
-
value: |
|
| 446 |
-
Should identify a stent or medical device mesh structure
|
| 447 |
-
|
| 448 |
-
# 29. Supernova Dataset
|
| 449 |
-
- vars:
|
| 450 |
-
question: |
|
| 451 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_029/data/data_020_256x256x256_float32.raw".
|
| 452 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_029/results/{agent_mode}/dataset_029.pvsm"
|
| 453 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_029/results/{agent_mode}/answers.txt"
|
| 454 |
-
assert:
|
| 455 |
-
- type: llm-rubric
|
| 456 |
-
subtype: text
|
| 457 |
-
value: |
|
| 458 |
-
Should identify supernova or astrophysical explosion simulation
|
| 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:
|
| 466 |
-
question: |
|
| 467 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_030/data/tacc_turbulence_256x256x256_float32.raw".
|
| 468 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_030/results/{agent_mode}/dataset_030.pvsm"
|
| 469 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_030/results/{agent_mode}/answers.txt"
|
| 470 |
-
assert:
|
| 471 |
-
- type: llm-rubric
|
| 472 |
-
subtype: text
|
| 473 |
-
value: |
|
| 474 |
-
Should identify turbulence or vortex flow structures
|
| 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:
|
| 482 |
-
question: |
|
| 483 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_031/data/data_021_103x94x161_uint8.raw".
|
| 484 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_031/results/{agent_mode}/dataset_031.pvsm"
|
| 485 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_031/results/{agent_mode}/answers.txt"
|
| 486 |
-
assert:
|
| 487 |
-
- type: llm-rubric
|
| 488 |
-
subtype: text
|
| 489 |
-
value: |
|
| 490 |
-
Should identify tooth or dental anatomy
|
| 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:
|
| 498 |
-
question: |
|
| 499 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_032/data/data_022_64x64x64_float32_scalar3.raw".
|
| 500 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_032/results/{agent_mode}/dataset_032.pvsm"
|
| 501 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_032/results/{agent_mode}/answers.txt"
|
| 502 |
-
assert:
|
| 503 |
-
- type: llm-rubric
|
| 504 |
-
subtype: text
|
| 505 |
-
value: |
|
| 506 |
-
Should identify tornado or vortex flow pattern
|
| 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:
|
| 514 |
-
question: |
|
| 515 |
-
Clear the ParaView pipeline and load the data file "anonymized_datasets/dataset_033/data/data_023_128x256x256_uint8.raw".
|
| 516 |
-
Use visualization tools to examine what is shown in this dataset. Save the paraview state as "anonymized_datasets/dataset_033/results/{agent_mode}/dataset_033.pvsm"
|
| 517 |
-
Provide a textual report identifying what you observe and save it to "anonymized_datasets/dataset_033/results/{agent_mode}/answers.txt"
|
| 518 |
-
assert:
|
| 519 |
-
- type: llm-rubric
|
| 520 |
-
subtype: text
|
| 521 |
-
value: |
|
| 522 |
-
Should identify human anatomical structures
|
| 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
main/bonsai/.DS_Store
DELETED
|
Binary file (8.2 kB)
|
|
|
main/bonsai/GS/.DS_Store
DELETED
|
Binary file (6.15 kB)
|
|
|
{main → paraview}/ABC/GS/ABC_gs.png
RENAMED
|
File without changes
|
{main → paraview}/ABC/GS/ABC_gs.pvsm
RENAMED
|
File without changes
|
{main → paraview}/ABC/GS/ABC_gs.py
RENAMED
|
File without changes
|
{main → paraview}/ABC/data/ABC.txt
RENAMED
|
File without changes
|
{main → paraview}/ABC/data/ABC_128x128x128_float32_scalar3.raw
RENAMED
|
File without changes
|
{main → paraview}/ABC/task_description.txt
RENAMED
|
File without changes
|
{main → paraview}/ABC/visualization_goals.txt
RENAMED
|
File without changes
|
{main → paraview}/Bernard/GS/Bernard_gs.png
RENAMED
|
File without changes
|
{main → paraview}/Bernard/GS/Bernard_gs.pvsm
RENAMED
|
File without changes
|
{main → paraview}/Bernard/GS/Bernard_gs.py
RENAMED
|
File without changes
|
{main → paraview}/Bernard/data/Bernard.txt
RENAMED
|
File without changes
|
{main → paraview}/Bernard/data/Bernard_128x32x64_float32_scalar3.raw
RENAMED
|
File without changes
|
{main → paraview}/Bernard/task_description.txt
RENAMED
|
File without changes
|
{main → paraview}/Bernard/visualization_goals.txt
RENAMED
|
File without changes
|
{chatvis_bench → paraview}/README.md
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/CMakeLists.txt
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/argon-bubble_gs.cxx
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/argon-bubble_gs.png
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeCache.txt
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CMakeCCompiler.cmake
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CMakeCXXCompiler.cmake
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CMakeDetermineCompilerABI_C.bin
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CMakeDetermineCompilerABI_CXX.bin
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CMakeSystem.cmake
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdC/CMakeCCompilerId.c
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdC/a.out
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdC/apple-sdk.c
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdCXX/CMakeCXXCompilerId.cpp
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdCXX/a.out
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/4.2.0/CompilerIdCXX/apple-sdk.cpp
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/CMakeConfigureLog.yaml
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/CMakeDirectoryInformation.cmake
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/InstallScripts.json
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/Makefile.cmake
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/Makefile2
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/TargetDirectories.txt
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/DependInfo.cmake
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/argon-bubble_gs.cxx.o
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/argon-bubble_gs.cxx.o.d
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/build.make
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/cmake_clean.cmake
RENAMED
|
File without changes
|
{main → paraview}/argon-bubble/GS/build/CMakeFiles/argon-bubble.dir/compiler_depend.make
RENAMED
|
File without changes
|