Issue66

[saroele]

It's not the intention to merge this pull request, just to pass on the model illustrating the issue:
The boundary does not have the wanted temperature.

[Mathadon]

If I plot fanSup.vol.T the temperature is correct.

Note that fanSup.T is the value of the parameter that can be used to set the boundary temperature but this is not used in this case since you use the input. Is this what caused confusion?

[saroele]

No, the confusion/error is the temperature of the boundary. It does not
seem to follow the input?

On Fri, Jun 13, 2014 at 7:34 PM, Filip notifications@github.com wrote:

If I plot fanSup.vol.T the temperature is correct.

Note that fanSup.T is the value of the parameter that can be used to set
the boundary temperature but this is not used in this case since you use
the input. Is this what caused confusion?

—
Reply to this email directly or view it on GitHub
#67 (comment).

[Mathadon]

In my previous post the second fanSup.T should have been airAmb.T. Note that the signal has the label 'T' but the actual signal name is T_in. I think this explains the issue?

[Mathadon]

@saroele can this be closed?

[saroele]

not yet, let me check again (maybe friday)

On Tue, Jun 24, 2014 at 2:50 PM, Filip notifications@github.com wrote:

@saroele https://github.com/saroele can this be closed?

—
Reply to this email directly or view it on GitHub
#67 (comment).

[rubenbaetens]

So, Jun 24 is long time ago: Can we close this one @saroele ? ;)

[rubenbaetens]

Shall we try to get rid of pull requests "which shouldn't be merged as it's to show something," that's the purpose of branches, no ? And it's enormously confusing.

[Mathadon]

Yup:)