# Pi\_z input to TransitionPath\_InfHorz and ValueFnOnTransPath\_InfHorz

**URL:** https://discourse.vfitoolkit.com/t/pi-z-input-to-transitionpath-infhorz-and-valuefnontranspath-infhorz/647
**Category:** Uncategorized
**Created:** [May 6, 2026, 8:47pm UTC](https://discourse.vfitoolkit.com/t/pi-z-input-to-transitionpath-infhorz-and-valuefnontranspath-infhorz/647 "2026-05-06T20:47:31Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![robertdkirkby](https://discourse.vfitoolkit.com/user_avatar/discourse.vfitoolkit.com/robertdkirkby/32/287_2.png) [@robertdkirkby](https://discourse.vfitoolkit.com/u/robertdkirkby)
#### Post date: [May 6, 2026, 8:47pm UTC](https://discourse.vfitoolkit.com/t/pi-z-input-to-transitionpath-infhorz-and-valuefnontranspath-infhorz/647/1 "2026-05-06T20:47:31Z")

</div>

Moved the pi\_z input so that it now comes after z\_grid (like it does in all the other commands). Three commands are impacted:  
TransitionPath\_InfHorz()  
ValueFnOnTransPath\_InfHorz()  
ValueFnOnTransPath\_InfHorz\_PType()

I added a check in case you put it in the old place, there will be an error thrown that tells you to check where you listed it as an input.

Going to go update all the examples now.

Annoying for users, but is part of the v2.5 cleaning up of how the InfHorz commands work.