1) Write separate output routines for different formats, each for a different code
2) Write a general output that is easily read by processing scripts and let them handle the format conversions
There are advantages in both options, and there alredy is the _res.m output that is kind of general, although not necessarily optimal for post-processing (except with matlab).
Since the procedure of group constant generation involves a large number of independent history calculations, it makes a lot of sense to use automated driver scripts that can divide the calculation into separate nodes in a cluster environment for optimum performance. It would also make sense to leave the collection and post-processing of output data for theses scripts, as is done by SerpentXS and STOP, for example. If we take this approach, it would definitely make life easier for us, leaving more time to focus on other issues.
So if we want to make use of a single "standardized" output format (in addition to the current _res.m output), I would like to get some feedback from the developers of these wrapper scipts and users who have made their own solutions as to what is the best approach. What I have in mind is something like this:
Code: Select all
<id> <nr> <nb> <nu> % restart index, total number of restarts, number of burnup points, number of universes <nc> % dimensions of the coefficient matrix <co_1> <co_2> ... <co_nc> % combination of bra-cards for this restart (text strings) <bu> % burnup for this restart (begin loop over universes) <uni> <np> % universe name and number of output parameters <ng> <E_0> <E_1> ... <E_ng> % number of energy groups and group boundaries (begin loop over output parameters) <param> <nv> <v_1> <v_2> ... <v_nv> % parameter name, number of values and list of values ... (end loop over output parameters) ... (end loop over universes)
This is all very preliminary, so any comments and ideas are welcome...