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
There's no reason we couldn't add blotter and/or sutherland tags within the transport section of the XML. This would help consolidate parsing for users as well if they want to experiment with these models (instead of our spread out ASCII format).
The text was updated successfully, but these errors were encountered:
Now we differentiate the parsing of the transport mixture data based
on the parser type. In particular, we should now be able to grab
the pure species data from the XML directly. We still support the
ASCII format. We can't do anything about the non-pure species
transport models since the Antioch XML parser doesn't support those
(see libantioch/antioch#256)
pbauman
added a commit
to pbauman/grins
that referenced
this issue
Jul 25, 2018
Now we differentiate the parsing of the transport mixture data based
on the parser type. In particular, we should now be able to grab
the pure species data from the XML directly. We still support the
ASCII format. We can't do anything about the non-pure species
transport models since the Antioch XML parser doesn't support those
(see libantioch/antioch#256)
There's no reason we couldn't add
blotter
and/orsutherland
tags within thetransport
section of the XML. This would help consolidate parsing for users as well if they want to experiment with these models (instead of our spread out ASCII format).The text was updated successfully, but these errors were encountered: