aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Garlick <pgarlick@tourbillion-technology.com>2018-04-09 19:30:03 +0100
committerPaul Garlick <pgarlick@tourbillion-technology.com>2018-04-09 19:30:03 +0100
commit8b89a66d98308432def2a485e3bd82e7d04185dd (patch)
tree8c23e0a76e1fa416a2e629a6923f868640c1444e
parent55c4565de8ebeb2e6f2eef6d368842bdf970bcc1 (diff)
downloadtweed-8b89a66d98308432def2a485e3bd82e7d04185dd.tar.gz
update README file, use relative path for connectivities diagram
-rw-r--r--README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index 7fe5d5f..d989826 100644
--- a/README.md
+++ b/README.md
@@ -134,7 +134,7 @@ use of both types of data format. Communication between the applications is
possible in a number of ways. A configuration of applications and exchange
formats that demonstrates the principle is shown in the diagram below:
-![](file:///data/paul/Ditaa/connectivities.png)
+![connectivities](file://images/connectivities.png)
This configuration forms a template for a typical engineering workflow. It is
suitable for a wide range of design and development projects. The *Gmsh*
@@ -155,8 +155,8 @@ In this configuration there are three standard file formats:
and two specific formats:
-a. [MSH](http://gmsh.info/doc/texinfo/gmsh.html#File-formats) - *Gmsh* mesh and result data
-b. [FOAM](https://cfd.direct/openfoam/user-guide/basic-file-format/) - *OpenFOAM* mesh and result data
+1. [MSH](http://gmsh.info/doc/texinfo/gmsh.html#File-formats) - *Gmsh* mesh and result data
+2. [FOAM](https://cfd.direct/openfoam/user-guide/basic-file-format/) - *OpenFOAM* mesh and result data
All of the applications in *TWEED* can read from and write to at least one