sysmlv2copilot
sysmlv2copilot is the Python SDK and CLI for the SysML Copilot service used by the Visual Design and Engineering Lab at Carnegie Mellon University.
This package is for authorized internal users. Installing it does not by itself grant service access.
What Users Can Do
- Generate SysML from text requirements
- Repair existing SysML
- Use either Python or the command line
Install
python -m pip install sysmlv2copilot
Upgrade an existing install:
python -m pip install -U sysmlv2copilot
Authentication
Set your API key once:
export SYSMLV2COPILOT_API_KEY=sysml_live_...
Or pass it directly in code:
from sysmlv2copilot import generate, repair
sysml = generate(
"Design a compact warehouse inspection drone that can hover for 15 minutes.",
api_key="sysml_live_...",
)
repaired = repair(
"broken.sysml",
api_key="sysml_live_...",
)
Python
Generate SysML:
from sysmlv2copilot import generate
sysml = generate("Design a compact warehouse inspection drone that can hover for 15 minutes.")
print(sysml)
Repair SysML:
from pathlib import Path
from sysmlv2copilot import repair
repaired = repair(Path("broken.sysml"))
print(repaired)
If a .txt file contains SysML, repair() can use that too:
from pathlib import Path
from sysmlv2copilot import repair
repaired = repair(Path("broken.txt"))
print(repaired)
You can pass:
- raw strings
Pathobjects- path strings like
"broken.sysml"or"requirements.html" - open text files
Use generate() for natural-language requirements and repair() for SysML, regardless of whether the file extension is .sysml or .txt.
CLI
Generate SysML from inline text:
sysmlv2copilot --api-key sysml_live_... \
generate \
--input "Design a compact warehouse inspection drone that can hover for 15 minutes."
Repair SysML from a file:
sysmlv2copilot --api-key sysml_live_... \
repair \
--input-file ./broken.sysml
The CLI accepts .txt, .sysml, and .html files for --input-file.
HTML files are converted to plain text before being sent to the API.
Metadata
Release files for sysmlv2copilot 0.2.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sysmlv2copilot-0.2.9.tar.gz | 15.8 kB | Without provenance | Details for sysmlv2copilot-0.2.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sysmlv2copilot-0.2.9-py3-none-any.whl | Python 3 | none | any | Details for sysmlv2copilot-0.2.9-py3-none-any.whl |
Total release size: 27.8 kB
Release files / sysmlv2copilot-0.2.9.tar.gz
| Download URL | sysmlv2copilot-0.2.9.tar.gz |
|---|---|
| Size | 15.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db864d2893ef611d907a3837e14834d994782cb18e9eec7d022de57b9ed46ca7
|
|
BLAKE2b-256 checksum How to use checksums |
8a0e4a4fead3018393bbc47013f92e0b47430d7789a18c10a134f51b5b11e980
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.2
|
Release files / sysmlv2copilot-0.2.9-py3-none-any.whl
| Download URL | sysmlv2copilot-0.2.9-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6640d28a05bd1c8ae34291c344d322560c759781c74775937d15efa73d2aed54
|
|
BLAKE2b-256 checksum How to use checksums |
d56fe9b59df9e6319d7d37d608375454343735b4763ae815b29e5b6017133d11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.2
|
Security for sysmlv2copilot 0.2.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.