mapstp 1.0.3

Transfers meta information from STP to MCNP

Contents

• Description

  • Problem #1

  • Problem #2

  • Solution

• Contributing

Description

Problem #1

You are an MCNP model developer. You have created simplified 3D CAD model using SpaceClaim, saved it to STP file, then converted it using SuperMC to an MCNP model. At this moment the MCNP model doesn’t have any information on relation of the MCNP came from cells to the CAD components, there’s no materials and densities in the cell specifications. The SuperMC (for the time of writing this) doesn’t transfer this information on exporting to MCNP model.

Problem #2

You have to provide results of neutron analysis in correspondence with 3D CAD model components. For example, you have to create a table describing activation of every component. To do this, you need some tools to associate CAD component with corresponding MCNP cells. Using this table the results of computation for MCNP cells can be aggregated to values for corresponding CAD component.

Solution

Using SpaceClaim you can add additional properties to components directly in STP file. The properties include: used material, density correction factor, classification tag. The properties are specified as a special label, which you can add to the components names. The properties are propagated over the CAD tree hierarchy from top to down and can be overridden on lower levels with more specific values. Using SpaceClaim for this is rather intuitive.

The using mapstp you can transfer this information from STP to MCNP: The mapstp:

• sets material numbers and densities in all the cells, where it was specified

• adds $-comment after each cell denoting its path in STP, with tag “stp:”,this lines can be easily removed later, if not needed

• adds materials specifications, if they are available for mapstp

• creates separate accompanying excel file with list of cells, applied materials, densities and correction factors, classification tag, and paths in STP

More details in documentation.

Contributing

Some specific: in development environment we use uv, just, ruff.

To setup development environment, run:

just install | reinstall

To build documentation, run:

just docs        # - for local online docs rendering, while editing
just docs-build  # - to build documentation

To release, run:

just bump [major|minor|patch]  # - in `devel` branch

Then merge devel to master (via Pull Request) and if all the checks are passed create Release. Manually.