Skip to content

Conversation

@MattRolchigo
Copy link
Collaborator

Also keeps the option to enter a single thermal conductivity value for backwards compatibility. Probably worth doing some optimization to keep the slowdown minimal

Copy link
Contributor

@streeve streeve left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could keep the original version if it's a big slowdown

// Thermal conductvity as a function of temperature in the form a + b *
// Temperature for solid and liquid. If only one value is given, fixed
// thermal conductivity for both phases are used
if ( db["properties"].contains( "thermal_conductivity_solid" ) &&
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these inputs "Mist compatible"?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to Steve, Mist supports having properties represented as polynomials in the Y = a + b*X format so I think we're good there

@MattRolchigo
Copy link
Collaborator Author

@streeve What do you mean by "keep the original version"? Do we want that much more repeated code and an if statement in the main code block that says "if num_k_inputs == 1, do this and if its 2 do that"?

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

Successfully merging this pull request may close these issues.

2 participants