Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generalize friction corrected Isentr nozzle flow model #24

Open
davideziviani opened this issue Nov 29, 2016 · 6 comments
Open

Generalize friction corrected Isentr nozzle flow model #24

davideziviani opened this issue Nov 29, 2016 · 6 comments

Comments

@davideziviani
Copy link
Collaborator

Allow to specify the calibrated coefficients if needed to apply the flow model to different compressors/expanders

@ibell
Copy link
Owner

ibell commented Nov 29, 2016 via email

@davideziviani
Copy link
Collaborator Author

Yes sure. I was working on the Z-compressor model and I am running the detailed flow model for two flow paths to determine the friction flow correction factor. As I am using the same fitting function you adopted in the hybrid leakage model, it is useful to enable the user to specify the a_0,...,a_10, Re_star coefficients.
Similar story applies for example to rolling piston compressor etc.

Does this make sense?

@ibell
Copy link
Owner

ibell commented Nov 29, 2016 via email

@davideziviani
Copy link
Collaborator Author

yup that is also true but in the case a user wanna use the friction corrected isentropic nozzle for a particular path of interest, currently it is not readily possible (let's say parametric studies on different path length and gap size). One has to change the coefficients first, and the recompile PDSim.

@ibell
Copy link
Owner

ibell commented Nov 29, 2016 via email

@davideziviani
Copy link
Collaborator Author

yes indeed. I am gonna take a look to create a callable class to cache the coefficients

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants