https://github.com/k1dv5/docal
Do calculations and automatically insert them into your document
https://github.com/k1dv5/docal
calculations engineering equation latex latex-document mathcad python python-library scientific-reports
Last synced: 2 months ago
JSON representation
Do calculations and automatically insert them into your document
- Host: GitHub
- URL: https://github.com/k1dv5/docal
- Owner: K1DV5
- Created: 2018-06-12T12:06:12.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2024-06-16T09:06:57.000Z (over 1 year ago)
- Last Synced: 2024-12-15T16:55:43.946Z (10 months ago)
- Topics: calculations, engineering, equation, latex, latex-document, mathcad, python, python-library, scientific-reports
- Language: Python
- Homepage:
- Size: 456 KB
- Stars: 46
- Watchers: 5
- Forks: 5
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# docal
[](https://pypi.python.org/pypi/docal)
Inject Python calculations into Word and LaTeX documents with ease!
- Free software: MIT license
docal is a tool that can be used to send calculations that are written in
python to Word or LaTeX documents. It evaluates equations in a separate python
script from the document and replaces hashtags in the document that indicate
where the calculations should be with the results of the evaluation. It comes
with a powerful python expression to document equations converter built-in, so
it converts the calculations and their results into their native equation forms
of the document before sending them, which makes it ideal to make academic and
scientific reports.
## Installation
### Requirements
The only requirement is Python with [this
version](https://github.com/K1DV5/docal/blob/e00bde00b67ef672816abc381ad1c36325137159/pyproject.toml#L14),
and with `pip`.
### Install
To install this package, type the following command and hit Enter.
```shell
pip install docal
```
Or from the source:
```shell
pip install .
```
To install the LSP support (see below), you can add `[lsp]`:
```shell
pip install docal[lsp]
```
## Usage
The typical workflow is as follows:
- The static parts of the document are written as usual (Word or
LaTeX) but leaving sort of unique hashtags (\#tagname) for the
calculation parts.
- The calculations are written on a separate text file with any text
editor and saved next to the document file. For the syntax of the calculation
file, see below. But it\'s just a python script with comments.
- The tool is invoked with the following command:
```shell
docal [calculation-file] -i [input-file] -o [output-file]
```
so for example,
```shell
docal calcs.py -i document.tex -o document-out.tex
```
- Then voila! what is needed is done. The output file can be used
normally.
## Example
Let\'s say you have a word document `foo.docx` with contents like this.
And you write the calculations in the file `foo.py` next to `foo.docx`
```python
## foo.py
## necessary for scientific functions:
from math import *
#foo
# The first side of the first triangle is
x_1 = 5 #m
# and the second,
y_1 = 6 #m
# Therefore the length of the hypotenuse will be,
z_1 = sqrt(x_1**2 + y_1**2) #m
#bar
# Now the second triangle has sides that have lengths of
x_2 = 3
y_2 = 4
# and therefore has a hypotenuse of
z_2 = sqrt(x_2**2 + y_2**2) #m,13
# Then, we can say that the hypotenuse of the first triangle which is #z_1 long
# is longer than that of the second which is #z_2 long.
```
Now, If we run the command
```shell
docal foo.py -o foo.docx
```
A third file, named `foo-out.docx` will appear. And it will look like this:
## Syntax
The syntax is simple. Just write the equations one line at a time. What
you write in the syntax is a valid Python file, (it is just a script
with a lot of assignments and comments).
### Equations (python assignments)
These are the main focus points of this module. Obviously, they are
evaluated as normal in the script so that the value of the variable can
be reused as always, but when they appear in the document, they are
displayed as equation blocks that can have up to three steps (that show
the procedures).
- If it is a simple assignment, like `x = 10`, they appear only having a single step, because there is no procedure to show.
- If the assignment contains something to be evaluated but no variable reference like `x = 10 + 5 / 2` or if it contains a single variable reference like `x = x_prime` then the procedure will have only two steps, first the equation and second the results.
- If the equation has both things to be evaluated and variable references, like
`x = 5*x_prime + 10` then it will have three steps: the equation itself, the equation with variable references substituted by their values, and the result.
These equations can be customized using comments at their ends (see below).
### Comments after equations (options)
These comments are taken to be customization options for the equations.
Multiple options can be separated by commas.
- **Units**: If you write something that looks like a unit (names or expressions of names) like `N/m**2` they are correctly displayed as units next to the result and whenever that variable is referenced, next to its value. Note that this is just showing units. Otherwise, units are not involved in computations.
- **Display type**:
- If the option is a single dollar sign `$`, the equation will be inline and if it has more than a single step, the steps appear next to each other.
- If it is double dollar signs `$$`, the equation(s) will be displayed as block (centered) equations (default).
- **Step overrides**: If it is a sequence of digits like `12`, then only the steps corresponding to that number will be displayed (for this case steps 1 and 2).
- **Matrix and array cut-off size**: Matrices are cut off and displayed with dots in them if their sizes are greater than this and arrays are cut off if they have more than this number. To override this number, the option is the letter m followed by a number like `m6`. Default: `m10`
- **Note**: If the option starts with a hash sign like `#this is a note`, what follows will be a little note that will be displayed next to the last step.
- **Omit**: If the option is `;` then it means omit this line in the document.
- **Override result**: If the option starts with an equal sign like `=34` then the value after the equal sign will be written in the document as the final answer.
- **Decimal points**: If the option starts with the letter d like `d2` then the number will specify the maximum number of digits after the decimal point. Default: `d3`
- **Force vertical**: You can force the steps to go vertically (as block equations) using `|` or horizontally (as inline equations) using `-`.
### Comments that take whole lines
These comments are converted to paragraphs or equations, depending on
what comes immediately after the hash sign.
- If the line starts with `#@` then the rest of the line is interpreted as options for subsequent assignments. See above about the options.
- Equations:
- If the hash sign is followed by a single dollar sign (`$`), the rest of that line is expected to be a python equation, and will be converted to an inline LaTeX equation.
- If what comes after the dollar sign is two dollar signs (`$$`), the rest of that line will be converted to a displayed (block) equation in the document.
- Running text: If the hash sign is followed by just running text, it is converted to a paragraph text.
In the last two cases, when a hash character immediately followed by a variable
name like `#x`, the value of that variable will be substituted at that place.
When a hash character immediately followed by an expression surrounded by
squirrely braces like `#{x + 2}` is encountered, what is inside the braces will
be evaluated and substituted at that place.
### Comments that begin with double hash signs
If you begin a comment line with double hash signs, like `## comment` it
is taken as a real comment. It will not do anything.
### Other code
Other code elements like import statements, loops, function definitions, etc.
are just executed and will not be included in the document.
### Variable names
The names of variables are transformed into a sensible mathematical notation in the following ways:
The variable can be made of parts joined by underscores (or a single part
without any) and the parts decide how the variable will be rendered in the
document.
- For any part of the variable,
- If it is a greek letter name, like `alpha`, it is rendered as the actual greek letter. To write capital Greek letters, start the variable name with a capital like `Alpha`.
- If the name is a single letter like `x` then it is rendered as an italic single letter.
- If is more than one character, it is rendered as text, with upright characters.
- If the variable contains two parts with a single underscore, like `x_y`:
- If the second part is the name of an accent or a prime listed in the following, like `x_hat`, it modifies the first part.
- `hat`
- `check`
- `breve`
- `acute`
- `grave`
- `tilde`
- `bar`
- `vec`
- `dot`
- `ddot`
- `dddot`
- `prime`
- `2prime`
- `3prime`
- If it contains two parts with double underscore, like `x__y`, the second part `y` becomes a superscript.
It is possible to combine the above into a name like `alpha_bar_foo__x`.
### Transformations
The following things are transformed into their mathematical notations:
- `sqrt()`: into the square root symbol as shown in the example
- `degC` and `degF`: into the degree Celsius or degree Fahrenheit symbols
- `deg`: the degree symbol for angles for example
- `integral()`: the integral sign from calculus
- Instances of `numpy.matrix` and 2D lists: into the matrix notation
- Instances of `numpy.array` and 1D lists: into the vector notation
### Fill tables from variables (Word only)
Tables can be filled from 2D variables (lists of lists or numpy matrices). To
do that, all that's required is to create a template table and place the name
of the variable as a \#hashtag inside the cell where we want the table to be
filled from. Then it starts filling the table from that cell to the right and
down. If there are no columns or rows left, new ones will be added, so that we
don't have to know the size of the final table beforehand.
## LSP support
There is LSP mode for basic assistance which evaluates and shows the
values of the variables as inlay hints which can be used to get immediate
feedback on our calculations. On Neovim, it looks like this:
To not clutter the screen, it doesn't show values for simple assignments of
constants, and it doesn't repeat the name of the variable when there is only
one.
It can be started as
```shell
docal --lsp
```
It only watches files whose name matches the pattern `*.docal.py` Right now, it
has been tested with the following editors.
### Neovim
Using the built-in config of Neovim v0.11, it is very easy to configure. The
following is an example config to use it:
```lua
vim.lsp.config.docal = {
cmd = { 'docal', '--lsp' },
filetypes = { 'python' },
}
vim.lsp.enable({'docal'})
-- inlay hints have to be enabled as well
vim.lsp.inlay_hint.enable()
```
### VSCode
There is no custom made extension for this, but it is faily easy to use a
generic LSP client extension like [this](https://github.com/zsol/vscode-glspc)
and make it work with it. For example, for the mentioned extension, the only
necessary settings are:
- `glspc.server.command`: `docal`
- `glspc.server.commandArguments`: Add one: `--lsp`
- `glspc.server.languageId`: `python`
Note that when the editor is started, `docal` has to be already instealled and
available in `$PATH`. [Read
more](https://github.com/zsol/vscode-glspc#failed-to-start-server-spawn-command-enoent)
## Notes
**Security**: `eval() and exec()` are used to get the actual values. In most
cases this should not be a problem as you are writing your own calculation
scripts which you want to run anyway. But still, I'm not an expert on the
possible security implications though you should make sure that imported code
is from a trusted source.
Python's AST changes almost every release. And since this package depends on
that, supporting every new version of python will be like a moving target. This
project has been developed against the Python versions available at the time of
writing. There was the option of using
[ast-compat](https://pypi.org/project/ast-compat/) to not be affected by the
changing AST, but I'm not sure if introducing a dependency is worth the
benefits. Therefore, my current approach is to update the code and release
major versions when there are changes to the AST that affect this package.