You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I monkey-patched your Graph class, put an add_pool(self, pool_name, pool_depth) method and exported it. In Craftrfile I explicitely called this method.
Actually, what you got there looks good. 😄 You're only missing a genpool(), or so, function in there. I'm thinking of whether it would make sense to have pool names also be automatically prefixed with the name of your Craftr module, or allow multiple modules create pools with the same name, effectively making them the same pool (even if the module's may not know about the other module that uses the same pool).
Well I'm using pools for a heavy-memory-usage rule in my custom geometric pipeline.
I'm not sure that it's possible to reuse pools transparently. I think that a root pipline author may create some kind of pool objects and pass them to the modules, but I'm not sure. But I think that using the module prefix should be an option (like gtn function calling).
Hi Niklas!
I also need to customize pools for my pipeline :)
I monkey-patched your Graph class, put an
add_pool(self, pool_name, pool_depth)
method and exported it. In Craftrfile I explicitely called this method.mcquay239@20544ab
But I suppose you planned to do it in a different way. What do I need to implement to create a pull request?
The text was updated successfully, but these errors were encountered: