# TRISO Model XML Generation and HPC Simulation with different Parameters **URL:** \ **Category:** User Support\ **Created:** [November 4, 2025, 12:50pm UTC](https://openmc.discourse.group/t/triso-model-xml-generation-and-hpc-simulation-with-different-parameters/6097 "2025-11-04T12:50:24Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Arcsin](https://avatars.discourse-cdn.com/v4/letter/a/59ef9b/32.png) [@Arcsin](https://openmc.discourse.group/u/Arcsin)\ **Post date:** [November 7, 2025, 2:36am UTC](https://openmc.discourse.group/t/triso-model-xml-generation-and-hpc-simulation-with-different-parameters/6097/2 "2025-11-07T02:36:39Z")
bump~ I’ve also placed my current python code here I wanted to reduce the processing time. I’m using an HPC with 60 threads to do this job and it takes about 1 hour each run. I based this on the VHTR example. Is there something wrong with what I’m doing? I have tried to increase the shape to a higher value as said here > [@OpenMC TRISO example is lagging when the height is increased.](https://openmc.discourse.group/t/openmc-triso-example-is-lagging-when-the-height-is-increased/664/2): > > Hi Sharif, One thing that jumps out to me is the shape of the TRISO lattice. I’d try creating a TRISO lattice with a shape greater than (1, 1, 1). The lattice is used to accelerate the cell containment search when sourcing and tracking particles by limiting the search to TRISOs in the same lattice cell as the particle. With a shape of (1, 1, 1), all of the TRISOs are in the same lattice cell and in turn all of the TRISOs are in the search list, which is likely why it’s taking so long to source … but it increased the simulation time instead [HTTR.py](https://openmc.discourse.group/uploads/short-url/trhFCNySdpR86TrKep2Yvg8dP37.py) (8.8 KB) --- _[View the full topic](https://openmc.discourse.group/t/triso-model-xml-generation-and-hpc-simulation-with-different-parameters/6097)._