semvec/pypi-packages huggingface dataset:
sdss-lvmcam 1.1.3
The package for lvmcam
Requires Python: <4,>=3.10

# lvmcam

![Versions](https://img.shields.io/badge/python->3.8-blue)
[![Lint](https://github.com/sdss/lvmcam/actions/workflows/lint.yml/badge.svg)](https://github.com/sdss/lvmcam/actions/workflows/lint.yml)
[![Documentation Status](https://readthedocs.org/projects/sdss-lvmcam/badge/?version=latest)](https://sdss-lvmcam.readthedocs.io/en/latest/?badge=latest)
<!-- [![codecov](https://codecov.io/gh/sdss/lvmcam/branch/main/graph/badge.svg)](https://codecov.io/gh/sdss/lvmcam) -->

Auto-guider (AG) camera control actor.
trackit-vcs 1.0.1
TrackIt is a basic version control system inspired by Git. It provides functionalities for creating commits, branches, tags, merging branches, and more.
Requires Python: >=3.12
Keywords: version control, personal version control, git, cli

# TrackIt

TrackIt is a basic version control system inspired by Git. It provides functionalities for creating commits, branches, tags, merging branches, and more.

## Installation

To install this package, run:

```sh
pip install .
```

Usage\
TrackIt provides a command-line interface (CLI) for interacting with the version control system. Below are some of the commands you can use:

Initialize a Repository\
To initialize a new TrackIt repository, run:
```sh
trackit init
```

Create a Snapshot\
To create a snapshot of the current state of the repository, run:
```sh
trackit snapshot
```

Read a Snapshot
To restore the repository to a previously stored snapshot, run:
```sh
trackit read-snapshot <snapshot_id>
```

Commit Changes\
To commit changes to the repository with a message, run:
```sh
trackit commit -m "Your commit message"
```

View Commit Log\
To display the commit log, run:
```sh
trackit log
```
Checkout a Commit or Reference\
To checkout a specific commit, run:
```sh
trackit checkout <commit_id_or_ref>
```
or reference(tag or branch), run:
```sh
trackit checkout -r <ref>
```
Create a Branch
To create a new branch, run:
```sh
trackit branch <branch_name>
```

Tag a Commit\
To tag a specific commit with a name, run:
```sh
trackit tag <tag_name> <commit_id>
```

Show Commit Details\
To show the content of a specific commit, run:
```sh
trackit show <commit_id>
```

Display Differences Between Commits\
To display the differences between two commits, run:
```sh
trackit diff <from_commit_id> <to_commit_id>
```

Merge Branches\
To merge two branches, run:
```sh
trackit merge <other_branch> <head_branch>
```

Find Common Ancestor of Two Commits\
To find the common ancestor of two commits, run:
```sh
trackit merge-base <commit_id1> <commit_id2>
```

Status\
View the status, run:
```sh
trackit status
```

Reset\
To reset the repository to a specific commit, run:
```sh
trackit reset <commit_id>
```

Find Common Ancestor of Two Commits
To find the common ancestor of two commits, run:
```sh
trackit merge-base <commit_id1> <commit_id2>
```

## Contributing
Contributions are welcome! Please open an issue or submit a pull request.

## License
This project is licensed under the MIT License.

## Acknowledgements
This project is inspired by Git and aims to provide similar functionalities for version control.
ngstSpaceKit 1.1.0
ngstSpaceKit is an addon to ngsolve, that provides several new spaces / finite elements.
Requires Python: >=3.10

# ![ngstSpaceKit](https://codeberg.org/johann-cm/ngstspacekit/raw/commit/ef2998214c4e2e5dccad57022b4e5962954250d6/assets/banner.png)

[![documentation](https://img.shields.io/badge/ngstSpaceKit-documentation-blue?logo=bookstack)](https://johann-cm.codeberg.page/ngstspacekit/docs/index.html)
[![examples](https://img.shields.io/badge/ngstSpaceKit-examples-%23F37626?logo=jupyter&logoColor=%23F37626)](https://johann-cm.codeberg.page/ngstspacekit/examples/index.html)

ngstSpaceKit is an add-on to [ngsolve](https://ngsolve.org/) and [ngstrefftz](https://github.com/paulSt/ngstrefftz),
and provides a collection of finite element spaces.
The goal of this project is to explore possibilities of the conforming Trefftz Method,
and provide concrete example uses for it.

## Implemented Spaces

ngstSpaceKit implements a series of well-known finite elements,
that are not yet implemented in [ngsolve](https://ngsolve.org/):
- [Argyris](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit.html#Argyris)
- [Bogner-Fox-Schmitt](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit.html#BognerFoxSchmitt)
- [Crouzeix-Falk](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit.html#CrouzeixFalk)
- [Hermite](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit.html#HDiv)
- [Morley](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit.html#Morley)

On top of that, there are other exotic spaces defined:
- a [weakly H1-conforming element](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit.html#WeakH1),
  with the option to use the inner dofs with an embedded Trefftz formulation
- an [H(div)-conforming element](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit.html#HDiv),
  with the option to use the inner dofs with an embedded Trefftz formulation
- a [Stokes mixed element](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit.html#WeakStokes),
  where the velocity part is weakly H(div)-conforming, and the remaining dofs adhering to a Stokes embedded Trefftz formulation
- a P1 / Q1 [Immersed Finite Element Space](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit.html#ImmersedP1FE),
  which is suitable
  to solve interface problems on a domain with a cut.
  Refer to [Lin et al.](https://doi.org/10.1137/130912700) for a proper introduction of the
  Immersed Finite Element method.

For demonstration purposes, there are some spaces implemented,
which already have a native [ngsolve](https://ngsolve.org/) implementation:
- [Brezzi-Douglas-Marini](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit/demo.html#BDM)
- [Crouzeix-Raviart](https://johann-cm.codeberg.page/ngstspacekit/docs/ngstSpaceKit/demo.html#CrouzeixRaviart)

## Citing
ngstSpaceKit is published on Zenodo. You may cite it as
> Meyer, J. C., & Lehrenfeld, C. (2025). ngstSpaceKit. Zenodo. <https://doi.org/10.5281/zenodo.17281221>

## License

ngstSpaceKit is available under the [LGPL-3.0](./LICENSE) license.
enforce-with 1.1.0
Enforce the usage of with keyword
Keywords: enforce, with

# enforce-with
This library makes it possible to enforce the usage of ```with``` keyword

# Installation
```pip install enforce-with```

# Usage
@enforce_with.**enforce_with**

Decorate your class with this decorator and it will no longer be possible to access the members of its instances unless you access them inside a ```with``` block. Example:
```python
@enforce_with.enforce_with
class MyClass:
    def __init__(self):
        self.var = 10

    def func(self):
        pass

    def __enter__(self):
        print("entering")
        return self

    def __exit__(self, exc_type, exc_value, traceback):
        print("exiting")

with MyClass() as obj:
    obj.var # Ok
    obj.func() # Ok

MyClass().var # Error
MyClass().func() # Error

```
strangeworks-optimization-models 0.1.68
Pydantic models for strangeworks optimization SDK and application
Requires Python: <3.14,>=3.10

![Tests](https://github.com/strangeworks/strangeworks-optimization-models/actions/workflows/cron_test.yml/badge.svg)

# Strangeworks-Optimization-Models
Pydantic models for use with Strangeworks Optimization API
- StrangeworksModel is an abstract base class for all Strangeworks optimization models.

These are all in the `strangeworks_optimization_models` module.

## Problem Models
In `problem_models` we have data structures representing the problems to be solved. these take the form

- Model is the native model used outside strangeowrks
- Model type is an enum of the types of native models
- StrangeworksModelType is an enum that defines the types of models available. These include:
    - BinaryQuadraticModel
    - ConstrainedQuadraticModel
    - DiscreteQuadraticModel
    - JiJProblem
    - AquilaModel
    - QuboDict
    - MPSFile
    - HitachiModel
- Each model has its own class, such as MPSFile, QuboDict, AquilaNDArray, and HitachiModelList. These classes contain the data for each model.


## Solver Models

Ways to specify solvers. Right now they are all basically `provider.solver`

## Solution Models
In `solution_models` we have data structures representing the solutions to the problems. These take the form:

- Solution is the native solution used outside strangeworks
- Solution type is an enum of the types of native solutions

The solution models also include methods for converting the solution to a string and from a string, similar to the problem models.