# ProbeVolumeWithModel produces wrong output in code

**URL:** <https://discourse.slicer.org/t/probevolumewithmodel-produces-wrong-output-in-code/22485>\
**Category:** Support\
**Created:** [March 13, 2022, 4:36pm UTC](https://discourse.slicer.org/t/probevolumewithmodel-produces-wrong-output-in-code/22485 "2022-03-13T16:36:23Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [March 14, 2022, 4:12pm UTC](https://discourse.slicer.org/t/probevolumewithmodel-produces-wrong-output-in-code/22485/8 "2022-03-14T16:12:33Z")

</div>

This is a very interesting discussion, I’ve started a new topic for it to get some more visibility:

> [@Make it easier to select input nodes for Python scripts](https://discourse.slicer.org/t/make-it-easier-to-select-input-nodes-for-python-scripts/22498):
>
> While discussing a [problem due to selecting the wrong input node in a Python script](https://discourse.slicer.org/t/probevolumewithmodel-produces-wrong-output-in-code/22485), we started to brainstorm about how to make it easier to select input nodes for Python scripts. The first idea was to [change vtkMRMLScene::GetFirstNodeByName to return non-hidden node](https://discourse.slicer.org/t/probevolumewithmodel-produces-wrong-output-in-code/22485/6) by default. Then @pieper raised the idea of [adding a slicer.util.pickNode method to show a popup where the user can select a node](https://discourse.slicer.org/t/probevolumewithmodel-produces-wrong-output-in-code/22485/7). I’ve created this topic to make this discussion more visible and get some more ideas and feedback …

---

_[View the full topic](https://discourse.slicer.org/t/probevolumewithmodel-produces-wrong-output-in-code/22485)._