semvec/pypi-packages huggingface dataset:
physicsml 0.6.0
A package for all physics based/related models
Requires Python: >=3.10

<picture>
  <source media="(prefers-color-scheme: dark)" srcset="docs/source/_static/PhysicsML_Logo_PhyML_logo%20full%20light-cropped.svg">
  <img alt="PhysicsML logo" src="docs/source/_static/PhysicsML_Logo_PhyML_logo%20full%20dark-cropped.svg">
</picture>

---

[![PyPI version](https://img.shields.io/pypi/v/physicsml)](https://pypi.org/project/physicsml/)
[![Supported Python versions](https://img.shields.io/badge/python-3.10%20%7C%203.11-blue.svg)](https://docs.python.org/3/whatsnew/index.html)
[![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/charliermarsh/ruff/main/assets/badge/v2.json)](https://github.com/charliermarsh/ruff)
[![Checked with mypy](https://img.shields.io/badge/mypy-checked-blue)](http://mypy-lang.org/)
[![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit)](https://github.com/pre-commit/pre-commit)


---

## What is PhysicsML?

PhysicsML is a package for all physics based/related models. It provides a standardised interface for handling, building,
and training 3d models!

## Installation
### With pip

```bash
pip install physicsml
```

#### Optional Dependencies

Some functionalities in `physicsml` require additional dependencies, which you can install as needed. For example

```bash
pip install physicsml[rdkit]
```

## Documentation

To learn more about how to use ``physicsml``, see the [documentation](https://exscientia.github.io/physicsml/).

## Contribution guidelines

Anyone is welcome to submit PRs for new functionality or fixes! Just create a pull request and we will review and get back to
you.

## License
[MIT License](LICENSE)

## Acknowledgements

The ``physicsml`` package has been developed by researchers at Exscientia

* Adam Baskerville
* Aayush Gupta
* Ward Haddadin
* Kavindri Ranasinghe
* Ben Suutari
swh.provenance 0.2.2
Software Heritage provenance
Requires Python: >=3.9

Software Heritage - Provenance
==============================

This service provide a provenance query service for the Software Heritage
Archive. Provenance is the ability to ask for a given object stored in the
Archive: "where does it come from?"

This question generally does not have a simple and unambiguous answer. It can
be, among other:

- what it the oldest revision in which this object has been found?
- what is the "better" origin in which this object can be found?

Answering this kind of question requires querying the Merkle DAG on which the
Software Heritage Archive is built with complex queries, mostly from the bottom
to the top (aka from Content to Origin objects).

The idea is to use both the compressed graph representation of the Archive
(swh-graph) and a preprocessed provenance index to speed up some of the
provenance queries.


Description
===========

The core feature of this tool is to provide a service to the reference to an
object within the Software Heritage Archive where the queried object can be
found.

There are mostly 2 kinds of provenance queries that can be done:
- search for the best provenance answer from a given object;
- search for all the possible provenance answers for a given object.

For each input object, the definition of "best provenance answer" is simple and
unambiguous; for now, the best answer is the *an* origin in which the oldest
revision (in the sense of the revision with the oldest commit date) in which
this object has been found.

Provenance can be looked for:

- ``Content``
- ``Directory``
- ``Revision``
- ``Release``

For each object::

    Input: SWHID (core SWHID of an artifact found in the user code base)

    Output: SWHID or origin URI where input SWHID was found + context information
        Context information, a subset of:
            snapshot (snp SWHID)
            release (rel)
            revision (rev)
            path (filesystem-style path)

    Non-functional requirements:
      - the returned object should be as high as possible; i.e. prefer an
        Origin (if any), then a Snapshot, then a Release, then a Revision,
      - the returned object should be the best possible answer, if possible;
        the definition of "best answer" being something like:

          *an* origin in which the oldest revision (in the sense of the
          revision with the oldest commit date) in which this object has been
          found.

.. Note:: This documents the backend provenance service; it is not meant to be
          used directly but rather via the Public API; please refer to its
          `description`_ for more details on how to use the Provenance public
          API.

.. _`description`: https://archive.softwareheritage.org/api/1/