From 88ac99fab2727b203b8950066bfe7e03b3b01a6d Mon Sep 17 00:00:00 2001 From: Nijso Date: Thu, 15 Jan 2026 23:38:58 +0100 Subject: [PATCH 01/15] Update tutorial title for clarity --- _tutorials/incompressible_flow/Inc_Urban_City/Inc_Urban_City.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_tutorials/incompressible_flow/Inc_Urban_City/Inc_Urban_City.md b/_tutorials/incompressible_flow/Inc_Urban_City/Inc_Urban_City.md index 353bef12..86196417 100644 --- a/_tutorials/incompressible_flow/Inc_Urban_City/Inc_Urban_City.md +++ b/_tutorials/incompressible_flow/Inc_Urban_City/Inc_Urban_City.md @@ -1,5 +1,5 @@ --- -title: unsteady pollutant dispersion in a city +title: Wind velocity and pollutant dispersion in a city permalink: /tutorials/Inc_Urban_City/ written_by: Nijso Beishuizen for_version: 8.4.0 From 58ba6a5807524eaf08d1e6751a65437e2e8a2190 Mon Sep 17 00:00:00 2001 From: Nijso Date: Tue, 20 Jan 2026 20:06:57 +0100 Subject: [PATCH 02/15] Update resource links to use 'develop' branch (#198) --- _tutorials/multiphysics/TFC_python/TFC_python.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_tutorials/multiphysics/TFC_python/TFC_python.md b/_tutorials/multiphysics/TFC_python/TFC_python.md index 819403b5..c68c858b 100644 --- a/_tutorials/multiphysics/TFC_python/TFC_python.md +++ b/_tutorials/multiphysics/TFC_python/TFC_python.md @@ -27,7 +27,7 @@ In this tutorial we will touch upon the following aspects: ## Resources -The resources for this tutorial can be found in the [TFC_python](https://github.com/su2code/Tutorials/tree/master/multiphysics/TFC_python) directory in the [tutorial repository](https://github.com/su2code/Tutorials). You will need the configuration file ([psi.cfg](https://github.com/su2code/Tutorials/tree/master/multiphysics/TFC_python/adiabatic/psi.cfg)) and the mesh file ([psi.su2](https://github.com/su2code/Tutorials/tree/master/multiphysics/TFC_python/adiabatic/psi.su2)). Additionally, the Gmsh geometry is also provided so you can recreate the mesh yourself: [psi.geo](https://github.com/su2code/Tutorials/tree/master/multiphysics/TFC_python/psi.geo). Files for the non-adiabatic case are in the folder [enthalpy](https://github.com/su2code/Tutorials/tree/master/multiphysics/TFC_python/enthalpy) and files for the case with source term quenching and custom wall boundary conditions are in the folder [quench](https://github.com/su2code/Tutorials/tree/master/multiphysics/TFC_python/quench) +The resources for this tutorial can be found in the [TFC_python](https://github.com/su2code/Tutorials/tree/develop/multiphysics/TFC_python) directory in the [tutorial repository](https://github.com/su2code/Tutorials). You will need the configuration file ([psi.cfg](https://github.com/su2code/Tutorials/tree/develop/multiphysics/TFC_python/adiabatic/psi.cfg)) and the mesh file ([psi.su2](https://github.com/su2code/Tutorials/tree/develop/multiphysics/TFC_python/adiabatic/psi.su2)). Additionally, the Gmsh geometry is also provided so you can recreate the mesh yourself: [psi.geo](https://github.com/su2code/Tutorials/tree/develop/multiphysics/TFC_python/psi.geo). Files for the non-adiabatic case are in the folder [enthalpy](https://github.com/su2code/Tutorials/tree/develop/multiphysics/TFC_python/enthalpy) and files for the case with source term quenching and custom wall boundary conditions are in the folder [quench](https://github.com/su2code/Tutorials/tree/develop/multiphysics/TFC_python/quench) ### Background @@ -55,7 +55,7 @@ Note that the python wrapper (or your python setup) might need additional python The geometry of this testcase is provided as a gmsh file and matches the of the experimental setup of Griebel et al (2007), [doi](https://doi.org/10.1016/j.proci.2006.07.042). -The mesh consists of a a coarse structured mesh with 16.3k cells and 16.6k points. The mesh was created using Gmsh and the configuration file to create the mesh can be found here: [psi.geo](https://github.com/su2code/Tutorials/tree/master/multiphysics/TFC_python/psi.geo). The only thing you need to do to create a mesh from the geometry is start Gmsh, and then load the .geo file. You will then see the geometry in the Gmsh visualization window. If you click on *Mesh->2D* the 2D mesh will be generated. You can then export the mesh as a .su2 file by choosing *File->Export*. The mesh will automatically be saved in su2 format when the filename has been given the extension .su2. In general, you should not choose *save all elements* because this will also save additional points that were used to construct the geometry but are not part of the final mesh, like for example the center of a circle. +The mesh consists of a a coarse structured mesh with 16.3k cells and 16.6k points. The mesh was created using Gmsh and the configuration file to create the mesh can be found here: [psi.geo](https://github.com/su2code/Tutorials/tree/develop/multiphysics/TFC_python/psi.geo). The only thing you need to do to create a mesh from the geometry is start Gmsh, and then load the .geo file. You will then see the geometry in the Gmsh visualization window. If you click on *Mesh->2D* the 2D mesh will be generated. You can then export the mesh as a .su2 file by choosing *File->Export*. The mesh will automatically be saved in su2 format when the filename has been given the extension .su2. In general, you should not choose *save all elements* because this will also save additional points that were used to construct the geometry but are not part of the final mesh, like for example the center of a circle. ### Configuration File Options From a311b464cf183ff1502920fb1e564ff51251cdaf Mon Sep 17 00:00:00 2001 From: Nijso Date: Tue, 20 Jan 2026 20:08:36 +0100 Subject: [PATCH 03/15] Update resource links in Inc_Urban_City.md (#199) --- _tutorials/incompressible_flow/Inc_Urban_City/Inc_Urban_City.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_tutorials/incompressible_flow/Inc_Urban_City/Inc_Urban_City.md b/_tutorials/incompressible_flow/Inc_Urban_City/Inc_Urban_City.md index 86196417..78a43d65 100644 --- a/_tutorials/incompressible_flow/Inc_Urban_City/Inc_Urban_City.md +++ b/_tutorials/incompressible_flow/Inc_Urban_City/Inc_Urban_City.md @@ -26,7 +26,7 @@ In this tutorial we will look at the modeling of wind speed and pollutant disper ## Resources -The resources for this tutorial can be found in the [incompressible_flow/Inc_Urban_City](https://github.com/su2code/Tutorials/tree/master/incompressible_flow/Inc_Urban_City) directory in the [tutorial repository](https://github.com/su2code/Tutorials). +The resources for this tutorial can be found in the [incompressible_flow/Inc_Urban_City](https://github.com/su2code/Tutorials/tree/develop/incompressible_flow/Inc_Urban_City) directory in the [tutorial repository](https://github.com/su2code/Tutorials). ### Background From 59bed6e902529b612258dc0ee08f0689dd6956ae Mon Sep 17 00:00:00 2001 From: Nijso Date: Tue, 20 Jan 2026 20:10:34 +0100 Subject: [PATCH 04/15] Fix tutorial link in NICFD nozzle documentation (#200) Updated the tutorial link to point to the correct URL for the NICFD nozzle tutorial. --- .../compressible_flow/NICFD_nozzle/NICFD_nozzle_datadriven.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_tutorials/compressible_flow/NICFD_nozzle/NICFD_nozzle_datadriven.md b/_tutorials/compressible_flow/NICFD_nozzle/NICFD_nozzle_datadriven.md index 62c23885..6bac3dcf 100644 --- a/_tutorials/compressible_flow/NICFD_nozzle/NICFD_nozzle_datadriven.md +++ b/_tutorials/compressible_flow/NICFD_nozzle/NICFD_nozzle_datadriven.md @@ -11,7 +11,7 @@ follows: ## Goals -Upon completing this tutorial, the user will be familiar with performing simulations of nonideal compressible fluids through the use of physics-informed neural networks. The flow is simulated through the same supersonic convergent-divergent nozzle as in the [tutorial](NICFD_nozzle.md) for nonideal compressible fluid flows. +Upon completing this tutorial, the user will be familiar with performing simulations of nonideal compressible fluids through the use of physics-informed neural networks. The flow is simulated through the same supersonic convergent-divergent nozzle as in the [tutorial](https://su2code.github.io/tutorials/NICFD_nozzle/) for nonideal compressible fluid flows. The following capabilities of will be showcased in this tutorial: - Using [SU2 DataMiner](https://github.com/EvertBunschoten/SU2_DataMiner.git) to train physics-informed neural networks for fluid simulations. - Data-driven equation of state with multi-layer perceptrons. From 34a792f827cc6e7afca4d72feb8dede9cbf08798 Mon Sep 17 00:00:00 2001 From: Nijso Date: Tue, 20 Jan 2026 21:07:08 +0100 Subject: [PATCH 05/15] fix links (#201) --- _data/tutorials.yml | 1 + .../ActuatorDisk_VariableLoad.md | 28 +++++++++---------- _tutorials/index.md | 2 ++ 3 files changed, 17 insertions(+), 14 deletions(-) diff --git a/_data/tutorials.yml b/_data/tutorials.yml index 069c9300..873857e1 100644 --- a/_data/tutorials.yml +++ b/_data/tutorials.yml @@ -19,6 +19,7 @@ - NICFD_nozzle - NICFD_nozzle_datadriven - Aachen_Turbine + - Actuator_Disk - title: Incompressible Flow tutorials: diff --git a/_tutorials/compressible_flow/ActuatorDisk_VariableLoad/ActuatorDisk_VariableLoad.md b/_tutorials/compressible_flow/ActuatorDisk_VariableLoad/ActuatorDisk_VariableLoad.md index f532d610..c1f7c967 100644 --- a/_tutorials/compressible_flow/ActuatorDisk_VariableLoad/ActuatorDisk_VariableLoad.md +++ b/_tutorials/compressible_flow/ActuatorDisk_VariableLoad/ActuatorDisk_VariableLoad.md @@ -55,8 +55,8 @@ The global propeller data are: - Advance Ratio = 2.81487 - Radius = 2.5146 m -The thrust coefficient is defined using the "Renard" definition: the reference force is , where *n* are the propeller rounds per second and *D* is the propeller diameter -The advance ratio is defined as . +The thrust coefficient is defined using the "Renard" definition: the reference force is $$\rho n^2D^4$$, where *n* are the propeller rounds per second and *D* is the propeller diameter +The advance ratio is defined as $$J=\frac{V_\infty}{nD}$$. ### Mesh Description @@ -167,16 +167,16 @@ The `MARKER_ACTDISK` option, as the same for the configuration file, is used to The `CENTER` option contains the coordinates of the actuator disk center, expressed in the grid reference system. The `AXIS` option contains the components of the unit vector normal to the actuator disk surface. The `RADIUS` option is used to specify the actuator disk radius. -The `ADV_RATIO` option contains the advance ratio of the propeller defined as , where *n* are the propeller rounds per second and *D* is the propeller diameter. +The `ADV_RATIO` option contains the advance ratio of the propeller defined as $$J=\frac{V_\infty}{nD}$$, where *n* are the propeller rounds per second and *D* is the propeller diameter. The `NROW` option isused to indicate the number of radial stations of the actuator disk in which we assign the load distribution. The next row is a dummy row, so it is skipped. Then there are 4 columns containing respectively: -- The non dimensional radial station -- The thrust coefficient distribution -- The power coefficient distribution -- The radial force coefficient distribution +- The non dimensional radial station $$\overline{r}=\frac{r}{R}$ +- The thrust coefficient distribution $$\frac{\mathrm{d}C_T}{\mathrm{d}\overline{r}}$$ +- The power coefficient distribution $$\frac{\mathrm{d}C_P}{\mathrm{d}\overline{r}}$ +- The radial force coefficient distribution $$\frac{\mathrm{d}C_R}{\mathrm{d}\overline{r}}$$ -These coefficients are defined using the "Renard" definition: the reference force is , while the reference power is reference force is +These coefficients are defined using the "Renard" definition: the reference force is $$\rho n^2D^4$$, while the reference power is reference force is $$\rho n^3D^5$$ *It is possible to append other propellers data at the end of the input file. Note that the order and the format of the options should not be changed.* @@ -195,13 +195,13 @@ This script allows the user to use the `VARIABLE_LOAD` actuator disk type also w The input is interactive, and requires the following data: 1. Number of radial stations (where local data should be generated). -2. CT: the total thrust coefficient defined using the "Renard" definition. -3. R: The propeller radius expressed in meters. -4. r_hub: the hub radius expressed in meters. -5. J: the advance ratio. -6. Vinf: the free-stream velocity expressed in m/s. +2. $$CT$$: the total thrust coefficient defined using the "Renard" definition. +3. $$R$$: The propeller radius expressed in meters. +4. $$r_{\textrm{hub}}$$: the hub radius expressed in meters. +5. $$J$$: the advance ratio. +6. $$V_{\textrm{inf}}$$: the free-stream velocity expressed in m/s. 7. Here, the script asks if you want to use the tip loss Prandtl correction (*yes* is the default choise). -8. N: if you chose yes in the previous stage, it requires also the number of propeller blades. +8. $$N$$: if you chose yes in the previous stage, it requires also the number of propeller blades. Once the input is given, the script provides 3 plots showing the tip loss Prandtl correction function, the axial and rotational interference factors and the thrust and power coefficients distributions along the non dimentional radius. The script also provides 2 files: diff --git a/_tutorials/index.md b/_tutorials/index.md index 0fa54c5a..0a0c86f1 100644 --- a/_tutorials/index.md +++ b/_tutorials/index.md @@ -54,6 +54,8 @@ Simulation of compressible flow in a nozzle using non-ideal thermodynamic models Demonstration of data-driven equation of state using a physics-informed neural network. * [Turbomachinery: Aachen Turbine stage with mixing plane](/tutorials/Aachen_Turbine/) Simulation of compressible flow of the Aachen turbine demonstrating turbomachinery application. +* [Actuator Disk with Variable Load](/tutorials/ActuatorDisk_VariableLoad/) +Simulation of an actuator disk with variable load. #### Incompressible Flow From 13ecc00ed6a484b7f66a0214e8a85537ced0b140 Mon Sep 17 00:00:00 2001 From: Nijso Date: Wed, 21 Jan 2026 09:04:05 +0100 Subject: [PATCH 06/15] Feature gsoc (#202) * add gsoc --- _config.yml | 12 +++++++ _data/gsoc.yml | 12 +++++++ _gsoc/Introduction.md | 36 +++++++++++++++++++++ _includes/gsoc_nav.html | 22 +++++++++++++ _includes/gsoc_section_nav.html | 52 +++++++++++++++++++++++++++++++ _includes/topnav.html | 1 + _layouts/gsoc.html | 55 +++++++++++++++++++++++++++++++++ 7 files changed, 190 insertions(+) create mode 100644 _data/gsoc.yml create mode 100644 _gsoc/Introduction.md create mode 100644 _includes/gsoc_nav.html create mode 100644 _includes/gsoc_section_nav.html create mode 100644 _layouts/gsoc.html diff --git a/_config.yml b/_config.yml index 0f60842f..e63bd734 100644 --- a/_config.yml +++ b/_config.yml @@ -86,6 +86,15 @@ defaults: seo: type: "WebPage" +- scope: + path: _gsoc + type: gsoc + values: + layout: gsoc + sectionid: gsoc + seo: + type: "WebPage" + collections: docs: permalink: /:collection/:path/ @@ -102,6 +111,9 @@ collections: su2gui: permalink: /:collection/:path/ output: true + gsoc: + permalink: /:collection/:path/ + output: true posts: permalink: /blog/:year/:month/:day/:title/ output: true diff --git a/_data/gsoc.yml b/_data/gsoc.yml new file mode 100644 index 00000000..cf2a70da --- /dev/null +++ b/_data/gsoc.yml @@ -0,0 +1,12 @@ +- title: GSOC + gsoc: + - Introduction + - Quick-Start + +- title: Participation + gsoc: + - Participation + +- title: Mentors + gsoc: + - Mentors diff --git a/_gsoc/Introduction.md b/_gsoc/Introduction.md new file mode 100644 index 00000000..df5897a5 --- /dev/null +++ b/_gsoc/Introduction.md @@ -0,0 +1,36 @@ +--- +title: Welcome to the SU2 Google Summer of Code Page +permalink: /gsoc/Introduction/ +--- + +**Welcome to SU2 - GSOC!** + +This is the ideas list for GSOC 2026. + +## Project BP: Adding pressure-based solver +Project Description (max. 5 Sentences) +The pressure-based solver has been requested for a long time. This solver is an important addition to the CFD solvers, especially for low Mach and incompressible flows. People have worked on it (detailed documentation available), and there is a branch that contains a working version, but this was never finalized and added to the main SU2 branch. Hence, the project's objective is to evaluate the current status of attempts, and propose a strategy for getting the pressure-based solver in the latest version of SU2. +Expected Outcome (deliverables): Finalize pressure-based solver, validate with test cases, tutorial and merge the PR. +Skills Required: C++, experience with CFD and numerical methods +Possible Mentors: Nitish Anand and Edwin van der Weide +Expected Project Size: 175 hrs/medium +Difficulty rating: medium-hard (needs experience with Computational Fluid Dynamics) + +## Project GPU: Continuation of GPU acceleration in SU2 +Project Description (max. 5 Sentences) +The SU2 code relies heavily on sparse linear algebra. In this area, there is significant speed-up potential with the adoption of GPU-based processing, as was demonstrated in the GSOC 24 project that applied CUDA to sparse matrix-vector multiplications in SU2. The objective of this project is to move more linear algebra operations to GPU in order to avoid host-device communication bottlenecks within the sparse linear system solver. +Expected Outcome (deliverables): Make SU2’s sparse linear solver GPU-native, i.e. minimal host-device communication after the initial setup of the system. +Skills Required C++ +Possible Mentors Pedro Gomes (lead), Ole Burghardt +Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) +Difficulty rating (easy (little experience/background), medium (some experience/background), hard (experienced)): medium + +## Project AMR: Quick Adaptive Mesh refinement for 2D testcases +Project Description (max. 5 Sentences) +Many users have asked for adaptive mesh refinement capabilities. Several research groups are working on this. The aim of this project is to introduce a quick and easy adaptive mesh refinement that simply reads an existing results file and adaptively refines the meshes based on the value of a field. +Expected Outcome (deliverables): SU2_AMR, an added executable that simply splits 2D quad and triangle cells +Skills Required: C++ +Possible Mentors: Nijso Beishuizen (lead) +Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) +Difficulty rating (easy (little experience/background), medium (some experience/background), hard (experienced)): medium + diff --git a/_includes/gsoc_nav.html b/_includes/gsoc_nav.html new file mode 100644 index 00000000..4065d44b --- /dev/null +++ b/_includes/gsoc_nav.html @@ -0,0 +1,22 @@ +
+{% for section in site.data.gsoc %} +
+
+

+ +

+
+
+
    + {% for item in section.gsoc %} + {% assign item_url = item | prepend:"/gsoc/" | append:"/" %} + {% assign p = site.gsoc | where:"url", item_url | first %} + {{ p.title }} + {% endfor %} +
+
+
+{% endfor %} +
diff --git a/_includes/gsoc_section_nav.html b/_includes/gsoc_section_nav.html new file mode 100644 index 00000000..f5feadf8 --- /dev/null +++ b/_includes/gsoc_section_nav.html @@ -0,0 +1,52 @@ +{% comment %} +Map grabs the doc sections, giving us an array of arrays. Join, flattens all +the items to a comma delimited string. Split turns it into an array again. +{% endcomment %} +{% assign gsoc = site.data.gsoc | map: 'gsoc' | join: ',' | split: ',' %} + +{% comment %} +Because this is built for every page, lets find where we are in the ordered +document list by comparing url strings. Then if there's something previous or +next, lets build a link to it. +{% endcomment %} + +{% for document in gsoc %} + {% assign document_url = document | prepend:"/gsoc/" | append:"/" %} + {% if document_url == page.url %} +
    + {% if forloop.first %} + + {% else %} + {% assign previous = forloop.index0 | minus: 1 %} + {% assign previous_page = gsoc[previous] | prepend:"/gsoc/" | append:"/" %} + + {% endif %} + + {% if forloop.last %} + + {% else %} + {% assign next = forloop.index0 | plus: 1 %} + {% assign next_page = gsoc[next] | prepend:"/gsoc/" | append:"/" %} + + {% endif %} + +
    + {% break %} + {% endif %} +{% endfor %} diff --git a/_includes/topnav.html b/_includes/topnav.html index 89903b83..0b792f9b 100644 --- a/_includes/topnav.html +++ b/_includes/topnav.html @@ -22,6 +22,7 @@
  • Dev Team Slack
  • Develop
  • GUI
    • +
  • GSOC
    diff --git a/_layouts/gsoc.html b/_layouts/gsoc.html new file mode 100644 index 00000000..1276685d --- /dev/null +++ b/_layouts/gsoc.html @@ -0,0 +1,55 @@ +--- +layout: default +--- + +
    +
    +
    + {% include gsoc_nav.html %} +
    + +
    +

    {{ page.title }}

    +
    {{ content }}
    +
    + {% unless true %} + + + + +
    +
    + {% endunless %} +

    +
    + + Improve this page + +

    + {% include gsoc_section_nav.html %} +
    + +
    +
    + + + From 5e499369c581a12756b424933b8348dc051aa75d Mon Sep 17 00:00:00 2001 From: Nijso Date: Wed, 21 Jan 2026 10:51:55 +0100 Subject: [PATCH 07/15] Revise GSOC 2026 ideas list with updates and formatting (#203) Updated the ideas list for GSOC 2026 with formatting improvements and added emphasis on skills required and difficulty ratings for each project. --- _gsoc/Introduction.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/_gsoc/Introduction.md b/_gsoc/Introduction.md index df5897a5..dd0a29b2 100644 --- a/_gsoc/Introduction.md +++ b/_gsoc/Introduction.md @@ -5,32 +5,32 @@ permalink: /gsoc/Introduction/ **Welcome to SU2 - GSOC!** -This is the ideas list for GSOC 2026. +This is the updated ideas list for GSOC 2026. ## Project BP: Adding pressure-based solver Project Description (max. 5 Sentences) The pressure-based solver has been requested for a long time. This solver is an important addition to the CFD solvers, especially for low Mach and incompressible flows. People have worked on it (detailed documentation available), and there is a branch that contains a working version, but this was never finalized and added to the main SU2 branch. Hence, the project's objective is to evaluate the current status of attempts, and propose a strategy for getting the pressure-based solver in the latest version of SU2. Expected Outcome (deliverables): Finalize pressure-based solver, validate with test cases, tutorial and merge the PR. -Skills Required: C++, experience with CFD and numerical methods -Possible Mentors: Nitish Anand and Edwin van der Weide -Expected Project Size: 175 hrs/medium -Difficulty rating: medium-hard (needs experience with Computational Fluid Dynamics) +- Skills Required: C++, experience with CFD and numerical methods +- Possible Mentors: Nitish Anand and Edwin van der Weide +- Expected Project Size: 175 hrs/medium +- Difficulty rating: **medium-hard** (needs experience with Computational Fluid Dynamics) ## Project GPU: Continuation of GPU acceleration in SU2 Project Description (max. 5 Sentences) The SU2 code relies heavily on sparse linear algebra. In this area, there is significant speed-up potential with the adoption of GPU-based processing, as was demonstrated in the GSOC 24 project that applied CUDA to sparse matrix-vector multiplications in SU2. The objective of this project is to move more linear algebra operations to GPU in order to avoid host-device communication bottlenecks within the sparse linear system solver. Expected Outcome (deliverables): Make SU2’s sparse linear solver GPU-native, i.e. minimal host-device communication after the initial setup of the system. -Skills Required C++ -Possible Mentors Pedro Gomes (lead), Ole Burghardt -Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) -Difficulty rating (easy (little experience/background), medium (some experience/background), hard (experienced)): medium +- Skills Required C++ +- Possible Mentors Pedro Gomes (lead), Ole Burghardt +- Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) +- Difficulty rating: **medium** ## Project AMR: Quick Adaptive Mesh refinement for 2D testcases Project Description (max. 5 Sentences) Many users have asked for adaptive mesh refinement capabilities. Several research groups are working on this. The aim of this project is to introduce a quick and easy adaptive mesh refinement that simply reads an existing results file and adaptively refines the meshes based on the value of a field. Expected Outcome (deliverables): SU2_AMR, an added executable that simply splits 2D quad and triangle cells -Skills Required: C++ -Possible Mentors: Nijso Beishuizen (lead) -Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) -Difficulty rating (easy (little experience/background), medium (some experience/background), hard (experienced)): medium +- Skills Required: C++ +- Possible Mentors: Nijso Beishuizen (lead) +- Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) +- Difficulty rating: **medium** From acf22eccfdb7488f5e3888a874baa0df6252b195 Mon Sep 17 00:00:00 2001 From: Nijso Date: Wed, 21 Jan 2026 11:17:39 +0100 Subject: [PATCH 08/15] add gsoc (#204) --- _gsoc/Participation.md | 39 +++++++++++++++++++++++++++++++++++++++ _includes/topnav.html | 2 +- 2 files changed, 40 insertions(+), 1 deletion(-) create mode 100644 _gsoc/Participation.md diff --git a/_gsoc/Participation.md b/_gsoc/Participation.md new file mode 100644 index 00000000..cc120f43 --- /dev/null +++ b/_gsoc/Participation.md @@ -0,0 +1,39 @@ +--- +title: Student Participation +permalink: /gsoc/Participation/ +--- + +**Welcome to SU2 - GSOC!** + +## What is Google Summer of Code? + +[Google Summer of Code](https://summerofcode.withgoogle.com/) + +Google Summer of Code is a program sponsored by Google to let students interested in Open Source work on cool and challenging open source projects. The basic idea is that you will work together with a mentor on a project. We have selected a couple of main topics for you but it is up to you to write a more complete project proposal. If you have ideas of your own, that is fine too but you will need to find a mentor to supervise such a project. + +If you would like to apply, please do the following: + +Make sure that you have subscribed to [CFD-online](https://www.cfd-online.com/Forums/su2/) and github, and additionally join the developers team on slack (see our main website [su2code](https://su2code.github.io/). If you are interested in applying, please do the following: + +1. send an application email to gsoc@su2foundation.org with some personal details, education background and motivation +2. become a member of our slack channel and subscribe to the **general** and **gsoc** subchannel of SU2. Please introduce yourself :-) + +## To Apply: +To be considered as a gsoc student for an SU2 project, it is not sufficient to simply write a proposal and send it to the google website. We will not accept students who never contacted us or did not finish the assignments. + +- Create a brief CV with your contact details, your education and code experience. +- Briefly write about your experience and interests in SU2 and the specific project you would like to work on (if you know this already) +- Briefly write about your current work schedule: are you studying/working, how will you manage the time, etc.. +- Send it to gsoc@su2foundation.org +- Make the assignments on the assignment page. + +Then in the last stage: + +- Together with a mentor you will create a project planning with a timeline containing a breakdown of the project in parts with periodic deliverables/milestones. + +## Evaluation +Note that applying does not mean acceptance into the program. We will carefully consider your application to see if you are capable of the job, taking into account your experience and availability. We heavily weigh your participation and visibility in the introduction phase. +Please note that experience with SU2 is required, but a merged Pull Request on github will be seen as sufficient proof that you are capable of the job. A pull request for a tutorial or validation testcase is also acceptable. + +## Use of AI +we allow usage of AI tools to help you with your work. However, we do not allow the use of AI in so-called vibe-coding, where you let AI generate code that you do not understand. We also do not allow AI for automatic discussions with mentor or other users. diff --git a/_includes/topnav.html b/_includes/topnav.html index 0b792f9b..60e22f64 100644 --- a/_includes/topnav.html +++ b/_includes/topnav.html @@ -19,7 +19,7 @@
  • Tutorials
  • V&V
  • User Forum
    • -
  • Dev Team Slack
    • +
  • Slack
  • Develop
  • GUI
  • GSOC
    • From 2aeb327c72579e6dce89dbb19f27fc05118d0b27 Mon Sep 17 00:00:00 2001 From: Nijso Date: Thu, 22 Jan 2026 10:49:55 +0100 Subject: [PATCH 09/15] add gsoc (#205) --- _data/gsoc.yml | 5 ++--- _gsoc/Assignments.md | 41 +++++++++++++++++++++++++++++++++++++++++ _gsoc/Participation.md | 22 +++++++++++----------- 3 files changed, 54 insertions(+), 14 deletions(-) create mode 100644 _gsoc/Assignments.md diff --git a/_data/gsoc.yml b/_data/gsoc.yml index cf2a70da..fad92a45 100644 --- a/_data/gsoc.yml +++ b/_data/gsoc.yml @@ -1,12 +1,11 @@ - title: GSOC gsoc: - Introduction - - Quick-Start - title: Participation gsoc: - Participation -- title: Mentors +- title: Assignments gsoc: - - Mentors + - Assignments diff --git a/_gsoc/Assignments.md b/_gsoc/Assignments.md new file mode 100644 index 00000000..a1a3ce60 --- /dev/null +++ b/_gsoc/Assignments.md @@ -0,0 +1,41 @@ +--- +title: Student Assignments +permalink: /gsoc/Assignments/ +--- + +**Welcome to SU2 - GSOC!** +What is Google Summer of Code? + +[Google Summer of Code](https://summerofcode.withgoogle.com/) + + +## SU2 introduction assignments + +To help newcomers start with SU2 and to help GSOC mentors with evaluating the level of students who would like to participate in Google Summer of Code, we have prepared a couple of introduction assignments. These assignments have to be made in the order they are given. These assignments give us an indication of your familiarity with SU2 and the SU2 code. These assignments, together with your active participation in the SU2 community, will be taken into account when deciding on GSOC projects. + +## Assignment 1: Compile SU2 + +- Clone SU2 from github [SU2](https://github.com/su2code/SU2) on your system and compile it [compile instructions](https://su2code.github.io/docs_v7/Build-SU2-Linux-MacOS/) with different options, and run some tutorials [Tutorials](https://su2code.github.io/tutorials/home/). Get a proper understanding of the input and output of SU2. +- Deliverable: None + +## Assignment 2: Set up a test case from scratch + +- Generate a 2D mesh for an axisymmetric, steady-state, turbulent jet case (for instance with [gmsh](https://gmsh.info/)), setup the configuration file, run the simulation, and extract results. +- Deliverable: Testcase and small report (markdown) describing motivation for set-up, configuration options, convergence history, comparison with experimental values. +Reference paper that could be used for comparison [report](https://www.researchgate.net/publication/254224677_Investigation_of_the_Mixing_Process_in_an_Axisymmetric_Turbulent_Jet_Using_PIV_and_LIF) + +## Assignment 3: Python wrapper test case + +- Set up a problem in the python wrapper (compile with python support) and run a test case. +Testcase for the python wrapper: [flatplate](https://github.com/su2code/SU2/blob/master/TestCases/py_wrapper/flatPlate_unsteady_CHT/launch_unsteady_CHT_FlatPlate.py) +- Deliverable: Testcase and small report describing the test case and showing the results. + +## Assignment 4: Modification of the python wrapper setup + +- Enable a spatially varying wall temperature for a steady-state compressible turbulent flat plate testcase. +- Deliverable: Testcase and small report describing the results. + +## Assignment 5: Addition of new volume output: + +- Add the local speed of sound as computed by SU2 in the volume output (paraview files) and the screen output. Run the turbulent test case from point 2 with this new volume and screen output enabled. +- Deliverable: explain implementation, show the history output of the new screen output and show some image with the volume output. diff --git a/_gsoc/Participation.md b/_gsoc/Participation.md index cc120f43..3e851834 100644 --- a/_gsoc/Participation.md +++ b/_gsoc/Participation.md @@ -11,29 +11,29 @@ permalink: /gsoc/Participation/ Google Summer of Code is a program sponsored by Google to let students interested in Open Source work on cool and challenging open source projects. The basic idea is that you will work together with a mentor on a project. We have selected a couple of main topics for you but it is up to you to write a more complete project proposal. If you have ideas of your own, that is fine too but you will need to find a mentor to supervise such a project. -If you would like to apply, please do the following: +If you would like to apply, please make sure that you have subscribed to [CFD-online](https://www.cfd-online.com/Forums/su2/) and github, and additionally join the developers team on slack (see our main website [su2code](https://su2code.github.io/). In that way you can stay informed about SU2, and our GSOC involvement. -Make sure that you have subscribed to [CFD-online](https://www.cfd-online.com/Forums/su2/) and github, and additionally join the developers team on slack (see our main website [su2code](https://su2code.github.io/). If you are interested in applying, please do the following: - -1. send an application email to gsoc@su2foundation.org with some personal details, education background and motivation +If you are interested in applying for GSOC with an SU2 project, please do the following: +1. send an application email to gsoc@su2foundation.org with some personal details, education background and motivation. 2. become a member of our slack channel and subscribe to the **general** and **gsoc** subchannel of SU2. Please introduce yourself :-) ## To Apply: -To be considered as a gsoc student for an SU2 project, it is not sufficient to simply write a proposal and send it to the google website. We will not accept students who never contacted us or did not finish the assignments. +To be considered as a GSOC student for an SU2 project, it is not sufficient to simply write a proposal and send it to the google website. We will not accept students who never contacted us or did not finish the assignments. We encourage students to participate in code development by fixing bugs or working on features. The minimum requirements to get accepted by the SU2 team for a GSOC project are: -- Create a brief CV with your contact details, your education and code experience. -- Briefly write about your experience and interests in SU2 and the specific project you would like to work on (if you know this already) +- Create a brief resume with your contact details, your education and code experience. If we cannot contact you, *we will not contact you*. +- Briefly write about your experience and interests in Computational Fluid Dynamics and SU2, and the specific project you would like to work on (if you know this already) - Briefly write about your current work schedule: are you studying/working, how will you manage the time, etc.. - Send it to gsoc@su2foundation.org -- Make the assignments on the assignment page. +- Make the assignments on the assignment page and send us your github page with your results. +- work on fixing things in SU2 Then in the last stage: -- Together with a mentor you will create a project planning with a timeline containing a breakdown of the project in parts with periodic deliverables/milestones. +- **Together with a mentor** you will create a project proposal and a planning with a timeline containing a breakdown of the project in parts with periodic deliverables/milestones. ## Evaluation Note that applying does not mean acceptance into the program. We will carefully consider your application to see if you are capable of the job, taking into account your experience and availability. We heavily weigh your participation and visibility in the introduction phase. -Please note that experience with SU2 is required, but a merged Pull Request on github will be seen as sufficient proof that you are capable of the job. A pull request for a tutorial or validation testcase is also acceptable. +Please note that experience with SU2 is required. A merged Pull Request on github is highly recommended experience. A pull request for a tutorial or validation testcase is also acceptable and will count as experience. ## Use of AI -we allow usage of AI tools to help you with your work. However, we do not allow the use of AI in so-called vibe-coding, where you let AI generate code that you do not understand. We also do not allow AI for automatic discussions with mentor or other users. +We allow usage of AI tools to *assist* you with your work. However, we do not allow the use of AI in vibe-coding where you let AI generate code that you do not understand. We also do not allow AI for automatic discussions with mentors or other users. AI is your assistant, not your replacement. If you do everything with AI, we might as well do it ourselves without you. From bbc1cb0e43e5e891a15d40862470bb095f5010e5 Mon Sep 17 00:00:00 2001 From: Josh Kelly <81244680+joshkellyjak@users.noreply.github.com> Date: Sat, 24 Jan 2026 15:19:53 +0000 Subject: [PATCH 10/15] Add project CMPLX for performance optimization in SU2 (#206) Added project description and details for CMPLX on performance optimization of complex arithmetic in SU2. --- _gsoc/Introduction.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/_gsoc/Introduction.md b/_gsoc/Introduction.md index dd0a29b2..ea24cb63 100644 --- a/_gsoc/Introduction.md +++ b/_gsoc/Introduction.md @@ -34,3 +34,12 @@ Expected Outcome (deliverables): SU2_AMR, an added executable that simply splits - Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) - Difficulty rating: **medium** +## Project CMPLX: Performance Optimization of Complex Arithmetic in SU2 +Project Description (max. 5 Sentences) +Complex arithmetic operations currently cause significant performance degradation in SU2 when features requiring complex numbers are enabled. This limitation affects the efficiency of certain solver capabilities and restricts their practical application in industrial-scale problems. Preliminary observations suggest that complex arithmetic is a primary bottleneck, but systematic profiling is needed to confirm and quantify these losses. The project's objective is to profile the solver to identify performance hotspots, validate that complex arithmetic is the root cause, and develop a custom complex arithmetic library optimised for SU2's specific use cases. This work will enable more efficient execution of complex-number-dependent features without compromising computational performance. +Expected Outcome (deliverables): Performance profiling report, custom complex arithmetic library (if validated as necessary), benchmark comparisons demonstrating speedup, integration into SU2 codebase, and documentation with usage guidelines. +- Skills Required: C++ +- Possible Mentors: Joshua A. Kelly (lead) +- Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) +- Difficulty rating: **medium** + From 1c1b0701b41a75ff31d3d7567218bd6c609589dc Mon Sep 17 00:00:00 2001 From: Evert Bunschoten <38651601+EvertBunschoten@users.noreply.github.com> Date: Wed, 28 Jan 2026 12:11:18 +0100 Subject: [PATCH 11/15] Added GSOC project (#207) Added project proposal for doing some exploratory work for physics-informed machine learning in SU2. --- _gsoc/Introduction.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/_gsoc/Introduction.md b/_gsoc/Introduction.md index ea24cb63..12d784a5 100644 --- a/_gsoc/Introduction.md +++ b/_gsoc/Introduction.md @@ -43,3 +43,13 @@ Expected Outcome (deliverables): Performance profiling report, custom complex ar - Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) - Difficulty rating: **medium** +## Project PIML: Towards physics-informed machine learning with SU2 +Project Description (max. 5 Sentences) +SU2 uses algorithmic differentiation (AD) for the adjoint solver and has the ability to use multi-layer perceptrons in data-driven equation of state models through the [MLPCpp](https://github.com/EvertBunschoten/MLPCpp.git) submodule. The aim of this project is to combine these two functionalities to enable physics-informed machine learning (PIML) in SU2 by updating the weights and biases of multi-layer perceptrons using AD for sensitivity calculation. PIML would enable data-driven turbulence modeling, solving partial differential equations without a mesh, and open the door to many other interesting research opportunities. +Expected Outcome (deliverables): Demonstration of training a MLP for a reference data set within SU2 and comparison, MLP training library including at least one commonly used training algorithm (e.g. Adam), and documentation explaining usage. +- Skills Required: C++, experience with machine learning +- Possible Mentors: Evert Bunschoten (lead) +- Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) +- Difficulty rating: **medium-hard** + + From c57b9bdd46b3b3a7054317de1e899aafd820a3b6 Mon Sep 17 00:00:00 2001 From: Nijso Date: Sun, 8 Feb 2026 17:01:30 +0100 Subject: [PATCH 12/15] Revise title and enhance GSOC participation info (#208) Updated the title and added participation details for GSOC 2026. --- _gsoc/Introduction.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_gsoc/Introduction.md b/_gsoc/Introduction.md index 12d784a5..b97c2bca 100644 --- a/_gsoc/Introduction.md +++ b/_gsoc/Introduction.md @@ -1,11 +1,11 @@ --- -title: Welcome to the SU2 Google Summer of Code Page +title: Ideas List for SU2 Google Summer of Code permalink: /gsoc/Introduction/ --- **Welcome to SU2 - GSOC!** -This is the updated ideas list for GSOC 2026. +This is the updated ideas list for GSOC 2026. If you are interested in participating in Google Sumemr of Code with the SU2 team, then please read the page on [participation](https://su2code.github.io/gsoc/Participation/). We can also accept personal ideas beyond the ones presented below but you need to convince one of the mentors to support you. We also need you to be proficient in SU2 and have some kind of technical background beyond general computer science (studying physics, mechanical engineering, aerospace engineering,...). ## Project BP: Adding pressure-based solver Project Description (max. 5 Sentences) From 825350f2e995990f192a4112b322556553715c75 Mon Sep 17 00:00:00 2001 From: Nijso Date: Fri, 13 Feb 2026 08:37:07 +0100 Subject: [PATCH 13/15] Revise GSOC 2026 introduction and project details (#209) Updated the introduction for GSOC 2026 with a corrected link to Google Summer of Code and clarified project details. --- _gsoc/Introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_gsoc/Introduction.md b/_gsoc/Introduction.md index b97c2bca..f2278b30 100644 --- a/_gsoc/Introduction.md +++ b/_gsoc/Introduction.md @@ -5,7 +5,7 @@ permalink: /gsoc/Introduction/ **Welcome to SU2 - GSOC!** -This is the updated ideas list for GSOC 2026. If you are interested in participating in Google Sumemr of Code with the SU2 team, then please read the page on [participation](https://su2code.github.io/gsoc/Participation/). We can also accept personal ideas beyond the ones presented below but you need to convince one of the mentors to support you. We also need you to be proficient in SU2 and have some kind of technical background beyond general computer science (studying physics, mechanical engineering, aerospace engineering,...). +This is the updated ideas list for GSOC 2026. If you are interested in participating in [Google Summer of Code](https://summerofcode.withgoogle.com/about) with the SU2 team, then please read the page on [participation](https://su2code.github.io/gsoc/Participation/). The projects listed below have been tuned to fit within the google summer of code program and they have mentors assigned to them. We can also accept personal ideas beyond the ones presented below but you need to convince one of the mentors to support you. We also need you to be proficient in SU2 and have some kind of technical background beyond general computer science (studying physics, mechanical engineering, aerospace engineering,...). ## Project BP: Adding pressure-based solver Project Description (max. 5 Sentences) From 97e82a426552e9f241a548d018fc6d3e9bbf479e Mon Sep 17 00:00:00 2001 From: Huseyin Ozdemir Date: Wed, 18 Feb 2026 11:33:22 +0100 Subject: [PATCH 14/15] Update Introduction.md Added a new project (FWH). --- _gsoc/Introduction.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/_gsoc/Introduction.md b/_gsoc/Introduction.md index f2278b30..b0e87ba9 100644 --- a/_gsoc/Introduction.md +++ b/_gsoc/Introduction.md @@ -52,4 +52,11 @@ Expected Outcome (deliverables): Demonstration of training a MLP for a reference - Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) - Difficulty rating: **medium-hard** - +## Project FWH: Generalizing FWH-Based Aeroacoustic Noise Prediction +This project aims to generalize a Python tool that implements Farassat’s 1A formulation of the Ffowcs Williams-Hawkings (FWH) equation for far-field noise prediction. While originally developed for tandem cylinder test cases and recently extended to airfoils, the current implementation is limited by case-specific logic. The primary objective is to refactor the codebase into a robust, geometry-agnostic framework capable of handling diverse and complex flow configurations. Test cases should be included in the regression tests. +Expected Outcome (deliverables): A stand-alone Python code. +- Skills Required: Python +- Possible Mentors: Huseyin Ozdemir, (lead) Nijso Beishuizen +- Expected Project Size (90 hrs/ small, 175 hrs/medium, 350 hrs/large): 175 hrs (medium) +- Difficulty rating: **medium** +- From 0d42dd11d03810d89c338079a1d1f576ac54ba76 Mon Sep 17 00:00:00 2001 From: Josh Kelly <81244680+joshkellyjak@users.noreply.github.com> Date: Fri, 20 Feb 2026 20:23:13 +0000 Subject: [PATCH 15/15] Revise GSoC project mentor information (#211) Added additional mentor --- _gsoc/Introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_gsoc/Introduction.md b/_gsoc/Introduction.md index b0e87ba9..f402af6d 100644 --- a/_gsoc/Introduction.md +++ b/_gsoc/Introduction.md @@ -39,7 +39,7 @@ Project Description (max. 5 Sentences) Complex arithmetic operations currently cause significant performance degradation in SU2 when features requiring complex numbers are enabled. This limitation affects the efficiency of certain solver capabilities and restricts their practical application in industrial-scale problems. Preliminary observations suggest that complex arithmetic is a primary bottleneck, but systematic profiling is needed to confirm and quantify these losses. The project's objective is to profile the solver to identify performance hotspots, validate that complex arithmetic is the root cause, and develop a custom complex arithmetic library optimised for SU2's specific use cases. This work will enable more efficient execution of complex-number-dependent features without compromising computational performance. Expected Outcome (deliverables): Performance profiling report, custom complex arithmetic library (if validated as necessary), benchmark comparisons demonstrating speedup, integration into SU2 codebase, and documentation with usage guidelines. - Skills Required: C++ -- Possible Mentors: Joshua A. Kelly (lead) +- Possible Mentors: Joshua A. Kelly (lead), Harsh Mishra - Expected Project Size (90 hrs/ small , 175 hrs/medium, 350 hrs/large): 175 hrs (medium) - Difficulty rating: **medium**