http://www.sidefx.com/docs/houdini/vex/functions/opfullpath.html [www.sidefx.com]
http://www.sidefx.com/docs/houdini/vex/functions/relativepath.html [www.sidefx.com]
Here's one way to use opfullpath to return a string node name:
s@pathfull = opfullpath("../timeshift1"); s[]@pathsplit = split(s@pathfull, "/"); s@nodename = s[]@pathsplit[-1];
Now I have to ask, what are you doing?
It isn't that efficient to fetch a single node name for all the data/points you are ripping through.
If you have unique nodes to apply to different items you are processing, sure. But strings aren't the most efficient method through vex for lots of data processing.
It may be better to put a local spare parameter on the node and build out the string once as a set of parameters when the node cooks.
Python is very powerful at string manipulation while in vex it is somewhat limited…