Conversation
|
At this stage, I'd like to add only the functionality of reading and interpolating a lookuptable, without immediately implementing a combustion solver that uses it. |
|
This pull request introduces 1 alert when merging 1202a60 into 2ce680a - view on LGTM.com new alerts:
|
|
The test would go in UnitTests |
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
|
This pull request introduces 1 alert when merging c439501 into 6ca6ec2 - view on LGTM.com new alerts:
|
|
This pull request introduces 1 alert when merging 9bb027f into 6ca6ec2 - view on LGTM.com new alerts:
|
|
This pull request introduces 1 alert when merging 0b7fdb0 into da4c75d - view on LGTM.com new alerts:
|
|
This pull request introduces 1 alert when merging 7cb4919 into f15fe75 - view on LGTM.com new alerts:
|
|
This pull request introduces 1 alert when merging 1b00541 into 7a57336 - view on LGTM.com new alerts:
|
|
This pull request introduces 1 alert when merging f4186f6 into ead83fe - view on LGTM.com new alerts:
|
| CTrapezoidalMap::CTrapezoidalMap(vector<su2double> const& samples_x, vector<su2double> const& samples_y, | ||
| vector<vector<unsigned long> > const& edges, |
There was a problem hiding this comment.
clang-format says this is OK. What would you like this to be? Every argument on a line when the list of arguments is too long? Would you like to see the behavior of:
BinPackParameters:false
If false, a function declaration’s or function definition’s parameters will either all be on the same line or will have one line each.
There was a problem hiding this comment.
Having the const first, but if clang format doesn't complain it's fine I guess, even if not super consistent.
There was a problem hiding this comment.
I noticed that BinPackParameters:false does this (put const in front) as well, maybe we should add it to .clang-format?
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
pcarruscag
left a comment
There was a problem hiding this comment.
Ah I think I forgot yesterday, these files would be better in common/*/containers
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
…ss functions const
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
…into feature_lookuptable
Proposed Changes
Give a brief overview of your contribution here in a few sentences.
Adds the functionality of reading fluid data from an unstructured triangulated lookup table and interpolating. No coupling with a solver (combustion) yet, at this point we will only add a verification test
Related Work
Resolve any issues (bug fix or feature request), note any related PRs, or mention interactions with the work of others, if any.
We split #1223 into smaller chunks
PR Checklist
Put an X by all that apply. You can fill this out after submitting the PR. If you have any questions, don't hesitate to ask! We want to help. These are a guide for you to know what the reviewers will be looking for in your contribution.