# Not Opening a File - Called by an external python Command line

**URL:** <https://discourse.slicer.org/t/not-opening-a-file-called-by-an-external-python-command-line/4144>\
**Category:** Support\
**Tags:** extensions-manager, python\
**Created:** [September 18, 2018, 3:18pm UTC](https://discourse.slicer.org/t/not-opening-a-file-called-by-an-external-python-command-line/4144 "2018-09-18T15:18:21Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [October 3, 2018, 7:34pm UTC](https://discourse.slicer.org/t/not-opening-a-file-called-by-an-external-python-command-line/4144/6 "2018-10-03T19:34:46Z")

</div>

See

> [@How to set volume rendering preset using Python](https://discourse.slicer.org/t/how-to-set-volume-rendering-preset-using-python/3063/2):
>
> Hi Oliver, There have been some improvements since 4.8.1 that makes it easier for us to do this. So if you use the latest nightly, then this is what you can do: Easier setup of volume rendering (no need to create the display node and update it from the logic): volRenLogic = slicer.modules.volumerendering.logic() displayNode = volRenLogic.CreateDefaultVolumeRenderingNodes(volumeNode) This is not very clean, because it uses widgets from the volume rendering module, but you can apply a shift li…

---

_[View the full topic](https://discourse.slicer.org/t/not-opening-a-file-called-by-an-external-python-command-line/4144)._