TOP Fetch to behave like ROP Fetch or ROPs in general

   Views 440   Replies 0   Subscribers 2
User Avatar
Member
9088 posts
Joined: July 2007
Offline
is there any way to make TOP Fetch or Import Workitems TOP to behave like ROP fetch TOP in a sense that it can

- reference TOP node from different (or even the same) TOPnet in the same file
- can Generate/Show workitems of the fetched top without needing to cook it (unless the fetched top is dynamic)
- essentially it should behave as if it was instance of the fetched TOP

the main usecase is to be able to Fetch terminal TOP from nodes like Filecache or Labs Filecache SOP which are already configured for the desired task (ranges, wedges, potentially resource requirements, ...) and be able to build larger dependency network among filecaches and other nodes or other scattered TOPnetworks in the file

I may be missing something, but I haven't seen any examples of this being possible and yet in ROPs is the may workflow
I have seen setups with ROP Fetch which heavily rely on this, but nothing that can reference the whole Topnet without having to pre-cook it or represent as an opaque single static workitem

- TOP Fetch TOP seems to require the topnet pre cooked to be able to show workitems and also seems to jump through hoops of caching external json so it feels very detached
- Workitem Import TOP seems closest to this, and it even has an option to Evaluate wit Work Item Attributes which sounds great for additional wedging
(it seems to always error out when referencing ropgeometry1 TOP node from Filecache SOP even the cooked one saying "TOP node cannot be cooked", it works when adding and referencing Output TOP under it)
however it also forces the cook even on generate, so it's also not a true representation of the fetched TOP


the example from Filecache talk [vimeo.com] seemed very convoluted as it involves creating matching Filecache TOP and referencing all parameters which doesn't generalize well to referencing custom topnets and doesn't feel very clean

does anyone have a successful workflow for fetching terminal nodes of separate TOPnets and building simple dependency network among them that can be statically resolved (to examine dependencies and workitem counts) if all fetched networks are static?
Edited by tamte - Jan. 31, 2025 02:04:21
Tomas Slancik
CG Supervisor
Framestore, NY
  • Quick Links