# Pythonic interface to ITK filters

**URL:** https://discourse.itk.org/t/pythonic-interface-to-itk-filters/1106
**Category:** Community
**Tags:** python
**Created:** [July 9, 2018, 3:14pm UTC](https://discourse.itk.org/t/pythonic-interface-to-itk-filters/1106 "2018-07-09T15:14:05Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![matt.mccormick](https://discourse.itk.org/user_avatar/discourse.itk.org/matt.mccormick/32/7_2.png) [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)
#### Post date: [July 19, 2018, 4:18pm UTC](https://discourse.itk.org/t/pythonic-interface-to-itk-filters/1106/7 "2018-07-19T16:18:36Z")

</div>

> [@gdevenyi](#):
>
> Okay, I’ll ask the question slightly differently then, what are the major differences between SimpleITK and ITK’s pythonic interfaces?

- For the procedural functions, SimpleITK has custom function names created per image filter that are CamelCase, e.g. `sitk.Median` versus the snake\_case version of the corresponding ITK filter, e.g. `itk.median_image_filter`
- Parameters for SimpleITK are often custom positional or camelCase, where parameters for ITK are the `snake_case` keyword arguments that correspond to the `SetParameterName` methods.
- SimpleITK supports image filters. ITK’s Pythonic functions are anything that inherits from `itk.ProjectObject`, i.e. mesh filters, point set filters, path filters, image filters …

---

_[View the full topic](https://discourse.itk.org/t/pythonic-interface-to-itk-filters/1106)._