commit cbf23af02cffb3cd5b92bc7a17adfee2ef04e973
parent b7165bd833b0215212645a8934167e1650ceb92c
Author: Vincent Forest <vincent.forest@meso-star.com>
Date: Fri, 28 Jul 2017 11:28:22 +0200
Merge branch 'release-0.2.3' into develop
Diffstat:
3 files changed, 24 insertions(+), 11 deletions(-)
diff --git a/README.md b/README.md
@@ -60,6 +60,16 @@ informations on CMake.
## Release notes
+### Version 0.2.3
+
+- Update the solstice-input file format. The anchor and entity name cannot
+ contain spaces or tabulations anymore.
+- Fix the reported sun directions in the solstice-output. For each submitted
+ sun direction, solstice correctly output its Cartesian coordinates but always
+ wrote the azimuthal and elevation angles of the first direction.
+- Update the solstice-output map page: add the missing `<efficiency>` grammar
+ rule and fix the definition of the `<map-side-data>` grammar rule.
+
### Version 0.2.2
- Fix how the AsciiDoc tool suite is looking for on Windows; it was never found
diff --git a/cmake/CMakeLists.txt b/cmake/CMakeLists.txt
@@ -100,7 +100,7 @@ configure_file(${SOLSTICE_SOURCE_DIR}/../doc/solstice.1.txt.in
################################################################################
set(VERSION_MAJOR 0)
set(VERSION_MINOR 2)
-set(VERSION_PATCH 2)
+set(VERSION_PATCH 3)
set(VERSION ${VERSION_MAJOR}.${VERSION_MINOR}.${VERSION_PATCH})
set(SOLSTICE_FILES_SRC
diff --git a/doc/solstice-input.5.txt b/doc/solstice-input.5.txt
@@ -649,9 +649,10 @@ identity, i.e. its *rotation* and *translation* are nulls.
Each entity has a *name* which must be unique per hierarchy level: 2 root
entities (i.e. entities without parent) cannot have the same name as well as
-the children of a same parent entity. A child entity is identified into the
-solar plant by successively concatenating, with the \'.' character, the name of
-its ancestors with its own name. This naming convention is used in the
+the children of a same parent entity. In addition, the name string cannot
+contain dots, spaces or tabulations. A child entity is identified into the
+solar plant by successively concatenating, with the \'.' character, the name
+of its ancestors with its own name. This naming convention is used in the
*solstice-receiver*(5) format to define the entities to track during the
*solstice*(1) computations. For instance, in the following example, the
*entity-identifier* of the child entity named *level2* is
@@ -764,13 +765,15 @@ Anchor
~~~~~~
An *anchor* defines a relative position into the entity hierarchy. They are
-particularly useful for pivots and hyperbolic shapes that may have to reference
-a position relative to an entity whose transformations may also depends of its
-ancestor. An anchor has a *name* that must be unique for the whole sets of per
-entity anchors. An anchor is identified into the solar plant by concatenating,
-with the \'.' character, its name to the *entity-identifier* of the entity into
-which it is declared. For instance, in the following example, the
-*anchor-identifier* of the anchor named *anchor0* is *level0.level1.anchor0*:
+particularly useful for pivots and hyperbolic shapes that may have to
+reference a position relative to an entity whose transformations may also
+depends of its ancestor. An anchor has a *name* that must be unique for the
+whole sets of per entity anchors. In addition, a name cannot contain
+dots, spaces or tabulations. An anchor is identified into the solar plant by
+concatenating, with the \'.' character, its name to the *entity-identifier* of
+the entity into which it is declared. For instance, in the following example,
+the *anchor-identifier* of the anchor named *anchor0* is
+*level0.level1.anchor0*:
.......
entity:
name: level0
