Hi there Jin Whan,
I’d have to dig a little into the code to be sure (and I’ve copied Xiaokang who implemented this).
For the subvoxel method, there can be many different materials in each voxel. It seems that in your case, there can be up to 9 different cells/materials in any voxel. We then generate a different source for each cell in each voxel. Some of the entries will be zero since some voxels will have fewer than 9 cells (perhaps only 1).
I’m not sure how this gets processed when you use pyne.mesh.Mesh to unpack it. Can you share your code snippet that did this?
Paul
--
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ --
Paul P.H. Wilson (he/him/his)
Grainger Professor of Nuclear Engineering
Chair, Department of Engineering Physics
o: 608-263-0807, c: 608-469-9615
paul....@wisc.edu
153 Engineering Research Bldg
1500 Engineering Dr, Madison, WI 53706
Zoom Meeting Room: https://uwmadison.zoom.us/j/6082630807
Zoom Phone Access: +1-929-205-6099, Access code: 6082630807
--
You received this message because you are subscribed to the Google Groups "PyNE Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
pyne-users+...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/pyne-users/6f8dec38-f0c0-442d-b33b-245fb849998bn%40googlegroups.com.
Hi Jin Whan,
Let's clear up some concept first. Every mesh element (voxel) may
overlap with multiple cells, and the intersection of a cell and a
voxel is the so-called sub-voxel. The PyNE R2S supports both voxel
and sub-voxel mode. The voxel mode uses homogenized material for
each mesh element (24 groups photon source for each voxel). The
sub-voxel mode deal with the sub-voxel individually
(24*max_num_cells photon source data for each voxel).
In your case, the 'max_num_cells' is 9, and the 216 number is the
number of energy groups (24) multiplied by 9. This indicating that
you are use "sub-voxel" mode, i.e., the value for 'sub-voxel' is
True in your "config.ini" file.
You mentioned that "the summation of the entire matrix is not equal to the value in `total_photon_source_intensity.txt`, which is the case for non-subvoxel calculations". This is because the data in `source_x.h5m` is the 'source density', in unit of particle per second per cubit centimeter [p/s/cm3]. Well, the data in `total_photon_source_intensity.txt` is the emit rate, in unit of particle per second [p/s]. You need to multiply the volume of each sub-voxel to get the total photon emitting rate. You can refer to the corresponding source code to deal with the volume is in line 392 to 400 in 'pyne/src/source_sampling.cpp' for more detail.
By the way, you can set the 'sub-voxel' in "config.ini" to False
to use voxel mode, then there will be only 24 data for each voxel.
Best regards,
Xiaokang
Hi again,
The sub-voxel data includes:
The volume of the whole voxel can be calculated from its bounding planes.
We do not know (and therefore record) the centroids of the sub-voxels. Instead, we have schemes for sampling the photon source from the subvoxels that is probably best described in code. So the sampling scheme preserves the correct location of each sub-voxel.
To view this discussion on the web visit
https://groups.google.com/d/msgid/pyne-users/bc900005-8ae7-45cf-bb39-127a71419411n%40googlegroups.com.