When using a transform in a cell definition (e.g., trcl=(5), and I also assume fill=.... (5)) numbered, or non-anonymous transforms, which are defined by a transform TR input in the data block is not supported. I would like to have this input style supported long term.
Example Input
1 0 -1 trcl=(5)
1 so 5.0
tr5 0.0 0.0 10.0
I understand this would be non-trivial to implement. I suspect at least:
TR inputs would have to be parsed on first read along with materials and passed around accordingly.- Translate this over to the OpenMC representation faithfully.
Note
I created a temporary work-around for myself that falls back on MontePy to pull this data out, but MontePy is too slow currently for this adapter. Maybe once I have shipped Just-in-Time parsing in MontePy it might worth considering adding MontePy as a backup parser for more complex sytnaxes.
When using a transform in a cell definition (e.g.,
trcl=(5), and I also assumefill=.... (5)) numbered, or non-anonymous transforms, which are defined by a transformTRinput in the data block is not supported. I would like to have this input style supported long term.Example Input
I understand this would be non-trivial to implement. I suspect at least:
TRinputs would have to be parsed on first read along with materials and passed around accordingly.Note
I created a temporary work-around for myself that falls back on
MontePyto pull this data out, but MontePy is too slow currently for this adapter. Maybe once I have shipped Just-in-Time parsing in MontePy it might worth considering adding MontePy as a backup parser for more complex sytnaxes.