[WIP] pywrapper - custom source terms for all solvers

[bigfooted]

Proposed Changes

Introduce custom source terms for all solvers through the python wrapper.

• reproduces the laminar buoyancy driven cavity testcase
• can simulate a turbulent premixed flame using turbulent flamespeed closure (TFC)

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.

• I am submitting my contribution to the develop branch.
• My contribution generates no new compiler warnings (try with --warnlevel=3 when using meson).
• My contribution is commented and consistent with SU2 style (https://su2code.github.io/docs_v7/Style-Guide/).
• I used the pre-commit hook to prevent dirty commits and used pre-commit run --all to format old commits.
• I have added a test case that demonstrates my contribution, if necessary.
• I have updated appropriate documentation (Tutorials, Docs Page, config_template.cpp), if necessary.

To fix the issue, we should remove the assignment to index_Vel entirely, as it is not used anywhere in the code. This will eliminate the unused variable and make the code cleaner. Since the right-hand side of the assignment (varindex.get("VELOCITY_X")) does not have any side effects, it is safe to remove the entire line.

---

To fix the problem, we should remove the unused variable primindex from the function update_temperature. This will clean up the code and remove any potential confusion about the purpose of the variable. Since the variable is not used anywhere in the function, we can safely delete the line where it is assigned without affecting the existing functionality.

[bigfooted]

The best way to fix the problem is to remove the unused variable iDENSITY. Since the assignment of iDENSITY does not have any side effects, we can safely delete the entire line where iDENSITY is assigned. This will clean up the code and remove any potential confusion about the purpose of the variable.

The best way to fix the problem is to remove the assignment of the index_Vel variable since it is not used anywhere in the code. This will clean up the code and remove any potential confusion about the purpose of the variable.

To implement this fix, we need to delete the line where index_Vel is assigned a value. This change should be made in the file TestCases/py_wrapper/turbulent_premixed_psi/run.py on line 229.

The best way to fix the problem is to remove the assignment of the custom_source_vector variable since it is not used anywhere in the code. This will clean up the code and remove any potential confusion about the purpose of the variable.

• Locate the assignment of the custom_source_vector variable on line 232.
• Remove the entire line where custom_source_vector is assigned a value.

To fix the problem, we should remove the commented-out code entirely. This will make the code cleaner and less confusing for future developers. Specifically, we need to remove lines 138 and 139 from the file TestCases/py_wrapper/turbulent_premixed_psi/run.py.

To fix the issue, we will remove the assignment to the primindex variable on line 106. This ensures that the code is cleaner and avoids confusion about the purpose of the unused variable. Since the variable is not used anywhere in the function or the provided code snippet, its removal will not affect the functionality of the program.

---

The best way to fix the problem is to either remove the commented-out code entirely or reinstate it if it is still relevant. In this case, the commented-out code appears to be a debugging statement that is no longer needed, as the surrounding code does not depend on it. Therefore, the appropriate fix is to remove the commented-out code on line 138 and the associated comment on line 139.

To fix the issue, we will remove the assignment to iDENSITY on line 226 since it is not used anywhere in the code. This will eliminate the unused variable and clean up the code. Care will be taken not to remove any code with side effects, but in this case, the primindex.get("DENSITY") call does not appear to have side effects, so it is safe to remove.

---

To fix the issue, we should remove the assignment of the unused variable index_Vel entirely, as it serves no purpose in the current code. This will clean up the code and improve readability. If the assignment has side effects (e.g., if varindex.get performs some operation), we need to ensure that removing it does not affect the program's behavior. However, in this case, varindex.get is a dictionary-like operation that does not have side effects, so it is safe to remove.

---

To fix the issue, we should remove the assignment to custom_source_vector entirely, as it serves no purpose in the current code. This will clean up the code and eliminate the unused variable. Care should be taken to ensure that removing this line does not affect any side effects, but since the right-hand side of the assignment is a simple list comprehension with no external dependencies, there are no side effects to consider.

---