# Can't turn off or capture INFO messages from vtkCutter in Python
**URL:** https://discourse.vtk.org/t/cant-turn-off-or-capture-info-messages-from-vtkcutter-in-python/14227
**Category:** Support
**Tags:** python
**Created:** [July 14, 2024, 6:39am UTC](https://discourse.vtk.org/t/cant-turn-off-or-capture-info-messages-from-vtkcutter-in-python/14227 "2024-07-14T06:39:24Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@michaelhogg](https://discourse.vtk.org/u/michaelhogg)
#### Post date: [July 14, 2024, 6:39am UTC](https://discourse.vtk.org/t/cant-turn-off-or-capture-info-messages-from-vtkcutter-in-python/14227/1 "2024-07-14T06:39:24Z")
Hi all,
I’m using a vtkCutter in Python to cut polydata with a plane and getting INFO output everytime I update the cutter. For example:
```auto
e[0me[2m2024-07-14 16:29:49.498 ( 1.109s) [722103]vtkPolyDataPlaneCutter.:589 INFO| e[0mExecuting vtkPolyData plane cuttere
```
I have tried to turn this off using vtk.vtkObject.GlobalWarningDisplayOff() or adding an observer to the cutter instance, but because it is INFO and not WARNING or ERROR, it appears that I can’t.
This appears to be unusual behaviour, and it doesn’t happen to any other vtk objects. Is this a bug? Or can I turn it off somehow?
vtk version is 9.3.1 running on MacOS 14.5
Cheers,
Michael
---
### Author:  [@cory.quammen](https://discourse.vtk.org/u/cory.quammen)
#### Post date: [July 14, 2024, 3:05pm UTC](https://discourse.vtk.org/t/cant-turn-off-or-capture-info-messages-from-vtkcutter-in-python/14227/2 "2024-07-14T15:05:54Z")
This was an accidental usage of INFO when TRACE was intended. It has been removed in [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/11260](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/11260).
You can disable it by setting the verbosity with [`vtkLogger::SetStderrVerbosity()`](https://vtk.org/doc/nightly/html/classvtkLogger.html#aafe642339f32388f839026a4087306c1) somewhere early in your application. Try setting it to `vtkLogger::VERBOSITY_WARNING` to turn off INFO messages.
---
### Author:  [@michaelhogg](https://discourse.vtk.org/u/michaelhogg)
#### Post date: [July 14, 2024, 11:24pm UTC](https://discourse.vtk.org/t/cant-turn-off-or-capture-info-messages-from-vtkcutter-in-python/14227/3 "2024-07-14T23:24:04Z")
Great, thanks for the answer
---
### Author:  [@michaelhogg](https://discourse.vtk.org/u/michaelhogg)
#### Post date: [October 24, 2024, 10:48am UTC](https://discourse.vtk.org/t/cant-turn-off-or-capture-info-messages-from-vtkcutter-in-python/14227/4 "2024-10-24T10:48:38Z")
Hey Cory,
I just tested 9.4.0rc2 and i’m getting INFO messages related to vtkExtractEdges:
2024-10-24 21:38:54.586 ( 13.364s) [18B3117] vtkExtractEdges.cxx:329 INFO| Executing edge extractor with original point numbering
2024-10-24 21:38:54.599 ( 13.377s) [18B3117] vtkExtractEdges.cxx:392 INFO| Created 132380 edges
Could this be related to INFO / TRACE again?
---
### Author:  [@cory.quammen](https://discourse.vtk.org/u/cory.quammen)
#### Post date: [October 24, 2024, 11:55am UTC](https://discourse.vtk.org/t/cant-turn-off-or-capture-info-messages-from-vtkcutter-in-python/14227/5 "2024-10-24T11:55:29Z")
Yep. Those should be changed to TRACE as well.
---
### Author:  [@cory.quammen](https://discourse.vtk.org/u/cory.quammen)
#### Post date: [October 28, 2024, 2:13am UTC](https://discourse.vtk.org/t/cant-turn-off-or-capture-info-messages-from-vtkcutter-in-python/14227/6 "2024-10-28T02:13:02Z")
Fix is here: [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/11591](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/11591)