Hi @jack7z - I see a few problems here -
- The file you sent me loads with two warnings:
Load-time warnngs, as opposed to run-time warnings, do not trigger an error popup and are easy to miss. I think I’ll promote this to a popup in the next release.
- After loading, the densities and molecular weights for ML and RM are zero:
This results in unbalanced reaction, which the GUI won’t even let you save.
- Setting the molecular weights to 1150 and 1194 respectively balances the reactions. When I run the job I get a messy solver backtrace:
At line 57 of file /home/cgw/Work/NETL/mfix/model/thermochemical/get_values.f
Fortran runtime error: Bad value during floating point read
Again this should probably be a popup, but it isn’t. Since FORTRAN is complaining about a bad value, let’s inspect the data file:
ML User Defined 0.S 200.000 6000.000 B1150.00000 1
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 2
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 3
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 4
RM User Defined 0.S 200.000 6000.000 B1194.00000 1
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 2
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 3
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 0.00000000E+00 4
Note the way in the definitions for ML and RM, the numbers 1150 and 1194 are right up against the preceeding field B. That looks bad and potentially troublesome.
As an experiment, in an external editor, let’s change these to have a space between the text and the number - I changed B1150.00000 to B 1150.0000 and the other
B1194.0000 to B 1194.000 - adding a space after the B and deleting a trailing 0 to keep the field width constant. (This format is a bit fussy).
Now, as long as I do not do a Save from the GUI, the job runs!
So there’s a bug in the GUI when molecular weights are greater than 1000, the THERMO DATA section is written incorrectly and the solver can’t read it. Additionally, the error messages are a bit hard to find.
We will address this in the next release, for now you can edit the MFiX file directly, just be careful when doing so. Note that every time you save from the GUI you are going to have to fix this again, sorry about that!
– Charles