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
Inverse sensor implementation #881
Labels
Comments
For h and Xi, you could use the ideal heater or ideal humidifier, assuming this serves your purpose. For C, it may be best to put a similar class in |
I was thinking about a model that allows to set all properties at once, since you can set all properties with |
That sounds good.
…On Mon, Jan 29, 2018 at 8:15 AM, Filip Jorissen ***@***.***> wrote:
I was thinking about a model that allows to set all properties at once,
since you can set all properties with Boundary_pT too. I'll at this to
Fluid.Sources then!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#881 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABRHuJs5bLYAhhYaZGONBohOaiJu2Sb0ks5tPe6egaJpZM4RvcSX>
.
|
Mathadon
added a commit
that referenced
this issue
Apr 30, 2018
Mathadon
added a commit
that referenced
this issue
Apr 30, 2018
implemented allowFlowReversal moved connector labels for #881
closed through #917 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I could use a component that essentially does the invers of a fluid sensor: it sets either
h_outflow
,Xi_outflow
orC_outflow
of a flow that passes through the component to an input value/vector of the component. Sensors do the opposite: they read the value. I'd make a single component that allows setting all three variables using conditionally enabled inputs, similar toMassFlowSource
. I suppose that I can add this? Any suggestions on where to put it?The text was updated successfully, but these errors were encountered: