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
{{ message }}
This repository was archived by the owner on Feb 2, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: docs/Documentation_Guidelines.txt
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -1,34 +1,34 @@
1
-
This file provides guidelines for developers on how to update the documentation. The content of the file will be added to the developers' document later. If you have any questions about this file or Intel(R) SDC documentation please contact Rujal Desai.
1
+
This file provides guidelines for developers on how to update the documentation. The content of the file will be added to the developers' document later. If you have any questions about this file or Intel® SDC documentation please contact Rujal Desai.
2
2
How to update the documentation
3
3
4
-
Intel(R) SDC documentation is built using Sphinx. Building the documentation is not part of Intel(R) SDC build as of now(that may change later). So you have to follow few extra steps to build new documentation.
4
+
Intel® SDC documentation is built using Sphinx. Building the documentation is not part of Intel® SDC build as of now(that may change later). So you have to follow few extra steps to build new documentation.
5
5
6
6
Sphinx uses RST files to generate html/pdf output. Therefore the new documentation should either be in RST file or standardized docstring(provided with the function/class definition inside source code).
7
7
8
8
There are two ways to contribute to the documentation:
9
-
1. Add documentation for a Pandas API overloaded in Intel(R) SDC
9
+
1. Add documentation for a Pandas API overloaded in Intel® SDC
10
10
2. Add/Change content of one of the section of the existing documentation
11
11
12
12
Pandas API Documentation
13
13
14
-
If you have implemented a Pandas function/operator in Intel(R) SDC follow these steps to add it to the new documentation:
14
+
If you have implemented a Pandas function/operator in Intel® SDC follow these steps to add it to the new documentation:
15
15
16
-
1. Write a docstring inside the function/operator definition and make sure it is in the standardized format that Intel(R) SDC follows
16
+
1. Write a docstring inside the function/operator definition and make sure it is in the standardized format that Intel® SDC follows
17
17
18
18
If you are not aware of the standardized format of docstring refer to pandas.Series.append method in hpat/datatypes/hpat_series_functions.py . Also, make sure the function definition has all the arguments included in it even though HPAt doesn't support that argument. For example, Pandas Series.ne(not equal) method has the following signature:
where new_funcname : function name given by developer
26
26
27
27
2. Edit the script rename_function.py
28
28
29
-
This step is part of a work around. Hence it is specific to Intel(R) SDC. Sphinx uses autodoc to automatically generate documentation from a function docstring. However, if we use that directly the function name displayed in User's Guide for Intel(R) SDC will be the function name that developer has used to overload Pandas API instead of the actual name of that Pandas API that is overloaded. For example,
29
+
This step is part of a work around. Hence it is specific to Intel® SDC. Sphinx uses autodoc to automatically generate documentation from a function docstring. However, if we use that directly the function name displayed in User's Guide for Intel® SDC will be the function name that developer has used to overload Pandas API instead of the actual name of that Pandas API that is overloaded. For example,
30
30
31
-
Pandas.Series.append method is overloaded in Intel(R) SDC by this function definition:
31
+
Pandas.Series.append method is overloaded in Intel® SDC by this function definition:
Copy file name to clipboardExpand all lines: docs/usersource/GettingStarted.rst
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,31 +1,31 @@
1
1
.. _GettingStarted:
2
2
3
-
Getting Started with Intel(R) SDC
3
+
Getting Started with Intel® SDC
4
4
~~~~~~~~~~~~~~~~~~~~~~~~~
5
5
6
-
Intel(R) SDC is useful to accelerate a subset of `Python <https://docs.python.org/3/>`_ operations working with `Pandas Series <https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.Series.html>`_ and `Dataframes <https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.html>`_ as well as with `Numpy Arrays <https://docs.scipy.org/doc/numpy/reference/generated/numpy.array.html>`_ . Being the just-in-time compiler built on top of `Numba <http://numba.pydata.org/numba-doc/latest/index.html>`_ Intel(R) SDC will compile a subset of Pandas and Numpy codes into the native code. The compilation is controlled by a set of `Numba decorators <http://numba.pydata.org/numba-doc/0.8/modules/decorators.html>`_ and **Intel(R) SDC decorators** that can be applied to a function.
6
+
Intel® SDC is useful to accelerate a subset of `Python <https://docs.python.org/3/>`_ operations working with `Pandas Series <https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.Series.html>`_ and `Dataframes <https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.html>`_ as well as with `Numpy Arrays <https://docs.scipy.org/doc/numpy/reference/generated/numpy.array.html>`_ . Being the just-in-time compiler built on top of `Numba <http://numba.pydata.org/numba-doc/latest/index.html>`_ Intel® SDC will compile a subset of Pandas and Numpy codes into the native code. The compilation is controlled by a set of `Numba decorators <http://numba.pydata.org/numba-doc/0.8/modules/decorators.html>`_ and **Intel® SDC decorators** that can be applied to a function.
7
7
8
-
The code below illustrates a typical workflow that Intel(R) SDC is intended to compile
8
+
The code below illustrates a typical workflow that Intel® SDC is intended to compile
9
9
10
10
.. todo::
11
11
Short code illustrating how hpat can compile read_csv and compute aggregators over columns
12
12
13
13
We also recommend to read `A ~5 minute guide to Numba <https://numba.pydata.org/numba-doc/dev/user/5minguide.html>`_ .
14
14
15
-
Installing Intel(R) SDC
15
+
Installing Intel® SDC
16
16
===============
17
17
18
18
.. todo::
19
19
20
20
instructions how to install hpat using 1) conda, 2) pip
21
21
22
-
Experienced users can also compile Intel(R) SDC from sources<link to github build instructions for hpat>
22
+
Experienced users can also compile Intel® SDC from sources<link to github build instructions for hpat>
23
23
24
-
How to use Intel(R) SDC
24
+
How to use Intel® SDC
25
25
================
26
26
27
27
.. todo::
28
-
Provide a few code snapshots illustrating typical usages of Intel(R) SDC:
28
+
Provide a few code snapshots illustrating typical usages of Intel® SDC:
29
29
• Reading a file
30
30
• Working with a column - a few basic ops, e.g. aggregation or sorting + UDF
31
31
• Working with a dataframe
@@ -54,11 +54,11 @@ What If I Get A Compilation Error
54
54
=================================
55
55
56
56
.. todo::
57
-
Need to give basic information that hpat and numba do not support full set of Pandas and Numpy APIs, provide the link to the API Reference section for Intel(R) SDC, relevant reference to Numba documentation.
57
+
Need to give basic information that hpat and numba do not support full set of Pandas and Numpy APIs, provide the link to the API Reference section for Intel® SDC, relevant reference to Numba documentation.
58
58
59
-
Also give very short introduction to what kind of code Numba/Intel(R) SDC can compile and what cannot, i.e. type stability etc. Provide the links to relevant sections in Intel(R) SDC and Numba documentations focusing on compilation issues/limitations
59
+
Also give very short introduction to what kind of code Numba/Intel® SDC can compile and what cannot, i.e. type stability etc. Provide the links to relevant sections in Intel® SDC and Numba documentations focusing on compilation issues/limitations
60
60
61
-
Measuring Intel(R) SDC performance
61
+
Measuring Intel® SDC performance
62
62
===========================
63
63
64
64
.. todo::
@@ -69,4 +69,4 @@ What If I Get Poor Performance?
69
69
70
70
.. todo::
71
71
Short introduction why performance may be slower than expected. GIL, Object mode and nopython mode. Overheads related to boxing and unboxing Python objects.
72
-
Reference to relevant sections of Intel(R) SDC and Numba documentation for detailed discussion
72
+
Reference to relevant sections of Intel® SDC and Numba documentation for detailed discussion
0 commit comments