Improvement to matlib creation

[makeclean]

Please correct me if this is already included, but its quite painful to have to pull out the materials from the .sat/.h5m geometry file to the matlib file. Can we not populate mat_rho- by querying the .sat/.h5m (I would prefer *.h5m) directly?

[elliottbiondo]

Nothing like this is included, but this is definitively something that should be addressed. The best way of doing this could be a point of contention. Paul's vision for this workflow involves making a Cubit model with material groups labeled with "engineering names" (e.g. "Stainless_Steel_304"). The first thing that comes to mind is that there could be a version controlled CNERG matlib containing PyNE (or PyNE readable) material definitions with these engineering names. There would need to be a script that would read an .h5m file and map each engineering material to its definition and then write MCNP definitions (with some assigned material number) and ALARA definitions. This step would have to occur before the neutron transport step.

I don't have any experience querying .h5m, but I am assuming there is some MOAB way of doing it (hopefully PyTAPS).