This is an automated email from the ASF dual-hosted git repository.
eamonford pushed a commit to branch update-docs
in repository https://gitbox.apache.org/repos/asf/incubator-sdap-ingester.git
The following commit(s) were added to refs/heads/update-docs by this push:
new 43242a3 Readme
43242a3 is described below
commit 43242a32fc7ac4831cf21b654e522e11461ea1b3
Author: Eamon Ford <[email protected]>
AuthorDate: Mon Dec 7 14:06:33 2020 -0800
Readme
---
collection_manager/README.md | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/collection_manager/README.md b/collection_manager/README.md
index bc630cd..5abbe80 100644
--- a/collection_manager/README.md
+++ b/collection_manager/README.md
@@ -94,12 +94,13 @@ collections:
j: 30
```
-Note that the dimensions listed under `slices` will not necessarily match
those under `dimensionNames`. This is because sometimes
+Note that the dimensions listed under `slices` will not necessarily match the
values of the properties under `dimensionNames`. This is because sometimes
the actual dimensions are referenced by index variables.
+
> **Tip:** An easy way to determine which variables go under `dimensionNames`
> and which ones go under `slices` is that the variables
-> on which the primary variable is dependent should go under `slices`, and the
variables on which _those_ variables are dependent
-> (which could be themselves, as in the case of the first collection in the
above example) should go under `dimensionNames`. The excepction
-> to this is that the primary variable is always listed under
`dimensionNames.variable`.
+> on which the primary variable is dependent should be listed under `slices`,
and the variables on which _those_ variables are dependent
+> (which could be themselves, as in the case of the first collection in the
above example) should be the values of the properties under
+> `dimensionNames`. The excepction to this is that the primary variable is
always listed under `dimensionNames.variable`.
## Running the tests
From `incubator-sdap-ingester/`, run:
