From aecd2dcd9af71911ce0b2be0ac74c1820c02f3f7 Mon Sep 17 00:00:00 2001 From: Thomas White Date: Fri, 26 Apr 2024 16:14:14 +0200 Subject: Further clarification about ordering of panel group directives See 79bda19687e425818888ce17cc6e2239744ee640 --- doc/man/crystfel_geometry.5.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/man/crystfel_geometry.5.md b/doc/man/crystfel_geometry.5.md index 0a3fffbd..640771ee 100644 --- a/doc/man/crystfel_geometry.5.md +++ b/doc/man/crystfel_geometry.5.md @@ -529,13 +529,15 @@ Groups can themselves be combined into higher-level groups, for example: group_all = abc,def -This defines a group called *all** which contains both of the groups created +This defines a group called **all** which contains both of the groups created above. The highest-level group should always be called **all**. -The group definitions must come **after** the panel definitions. A good way -to go is to put all the group definitions at the very end of the geometry file. +All members of a group need to be defined before defining the group. This +means that the group definitions must come **after** the panel definitions, and +the groups should be defined from the bottom to top level of the hierarchy - +the **all** group coming last. If you do not define any groups, CrystFEL will automatically create the **all** group for you, containing all panels in a flat hierarchy. This allows basic -- cgit v1.2.3