That is works!
But how did you set “ResultData” for “Generic Generator” from CMD execution? How to do it for some other command?
Found 180 posts.
Search results Show results as topic list.
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
Clear enough.
Let's focusing on your example as it is far not so bad solution.
Your example is better because of port/ip sets automatically and we don't need to care about the shutdown.
But how to make it work?
- it doesn't work in my case because “Attribute Create” node create empty ‘trackaddress’ parm early then tracker is started.
- “Dynamic” generation is helping to create attrs in the right time but ROPFetch is saying: “When not generating static items, batch mode can only be used when the ”Full Range for Upsteam Items“ is selected”
- “Python Script” node still doing it after ‘onGenerate’ callback
Let's focusing on your example as it is far not so bad solution.
Your example is better because of port/ip sets automatically and we don't need to care about the shutdown.
But how to make it work?
- it doesn't work in my case because “Attribute Create” node create empty ‘trackaddress’ parm early then tracker is started.
- “Dynamic” generation is helping to create attrs in the right time but ROPFetch is saying: “When not generating static items, batch mode can only be used when the ”Full Range for Upsteam Items“ is selected”
- “Python Script” node still doing it after ‘onGenerate’ callback
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
oh.. now it is clear. It wasn't intuitive that tracker doesn't work anymore. So how about to make it intuitive: if workitem state is cooked then tracker is alive and some another workitem has to stop tracker or when workitem is dirty (then tracker stops too)?
Anyway, “attribute create” doesn't work because it doesn't wait for values above.
Let's take a look on our issue again - would be nice to have the possibility to define workitem slices before ROPFetche (because we have some individual data for each slice) and actually, you already doing it in your example. So the question is to find completely another approach for it or make (finalise) simtracker outside of ROPFetch node?
Looking forward to your reply.
Anyway, “attribute create” doesn't work because it doesn't wait for values above.
Let's take a look on our issue again - would be nice to have the possibility to define workitem slices before ROPFetche (because we have some individual data for each slice) and actually, you already doing it in your example. So the question is to find completely another approach for it or make (finalise) simtracker outside of ROPFetch node?
Looking forward to your reply.
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
But even if I pointing to $HFS directory and the task is a success (state: Cooked) with the resulting output: http://mycomputer:36329
Even then tracker didn't start (by this web address - http://mycomputer:36329)
Even then tracker didn't start (by this web address - http://mycomputer:36329)
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
Maybe I'm doing something wrong but tracker doesn't work for me : (
Attribute Create doesn't work when you run the whole chain (values just empty after Generic Generator). If I run manually node by node then values passing.
When I run your scene as it is tracker (Generic Generator) raising error:When I'm pointing directly to the tracker.py file then
tracker (Generic Generator) creating tracker/webpage address but this address is empty.
Why you are copying tracker.py script to temp PDG_SCRIPTDIR? Why not run it from directly from a $HFS folder? Ca you please point me to the mechanism which is knowing what has to be copied to PDG_SCRIPTDIR?
Houdini build 15.5.277
Can you help, please.
Attribute Create doesn't work when you run the whole chain (values just empty after Generic Generator). If I run manually node by node then values passing.
When I run your scene as it is tracker (Generic Generator) raising error:
.../tracker.py, line 31, in <module> from pdgjob.pdgcmd import pdgjob.pdgcmd reportResultData ImportError: No module named pdgjob.pdgcmd
tracker (Generic Generator) creating tracker/webpage address but this address is empty.
Why you are copying tracker.py script to temp PDG_SCRIPTDIR? Why not run it from directly from a $HFS folder? Ca you please point me to the mechanism which is knowing what has to be copied to PDG_SCRIPTDIR?
Houdini build 15.5.277
Can you help, please.
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
Ohh… That is a really cool example! Especially I like this trick with tracker/sharedserver!
But as usual, I have a question: Where/Why you are using slicetype and control attrs (from Wedge node)?
But as usual, I have a question: Where/Why you are using slicetype and control attrs (from Wedge node)?
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
We all know Houdini for freedom of customization and combination and looks like PDG developing in the same way.
So if you allowed, I would like to show you one of the possible options for simtraker and ROPFetch combination (hip file in attachment). In this example, logic is divided into the smaller block and what is most important for us - is geometry path output could be inherited from upstream workitem (in our case, each slice has a completely different path). simtraker - is not a part of geometry so I removed it out from the main dependencies scope (to make geometry dependencies more cleaner)
I will be appreciated for your review.
So if you allowed, I would like to show you one of the possible options for simtraker and ROPFetch combination (hip file in attachment). In this example, logic is divided into the smaller block and what is most important for us - is geometry path output could be inherited from upstream workitem (in our case, each slice has a completely different path). simtraker - is not a part of geometry so I removed it out from the main dependencies scope (to make geometry dependencies more cleaner)
I will be appreciated for your review.
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
Would be super nice if distributed slices can source workitem from the wedge. In this case, we can predefine some additional parameters (like output file per slice) more procedural.
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
Thanks for the explanation.
I thought that make separated simtracker and ROPFetch node will make logic slightly ease and in case (of using distributed option) will not change ROPFetch node behavior so dramatically.
Question is still open - how to make procedural dependencies between distributed nodes?
Can you please take a look at this example?
I thought that make separated simtracker and ROPFetch node will make logic slightly ease and in case (of using distributed option) will not change ROPFetch node behavior so dramatically.
Question is still open - how to make procedural dependencies between distributed nodes?
Can you please take a look at this example?
Edited by Ostap - May 28, 2019 04:26:48
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
Hi,
Is it possible to take a look at this issue?
We are not sure how to work with it.
Thanks
Ostap
Is it possible to take a look at this issue?
We are not sure how to work with it.
Thanks
Ostap
PDG/TOPs » Long `onGenerate` callback
- Ostap
- 209 posts
- Offline
PDG/TOPs » Long `onGenerate` callback
- Ostap
- 209 posts
- Offline
Hi,
Is it possible to visualize long `onGenerate` process without holding the whole Houdini?
Just to show to user that something is going on.
Like you have with a dynamic generation or cmd execution.
Thanks
Ostap
Is it possible to visualize long `onGenerate` process without holding the whole Houdini?
Just to show to user that something is going on.
Like you have with a dynamic generation or cmd execution.
Thanks
Ostap
PDG/TOPs » Set spare parameters from Python Processor Node
- Ostap
- 209 posts
- Offline
In my case, it is for data visual representation without clicking on workitems.
I agree that we need to be careful with this possibility but anyway, nice that we have this option.
I agree that we need to be careful with this possibility but anyway, nice that we have this option.
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
And when dist. sim. is on (ROPFetch) then ‘Evaluate Using: Single Frame’ doesn't work. Is any reason why?
Houdini build: 17.5.242
Houdini build: 17.5.242
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
Is it possible to take over control on slice workitems? To have the possibility first prepare slice workitems and then deliver them to ROPFecth (to make it procedural)? Because looks like, slices behave just like wedges. Maybe it will be more PDG way?
Edited by Ostap - May 27, 2019 00:59:18
PDG/TOPs » Set spare parameters from Python Processor Node
- Ostap
- 209 posts
- Offline
PDG/TOPs » ROP Fetch: Distribution options as a separate node
- Ostap
- 209 posts
- Offline
HI,
Can you please explain why you integrated distribution option to ROP Fetch node? I'm asking because it slightly confusing me that it is a function of fetching.
It doesn't make sense for all other ROPs (except geometry) to have this option.
I remember that in first builds of Houdini 17.5 it was as a separate node.
For me, it makes sense as a custom wedge node.
Thanks
Ostap
Can you please explain why you integrated distribution option to ROP Fetch node? I'm asking because it slightly confusing me that it is a function of fetching.
It doesn't make sense for all other ROPs (except geometry) to have this option.
I remember that in first builds of Houdini 17.5 it was as a separate node.
For me, it makes sense as a custom wedge node.
Thanks
Ostap
PDG/TOPs » Set spare parameters from Python Processor Node
- Ostap
- 209 posts
- Offline
Hi,
Is it possible to set spare parameters value from Python Processor or any other PDG Node?
Thanks
Ostap
Is it possible to set spare parameters value from Python Processor or any other PDG Node?
Thanks
Ostap
Edited by Ostap - May 19, 2019 18:45:16
PDG/TOPs » Processing multiple wedged simulations
- Ostap
- 209 posts
- Offline
Agree. Should be a nice solution.
Are you planning to implement it for all ROP Feth nodes?
Are you planning to implement it for all ROP Feth nodes?
-
- Quick Links