You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-1Lines changed: 20 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,8 @@ The MANGO model proposes a flexible way to expose data related to astronomical s
10
10
11
11
# Document Building
12
12
13
+
## Why such a Complex Workflow?
14
+
13
15
The process of creating the document is a bit complex due to the following facts:
14
16
15
17
- The model is maintained with Modelio which does not support any version control.
@@ -22,10 +24,27 @@ The process of creating the document is a bit complex due to the following facts
22
24
this must be corrected to have a consistent table of content
23
25
24
26
This process is achieved by scripts located in `utils`. Please read `utils/README.rst`.
25
-
26
27
If you want to contribute, please have a look at this workflow or ask the editor.
27
28
This will prevent your work to be overridden by some script.
28
29
30
+
## How to Contribute Anyway
31
+
32
+
- Install `mivot-validator`in your favorite virtual environment
33
+
- Modify the description of some model elements (section 3-11 at the time of writing)
34
+
- go into `./vo-dml/desc`
35
+
- edit the file you want to update
36
+
- go into `utils`
37
+
- run `./buildDoc.bash`
38
+
- Modify the plain text (section out of 3-11 at the time of writing)
39
+
- go into `./doc
40
+
- edit `MANGO.tex` or `tap.tex`, those files are never overridden.
41
+
- go into `utils`
42
+
- run `./buildDoc.bash`
43
+
- Modify the model itself
44
+
- ask the editor with an issue
45
+
46
+
If you want to contribute, please have a look at this workflow or ask the editor.
47
+
29
48
# PDF preview
30
49
31
50
The PDF preview can be seen [here](https://github.com/ivoa-std/MANGO/releases/download/auto-pdf-preview/MANGO-draft.pdf) thanks to the ADQL team who has written a workflow generating it automatically.
Copy file name to clipboardExpand all lines: doc/model.tex
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -413,7 +413,7 @@ \section{Model: mango }
413
413
414
414
\subsection{Shape}
415
415
\label{sect:Shape}
416
-
Description of the spatial extension of the MANGO object (for e.g. dust clouds)
416
+
Description of the spatial extent of the MANGO object (e.g. for dust clouds). Shape is serialized as a string. \begin{itemize} \item The supported serialization modes are listed in the \texttt{ShapeSerialization} enumeration. \item If the space coordinate system is not embedded in the serialization mode, it can be defined by the \texttt{spaceSys} reference. \end{itemize}
\textbf{description:} Label indicating that the shape has been serialized as a SMOC \citep{2022ivoa.spec.0727F}. SMOC should be in equatorial ICRS. This overrides the attached space coordinate system (\texttt{spaceSys} reference). When using this serialisation, \texttt{spaceSys} can be ignored.
\textbf{description:} Label indicating that the shape has been serialized as a STC-S string (see \url{https://www.ivoa.net/documents/STC-S/20130917/index.html}). SMOC should be in equatorial ICRS. This overrides the attached space coordinate system (\texttt{spaceSys} reference). When using this serialisation, \texttt{spaceSys} can be ignored.
\textbf{description:} Label indicating that the shape has been serialized as a polygon (cf xtypes)
509
+
\textbf{description:} Label indicating that the shape has been serialized as a polygon as defined in \cite{2017ivoa.spec.0517D} section 3.3.7. Using the polygon serialization requires the space coordinate system to be defined.
Copy file name to clipboardExpand all lines: doc/model_toc.tex
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -478,7 +478,7 @@ \section{Other Properties}
478
478
479
479
\subsection{Shape}
480
480
\label{sect:Shape}
481
-
Description of the spatial extension of the MANGO object (for e.g. dust clouds)
481
+
Description of the spatial extent of the MANGO object (e.g. for dust clouds). Shape is serialized as a string. \begin{itemize} \item The supported serialization modes are listed in the \texttt{ShapeSerialization} enumeration. \item If the space coordinate system is not embedded in the serialization mode, it can be defined by the \texttt{spaceSys} reference. \end{itemize}
\textbf{description:} Label indicating that the shape has been serialized as a SMOC \citep{2022ivoa.spec.0727F}. SMOC should be in equatorial ICRS. This overrides the attached space coordinate system (\texttt{spaceSys} reference). When using this serialisation, \texttt{spaceSys} can be ignored.
\textbf{description:} Label indicating that the shape has been serialized as a STC-S string (see \url{https://www.ivoa.net/documents/STC-S/20130917/index.html}). SMOC should be in equatorial ICRS. This overrides the attached space coordinate system (\texttt{spaceSys} reference). When using this serialisation, \texttt{spaceSys} can be ignored.
\textbf{description:} Label indicating that the shape has been serialized as a polygon (cf xtypes)
515
+
\textbf{description:} Label indicating that the shape has been serialized as a polygon as defined in \cite{2017ivoa.spec.0517D} section 3.3.7. Using the polygon serialization requires the space coordinate system to be defined.
0 commit comments