You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The visualize_materials method uses the morphology_visualizer function to produce a visualization of composition and orientation of the model within the morphology object.
Currently, the library only supports visualization of horizontal slices. This can make visualization checks difficult when meaningful structure is included in the z-direction. A vertical modality for visualization would be a significant enhancement.
TODO:
Construct and integrate a vertical visualization modality
To avoid breaking changes, it may make sense to create this as a separate method from the current visualize_materials, which has a crazy number of optional arguments aleady.
The style of the plots should match existing visualizer, and similar optional arguments should be provided.
IMPORTANT:
The visualization modules of the NRSS MUST be bugproof and heavily vetted. Users will rely on them as the ground truth of what was simulated. User experience strongly suggests that mistakes with regard to algorithmically created morphologies - specifically misunderstandings about what the morphologies actually contain - are one of the principal sources of error, confusion, and lost time with NRSS workflows. A visualization with any potential to lie to the user would be worse than no visualization.
The text was updated successfully, but these errors were encountered:
The visualize_materials method uses the morphology_visualizer function to produce a visualization of composition and orientation of the model within the morphology object.
Currently, the library only supports visualization of horizontal slices. This can make visualization checks difficult when meaningful structure is included in the z-direction. A vertical modality for visualization would be a significant enhancement.
TODO:
IMPORTANT:
The visualization modules of the NRSS MUST be bugproof and heavily vetted. Users will rely on them as the ground truth of what was simulated. User experience strongly suggests that mistakes with regard to algorithmically created morphologies - specifically misunderstandings about what the morphologies actually contain - are one of the principal sources of error, confusion, and lost time with NRSS workflows. A visualization with any potential to lie to the user would be worse than no visualization.
The text was updated successfully, but these errors were encountered: