Adding Semantic Information to an "instance proxy"

Omniverse Synthetic Data Generation (SDG)
1

Dear Omniverse Community,

when I tried to assign semantic data to the objects in the warehouse demo scene, i came across this problem:
As this rack for example is an instance of another usd from the content browser, i cant assign any semantic data to its components. I could only assign data to the whole RackLarge Xform.

grafik
grafik1920×897 147 KB

Here is the complete error message:

2024-10-03 18:50:07 [172,330ms] [Error] [omni.ui.python] ErrorException:
        Error in 'pxrInternal_v0_22__pxrReserved__::UsdStage::_ValidateEditPrim' at line 1330 in file C:\g\97199581\USD\pxr\usd\usd\stage.cpp : 'Cannot create prim spec at path </World/RackLarge_A7/RackLarge_A7_05/RackLargeEmpty_A1>; authoring to an instance proxy is not allowed.'

At:
  c:/users/reiem/appdata/local/ov/pkg/isaac-sim-4.2.0/extscache/semantics.schema.editor-0.3.8/semantics/schema/editor/ext.py(286): _update_single_entry
  c:/users/reiem/appdata/local/ov/pkg/isaac-sim-4.2.0/extscache/semantics.schema.editor-0.3.8/semantics/schema/editor/ext.py(283): add_entry
  c:/users/reiem/appdata/local/ov/pkg/isaac-sim-4.2.0/extscache/semantics.schema.editor-0.3.8/semantics/schema/editor/ext.py(431): _add_to_all_entries
  c:/users/reiem/appdata/local/ov/pkg/isaac-sim-4.2.0/extscache/semantics.schema.editor-0.3.8/semantics/schema/editor/ext.py(509): <lambda>

Does someone know how i can assign semantic labels to the individual objects?

Thanks for the help

2

@valentin.meier, i am just another user, but you may need to open up the RackLarge_A7.usd to do the semantic labels. but once it’s done, it should propagate your labeling to all instances of that asset used elsewhere (even outside of the warehouse scene). the reason why you aren’t able to is likely because the asset you are trying to modify is…1) an instanceable asset 2) a reference of another file. so by opening up the source and modify it there, you should have direct access to all the individual components that is in the original usd file (RackLarge_A7.usd).

in case you can’t make modifications on the RackLarge_A7.usd, it could be related to it being a library asset; thus, preventing you from making modifications. if that’s the case, you could then try making a copy of the asset first to either localhost server or local drive before making changes there. just remember to repath the asset in the warehouse scene so it uses the newly duplicated usd asset with proper labeling.

3

Thanks for the help. I will try this, even though it will be very tedious.