Failed to launch example command of replicator composer

[hirose.sgia]

Hi!
when i try to use replicator composer from command line, i failed launch it and got error of “import Error”.

i have used command of replicator composer tutorial without --headless argument.
https://docs.omniverse.nvidia.com/app_isaacsim/app_isaacsim/tutorial_replicator_composer.html#sample-input-parameterizations

the command is
“./python.sh tools/composer/src/main.py --input parameters/warehouse.yaml --output */datasets/warehouse --num-scenes 10 --mount ~/workspaces/isaac/”

the error is
"ImportError: /home/sota/.local/share/ov/pkg/isaac_sim-2021.2.1/kit/extscore/omni.usd.libs/bin/libjs.so: undefined symbol: _ZN32pxrInternal_v0_20__pxrReserved__18
Tf_PostErrorHelperERKNS_13TfCallContextENS_16TfDiagnosticTypeEPKcz
"

i use isaac sim 2021.2.1.

]

could you show me how to resolve error and launch replicator composer?

[hirose.sgia]

I have solved this problem.

I researched about this and found a report that several packages with Isaac depend on an instance of SimulationApp, and the dependent packages must be imported after the instance is created, or it will result in an ImportError.

Omni Kit Error - Isaac Sim Implementation

Hello, I have found an extension called omni.isaac.jetbot in ~./local/share/ov/pkg/isaac_sim-2021.2.1/standalone_examples/api/ and I want to create a modification of the package using my own urdf model for the robot without changing the original folder. I want to make a separate folder with the code. I placed this directory with formatted code in the api directory and used ./python.sh to execute the code, however, it cannot identify the pxr library nor omni.kit.commands library. Traceback (mo…

Therefore, we edited the executable file tool/composer/main.py and changed it so that the SimulationApp instance is created first.
First, open the relevant file in an editor.

Add the following process to line 16

kit = SimulationApp()

Comment out line 52.

# self.sim_app = SimulationApp(config)kit = SimulationApp()

In this state, we have confirmed that the ImportError is no longer generated when the Tutorial command is executed.
Thanks.