semvec/pypi-packages huggingface dataset:
casify 0.6.18
A CAS-library wrapped around sympy to simplify use of CAS-functionality in mathematics.
Requires Python: >=3.7

# `casify`
`casify` is a Python package that implements a simplified CAS (Computer Algebra System) for symbolic computation, wrapping around `sympy` for facilitate its computations. The implementation provides both Norwegian and English names for all of its functions. 

## Basic examples

### Example 1: solving equations

```python
from casify import *

solution = solve("x**2 - x - 6 = 0")
print(solution)

```

### Eksempel 1: løse likninger

```python
from casify import *

løsning = løs("x**2 - x - 6 = 0")
print(løsning)

```


### Example 2: solve system of equations

```python
from casify import *

solution = solve("x + y = 2", "x - y = -1")

print(solution)

```

### Eksempel 2: løse likningssystemer

```python
from casify import *

løsning = løs("x + y = 2", "x - y = -1")

print(løsning)
```


### Example 3: function evalution

```python
from casify import *

f = function("x**2 - x - 6")

print(f(2)) # Computes f(2)
```

### Eksempel 3: funksjonsverdier

```python
from casify import *

f = funksjon("x**2 - x - 6")

print(f(2)) # Regner ut f(2)
```


### Example 4: Differentiation

```python
from casify import *

f = function("x**2 - x - 6")


print(f.derivative()) # Gives the general expression for the derivative

print(f.derivative(2)) # computes f'(2)
```

### Eksempel 4: Derivasjon

```python
from casify import *

f = funksjon("x**2 - x - 6")

print(f.derivert()) # gir det generelle uttrykket for den deriverte

print(f.derivert(2)) # regner ut f'(2)
```


### Example 5: algebraic expansion and factorization

```python
from casify import *

print(factor("x**2 - x - 6"))  # faktoriserer x**2 - x - 6

print(expand("2*(x - 1) * (x + 4)"))  # utvider 2 * (x - 1) * (x + 4)
```

### Eksempel 5: algebraisk utvidelse og faktorisering

```python
from casify import *

print(faktoriser("x**2 - x - 6"))  # faktoriserer x**2 - x - 6

print(utvid("2*(x - 1) * (x + 4)"))  # utvider 2 * (x - 1) * (x + 4)
```
tsyganenko 2020.2.3
A Python wrapper for N A Tsyganenko’s field-line tracing routines.
Requires Python: >=3.12
Keywords: magnetic field, magnetosphere

# tsyganenko

[![Zenodo badge](https://zenodo.org/badge/190026596.svg)](https://doi.org/10.5281/zenodo.3937276)
[![Tests badge](https://github.com/johncoxon/tsyganenko/actions/workflows/tests.yaml/badge.svg)](https://github.com/johncoxon/tsyganenko/actions/workflows/tests.yaml)

A Python wrapper for N. A. Tsyganenko’s field-line tracing routines.

[For information on the models and routines that are wrapped by this package, please visit Empirical Magnetosphere
Models by N. A. Tsyganenko.](https://geo.phys.spbu.ru/~tsyganenko/empirical-models/)

## Citation

When using this software, please cite [the Zenodo record](https://zenodo.org/records/15763019) as well as citing the relevant papers.

## Copyright

Geopack and the other Fortran code in this repository are developed by N A Tsyganenko et al. and licenced under the GPL
v3 or later.

The Python wrappers were originally written by Sebastien de Larquier in 2012. They are now maintained by John C Coxon.
Small edits have been made to `Geopack-2008.for` to allow for `f2py` compilation. Code in this repository other than the
original Fortran is licenced under the MIT licence.

## Funding

John C Coxon was supported during this work by Science and Technology Facilities Council (STFC) Consolidated Grants 
ST/R000719/1 and ST/V000942/1, and Ernest Rutherford Fellowship ST/V004883/1.

## Installation

    pip install tsyganenko
    pytest tests/test.py

Please note that at this time, Windows is not well-supported by this package; if you would like to help resolve this,
please check out [issue #15](https://github.com/johncoxon/tsyganenko/issues/15).

Tests take around 1 hour to run, so don’t be alarmed if you see this behaviour on your machine.

The tests are run against the `csv` files in the repository which were created on an Apple Silicon (M1) Mac. Compiling 
the package on other machines leads to disparities which reflect the change in underlying architecture rather than
reflecting changes in code. As such, by default, `tests.py` is extremely permissive; it will test to a relative accuracy
of 0.5 or an absolute accuracy of 10.0. If you want to run tests with the `pytest` defaults, run
`pytest tests/test_exact.py`, and expect a large number of tests to fail unless you are running on an M1 chip.

## Usage

To use this module, simply follow the example provided in the Trace object docstring.

    from tsyganenko.trace import Trace
    help(Trace)

Alternatively, there are example notebooks provided which can be used to explore what this module can do:

    cd notebooks
    jupyter notebook
pymontrace 0.1.0.dev13
dynamic python tracing
Requires Python: >=3.9
Keywords: tracing

First Terminal

    python3 examples/script_to_debug.py

Second terminal

    pymontrace -p "$(pgrep '[Pp]ython')" -e 'line:*/script_to_debug.py:13 {{ print("a", ctx.a, "b", ctx.b) }}'
    Waiting for process to reach safepoint...
    Probes installed. Hit CTRL-C to end...
    a 4 b 3
    a 3 b 7
    a 7 b 1
    a 1 b 8
    a 8 b 0
    ^CRemoving probes...
    Waiting for process to reach safepoint...
    .


INSTALLATION:

    pymontrace can be installed with pip or pipx or just run with pipx run at
    your preference.

        pip install pymontrace

        pipx install pymontrace

        pipx run pymontrace

        uvx pymontrace


DOCUMENTATION:

    See  pymontrace -h  and  https://cakemanny.com/pymontrace  or
    docs/SUMMARY.md in the github repository for some initial documentation.


WARNING:

  - This is under early development and is in no way safe to use against
    production workloads.

  - The interface will change wildly without warning. There are no versioning
    guarantees at this point.


CAVEATS:

  - Use on macOS requires root. Use `sudo`.

  - Probes will only fire if the function is entered after the probe has
    been installed. This means that top level statements cannot be traced and
    that the statements inside an outermost forever-loop cannot be traced.