You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If applicable, please include a small section of the input file you were working on. If it includes any specific values please change or remove them. For example:
TEST
1 0 -1 IMP:N=1
2 0 1 IMP:N=0
1 SO 20
NPS 1
MODE N
C
FC11 Neutron current
F11:N 1
FT11 INC
FU11 0 1
FM11 1.9730E+19
FQ11 s u
C
Version
Version 0.5.0
The text was updated successfully, but these errors were encountered:
dodu94
added
the
bugs
A deviation from expected behavior that does not reach the level of being reportable as an "Error".
label
Oct 24, 2024
I quickly went through #11 and, if I understand correctly, that is about having a full support of tallies. I support that, but in the meantime I guess montepy should just recognize FQ simply as a data card without knowing what it is exactly and just go on with the parsing right?
Yes. It's just that we don't have a rule for a data input that is all text right now. So yes we'll do a stop gap measure to just make it parsable and not error out.
Describe the bug
It seems that montepy is not able to parse correctly FQ cards
To Reproduce
Error Message (if any)
MCNP input file snippet
If applicable, please include a small section of the input file you were working on. If it includes any specific values please change or remove them. For example:
Version
The text was updated successfully, but these errors were encountered: