meso-web

Sources of the |Méso|Star> website
git clone git://git.meso-star.fr/meso-web.git
Log | Files | Refs | README | LICENSE

commit 3791b14fb83e95f7da4b4a79531f4f2334436792
parent d371374395eb9c14aad57aeb170799066bdb37c2
Author: Vincent Forest <vincent.forest@meso-star.com>
Date:   Tue, 28 May 2019 16:19:53 +0200

Add images to Star-3D, Star-VX and Star-SF

Diffstat:
Mmeso.css | 2+-
Astar-engine/.gitattributes | 3+++
Astar-engine/octree.jpg | 3+++
Astar-engine/polar.svg | 3+++
Mstar-engine/star-3d.html.in | 12+++++++++++-
Mstar-engine/star-sf.html.in | 11+++++++++++
Mstar-engine/star-vx.html.in | 19++++++++++++++++---
Astar-engine/turbine.jpg | 3+++
8 files changed, 51 insertions(+), 5 deletions(-)

diff --git a/meso.css b/meso.css @@ -206,7 +206,7 @@ hr { .img { float: right; - margin: 0 0 1em 1em; + margin: 0em 0em 1em 1em; } .caption { diff --git a/star-engine/.gitattributes b/star-engine/.gitattributes @@ -0,0 +1,3 @@ +octree.jpg filter=lfs diff=lfs merge=lfs -text +polar.svg filter=lfs diff=lfs merge=lfs -text +turbine.jpg filter=lfs diff=lfs merge=lfs -text diff --git a/star-engine/octree.jpg b/star-engine/octree.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0dd36589a7ad60e20642bb89b8a0f5f9c2f8ec4fb8f15300227f5f652182e787 +size 380694 diff --git a/star-engine/polar.svg b/star-engine/polar.svg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9fef1da10906b3231c26a644fc77ba2de89b29cd4792724327d30e70a198101 +size 21053 diff --git a/star-engine/star-3d.html.in b/star-engine/star-3d.html.in @@ -30,7 +30,17 @@ or several shapes to a <b>scene</b>. A scene can be <b>instantiated</b> into one or several shapes that can be then attached to a scene as any regular shapes. Each instance has its own position and orientation while the instantiated geometry is stored once even though it is instantiated several -times. This feature can thus be used to create extremely complex environment +times. +<span class="img" style="width: 18em; padding-top: 1em"> + <a href="turbine.jpg"> + <img src="turbine.jpg" alt="Turbine"> + </a> + <span class="caption"> + Exemple of a geometry handled by Star-3D + </span> +</span> + +This feature can thus be used to create extremely complex environment with a low memory footprint.</p> <p>To access the scene data through uniform sampling or ray-tracing, one has to diff --git a/star-engine/star-sf.html.in b/star-engine/star-sf.html.in @@ -21,6 +21,17 @@ Scattering Distribution Functions (BSDF), microfacet distributions and fresnel terms, and in a volume with <b>phase functions</b>. The main target of Star-SF are programmers that have to evaluate or sampled these scattering effects.</p> +<span class="img" style="width: 18em; padding-top: 1em"> + <a href="polar.svg"> + <img src="polar.svg" alt="Phase function"> + </a> + <span class="caption"> + 2D illustration of a phase function: probability to scatter in any + direction + </span> +</span> + + <p>The Star-SF API makes no reference to the implementation of the aforementionned data structures. In addition, it publicly exposes their <b>interface</b>. Consequently, the user can not only switch the BSDF, diff --git a/star-engine/star-vx.html.in b/star-engine/star-vx.html.in @@ -24,9 +24,22 @@ partitioning data structures or to access them through <b>ray-tracing</b>.</p> and the <b>octree</b> that are used to partition 1D or 3D data, respectively. For both structures, data are partitionned following a bottom-top strategy: the caller submits the raw data to Star-VoXel that it recursively structures from -the leaf (the user data) to to the root of the tree. The policies used to merge -input data as well as the merge operator itself are defined by the caller; -Star-VoXel settles for building the hierarchical structure only.</p> +the leaf (the user data) to to the root of the tree. + +<span class="img" style="width: 16em; padding: 1em"> + <a href="octree.jpg"> + <img src="octree.jpg" alt="Octree"> + </a> + <span class="caption"> + Octree built by Star-VoXel from cloud field data produced by a Large Eddy + Simulation. + </span> +</span> + + +The policies used to merge input data as well as the merge operator itself are +defined by the caller; Star-VoXel settles for building the hierarchical +structure only.</p> <p>The way data are accessed through indexing or ray-tracing can be finely tuned by the caller. Beyond the probe position or the ray to trace, the user diff --git a/star-engine/turbine.jpg b/star-engine/turbine.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec9e1cd906ca046b6d77fe44c8093bb00ec6c83004dc037e582345fd4651866c +size 275266