-

Introduction_to_CFD_with_Python_kardontchik/README.md

@@ -0,0 +1,63 @@
+# README
+
+Dr. Kardontchik shared these codes with me which closely follow Toro's book
+Riemann Solvers and Numerical Methods for Fluid Dynamics. 
+
+Reference papers:
+
+1) “A Python way to an undergraduate CFD course”
+
+2) “Performance of simple spatial-discretization methods in two dimensions”
+
+3) “Teaching CFD with Python”
+
+The code to run all the examples in the papers is sent in different
+zipped files that should be placed in separated folders. These folders
+are:
+
+a) Paper1
+
+b) Paper2_LISKA_WENDROFF_cases_HLLC_ENO
+
+c) Paper2_LISKA_WENDROFF_cases_HLLC
+
+d) Paper3_DISTMESH
+
+e) Paper3_body_fitted_meshes
+
+f) Paper3_applications
+
+
+In every folder you will find a text file named AA_README with a
+description of what the files in that folder do and how to run them.
+
+For first-time users I recommend the following sequence, based on the
+criterion that is best to begin with short simulations (to understand
+the mechanics) and end with long simulations:
+
+1) Begin with the one-dimensional simulations in folder Paper1 (Toro’s
+5 classical tests).  These simulations run very fast, usually less
+than 1 minute each
+
+2) Then go to the folder Paper3_DISTMESH and run the simulations to
+obtain the meshes of simple domains (1-2 minutes each). This will let
+you become familiar with Persson’s DISTMESH mesh generator.
+
+3) Then go to any of the two folders that run the simulations of
+Liska-Wendroff’s six 2D cases. Although these simulations might last
+up to 30 minutes (when run with a very fine mesh), they are simple
+since the mesh is simple and you can run them first in a few minutes
+by using a coarse mesh first. These simulations introduce you to the
+world of 2D simulations so you can begin getting familiar with the
+graphical displays used for 2D.
+
+4) Finally, you can go to the folder Paper3_applications to run the
+more complex files dealing with Toro’s explosion and wedge tests, the
+blunt-nosed cylinder and the NACA0012 airfoil.
+
+IF YOU USE THE CODE OR MY PAPERS IN YOUR WORK WITH YOUR PEERS, OR WITH
+STUDENTS OR IN YOUR PUBLICATIONS, KINDLY ACKNOWLEDGE THEIR USE BY
+REFERRING TO MY PAPERS AS THEY APPEARED AT http://www.researchgate.net
+NO PART OF THE CODE SHOULD BE USED FOR COMMERCIAL PURPOSES. IT IS
+INTENDED TO BE USED ONLY AT EDUCATIONAL INSTITUTIONS.  Jaime
+E. Kardontchik, PhD Sunnyvale, CA

Numerical_Methods_for_PDEs_CS555_Kloneckner/.gitignore

@@ -0,0 +1,20 @@
+*~
+.sw[op]
+.*.sw[pno]
+*-dot.fig
+out
+*.tar.gz
+*.ps.gz
+data/out
+prev
+lectures/fast-alg-notes.pdf
+fontconfig
+__pycache__
+
+.#*
+\#*#
+
+*.orgmk
+.ipynb_checkpoints
+
+common-lisp-jupyter

Numerical_Methods_for_PDEs_CS555_Kloneckner/.gitmodules

@@ -0,0 +1,6 @@
+[submodule "notes/orgmk"]
+	path = notes/orgmk
+	url = https://github.com/inducer/orgmk
+[submodule "demos/ipython-demo-tools"]
+	path = demos/ipython-demo-tools
+	url = https://github.com/inducer/ipython-demo-tools.git

Numerical_Methods_for_PDEs_CS555_Kloneckner/README.md

@@ -0,0 +1,81 @@
+# Numerical Methods for Partial Differential Equations
+
+Slides/notes and Jupyter notebook demos for an introductory course of numerical
+methods for PDEs.
+
+Originally developed for [CS555 in the spring of 2020](https://relate.cs.illinois.edu/course/cs555-s20/)
+in the [Department of Computer Science](https://cs.illinois.edu/)
+at the [University of Illinois](https://illinois.edu/), based on prior versions of the
+class taught by Luke Olson.
+
+-   [PDF](https://andreask.cs.illinois.edu/cs555-s20/notes.pdf) of these slides/notes (see `notes`
+    for source)
+
+-   [Demos](https://mybinder.org/v2/gh/inducer/numpde-notes/main?filepath=demos)
+    in [Binder](https://mybinder.org/)
+
+-   The demos use annotations for [`ipython-demo-tools`](https://github.com/inducer/ipython-demo-tools).
+    A `#clear` annotation at the beginning of a code cell allows the
+    `clear-marked-inputs` subcommand of
+    [`prepare-ipynb`](https://github.com/inducer/ipython-demo-tools/blob/main/prepare-ipynb) 
+    to remove the content of those input cells, maybe to use them for live coding in class.
+    The `#clear` marks themselves can be removed by that `remove-marks` subcommand.
+
+-   The notes are written in [Org mode](https://orgmode.org/), which serves as a lightweight
+    markup language over LaTeX. They're easiest to edit in Emacs, but
+    [vim-orgmode](https://github.com/jceb/vim-orgmode) will do as well.
+
+    To build the notes, you need any recent version of Emacs installed. Also make sure that
+    submodules cloned properly:
+    ```
+    git submodule update --init
+    ```
+
+    Then simply change to the `notes` subdirectory and say:
+    ```
+    ./make.sh
+    ```
+    The script will optionally make use of [`latexrun`](https://github.com/cjoach/latexrun).
+    If you get
+    ```
+    There were errors; output not updated
+    ```
+    on the first go, simply rerun `make.sh`.
+
+-   `make.sh` will generate two PDFs: `notes.pdf` and `notes-folded.pdf`.
+    They differ in whether the boxes present in the notes (containing many
+    of the most salient mathematical developments) are filled in or not.
+
+    I use the un-filled version for class and fill in the boxes by hand
+    during class using [Xournal++](https://github.com/xournalpp/xournalpp/)
+    (but equivalent notetaking applications should work just as well).
+
+## Problems and Assignments
+
+If you can demonstrate that you are teaching a related course
+at a college or university anywhere in the world, I have
+homework assignments and projects (some of which are autograded
+using the [RELATE](https://github.com/inducer/relate/) system)
+that I would be happy to share with you.
+
+## MIT License
+
+Copyright (C) 2020 Andreas Kloeckner
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.