|
638 | 638 | </programlisting> |
639 | 639 | </example> |
640 | 640 |
|
| 641 | + <funcsynopsis> |
| 642 | + <funcprototype> |
| 643 | + <funcdef><function>max_order</function></funcdef> |
| 644 | + <paramdef>smoc</paramdef> |
| 645 | + </funcprototype> |
| 646 | + </funcsynopsis> |
| 647 | + <para> |
| 648 | + Returns the maximal order of an smoc. |
| 649 | + </para> |
| 650 | + <para> |
| 651 | + The maximal order of a MOC can be higher than than the highest |
| 652 | + order appearing in the serialisation. For instance, in the example |
| 653 | + below the full-sky coverage given at order 6 means that no patch |
| 654 | + larger than about 1 degree is not covered. In the ASCII |
| 655 | + serialisation, give the maximum order with an with an empty cell |
| 656 | + list. |
| 657 | + </para> |
| 658 | + |
| 659 | + <example> |
| 660 | + <title>Obtaining a MOC order</title> |
| 661 | + <programlisting> |
| 662 | +<![CDATA[SELECT max_order(smoc('0/0-11 6/')) as order;]]> |
| 663 | +<![CDATA[ order]]> |
| 664 | +<![CDATA[-----------]]> |
| 665 | +<![CDATA[ 6 ]]> |
| 666 | + </programlisting> |
| 667 | + </example> |
| 668 | + |
641 | 669 | </sect2> |
642 | 670 |
|
643 | 671 | </sect1> |