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
So there are a few options for generating propellant datasets:
A) We could scrape CEAWeb; but for each Mixture Ratio+exit pressure combination we'd need 60 plus data points (chamber pressure). So a full data set for one propellant would likely require 600+ data points, likely more.
CEAWeb has a bug where if you're defining P_Chamber/P_Exit you can only input one MR and one pressure ratio, meaning that only one data point can be pulled from a request to CEAWeb.
B) We could build a wrapper around CEA executables//use f2py to port CEA to python. This option is more feasible but possibly introduces bugs//errors into our code base. More importantly, it rather defeats the purpose of 'Open' in openrocketengine as we'd be interacting with a black box of sorts, likely with more utility than we'd need. This would make maintenance of the code base more complicated.
C) Either use or develop a computational chemistry solution that's lightweight and maintainable.
The text was updated successfully, but these errors were encountered:
I'm leaning towards option B.
Porting CEA to python using f2py. We should test the ported version of CEA to make sure we are getting the expected values.
So there are a few options for generating propellant datasets:
A) We could scrape CEAWeb; but for each Mixture Ratio+exit pressure combination we'd need 60 plus data points (chamber pressure). So a full data set for one propellant would likely require 600+ data points, likely more.
CEAWeb has a bug where if you're defining P_Chamber/P_Exit you can only input one MR and one pressure ratio, meaning that only one data point can be pulled from a request to CEAWeb.
B) We could build a wrapper around CEA executables//use f2py to port CEA to python. This option is more feasible but possibly introduces bugs//errors into our code base. More importantly, it rather defeats the purpose of 'Open' in openrocketengine as we'd be interacting with a black box of sorts, likely with more utility than we'd need. This would make maintenance of the code base more complicated.
C) Either use or develop a computational chemistry solution that's lightweight and maintainable.
The text was updated successfully, but these errors were encountered: