Hi Lorenz,
Thanks for bringing this to our attention. We have struggled to keep the ENSDF part of PyNE up-to-date in both the data and processing codes. Hopefully, we can find someone willing to help out with that.
Paul
--
-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ --
Paul P.H. Wilson (he/him/his)
Grainger Professor of Nuclear Engineering
Chair, Department of Nuclear Engineering & 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
Computational Nuclear Engineering Research Group
--
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/b13bf9bd-9826-4097-ab2b-2f8ed771357bn%40googlegroups.com.
Hi Lorenz,
That’s not quite correct. There should be a way to generate your own nuc_data.h5 file from original data, in the same way that we do that.
I’m not sure:
To view this discussion on the web visit https://groups.google.com/d/msgid/pyne-users/af5ad622-efe2-4958-97c4-de009ec7cffan%40googlegroups.com.